Use observations of the applicant’s actual knowledge and work, with the relevant context. Distinguish the writer’s direct knowledge from assumptions.
Connect examples to the proposed role
A project success can be relevant without proving every statutory condition. Explain the applicant’s contribution accurately.
Design documents, release notes, internal training material, project assignments and performance records that show the specialist's knowledge of the company's own system, together with a letter explaining why that knowledge is required at the U.S. site. Use whatever contemporaneous evidence exists — internal notes, project files, correspondence, or third-party records — to document how the knowledge was developed and applied. More detailed exhibits may describe training modules, project phases, system architecture, quality controls, or implementation decisions without publishing sensitive source code or customer data. Gather dated internal manuals, controlled revisions, training records, project assignments, supervisor declarations grounded in examples, and work products that can be disclosed lawfully. Supplement the paper with training records, project assignments, technical evaluations, and comparisons showing special or advanced company knowledge; authorship by itself is not the standard.