IN THIS GUIDE · Ask what the employee knows that a new hire would not
Start with the L-1B eligibility and application overview
Ask the question that separates the two
Put it to the engineering manager plainly. If this person left and you hired the best available replacement from the industry, what would still be missing on day one, and what document or system would the replacement have to learn it from? Answers that point at a specific artefact, such as an internal configuration, a proprietary routine or a method documented only inside the organisation, describe knowledge the classification can reach. Answers that describe general competence, local scarcity or long service describe a hiring problem. The difference is not rhetorical and it decides the case. Identify the knowledge precisely enough that an adjudicator can ask where it lives and how it was acquired. A product architecture, internal test method, or deployment procedure is stronger when its connection to the organisation can be shown through records rather than through a supervisor’s praise.
Ask what was written down at the time
Evidence created before anyone contemplated a transfer carries far more weight than a letter written afterwards. Ask what exists: revision histories naming the employee, internal design or commissioning documents, training material they authored, project files showing the sequence of work, purchase records showing equipment was adapted rather than bought as standard, and any registered intellectual property. Then ask honestly what does not exist. Small engineering groups often do excellent work with thin documentation, and describing that limit accurately is a better position than presenting a reconstructed account as contemporaneous. Preserve native files and metadata where possible. Version-control logs, training records, access histories, and contemporaneous project notes show who learned the method and when. A polished statement prepared later can explain these records, but rarely carries the same weight by itself.
Ask whether the structural conditions actually hold
This classification relaxes none of the threshold requirements. Ask counsel to confirm the qualifying relationship between the two organisations from ownership documents, ask payroll to confirm one continuous year of qualifying employment abroad within the preceding three years, and confirm both entities are actively doing business. A compelling technical story attached to a broken year is not a filing. Ask these first, because they can be checked in a day and they determine whether the technical work is worth doing at all. Confirm the qualifying relationship and the year abroad before asking technical staff to prepare evidence. If either structural fact fails, detailed explanations of the knowledge do not cure it. This order protects the team from spending scarce engineering time on an unavailable category.
Ask where the person will sit and for how long
This classification carries a five-year maximum, which is shorter than the managerial one and should shape the plan from the outset rather than surface late. Ask where the technician will physically work: if the answer is a customer's territory or a client's control room, ask who directs the work; the petitioner must retain control, and an arrangement that functions as labour supplied for hire to another business falls outside what the classification permits. Ask what the intention is at the end of five years, since the honest answer affects whether a different route should be considered now. Map the assignment against the five-year ceiling and the company’s actual implementation schedule. If a short task is said to require a long stay, explain the stages and the handoff. If the operation is new, premises and funding evidence are separate questions from the employee’s expertise.
Sources reviewed 2026-09-07. This guide covers a preparation focus; it is not an individual eligibility assessment.