The O*NET/DOT Crosswalk Explained for Vocational Work

A Deadline Notice Written in a Language No One Uses Anymore

A report lands on a counselor's desk citing DOT code 209.687-014 — "Mail Clerk" — as the claimant's past relevant work. The claimant's attorney wants to know what that occupation looks like in today's labor market: current wage data, current demand, current physical demands as the U.S. Department of Labor understands them now. But the wage tables the counselor has open are organized by Standard Occupational Classification (SOC) code, and the transferable skills software pulls its occupational descriptors from O*NET. Three systems, three numbering schemes, one occupation — and the report is due Friday.

This is not a rare situation. It is the default situation in vocational rehabilitation, because the field never fully migrated off the Dictionary of Occupational Titles (DOT) even after the government did. Every counselor who touches transferable skills analysis, labor market surveys, or wage-earning-capacity opinions works across at least two of these three systems, often three, on the same case. Getting the crosswalk right — and being able to show the crosswalk on paper — is what keeps an occupational citation from becoming the weakest link in a report under cross-examination.

By the end of this guide, you'll be able to explain how DOT, O*NET, and SOC codes relate to one another, know where the crosswalk between them loses precision, and record occupation codes in a way that holds up when someone on the other side of the table asks you to defend them.

Three Systems, One Vocational Puzzle

The Dictionary of Occupational Titles (DOT). Published by the U.S. Department of Labor, the DOT catalogued a large number of narrowly defined occupational titles, each described with a nine-digit code and a structured set of worker-function and physical-demand ratings. The Department of Labor stopped updating the DOT decades ago, replacing it with O*NET as the government's active occupational database. Despite that, Social Security Administration disability adjudication and many state workers' compensation systems still reference DOT codes and terminology directly, which is why the DOT remains functionally alive in vocational work even though it is frozen in time. Its descriptions reflect the labor market as it existed at the point the Department of Labor stopped updating it, not the labor market as it exists today.

O*NET (Occupational Information Network). ONET is the U.S. Department of Labor's current, actively maintained occupational database, built and updated by the National Center for ONET Development under USDOL/ETA. As of the most recent release, ONET covers roughly 900 occupation profiles spanning over 55,000 jobs in the current economy, each described with skills, tasks, knowledge areas, and work context data collected and refreshed on an ongoing basis. ONET content used here is included under ONET's CC BY 4.0 license; ONET is a trademark of USDOL/ETA.

SOC (Standard Occupational Classification). SOC is the statistical classification system the federal government uses to group occupations for data collection and publication — most importantly, the Bureau of Labor Statistics uses SOC codes to publish the wage and employment estimates in its Occupational Employment and Wage Statistics (OEWS) program, built from a probability sample of roughly 1.1 million establishments surveyed in semiannual panels. If you need a defensible wage figure for an occupation, you are, sooner or later, going to need its SOC code — because that is the code the wage data is actually organized around.

ONET occupations are built on top of SOC: each ONET-SOC code is the six-digit SOC code extended with two additional digits that let ONET split a single broad SOC category into more specific, more granular occupations. DOT sits outside this modern structure entirely — it predates ONET and SOC's current form — which is exactly why a crosswalk is needed to move between them at all.

How the DOT to O*NET/SOC Crosswalk Actually Works

A DOT to O*NET/SOC crosswalk is a published mapping table that links each historical DOT occupational code to its nearest equivalent ONET-SOC occupation, and from there to the SOC code used for wage publication. The Department of Labor built this crosswalk when it retired the DOT in favor of ONET, precisely because thousands of narrowly defined DOT titles needed some path forward into the new, more consolidated occupational structure.

That mapping is necessarily a collapse. The DOT defined occupations at a very fine grain — often distinguishing jobs by minor variations in setting, tools, or industry that ONET does not preserve as separate occupations. When you cross-walk a DOT code into ONET-SOC, multiple distinct DOT titles frequently land on the same broader O*NET occupation. That is not an error in the crosswalk; it is the structural difference between a system built to catalogue narrow job titles and one built to describe occupations at a level useful for skills, training, and labor-market data today.

Once you have the ONET-SOC code, the path to a SOC code and from there to OEWS wage data is more direct, because ONET-SOC codes are built as extensions of SOC codes rather than an independent system. This is the sequence worth memorizing: DOT code → O*NET-SOC code (via the published crosswalk) → SOC code (by truncation) → OEWS wage and employment data (by SOC lookup). Skipping a step, or assuming a DOT code maps one-to-one onto a single modern wage figure, is where crosswalk errors creep into reports.

Where the Crosswalk Breaks Down

The crosswalk is a genuine tool, not a shortcut, and it has real limits a careful counselor should name in writing rather than paper over.

Many-to-one collapse loses granularity. Because several DOT titles often map to one ONET occupation, physical-demand or exertion-level distinctions that mattered under the DOT can disappear once you move to the ONET occupation, which describes the modern job more broadly. If exertion level is central to the transferable skills question — as it often is — check the crosswalk result against the original DOT physical-demand rating rather than assuming the O*NET occupation preserved it exactly.

Some DOT occupations have no clean modern analog. The DOT describes a labor market that existed when the Department of Labor stopped updating it. Occupations that have materially changed, consolidated, or disappeared since then get mapped to the nearest available O*NET occupation — "nearest," not "identical." That distinction belongs in the report narrative, not left implicit.

SOC and O*NET-SOC are not always a clean one-to-one either. A single six-digit SOC category can split into several distinct eight-digit ONET-SOC occupations, each with different task and skill profiles but the same underlying wage data, because BLS publishes OEWS wage estimates at the SOC level, not the more granular ONET-SOC level. Two O*NET occupations with genuinely different job content can end up citing the identical published wage figure once you step back up to SOC. That is a limitation of the published wage data's granularity, not a flaw in your analysis — but it needs to be disclosed, not glossed over.

Rules about which code a forum expects are jurisdiction-specific. Some SSA disability contexts and certain state workers' compensation systems still expect DOT-anchored language; others accept or prefer O*NET/SOC framing. There is no single national standard for which system a given hearing officer, adjudicator, or carrier will expect. Confirm the expected framework with the relevant authority for that jurisdiction or forum before you finalize a report — never assume the convention from one state or one SSA region generalizes to another.

Recording Occupation Codes So They Survive Cross-Examination

The practical fix for all of the above is disclosure, not perfection. For every occupation cited in a report that carries any weight — past relevant work, alternative occupations identified in a transferable skills analysis, occupations used in a labor market survey — record all three codes together, not just whichever one your software surfaced first:

• The DOT code and title, sourced to the Dictionary of Occupational Titles, noting that the DOT reflects labor-market conditions as of its last government update, not the current market.
• The ONET-SOC code and title, sourced to ONET, with the release or database version noted (O*NET content is updated periodically; a code's task list in one release can shift in the next).
• The SOC code used to pull any wage figure, with the OEWS publication date the wage data came from.

A report that cites a DOT title, an O*NET task list, and a BLS wage figure without ever showing how those three numbers connect is asking the reader to trust a crosswalk they can't see. Show the crosswalk.

This is also where a working knowledge of the DOT occupation codes list structure pays off — knowing how a nine-digit DOT code is built (industry designation, occupational group, worker-functions ratings, and an alphabetical-order code) makes it much easier to spot when a crosswalk result looks off, because the original code's internal logic tells you something about what kind of work it was actually describing. The same discipline applies on the O*NET side: searching directly in O*NET Online's occupation search rather than trusting a single auto-generated match lets you confirm the mapped occupation's task list actually resembles the work in question before you commit to it in a signed report.

Building a Repeatable Crosswalk Workflow

Most private-practice counselors handle this today with a spreadsheet, a printed or bookmarked copy of the official DOT-to-ONET/SOC crosswalk table, and a separate ONET Online lookup — three tools, one occupation, and a real risk of a re-keyed digit breaking the chain between report and citation. That manual process works, but it does not scale past a handful of cases a week without something slipping.

Rehabilitation Management Suite's transferable skills workflow builds the crosswalk logic into the case record itself: enter a DOT code once, and the system carries the matched ONET-SOC occupation and its associated SOC code forward through the transferable skills analysis and into the wage-earning-capacity calculation, with each source and version tracked alongside it. The software organizes the citation chain — DOT to ONET-SOC to SOC to OEWS wage — so it is visible in the finished report rather than buried in a counselor's private spreadsheet. It does not decide which occupation is the right transferable match; that judgment, like the signature on the report, is the credentialed counselor's.

If you want the crosswalk logic in a format you can check by hand before you trust any software's output, the O*NET/DOT Occupation Crosswalk Reference Workbook lays out the mapping structure and code anatomy discussed above in a working reference format. Pair it with a look at our broader transferable skills analysis resource hub for the rest of the TSA methodology this crosswalk feeds into.