IN THIS GUIDE · Separate the vendor's product from what the company built on it
Start with the L-1B eligibility and application overview
Identify the layer the company actually owns
The petition should draw the line explicitly. Knowledge of a commercially licensed dispatch product is available in the labour market and is general skill however deep it runs. What may be specialized is the layer built on top: the data model the group designed, the rules encoded in its integration, the exception handling written for its own operating patterns, and the undocumented reasons behind each of those decisions. Ravi's file should describe that layer as a thing with a history, and describe what he knows about it, rather than describing his competence with the vendor's software. If the company cannot point to something it built, the case is weak and should be recognized as such early.
Show scarcity inside the organization
Useful evidence includes how many people in the group could maintain the integration, how long it would take to bring someone else to the same level, what the operational consequence of a gap would be, and why this employee rather than another is being transferred. Source repositories with commit history, internal design notes, change records and support tickets showing who resolves what are contemporaneous and persuasive. A manager's statement that he is indispensable adds little on its own. Where the honest answer is that two people hold the knowledge, saying so and explaining why one must stay in Barriere reads better than an overstatement that the record contradicts.
Wages and role should match the claim
A petition asserting advanced knowledge is read alongside how the organization treats the person. Compensation well below what the described expertise commands, a job title that suggests routine support, and a duty list of helpdesk tasks all pull against the claim. This does not mean a company must restructure its pay, but it does mean the petition should explain the actual role rather than leaving an apparent mismatch unaddressed. The receiving position should also be described concretely: what he will implement, over what period, with whom, and what the affiliate will be able to do afterwards that it cannot do now.
Count the qualifying year and the five-year ceiling
One continuous year of employment by the qualifying organization within the preceding three years is required, in a qualifying capacity, and payroll records rather than recollection should establish it. Periods on contract, on secondment to a non-group entity, or unpaid can interrupt the year. This classification is limited to five years in total, and prior time in the United States in L or H status generally counts toward that ceiling, so a person who has been transferred before should have that history reviewed before a long assignment is planned. Where a longer horizon is needed, the limit is a fact to plan around rather than a detail to discover later.
Sources reviewed 2026-09-07. This guide covers a preparation focus; it is not an individual eligibility assessment.