Skip to content
NORTH VANCOUVER (DISTRICT) · L-1B FIELD GUIDE

What evidence rebuilds a technical record that has gone quiet?

Sources checked:

THE DIRECT ANSWER

Older design documents, internal procedure manuals the applicant wrote or maintained, escalation records, training material, release notes, and system configuration histories. Colleagues who can describe what the applicant contributed also help. The aim is a traceable line between the organization's own methods and this individual's working knowledge of them.

Prefer contemporaneous material over recollection

Documents created at the time carry more weight than a summary written for the filing. Search internal wikis, ticket systems, and archived project folders before asking people to remember. Where a system has been replaced, note whether the current version still relies on the applicant's work.

Redact customer or commercial detail according to the company's own rules, and let counsel decide what belongs in the packet. Search internal wikis, ticket systems, and archived project folders before asking anyone to remember, because documents created at the time carry more weight than a summary written for the filing. The useful material is older design documents, internal procedure manuals the applicant wrote or maintained, escalation records, training material, release notes, and system configuration histories, supported by colleagues who can describe what the applicant contributed.

Where a system has been replaced, note whether the current version still relies on the applicant's work, since that fact often connects a quiet period to the proposed role. Redact customer or commercial detail according to the company's own rules.