Actual task plans, training material and evidence of the employee’s contribution can explain the sequence.
Distinguish company information from personal knowledge
A manual alone may show the process without proving the applicant’s experience. Identify what each record establishes and handle sensitive material appropriately.
Artefacts generated by the proprietary work: design documents, release notes, revision histories naming the specialist, internal training records, and customer contracts describing delivered systems. Use travel evidence only to place the employee at an assignment; pair it with dated work orders, technical reports, access logs, correspondence and supervisor explanations showing what was actually learned or performed. Add revision histories showing decisions the specialist made and why, validation and requalification reports, deviation or non-conformance investigations the specialist resolved, and internal training material the specialist wrote for operators or auditors. Build the record around artifacts created before the petition: internal manuals, access histories, training materials, change logs, and messages assigning unusual problems. Where a filing is imminent and the records are thin, it is better to acknowledge that and build from whatever contemporaneous material exists — job records, emails, revision histories — than to create a polished narrative with nothing behind it.