Prepare a meaningful description and supporting evidence while addressing confidentiality with counsel. Omitting the substance entirely leaves the claimed knowledge unexplained.
Choose evidence that demonstrates the relevant features
Identify process documents, development records, training history or examples that show what the applicant knows. Ask what extracts or explanations are sufficient for the actual petition and how sensitive records should be handled. A generic letter saying the system is confidential is not a substitute for evidence. Keep the description accurate and avoid claiming that redaction has already been accepted.
For L-1B, document the qualifying relationship, doing-business evidence, one continuous qualifying year abroad within the preceding three years, and knowledge that is special or advanced in relation to the organization. The five-year overall limit is a planning boundary, not a promise of future approvals. Hypothetical example: a satellite-imagery analyst’s relevant work is covered by customer confidentiality agreements. The employer can prepare a detailed non-confidential explanation of the internal workflow, training record, system permissions, and role of the applicant, while identifying the protected materials. The decision is how to corroborate the knowledge without claiming secrecy as proof by itself.
Put that conclusion beside the record that demonstrates it, then identify any mismatch between the technical narrative, training file, and actual U.S. assignment. A label for expertise is less useful than a traceable explanation of the work it enables.
The evidence index should show where each assertion is corroborated, so the reviewer can test the claim without inferring facts from a product label or confidential designation alone.