Provide the relevant effective ownership and organizational evidence needed to explain the actual relationships, alongside the employment record.
Distinguish announcement from completion
A public announcement or signed proposal may not establish the transaction’s effective date. Use accurate final records where required and disclose remaining conditions.
Training records, permitted project descriptions, internal qualification documents, and other evidence that accurately explains the knowledge can usually support the claim, and the company should decide in advance what can be shared and what needs special handling. Records created before the transfer was contemplated carry the most weight: training logs, validation reports, procedure documents naming the employee, project records and correspondence about the process in question. Beyond the usual corporate and employment records, the file needs the contract or statement of work, a written description of supervision arrangements, and material showing the method is the petitioner's own. Identify the claimed organizational knowledge, the American tasks requiring it, who can authenticate each record, and which material can be summarized, excerpted, or redacted without making the explanation unverifiable. Signed procedure records, approved deviation reports, validation protocols and handover notes all qualify; a credit list does not, because it names participation without locating it. Use the system's own outputs to keep the cost down, since quality systems already record authorship, approvals, and audit participation, and much of the evidence can therefore be produced by running reports rather than by writing narratives.