Authored internal documents carry more weight than testimonials. Protocol manuals with her name and revision history, plant variety protection filings listing her as breeder, database design records, training logs and a reasoned replacement-training estimate all show the knowledge exists and where it came from.
Build the file from what the company already produced
Most of what proves this case was written years before anyone thought about a transfer. Standard operating procedures for the selection pipeline, dated and attributed. Laboratory notebooks or electronic equivalents showing method development.
Applications for plant variety protection or patents naming her among the breeders. Internal presentations in which she set the thresholds the company now uses. Commit histories or change logs for the trait database if it was built in-house.
Around that core sit two constructed documents that must be written honestly. One is a statement from the research director explaining how the affiliate's project depends on that knowledge and why nobody at the American entity holds it. The other is a training estimate: how many months, covering what, and why the gap cannot be closed by hiring.
Where a document was created in Dutch or French, provide a complete certified translation rather than a summary.