IN THIS GUIDE · A product rollout that depends on the employee’s knowledge
Start with the L-1B eligibility and application overview
Describe the product and the employee’s contribution
Explain what the product does, how the employee learned it and which development, testing or implementation work they performed. Distinguish personal knowledge from mere membership in the product team. Knowledge need not be patented, but the record should establish the special or advanced understanding claimed rather than ordinary familiarity with sales materials.
Identify the rollout problems to solve
Specify the U.S. work: configuration, integration, validation, specialist support or another supported phase. Explain which existing knowledge each duty requires. A broad statement that the employee is needed for a successful launch is less useful than a clear connection between their capability and the actual tasks.
Support the assignment’s reality
Use current launch approvals, implementation plans, product documentation and relevant customer agreements. Mark contingencies accurately. A marketing announcement alone may not establish the employee’s duties or a confirmed client engagement. Check worksite and supervision, including the additional rules for primary assignment at an unaffiliated location.
Keep later support in view
Explain the anticipated transition from rollout to ongoing work without promising that every future phase will qualify. If specialist duties end or the role changes materially, obtain an immigration review before simply continuing under the same description. Maintain records of the work actually performed and how the product plan evolves.
How specialised-knowledge cases usually come apart
Substitution is the usual failure: the file proves the product is unusual instead of proving that this employee’s knowledge of it is special or advanced, and the two claims are not the same. A second is dilution, where the duty description spans configuration, training, support and account management, so nothing in it clearly requires the knowledge claimed. Hypothetical example: a compounding-pharmacy software vendor files a thick appendix of technical documentation and a single paragraph attributing work to the transferee, and the request that follows asks the one question the bundle never answered. Unwinding either problem after filing costs more than preparing it properly, because the employer must now explain a record it has already submitted rather than write one from the beginning.
Worksite and duration mistakes that surface late
Placement at an unaffiliated worksite carries additional conditions, and a rollout that quietly relocates the employee into a customer’s premises under that customer’s supervision can depart from the terms the petition described. Maximum periods also catch employers out: L-1B is capped at five years and L-1A at seven, and time already spent counts towards them. Where a specialised-knowledge role is expected to become an ordinary operational one, that is a change to review before it happens rather than at the next extension, by which point the evidence of what actually occurred has already been created. Keep a contemporaneous note of where the work was performed and who directed it, since reconstructing that afterwards from memory rarely persuades anyone.
Sources reviewed 2026-09-07. This guide covers a preparation focus; it is not an individual eligibility assessment.