Use carefully selected technical and operational evidence, accompanied by explanations of relevance. Confidential material should be handled thoughtfully, but confidentiality does not remove the need for proof.
Show enough detail to make the claim testable
Create a layered record. A nonconfidential overview can identify the product, service, market, or process and explain the applicant’s role. More detailed exhibits may describe training modules, project phases, system architecture, quality controls, or implementation decisions without publishing sensitive source code or customer data.
Declarations should come from people who can explain the knowledge firsthand and should give examples instead of repeating conclusions. Mark confidential business information consistently and consider whether portions can be redacted while preserving the key point. Training logs, internal certifications, project assignments, and comparisons with ordinary roles may help establish how the knowledge was acquired and applied.
The U.S. job description should then show the use case: what the transferee will configure, teach, troubleshoot, design, or oversee. Do not rely on an assertion that secrecy itself proves specialization.
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. Confidentiality measures should be explained in a way that permits review: identify the document custodian, the reason for any redaction, and the unredacted fact being supported. Never redact the point the exhibit is meant to prove.
A controlled disclosure can protect commercial interests while keeping the evidence meaningful.