NOC TEER Reference Letter — The Working Template (with Worked Example)

The single most-referenced document in any Express Entry, PNP, or work-permit file is the employer reference letter. It's the document IRCC officers read first and reread last. It's the document that loses files when it's wrong — and saves files when it's right.

This post is the working template we hand Halani Immigration clients. It includes the format, a complete worked example for a software developer (NOC 21232), and the audit checklist we run before any letter goes into a federal submission.

1. What IRCC actually wants

Per IRCC instructions and IRPR practice, every reference letter must contain all eight of the following:

1. Employee's full legal name — must match the passport biographical page
2. Employer details — full company name, address, on official letterhead
3. Job title — your formal title at that employer
4. Employment dates — start date and end date (or "to present"), explicit
5. Hours per week — actual hours worked, not just "full-time"
6. Gross annual salary plus benefits — total compensation in the local currency
7. Specific duties — 5–10 bullet points describing your responsibilities, aligned with the NOC's lead statement and main duties
8. Signatory information — the writer's full name, job title, direct phone, direct email, and signature on company letterhead

Missing any one of these is grounds for an officer to discount or refuse the experience claim. Reference letters that are perfect on substance but missing the writer's email get reclassified as "unverified" — which can be the difference between approval and refusal.

2. The format — top to bottom

Here is the structure we use for every Halani client:

[COMPANY LETTERHEAD]

[Date]

To Whom It May Concern:

This letter is to confirm that [Full Legal Name of Employee] has been
employed at [Company Name] in the position of [Job Title] from
[Start Date] to [End Date or "present"].

During this period, [Employee Name] has been working full-time, [X] hours
per week. Their gross annual salary is [Amount] [Currency], plus
[describe benefits — health insurance, paid leave, bonuses, etc.].

In their role as [Job Title], [Employee Name] is responsible for the
following duties:

  • [Duty 1 — written to align with NOC main duty]
  • [Duty 2]
  • [Duty 3]
  • [Duty 4]
  • [Duty 5]
  • [Duty 6]
  • [Duty 7]
  • [Duty 8]
  • [Duty 9]
  • [Duty 10]

[Optional paragraph about contribution / performance / scope of work.]

Should you require any further information regarding [Employee Name]'s
employment with us, please feel free to contact me directly.

Sincerely,

[Signature]

[Signatory's Full Name]
[Signatory's Title]
[Direct Phone]
[Direct Email]
[Company Address]

Two formatting notes:

• One page is fine. IRCC officers read hundreds of these. A clear, tightly-written one-page letter is more credible than a sprawling three-page narrative.
• Bullet points beat prose for duties. Officers compare the letter against the NOC dictionary by scanning for matching action verbs. Bullets make the comparison faster and the match more obvious.

3. Worked example — Software Developer (NOC 21232)

Here is a complete, NOC 21232-compliant reference letter for a Software Developer working in Bangalore, India:

ACME Software Solutions Pvt. Ltd. (Letterhead with address, phone, website, GST/registration number)

Date: 4 May 2026

To Whom It May Concern:

This letter is to confirm that Rahul Kumar Sharma has been employed at ACME Software Solutions Pvt. Ltd. in the position of Software Developer from 15 June 2022 to present.

During this period, Mr. Sharma has been working full-time, 40 hours per week. His gross annual salary is INR 1,800,000 (approximately CAD 29,500), plus health insurance, paid annual leave (24 days), provident fund contributions, and an annual performance bonus of approximately 10–15% of base.

In his role as Software Developer, Mr. Sharma is responsible for the following duties:

• Collaborates with business analysts and product owners to research, evaluate, and analyze user requirements for new and existing software systems
• Designs, develops, tests, and implements software code in Python, Java, and JavaScript using modern frameworks (Django, Spring Boot, React)
• Writes, modifies, integrates, and tests software code for new and existing applications
• Maintains existing applications, performs root-cause analysis on bugs, and implements code-level fixes
• Identifies and communicates technical problems, processes, and solutions to development teams and senior management
• Prepares reports, manuals, and other technical documentation for software systems
• Conducts code reviews of peers' work, ensuring adherence to coding standards, security best practices, and architectural patterns
• Participates in agile sprint ceremonies (planning, retrospectives, daily stand-ups) and contributes to estimation and prioritization
• Mentors junior developers on coding practices, debugging techniques, and architectural design decisions
• May lead small projects from technical specification through deployment and post-launch support

Mr. Sharma has been a strong contributor on multiple critical projects since joining the team and has demonstrated technical depth and leadership beyond his level.

Should you require any further information regarding Mr. Sharma's employment with us, please feel free to contact me directly.

Sincerely,

[signature]

Anjali Reddy Engineering Manager, ACME Software Solutions Pvt. Ltd. +91 80 4000 1234 (direct) anjali.reddy@acmesoftware.com [Company address]

Why this letter works:

• All 8 IRCC requirements are present and explicit
• Duties map to NOC 21232 main duties — research user requirements, design and develop, test and implement, maintain, document, code review (NOC 21232 main duties cover all of these)
• Specific technologies named — Python, Java, Django, Spring Boot — these are the kind of details that prove the letter wasn't generic-cribbed
• Direct supervisor signs — Engineering Manager, with direct phone + email (not the company main line)
• Salary in local currency with CAD reference — preempts an officer's currency-conversion question
• Hours per week explicit — "40 hours per week," not "full-time"

4. The audit checklist — run before submission

Before any reference letter goes into an eAPR or PNP submission, run this 12-point check:

1. ☐ Employee's full legal name matches passport
2. ☐ Company name, address, and letterhead present
3. ☐ Job title stated (and reasonably aligned to NOC)
4. ☐ Employment start date stated (DD/MM/YYYY or month-year)
5. ☐ Employment end date stated (or "present" with letter date recent)
6. ☐ Hours per week stated as a number, not "full-time" alone
7. ☐ Gross annual salary stated, currency named, benefits described
8. ☐ At least 5 duties listed, ideally 7–10
9. ☐ Duties align with the NOC's lead statement and at least 50% of its main duties
10. ☐ Signatory's full name, title, direct phone, direct email present
11. ☐ Signatory is direct supervisor or HR (not a peer, not the candidate)
12. ☐ Letter signed and dated within the last 90 days at submission

Letters that fail any single item should be returned to the issuer for correction.

5. When the employer won't cooperate

The hardest reference-letter cases are when a current or former employer will not write a letter. Options, in order of preference:

1. Former direct supervisor at that employer, now working elsewhere, willing to write on their current letterhead or as a personal letter referencing the period
2. HR department — sometimes will issue a generic but compliant letter from your personnel file even when your direct manager has left
3. Statutory declaration — your own sworn statement of duties, supplemented by pay stubs, T4s/foreign tax records, contracts, performance reviews, IDs/access cards, LinkedIn evidence, colleague witness statements
4. Independent verification — sometimes a notary or chamber of commerce can verify employment via a sworn affidavit if pay records are clear

The case can be built without a clean reference letter, but the documentation burden multiplies. We file these only when the alternative is no claim at all — and we manage officer expectations through the letter of explanation that accompanies the eAPR.

6. NOC classification — get this right first

Before you draft the reference letter, lock the NOC classification. Use our NOC Lookup to find the right TEER 2021 code based on the duties you actually performed. The NOC determines:

• Which Express Entry programs you qualify under (FSW vs CEC vs FST)
• Whether you're eligible for category-based draws (healthcare, STEM, trades, transport, agriculture, French)
• Which PNP streams you can apply to
• How your CRS skill-transferability points are calculated

Once the NOC is locked, the reference letter's duties section is written to align with that specific NOC's main duties — not generic "software work."

Halani Immigration Services Inc. drafts and audits reference letters as part of every Express Entry and PNP retainer. We've reviewed thousands of these letters; the failure modes are consistent and the fixes are surgical. The first consultation is free. Start your free assessment or book a strategy call.

For the bigger picture on how reference letters fit into the Express Entry filing strategy, see our Express Entry pillar guide. For category-based draw positioning specifically, see our category-based draws update.