IN THIS GUIDE · L1B preparation that ties company-specific product knowledge to defined US launch deliverables
Start with the L-1B eligibility and application overview
Describe the product and the assigned deliverables together
Write the two halves side by side: what the product is, in terms a reviewer without the company's vocabulary can follow, and what this person will do about it during the assignment. Deliverables should be nameable — configure the platform for a market, prepare the support organization, resolve integration issues found in the first deployments. A description that stops at supporting the launch leaves the knowledge claim floating with nothing to attach to.
Show where the knowledge came from during development
Pre-release knowledge has a clear origin: design decisions, failed approaches, tested limits, and the reasoning behind trade-offs that never reached documentation. Ask the employee to name their part in that work and the period it covered. Development records, specifications they authored, and defect histories tie the person to the product rather than to a job title. This is where the knowledge stops being general engineering ability and becomes knowledge of a particular thing the company makes.
Explain what the assignment depends on
The record should explain why the deliverables call for someone who knows the product from the inside, without claiming that the knowledge is unique or that nobody else could ever learn it — neither is required, and overstatement invites challenge. Depth and origin are the point. Describe what a person arriving without that background would have to be taught, and roughly over what period, then let those facts carry the argument on their own.
Freeze the record while the product keeps moving
Products change during preparation, and a description written against last quarter's build can read as inaccurate later. Date each document, note the version it describes, and assign one person to check the file before anything is filed. Where the launch scope shifts, revisit the deliverables rather than leaving old wording in place. Keep the assignment's stated duration consistent with what the launch plan actually requires of this person.
Write the end of the assignment while you are writing its beginning
Two things push in the same direction here. L-1B stay is limited to five years in total, and a launch-driven assignment is one of the most likely to be extended, because a product that ships late keeps needing the person who built it. Deciding now what the assignment is actually for makes the later conversation manageable. If the purpose is to transfer knowledge to a local team, name that team, set milestones for the transfer, and record them, because the file then describes a defined piece of work rather than an open-ended posting and the business has something to manage against. If the intention is genuinely longer term, the alternatives deserve examination early: a move to a managerial or executive role would be assessed on its own requirements and is not an administrative step, and other routes carry their own conditions and timelines. What does not work is arriving at the fourth year with no plan and an urgent need. Put a review in the calendar at the halfway point, with the specific question of what happens at the ceiling. Hypothetical example: an engineer transferred to commission a new vessel monitoring product agrees a two-year knowledge transfer plan with named counterparts, so the extension question, when it arrives, is answered with a progress record rather than an improvisation.
Sources reviewed 2026-09-07. This guide covers a preparation focus; it is not an individual eligibility assessment.