Preserve both accounts and ask the responsible parties to explain the difference. A combined summary should not conceal inconsistent evidence.
Reconstruct the actual secondment tasks
Identify dates, supervision, deliverables and which organization can confirm each fact. Distinguish training from productive work and changes over time. Use reliable records to resolve the account rather than selecting the more favorable description. The technical knowledge and employment chronology should be coherent without rewriting what actually occurred.
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. More detailed exhibits may describe training modules, project phases, system architecture, quality controls, or implementation decisions without publishing sensitive source code or customer data. Obtain the final publication, contributor statements, drafts or revision history, and employer records identifying which tests, diagrams, or explanations the applicant produced. Gather original job descriptions, payroll entries, training certificates, project assignments, product documentation, and manager statements explaining which duties continued after reclassification and which were added. Where confidentiality limits what the employer will release, agree in advance on a substitute that still settles the point: a redacted document, a description of the system prepared by someone senior, or a statement from the person who supervised the work.