Read the general professional work overview
A technical title can cover many different jobs. Organize evidence around actual responsibilities, deliverables and qualifications so a reviewer can assess the proposed profession. This exercise should make the work more understandable; it should not turn a technical résumé into an assertion that every software or technology position qualifies. TN is available only to citizens of Canada or Mexico performing qualifying professional work, and the record must support the listed profession rather than a convenient title. A first review usually produces a duty matrix, a credential checklist, and a list of documents that need an authorized employer explanation. Hypothetical example: An actuary receives an offer combining pricing models with account-management meetings. The employer must decide whether the actual role is presented around actuarial analysis before collecting a polished but inaccurate letter.
Group duties by actual output
Ask the employer to identify what the employee produces or analyzes and why the proposed qualifications are relevant. Separate technical work from sales, general support or administration where those activities exist. Use a representative account of the whole role rather than selecting only the tasks that seem most favourable. Make the employer choose a sensible grouping before drafting: analysis, deliverables, client communication, supervision, and administration. The decision is whether the professional activity is central across the role, not whether isolated favourable tasks can be listed without their surrounding work.
Use understandable supporting examples
An employer may be able to provide a nonconfidential explanation of typical assignments or deliverables. Avoid uploading proprietary materials through an initial consultation form. Ask what evidence can be shared appropriately and whether a written explanation is sufficient for the initial assessment before collecting unnecessary technical files. For each example, identify the person who can authenticate it and the nonconfidential record that supports it. A first consultation can then determine whether a manager statement, work sample description, transcript, or licence record settles the point without sending sensitive files unnecessarily.
Check the summary against the source description
Have the person who knows the role review the plain-language summary for accuracy. Preserve the original description alongside it. A reviewer should be able to identify what the summary clarifies and what it leaves unresolved. Do not use a renamed job title to bypass a substantive category mismatch. Compare the final letter with the original job description, offer, and credential records on the same day. If a material duty or reporting relationship has changed, resolve it before travel or filing; a later explanation cannot make an earlier description accurate.
Hypothetical example: a summary that outran the source
Hypothetical example: a mathematician receives a support letter in which a manager, trying to make the role sound rigorous, describes the applicant as leading the analytics function. The applicant performs statistical modelling and leads nobody. The description was written to help, and it introduces a claim the rest of the file contradicts. This is the ordinary failure in technical files: clarity drifts into elevation one sentence at a time, and nobody compares the finished summary against the source description. Read the two documents together at the end, sentence by sentence, and correct anything the source does not support. A file that overstates or understates the role should be corrected before submission; unsupported elevation is particularly difficult to repair.
What else is on your mind?
Is a matching job title enough for TN?Can years of experience replace a degree for TN?Can my own U.S. company employ me under TN?Can my spouse work if I hold TN status?Editorial source review: 2026-09-07. General preparation guidance, not an individual assessment.