Start with the L-1B eligibility and application overview
Explain the knowledge used in the short assignment
L-1B can involve special knowledge of company products or interests and international application, or advanced knowledge of processes and procedures. It need not be unique or proprietary. If the employee will work primarily at an unaffiliated client site, the petitioner must control the work and the placement must not be labour-for-hire.
Complete the service and business conditions
A continuous qualifying foreign year within the relevant three years remains required; US days do not count toward it. The US and foreign entities must have a parent, branch, subsidiary or affiliate relationship, and both must remain actively doing business. New-office treatment concerns actual US doing business for less than one year and requires sufficient premises and financial ability to pay and commence business; initial approval is limited to one year. Total L-1B stay is capped at five years. Hypothetical example: a Canadian producer of thermal-coating equipment wants to send its process specialist to a U.S. affiliate during the launch of a new curing line. The file says she knows the equipment “better than anyone,” yet her daily U.S. tasks are not identified and a customer proposes to direct her shift schedule. She must decide whether the claim rests on special knowledge and whether the placement preserves the required control. Training records, versioned process manuals, troubleshooting reports, foreign payroll, the affiliate’s work plan, and the customer contract answer different parts of that review. A generic résumé is weak evidence of how advanced or company-specific the knowledge is. The company should also calculate earlier L time before selecting the requested period; a five-year L-1B ceiling cannot be solved by calling the assignment short. The review should sequence the foreign-service dates, the qualifying corporate relationship, the knowledge evidence, and the proposed U.S. supervision. Each record has a different job. A training log does not establish payroll service, and a customer statement does not establish that the affiliate, rather than the customer, will control the worker. Resolving those gaps before filing avoids an explanation that relies only on a confident label.
Separate general technical skill from employer knowledge
Identify the deliverable and why specialized knowledge specific to the petitioning employer is necessary. A new title neither creates that knowledge automatically nor necessarily marks its beginning; uniqueness and proprietary status are not universal requirements. General skill in analysis or a sophisticated model does not by itself establish what special or advanced knowledge the applicant possesses. Start with a concrete before-and-after account of the US work: which internal product features, procedures, or international practices the employee will apply, and why ordinary onboarding would not supply that knowledge in the same way. A second failure is subtler: the knowledge is described entirely in internal vocabulary — module names, release numbers, an internal certification level — so a reader outside the company cannot tell whether it is genuinely specialized or simply proprietary labelling. A persuasive account explains the difficulty of transferring the knowledge and the business consequence if it is unavailable, without claiming that nobody else can learn it. The useful record is usually a training history, controlled procedure, technical decision, or project file that connects the employee’s knowledge to the organization rather than to a common software product. Identify the internal methods, product history, or cross-border process the employee learned, then show the decisions the U.S. team expects the employee to make with it.
Sources reviewed 2026-09-07. This guide covers a preparation focus; it is not an individual eligibility assessment.