IN THIS GUIDE · Explain specialized knowledge when older records use different names
Start with the L-1B eligibility and application overview
Create a factual name history
Hypothetical example: training records use an old system name while the proposed assignment uses its successor’s name. Explain whether the product was renamed, replaced or substantially redesigned. A name cross-reference helps the reviewer understand records; it should not imply technical continuity that the company cannot support. Hypothetical example: after an acquisition, an infusion pump platform is sold under a new commercial name while its service architecture is unchanged, and a second product in the same catalogue is renamed after being redesigned end to end. The two look identical from the outside — old name, new name — and only the company knows which is which. Written as a table with three columns, the former name, the current name, and what actually changed, the history becomes checkable. Written as prose, it reads as an assurance.
Identify what the applicant actually knows
Describe the relevant product knowledge and international application, or advanced process or procedure knowledge. Distinguish knowledge carried forward from material learned later. There is no universal secrecy or uniqueness requirement, but long association with a product name alone does not explain the applicable standard. 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. Translate each item once into what the person can do and what would happen without them: which fault they can diagnose that others escalate, which procedure they were trained to run, which configuration decisions they make unaided. Then say where that knowledge came from and when.
Use dated contributions rather than a brand history
Identify the applicant’s work, training and responsibilities at relevant stages. Explain who can verify the records and any gaps. Company longevity does not establish the applicant’s qualifying foreign employment; have the employment period and actual employing entities assessed. Archives create their own trap. A broad retrieval request returns hundreds of documents bearing the product name and almost none bearing the applicant's, because release notes and specifications rarely name individuals. What identifies a person in an engineering or service record is narrower: training completions, signed work orders, escalation tickets closed under a login, validation reports countersigned by a supervisor. Ask the record holder which of those categories exists and for which years, before commissioning a search by product name.
Connect the historical evidence to current duties
Choose proposed U.S. activities and explain which documented knowledge they require. Identify any new learning still needed. A predecessor-system record can be relevant without proving every aspect of the current assignment, so make the limits visible and review material role changes. The connection fails last, and usually in one sentence: the U.S. assignment is described as supporting a rollout, which requires nothing in particular and therefore demonstrates nothing. Break the assignment into the tasks that actually depend on the documented knowledge, and mark honestly the tasks that do not. Where a task needs learning the applicant does not yet have, say so and say who provides it. A limit stated in the file is far less damaging than a limit a reviewer finds unmentioned.
Sources reviewed 2026-09-07. This guide covers a preparation focus; it is not an individual eligibility assessment.