IN THIS GUIDE · Explain personal knowledge gained through a jointly developed process
Start with the L-1B eligibility and application overview
Identify the applicant’s actual work within the collaboration
Hypothetical example: two organizations developed a process together, but the applicant worked on one defined component. Explain the personal contribution, learning and practical application. Do not attribute the partner’s entire technical work to the applicant or imply experience with components the employee did not handle. Ask for examples of the employee applying the knowledge, not merely attending meetings about it. Dated training material, work records, and a supervisor’s explanation can distinguish direct experience from exposure.
Explain the relevant organizational knowledge
Describe the special or advanced knowledge the applicant acquired and how it relates to the employer’s product or process. Shared development does not create a universal bar, because secrecy and uniqueness are not universal requirements. The actual nature of the knowledge still needs evidence. Describe why the knowledge matters to this employer’s operations and to the proposed assignment. Avoid treating confidentiality wording as a substitute for explaining the method itself.
Keep the legal employers distinct from the project team
Identify who employed the applicant during the relevant periods and the actual relationship to the proposed U.S. employer. Working alongside partner employees does not itself establish qualifying employment with their organization. A strong knowledge explanation cannot replace the required company relationship or foreign employment. Verify the employer on payroll documents rather than relying only on project correspondence. This matters when a vendor, affiliate, and client all appear in the same technical records.
Use collaboration records with accurate attribution
Select relevant work and training records and explain who created or performed each part. Handle shared information appropriately and clarify genuine evidence gaps. The proposed U.S. duties should connect to knowledge the applicant actually possesses, not merely to the collaboration’s overall achievements. Test the timing separately from the knowledge narrative. The employee must have completed one continuous qualifying year abroad within the three years before the L-1 filing, while L-1B status is ordinarily limited to five years in total. Payroll, work-location, and role records often settle timing more reliably than a later summary letter. Hypothetical example: a firm restoring astronomical clock mechanisms proposes its Canadian diagnostic specialist for a U.S. workshop after a lengthy unpaid leave. The decision is whether the documented qualifying employment year is continuous and whether the stated knowledge will be used in the U.S. role; a catalogue of repairs alone proves neither point. A practical first review compares the foreign and U.S. roles line by line. It identifies which internal methods, tools, or problem histories the employee uses, who trained them, and why the assignment needs that knowledge. Generic technical competence or a strong résumé cannot substitute for that connection. For the proposed role, identify the decisions or problems that require the claimed knowledge. A task list that could be performed through ordinary training weakens the connection to the individual employee.
Sources reviewed 2026-09-07. This guide covers a preparation focus; it is not an individual eligibility assessment.