Keep it if it helps explain the applicant’s knowledge history, while clearly identifying its version and relevance. Do not present an obsolete manual as current operating instructions.
Connect documents to the stage they describe
Label dates and versions, identify the applicant’s participation and provide the current assignment scope. Explain material changes with reliable records. A chronological explanation can show how knowledge developed; silently updating old documents to current terminology can misrepresent what the applicant actually knew at the time.
Organize documents by the fact they prove: corporate relationship, qualifying foreign employment, specialized knowledge, and actual U.S. assignment. Formation records and ownership evidence support the first issue; payroll, tax, leave, and supervisor records support the second. Process material, training history, access controls, and concrete project examples support the knowledge explanation. Hypothetical example: a spacecraft composite layup analyst trained on a proprietary defect-detection workflow, but the company has only a general job title and a public brochure. Collect the internal training sequence, dated project assignments, and a declaration that explains the workflow without disclosing protected details. The deciding document is not a glossy product description; it is evidence connecting this individual’s uncommon knowledge to the work proposed. If the record shows generic skills, reconsider the category before filing.