IN THIS GUIDE · Transferring knowledge to a U.S. team
Start with the L-1B eligibility and application overview
Establish the trainer’s own knowledge
Identify how the employee gained the special or advanced knowledge and demonstrate its use through prior work. Being selected to teach is not independent proof of expertise. Support the record with training history, difficult assignments and explanations from people who observed the employee’s capability before the U.S. transfer was proposed.
Describe what the U.S. team will learn
Outline the subject matter, practical exercises and intended competencies. Distinguish ordinary onboarding from transfer of the knowledge claimed in the petition. A curriculum should explain depth and application, not merely fill a calendar. Identify why the proposed trainer’s existing knowledge is relevant to those specific learning outcomes.
Explain training alongside other duties
Set out demonstrations, implementation, troubleshooting and follow-up responsibilities where they are actually planned. Do not invent a long technical assignment to justify a short orientation session. If knowledge is easily imparted, address the effect on the specialised-knowledge argument candidly; teaching it to others does not automatically defeat a supported case.
Review the role after training
Explain the anticipated work once the U.S. team develops proficiency. The initial teaching plan does not automatically support an unrelated later assignment. Document actual progress and review material changes in duties or locations before implementation. The company should be able to explain both the present need and the intended duration without promising indefinite specialist demand.
When the assignment moves after approval
Material change is the concept worth watching: a different worksite, a substantially different set of duties, or a move to a different employing entity can each take an approved petition out of alignment with what is actually happening. Whether an amendment is required is a legal question, so the practical discipline is to raise the change before it is implemented rather than describe it afterwards. Hypothetical example: a video post-production house wins a second client and reassigns its specialist to that client’s premises for most of the working week; the technical work is unchanged, the worksite is not, and whether the petition still describes the assignment now needs an answer. Log the change with its effective date and put the question to counsel.
Keeping the knowledge claim current
Specialised knowledge is a claim about one person at one moment, and both the person and the moment keep moving. Should the proprietary system be replaced, the process be documented and published internally, or the U.S. team become independently proficient, the argument supporting the transfer weakens even though nobody has done anything wrong. That is not a reason to conceal the development; it is a reason to describe honestly what the employee still contributes and why. Where the remaining need has genuinely changed shape, say so and let counsel assess whether an extension rests on the original basis or a new one. An extension built on a description that quietly stopped being accurate is the harder position to hold.
Sources reviewed 2026-09-07. This guide covers a preparation focus; it is not an individual eligibility assessment.