The NOC-to-SOC Crosswalk Between Canada and the US

Why cross-border cases need a crosswalk at all

A vocational counselor based in Windsor, Ontario is retained on a long-term disability file for a claimant who spent eleven years assembling components in a Detroit plant before a layoff sent him home across the bridge. The insurer wants a labor market survey built on US wage data, tied to a specific occupation code. The claimant's own work history, though, is documented the way Canadian records document it: a job title and, if the counselor is lucky, a National Occupational Classification (NOC) code buried in a T4 or a service record. There is no single government-issued table that converts a NOC code into a US Standard Occupational Classification (SOC) code. The counselor has to build the bridge by hand, occupation by occupation, and be ready to explain how.

This is the quiet complication behind every cross-border vocational file, whether the claimant worked in Canada and now lives in the US, or the reverse. Two countries, two classification systems, two labor market data sets, and no official concordance connecting them directly. By the end of this article you should be able to explain how NOC and SOC are each built, where the two systems line up closely enough to support a defensible match, where they diverge, and how to document the match so it holds up when a carrier, an attorney, or opposing counsel asks how you got there.

How Canada's NOC 2021 is built

The NOC groups occupations by a framework Statistics Canada calls TEER — Training, Education, Experience, and Responsibilities — running from TEER 0 (management occupations) through TEER 5 (occupations usually requiring no formal education and short-duration on-the-job training). Within that framework, occupations are organized into unit groups, each carrying a five-digit code and a written description of typical duties, employment requirements, and related job titles. A counselor working a Canadian file starts here: the unit group description, not the job title on a pay stub, is the unit of comparison that matters. For a fuller walkthrough of how the TEER structure is organized and where practitioners most often misread it, see our companion piece on the NOC 2021 occupation classification.

How the US SOC and O*NET extend it

The US system starts at a coarser level and then adds detail. The Standard Occupational Classification groups occupations into major groups and then detailed occupations, each carrying a six-digit SOC code. The Occupational Information Network (ONET) extends that structure further, attaching a more granular ONET-SOC code and a rich profile of tasks, skills, and work context to each detailed occupation. As of the current release, ONET covers roughly 900 occupation profiles spanning more than 55,000 job titles — includes information from ONET, used under CC BY 4.0; ONET is a trademark of USDOL/ETA. That granularity is exactly what a labor market survey or a transferable skills analysis needs, and it's also exactly what has no Canadian counterpart at the same depth. If you haven't worked through how DOT codes, ONET, and SOC relate to one another inside the US system, our breakdowns on the DOT-to-O*NET/SOC crosswalk and the O*NET-DOT crosswalk explained cover that groundwork, and our SOC code lookup by job title guide covers the practical side of finding the right code from a title alone.

Where NOC and SOC line up — and where they don't

At the level of broad occupational categories, NOC and SOC describe a recognizably similar world: management, business and finance, health, trades, sales, and so on. The trouble starts one or two levels down. NOC's TEER-based grouping and SOC's major-group structure don't slice the labor market along identical seams — an occupation that sits cleanly inside one Canadian unit group can straddle two or three US detailed occupations, or vice versa, because the two systems were built for different national labor market surveys with different histories and different levels of granularity. There is no published bilateral concordance table from Statistics Canada or the US Bureau of Labor Statistics that resolves this automatically. A title-to-title match — "Machine Operator" in one system to "Machine Operator" in the other — is a starting guess, not a finding.

A title match is not an occupation match. The duties have to line up before the codes do.

A documented method for matching occupations across the border

The defensible version of this work happens in a specific order, and the order matters as much as the outcome:

1. Start from duties, not titles. Pull the actual task list from the source-country record — the NOC unit group description, or the O*NET/SOC task statements — before looking at the destination-country catalog.
2. Search the destination system by duty content. Look for the unit group or detailed occupation whose task description overlaps most closely, not the one whose title sounds most familiar.
3. Check TEER against skill-and-training level. A NOC TEER 2 occupation should generally land near a SOC detailed occupation with comparable training and experience requirements — if it doesn't, treat that as a flag to re-examine the match, not a reason to force it.
4. Keep the wage data separate from the code match. US wage benchmarking through the Occupational Employment and Wage Statistics program draws on a probability sample of roughly 1.1 million establishments; Canadian wage data comes from a different survey instrument entirely. Matching the occupation code is step one — matching, or explicitly declining to match, the wage source is a separate, later step that deserves its own documented reasoning.
5. Write down the rejected alternatives. The unit groups or SOC codes you considered and ruled out are as important to the file as the one you selected, because that's what shows the match was reasoned rather than assumed.

Practice-management stakes for CRCs handling cross-border cases

This isn't a niche problem. Certified Rehabilitation Counselors practice on both sides of the border — the Commission on Rehabilitation Counselor Certification counts over 15,000 CRCs practicing in the United States, Canada, and several other countries. And the population of claimants with a disability affecting daily activities is substantial in Canada as well as the US: Statistics Canada's 2022 Canadian Survey on Disability found 27% of Canadians aged 15 and over — 8.0 million people — reported one or more disabilities limiting daily activities, up from 22% (6.2 million) in 2017. Cross-border work histories, cross-border families, and cross-border claims are a normal part of the caseload, not an edge case. For the broader picture of how transferable skills analysis is practiced under Canadian frameworks, see our guide to vocational rehabilitation in Canada.

Build the crosswalk into your case file

None of this replaces professional judgment, and no software resolves a NOC-to-SOC match automatically — the classification systems themselves don't provide that answer, and a credentialed practitioner's documented reasoning is what makes the resulting opinion defensible. What a good reference tool can do is keep the comparison organized: the source occupation, the destination candidates you considered, the duty overlap you found, and the rationale for the one you chose, all in one place instead of scattered across sticky notes and half-remembered searches. Our O*NET/DOT Occupation Crosswalk Reference Workbook is built for exactly that kind of side-by-side documentation work. Download the template and see how it structures a cross-border occupation match before your next file lands on your desk.