Use relevant project records, technical descriptions, training history and detailed employer explanations that establish the claimed knowledge. Identify genuine confidentiality restrictions and an appropriate way to provide required evidence. A confidentiality label does not excuse an unsupported filing, but wholesale public release of source code is not a universal L-1B requirement.
Select evidence that answers the legal question
A redacted implementation record may identify the applicant’s role and the complexity addressed, while a manager’s explanation connects it to the US assignment. Check that any redaction leaves enough substance to evaluate the claim. Obtain advice on agency submission requirements and contractual restrictions before assuming a summary is sufficient or a protected document cannot be provided.
An employer that has genuinely built procedures around a supplier’s equipment usually holds a controlled document register: numbered procedures, revision dates, and a named author or approver for each version. Build a dated record of the pilot’s true progression: design notes, test versions, results, unresolved defects, training materials, and examples of the employee’s contribution. Supporting material may include authored analyses, configuration records, training histories, decision memoranda, and statements from people who can explain the contribution firsthand. Many confidential documents are not evidence of specialized knowledge, and many strong L-1B cases can be explained without giving a reviewer unrestricted access to commercially sensitive material.