The internal protocol with its version history and validation data, evidence of authorship, a written comparison with the published method, and a job description built around work that requires the protocol.
Build the technical file first
The technical file is slower to assemble than the legal one, so start there. It should contain the protocol as internally recorded, earlier versions showing how it developed, the validation studies and the data behind the control limits, internal approval records, and the laboratory notebooks or reports connecting the named scientist to each element. Add a short written comparison with the published standard or the commercially available method, stating plainly what the company knows that the market does not and why the affiliate cannot simply hire it locally. Then the U.S. job description, written around tasks that require the protocol rather than around a training schedule. Support the whole with corporate evidence: registry extracts, share registers, financial statements showing both entities trade, and payroll covering the qualifying year abroad.
Hypothetical example: a ceramic-tile manufacturer wants to send the employee who developed its proprietary kiln-loading sequence to a U.S. affiliate. A first review should produce a technical index: the current procedure, earlier versions, validation results, internal approvals, and records linking the employee to each development step. The U.S. position description then explains where that sequence will be applied and why local staff cannot simply use a published method. Keep technical evidence intelligible by adding a short plain-language explanation, but retain the original records behind it. The common mistake is submitting confidential material without a roadmap, or a polished summary with no source record. Mark sensitive exhibits appropriately, reconcile their dates, and ensure the claimed work is specialized implementation rather than a generic training assignment.