Benchmarking Canadian Pay with Statistics Canada NOC Wage Data
Why Canadian HR Teams Need a Government Wage Source — Not Just Gut Feeling
Picture this: you're the HR Manager for a 75-person professional-services firm headquartered in Toronto, with a handful of staff in Vancouver and a growing team in Winnipeg. Your CEO has just asked you to post three new roles under Ontario's new pay-transparency rules, and a department head in BC is pushing back on a salary offer, claiming "the market is higher." You open the spreadsheet you've been maintaining since 2021 and realize the comp data in it is a mix of LinkedIn salary posts, one-off survey responses, and your own memory of what you paid someone three years ago.
That spreadsheet cannot answer the question your CEO is asking, and it cannot defend a pay range if a candidate or regulator challenges it.
What can answer it is a public, government-administered wage dataset built specifically for Canadian labour markets: Statistics Canada's Occupational Employment and Wage Statistics, delivered through Table 14-10-0417-01. It is free, it covers every province and most major cities, and it is organized by the National Occupational Classification — the same taxonomy your job postings already reference whenever you write "NOC" anywhere near a work permit application.
This article shows you exactly how to find, read, and apply that data to build defensible Canadian pay bands — step by step, from pulling the table to setting a min/mid/max range.
What Statistics Canada's NOC Wage Data Actually Is
Statistics Canada publishes wage data organized by the National Occupational Classification (NOC), Canada's standardized system for categorizing jobs. The relevant table — Table 14-10-0417-01 — provides hourly and annual wage estimates broken down by:
- NOC code and title (the occupation)
- Geography — at the national level, by province or territory, and by Census Metropolitan Area (CMA)
- Wage percentiles — typically the 10th, 25th, median (50th), 75th, and 90th percentile, plus a mean
The data is collected through the Labour Force Survey and related administrative sources and is released under the Open Government Licence — Canada, which means you may use, reproduce, and redistribute it, including for commercial purposes, as long as you attribute Statistics Canada as the source.
This matters for HR teams in two ways. First, it is free — there is no subscription, no per-seat fee, and no data agreement to negotiate. Second, because it is government-administered and publicly citable, it provides a defensible audit trail if you are ever asked to justify a pay range to a regulator, an employee, or your own board.
Table 14-10-0417-01 is released under the Open Government Licence — Canada, meaning you can use it freely as a benchmark source — but you must attribute Statistics Canada when you do.
Understanding the NOC System Before You Search
The NOC is Canada's equivalent of the US Standard Occupational Classification (SOC) system. If your team has ever used BLS OEWS data for US roles, the logic is identical: you find the code that best describes the job, then read the wage distribution for that code in your geography. (For a parallel walkthrough of the US side, see our BLS OEWS benchmarking guide.)
Since 2022, Canada has used NOC 2021, a five-digit structure. The first digit is the broad category (e.g., 1 = Business, finance and administration), the second is the major group, and the remaining digits narrow to the specific occupation. A payroll administrator, for example, sits in a different five-digit code than a compensation and benefits manager, even though both are in the broad "Business, finance and administration" category.
How to identify the right NOC code for a role:
- Start with the job's core duties — what does the person actually produce or decide?
- Search the NOC browse tool at the Statistics Canada or Employment and Social Development Canada (ESDC) website using plain-language terms (e.g., "software developer," "warehouse supervisor").
- Read the lead statement and main duties for the top two or three candidates. Match on duties, not just title — a "Senior Analyst" in your company may align to an analyst code or a specialist code depending on what the person actually does.
- Record both the five-digit code and the exact NOC title — you will need both when you pull the table.
One common mistake: choosing a code because the title sounds right, then pulling wage data that reflects a fundamentally different job. A financial analyst and a financial auditor carry different codes and meaningfully different wage distributions. Take five minutes to read the duty statements.
Pulling the Data from Table 14-10-0417-01
Once you have your NOC code, the retrieval process is straightforward.
Step 1 — Navigate to the table. Search "Statistics Canada Table 14-10-0417-01" in any browser. The table lives on the Statistics Canada website under the Labour section. Bookmark it; you will return to it repeatedly.
Step 2 — Set your filters. The table interface lets you filter by:
- Geography — select your province (e.g., Ontario, British Columbia) or a specific CMA (e.g., Toronto, Vancouver, Winnipeg). CMA-level data is more granular and more useful for hiring decisions in major cities; provincial data is more stable and better for roles spread across a region.
- NOC code — enter or browse to the five-digit code you identified.
- Wages — select the wage statistics you want: median hourly, mean hourly, and/or the percentile breakpoints.
Step 3 — Download to CSV. The table exports cleanly to CSV. Pull national, provincial, and at least one CMA in one download — it takes seconds and means you have a comparison set before you start building the band.
Step 4 — Note the reference period. Statistics Canada updates OEWS data periodically. The reference period is shown in the table header. Always record it in your working file and replace the data when Statistics Canada publishes a new release. Stale benchmarks are one of the most common compensation compliance risks — you do not want to defend a range in 2027 using data from 2022.
Reading the Percentile Distribution
The wage table gives you a distribution, not a single number. Here is what each percentile tells you:
| Percentile | What it means for benchmarking |
|---|---|
| P10 | Bottom of the market — typically below minimum viable compensation for experienced hires |
| P25 | Lower market — reasonable for entry-level or developing performers in the role |
| P50 (median) | True market midpoint — what half of incumbents earn less than, half more |
| P75 | Upper market — competitive for strong performers or talent-scarce roles |
| P90 | Top of market — used to anchor ranges for critical/hard-to-fill positions |
For most statistics canada wage benchmarking applications, the P50 is your starting point. It anchors the midpoint of your pay band. The P25 and P75 then frame the width of the market — and your band minimum and maximum can be set relative to those anchor points.
One important nuance: the Statistics Canada table reports hourly wages as its primary unit, with annual equivalents calculated at standard hours. If your organization pays salaried employees and quotes annual figures in job postings (as Ontario's pay-transparency rules require), convert carefully — confirm the hours assumption Statistics Canada uses for the annualization, and apply the same assumption consistently across all your roles.
Building a Pay Band from NOC Wage Data: A Worked Example
The following is a purely illustrative example to show the arithmetic. The dollar figures below are placeholders; replace them with real values from Table 14-10-0417-01 for your specific NOC and geography before using this in a posting or an offer.
Suppose you are benchmarking a mid-market professional role in Ontario (imaginary figures for illustration only):
- Statistics Canada P25 (Ontario): $X/hr
- Statistics Canada P50 (Ontario): $Y/hr
- Statistics Canada P75 (Ontario): $Z/hr
Setting the band midpoint. The P50 — the median — becomes your target midpoint. If you are explicitly trying to pay at market, your band midpoint equals P50.
Setting the band minimum and maximum. A standard approach is to apply a range spread — typically 40–60% for individual-contributor roles, wider for senior or specialized roles. A 50% spread means the band maximum is 50% above the minimum.
Using the formula:
- Band Minimum = Midpoint ÷ 1.25 (places the midpoint 25% above the minimum)
- Band Maximum = Minimum × 1.50
So if P50 yields a midpoint of, say, $75,000/yr (again, illustrative), then:
- Minimum = $75,000 ÷ 1.25 = $60,000
- Maximum = $60,000 × 1.50 = $90,000
- Range width = $90,000 − $60,000 = $30,000 (50% spread)
This band — $60,000–$90,000 — satisfies Ontario's requirement that a publicly advertised pay range not exceed $50,000 in width (the $30,000 width is well within that cap), and it gives your hiring managers a defensible, market-anchored corridor to work within.
For a deeper look at how to build the full band structure — levels, titles, and multiple grades — see our complete guide to job band structure.
Provincial vs. CMA Data: When to Use Each
This is the question most Canadian HR teams get wrong: they pull provincial data and apply it to a Vancouver or Toronto hire, then wonder why candidates push back.
Use provincial data when:
- The role can be performed anywhere in the province and you will not adjust pay for location
- You are setting a policy-level range that applies to all provincial employees regardless of city
- CMA data for your target NOC is thin (small sample, suppressed values)
Use CMA data when:
- You are hiring specifically in Toronto, Vancouver, Calgary, Ottawa, or another major CMA
- Your competitors for talent are primarily other employers in that CMA
- You are preparing a job posting under BC or Ontario pay-transparency rules and the role is headquartered in a specific city
In practice, many HR teams do both: pull the CMA median to set the midpoint for city-based hires, and pull the provincial median to set policy minimums that apply province-wide. The gap between the two tells you something useful — if the Toronto median for a role is meaningfully above the Ontario provincial median, you have a geographic differential you need to build into your structure explicitly, not paper over with a single range.
Pay-transparency obligations in both provinces make this precision more important than ever. Ontario's rules, which took effect January 1, 2026, require employers with 25 or more employees to include a salary range in publicly advertised postings for roles up to $200,000 — and that range must not exceed $50,000 in width. BC has required pay ranges in all job postings since November 1, 2023, and explicitly prohibits open-ended ranges ("up to $30/hr" or "$20/hr and up" are not compliant). Ranges anchored to CMA-level NOC data satisfy both requirements more credibly than ranges built from anecdote. For the full compliance picture in each jurisdiction, see our articles on Ontario pay transparency and BC pay transparency.
Common Pitfalls in Canadian NOC Benchmarking
Pitfall 1: Using the national average when a CMA number exists. National averages flatten meaningful geographic variation. The national median for a role can be substantially different from what the Toronto or Vancouver labour market actually pays — and it is the local market that will determine whether your offer is accepted.
Pitfall 2: Ignoring suppressed values. Statistics Canada suppresses cells where the sample is too small to produce a reliable estimate. If you see a suppressed value for your NOC in a smaller province or CMA, do not substitute a number — either use the provincial figure, expand to the nearest adjacent major region, or note the data gap explicitly in your compensation documentation.
Pitfall 3: Treating wage data as performance data. The P75 in the Statistics Canada table tells you what 75% of incumbents in that role earn less than. It does not tell you that your specific employee performs at the 75th percentile. Band positioning and individual-employee placement within the band require a separate performance or experience framework on top of the market anchor.
Pitfall 4: Updating once and forgetting. Statistics Canada's OEWS data is a snapshot. Labour markets shift. Build a calendar reminder to refresh your benchmarks every time Statistics Canada publishes a new OEWS release, and document the refresh date in every band you build. Stale data is not a defence — it is a liability.
Pitfall 5: Anchoring only to hourly figures when you post annual salaries. Verify the annualization methodology Statistics Canada uses, apply it consistently, and show your conversion in your working file. If a candidate or regulator ever asks how you arrived at a posted range, you want a clean, traceable answer.
Putting It Together: Statistics Canada Wage Benchmarking as a Repeatable Process
Statistics canada wage benchmarking does not need to be a one-off exercise done under deadline pressure every time you open a new role. Built as a repeatable process, it takes less than an hour per role and produces documentation you can keep on file for the three-year retention period Ontario's ESA now requires for job postings and related records.
A clean process looks like this:
- Identify the NOC code — read the duty statement, not just the title.
- Pull Table 14-10-0417-01 — filter to your province and CMA; download to CSV; record the reference period.
- Set the band midpoint — anchor to P50 unless you have a deliberate reason to pay above or below market.
- Apply a range spread — 40–60% for most individual-contributor roles; document your rationale.
- Check the width — confirm the band does not exceed the $50,000 cap for Ontario postings.
- Record everything — the NOC code, the source table, the reference period, the percentile you used, and the spread formula. This is your audit trail.
- Refresh on the next OEWS release — set the calendar reminder now.
When you are managing NOC wage benchmarking across multiple roles, provinces, and CMAs simultaneously, a structured compensation band tool can hold the framework so the logic does not live only in your head or in a spreadsheet where, as research consistently shows, errors accumulate invisibly. If you are ready to move from a manual process to a structured one, explore Job Band Builder's pricing or start a free trial to see how band management works in practice.
Canadian salary benchmarking is not a black box. The data is free, the methodology is learnable, and the compliance case for doing it properly has never been stronger. ```
Ready to go beyond the guide?
Build a defensible, BLS-benchmarked band structure in under 30 minutes.