IN THIS GUIDE · Proving a client-facing specialist's knowledge through sanitised examples rather than confidential records
Start with the L-1B eligibility and application overview
Work out what the confidential material would prove
Start by naming the proposition, not the file. If the applicant built a rare implementation, the point is the configuration and who did it, not the client's identity or data. Write the two or three propositions the case depends on, then ask which facts are genuinely needed to support each. Most confidential detail turns out to be background; the load-bearing facts are usually about the applicant's own actions and the organisation's methods. Begin by writing the propositions on a single sheet and circulating it before anyone opens a client file. Teams that skip this step redact for weeks and finish with documents proving the engagement existed and little else. A proposition such as the applicant authored the escalation procedure the organisation now uses in every deployment can often be evidenced entirely from internal material.
Build sanitised examples that keep their edges
A sanitised example must lose the identifiers and keep the specifics. Replace the client name with a description of sector and scale, and keep the technical problem, the approach taken, the internal tooling used, and the applicant's role and dates. Vague summaries such as complex enterprise deployments prove nothing at all. Three or four worked examples described this way carry more weight than a long list of engagements reduced to job titles. Give each example a fixed shape so reviewers can compare them: the problem, the constraint that made it hard, what the applicant personally did, which internal tool or method was used, the dates, and the outcome. Six sentences is usually enough. A worked example in that shape survives clearance better than free prose, because a reviewer removing an identifier can see immediately whether anything load-bearing goes with it.
Clear the wording with the people who own the obligation
Confidentiality duties usually sit in client contracts, in security policy, and sometimes in regulation, and different people own each. Identify them early and have them approve the sanitised text before it becomes the backbone of a filing. Where a client's consent is needed, ask for it in writing and allow real time for it. A description withdrawn late is far worse than a narrower description agreed at the start. Name the approvers in writing and ask each for a turnaround date. The common failure is discovering three weeks in that the account lead who approved the text had no authority to waive a contractual confidentiality term. Where a client consent is genuinely required, send a short specific request rather than a general one, because a narrow request tends to be answered while a broad one is escalated and forgotten.
Keep the account verifiable and the placement clear
Because the underlying records stay behind, statements from managers who supervised the work carry more weight, so name who can confirm each example. Where the applicant would work at client premises in the United States, placement primarily at an unaffiliated employer’s workplace raises specific limits on supervision and on arrangements resembling labour for hire. Record the intended sites and reporting lines and send that question to licensed United States immigration counsel. Hypothetical example: a payments-integration specialist deploys the employer's own reconciliation engine inside bank customers, spending most of each engagement on customer premises. The knowledge belongs to the employer and can be described without naming any bank. The placement question is separate and turns on who supervises the work in the United States, so record the intended sites and reporting lines and refer that assessment to counsel before commitments are made.
Sources reviewed 2026-09-07. This guide covers a preparation focus; it is not an individual eligibility assessment.