Collect records that prove the real transaction, role, relationship, and timeline rather than polished summaries alone.
L1B planning question: documents
Build records around acquisition, use, and necessity of the knowledge. Helpful material can include training histories, project assignments, internal role descriptions, product or process documentation, supervisor letters, samples that can be shared lawfully, and the U.S. assignment description.
Do not submit sensitive information carelessly; explain confidential systems at an appropriate level while still making the knowledge intelligible. Hypothetical example: an internal manual is available to many staff, but the applicant developed a particular implementation method through years of deployments. Show the personal project history and how the method will be used, rather than relying on the manual's existence.
Corporate relationship, foreign payroll, and organizational records remain necessary alongside the knowledge evidence. Create an index that gives each record a date, issuer, purpose, and relationship to the next record. Where a document is translated, preserve the original and the translation in the required form.
Reconcile names, account numbers, addresses, entity names, and dates before submitting anything. An unexplained inconsistency can distract from otherwise strong evidence. Avoid altering historical records to make a file neater; a transparent explanation is safer than a manufactured appearance of continuity.
Keep copies of final versions and receipts so later questions can be answered from the same factual record. Current official forms and filing instructions should be checked close to the relevant process because a well-organized older package can still use obsolete requirements.