A licence can show a usage right without establishing individual authorship or expertise.
Support the contribution with facts
Identify relevant work, configuration or problem-solving records. Do not attribute a team’s complete system to the transferee without evidence.
Version histories of procedure documents naming the employee, records of revisions made after incidents, decision notes explaining changes, and escalation logs showing which questions reach them. Redacted internal documentation, training and certification records, project summaries naming the employee's role, and a letter explaining the process in enough detail to be understood. A reviewer needs to understand the relevant process and the employee's real experience with it, not an unexplained bundle of sensitive files. Identify which specific examples establish the key facts, and coordinate with legal counsel before deciding what confidential detail can be shared and in what form. Start with a knowledge map: identify the company product or process, what the employee knows, how that knowledge was acquired, and why the proposed American duties require it. Provide appropriate context and genuine supporting records rather than assuming the form itself establishes advanced expertise.
Use evidence created during ordinary work wherever possible: mentor statements, shift assignments, maintenance tickets, annotated diagrams, training attendance, quality records, and messages resolving particular production failures. If the senior builder's name appears as author on the first version and as reviser on later ones, the authorship claim is proven without narrative.