Use company records demonstrating how the employee applied that understanding to products, services or processes, together with a specific account of the U.S. assignment. The evidence should connect experience to decisions rather than merely list countries visited.
Choose attributable examples
A process adaptation, implementation record or documented resolution can show the employee’s contribution when explained by someone familiar with the work. Identify what was learned and why it matters now. Separate public market background from evidence of the employee’s own knowledge, and avoid attributing team results entirely to one person without support.
Contemporaneous documents outperform reconstructed ones by a wide margin, and the difference is usually visible on the page. A record created while the work was happening carries incidental detail — version numbers, colleagues copied, an issue reference — that a summary written for the petition cannot honestly reproduce. Where a summary is genuinely necessary, label it as one and cite the underlying records it draws on.
Hypothetical example: an academic publishing services business documents an editor’s specialised knowledge through the workflow specifications and vendor exception notes she produced across two years, then adds one short current statement explaining, with citations, how those artefacts connect to the proposed U.S. assignment. That combination lets a reviewer test the claim against something other than the author’s confidence.
Any statement that cannot be checked against a dated artefact remains an assertion awaiting support.