Identify the dates, versions and actual connection to current work. Preserve their original context.
Link the evidence without rewriting it
Explain the relevant continuity and limitations. Do not replace historical names in original records or imply the applicant worked on a version that did not yet exist.
Dated artifacts from the company's own systems: version-control histories, design specifications, patent or invention records, validated procedures, training materials and internal staffing data. 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. Describe the protocol in a summary that explains its proprietary elements without disclosing them, attach the version history and training records, and offer the full document for inspection if requested. Provide training records, permitted project summaries, internal role descriptions and other evidence that accurately explains the knowledge, deciding in advance with the applicant what needs special handling. Useful material can include internal training paths, product manuals not generally available, implementation histories, project records, peer comparisons, and statements from knowledgeable managers. Build the account chronologically from personnel and project records rather than from memory: assignment dates, plant locations, commissioning reports, revision histories on work instructions.