Discuss training records, permitted project descriptions, internal qualifications and other evidence that accurately explains the knowledge, and ask the company to identify what can be shared and what requires special handling.
Choose records that answer the actual question
A reviewer needs to understand the process and the person's experience with it, not receive an unexplained collection of sensitive files. Ask which examples establish the material facts, and coordinate the employer's technical staff and legal reviewer before submission so the evidence neither overexposes confidential information nor becomes too generic to support the claim.
Start with a knowledge map: identify the company product or process, what the employee knows, how that knowledge was acquired, and why the proposed American duties require it. One L-1B branch examines special organizational knowledge concerning products and services, research and equipment, techniques and management, other interests, and those matters’ international-market application. Its second branch examines advanced knowledge of the organization’s processes and procedures. Support the map with training, project, authorship, internal-certification, and assignment records. Have technical, privacy, security, and legal reviewers agree on lawful redactions. The frequent mistake is replacing a comprehensible evidentiary chain with unexplained confidential files or vague praise.
Hypothetical example: an Ottawa clinical-trial software configurator has implemented the employer’s proprietary consent workflow across several regulated studies. Useful records could include permitted course completion, configuration-change logs, sanitized rollout plans, and a manager’s comparison of the employee’s experience with the proposed tasks. The team should exclude patient information and explain each exhibit’s purpose. A confidentiality label cannot replace proof of knowledge, while a document dump may obscure the exact company process supporting the petition.