By Rovaryn Digital · May 16, 2026 · 7 min read
Why O*NET Online Is the Working Reference in Vocational Practice
You're two days from a report deadline and the claimant's last job title — punch press operator, per the old personnel file — doesn't map cleanly to anything current. The employer folded a decade ago. The Dictionary of Occupational Titles code on the file is accurate for 1991, but you need to know what that work looks like today, in current labor-market terms, before you can even start comparing it to anything else. This is the moment an O*NET Online occupation search either saves your afternoon or costs you another hour of guessing.
ONET Online is the U.S. Department of Labor's public database of occupational information — built and maintained by the National Center for ONET Development for the Employment and Training Administration — and it is the working reference most vocational practitioners reach for first when identifying, describing, or comparing occupations. As of the most recent release, it covers 900 occupation profiles drawing on more than 55,000 job titles feeding into those profiles. That scale is exactly why it functions as the connective layer between an outdated Dictionary of Occupational Titles code and a Standard Occupational Classification (SOC) code a labor market survey or wage table will recognize.
By the end of this walkthrough, you'll know how to run an ONET Online occupation search three different ways, what to pull off the resulting report for a transferable skills analysis, and how to record the DOT-to-ONET-SOC path so the number in your report doesn't fall apart under cross-examination.
Three Ways to Run an O*NET Online Occupation Search
O*NET Online supports three practical entry points, and knowing which to use first depends on what you're holding.
Keyword search, when you have a job title but no code — type "punch press operator" and ONET Online returns a ranked list of current occupation matches with their ONET-SOC codes attached. Browse by industry or job family, when you have a sense of the field but not the title — useful for exploratory work or when a claimant describes duties rather than naming a role. Crosswalk search, when you're starting from a code rather than a title — ONET Online's crosswalk tool accepts a DOT code, a Military Occupational Classification code, or an existing SOC code and returns the current ONET-SOC equivalent.
For most vocational files, the crosswalk search is the fastest path, because most source records — old personnel files, prior TSA reports, disability applications — carry a DOT code, not a modern title. That crosswalk function is also where the most common data-entry mistake in vocational practice happens: treating a one-to-one crosswalk hit as a guarantee, when many older DOT codes actually split across several current O*NET-SOC occupations. Confirming which of several possible matches actually fits the work performed is a judgment call for the practitioner, not something the search box resolves automatically. If this crosswalk logic is unfamiliar, the O*NET–DOT crosswalk explained covers the mechanics in more depth than fits here.
Reading the Occupation Report: What to Pull for a TSA
Once you land on an occupation, O*NET Online presents two report formats: the Summary Report and the Details Report. For transferable skills work, both matter, but for different reasons.
The Summary Report gives you the fast read — tasks, knowledge, skills, abilities, and work context at a glance. This is what you scan first to confirm you've landed on the right occupation before committing time to it.
The Details Report is where the TSA-relevant substance lives: work activities broken down further, detailed work context items (including physical demands like standing, climbing, and exposure to conditions), and — critically — the O*NET-SOC code itself, which is what a subsequent BLS OES wage lookup or labor market survey will need to key against. If you're building or refining your search-by-title process specifically, the walkthrough on SOC code lookup by job title covers that lookup end to end.
Pull and record, at minimum: the ONET-SOC code, the occupation title as ONET currently states it, the physical demand characterization, and the specific vocational preparation or education context noted in the report. Skipping any of these means re-doing the search later when a reviewing party — an adjuster, an opposing expert, a hearing officer — asks where a number came from.
Where the DOT Still Shows Up — and Why the Crosswalk Matters
Here's the part that trips up newer practitioners: the Dictionary of Occupational Titles was last substantively updated in 1991, and the Department of Labor stopped maintaining it in favor of ONET decades ago — yet the DOT has not disappeared from vocational practice. Some state workers' compensation systems, some Social Security Administration vocational expert testimony conventions, and some older insurance file formats still reference DOT codes and DOT-specific concepts like Specific Vocational Preparation (SVP) levels, because those frameworks were built around DOT terminology before ONET existed. Whether a given jurisdiction or referral source still expects a DOT code alongside your O*NET-SOC data varies, and it is worth confirming directly with the relevant workers' comp board or referral source rather than assuming your last file's convention carries forward — these requirements are jurisdiction-specific and do not generalize from one state or one carrier to another.
This is exactly why the crosswalk step is not optional busywork. A report that cites only a current O*NET-SOC code, when the reader expects a DOT code and SVP figure they recognize, creates friction that has nothing to do with the quality of your analysis. The reverse is also true — citing only a DOT code in front of a party using current labor-market data leaves your figures untethered from anything a wage table can verify. For the mechanics of moving in either direction, see the DOT-to-O*NET-SOC crosswalk and the broader case for why the Dictionary of Occupational Titles is still used in current practice.
Recording Physical Demands and Worker Requirements Without Losing Fidelity
The physical-demand and worker-requirement data on an ONET Details Report is descriptive, not diagnostic — it describes what the occupation, in the aggregate, typically requires, not what any one employer's version of that job demands, and it is not a substitute for a treating provider's functional capacity assessment. Where your file includes documented physical restrictions, your job is to compare those restrictions against the ONET work-context data for candidate occupations, not to treat the O*NET figures as medical findings.
Practically, that means recording the specific O*NET work-context items you relied on — not just "sedentary" or "light," but which line items in the report support that characterization — so a reader can trace your conclusion back to the source data rather than taking your characterization on faith. This is also where consistent field-by-field recording pays off across a caseload: the same occupation should generate the same physical-demand notes every time it's pulled, regardless of which counselor in the practice ran the search.
Building the Search Into a Repeatable TSA Workflow
An O*NET Online occupation search is only as useful as what happens to the result afterward. On a single file, running the search, reading the report, and recording the relevant fields by hand works fine. Across a caseload — five, fifteen, forty open files, each needing occupations searched, crosswalked, and recorded consistently — the manual version is where fields get skipped, codes get transposed, and reports start disagreeing with each other on the same occupation. That consistency question sits at the center of how to perform a transferable skills analysis, and it's worth reviewing the full method if you haven't standardized your TSA process yet — the transferable skills analysis resource hub collects the related pieces in one place.
To make the DOT-to-ONET-SOC step faster and more consistent across your files, we built the *ONET/DOT Occupation Crosswalk Reference Workbook* — a downloadable reference for practitioners who move between DOT-era file data and current O*NET-SOC codes on a regular basis. Download the workbook and keep the crosswalk step from becoming the slowest part of your search.
This article includes information from ONET Online, used under CC BY 4.0; ONET is a trademark of the U.S. Department of Labor, Employment and Training Administration.