Is the Dictionary of Occupational Titles Still Used?

Why a Counselor Still Opens a Book the Government Stopped Printing

A vocational expert preparing testimony pulls up DOT code 690.685-014 — a job title last touched by a Department of Labor analyst before most of the firm's junior counselors were born — and cites it in a report going to a federal administrative law judge this year. Meanwhile, opposing counsel's expert has built a rebuttal entirely from ONET data, current as of the last quarterly release. Both experts are working the same case. Neither is wrong. That contradiction — a functionally frozen government publication still shaping active disability and workers' compensation outcomes — is where most practitioners new to forensic vocational work get stuck, and where new hires start asking their supervisor why the firm keeps a DOT reference on the shelf at all. By the end of this piece, you'll know exactly why the Dictionary of Occupational Titles still gets cited, what ONET was built to replace it with, and how the two sources are meant to work together rather than compete.

The DOT's Origin and Why the Department of Labor Stopped Updating It

The Dictionary of Occupational Titles was the U.S. Department of Labor's standardized catalog of job titles, each assigned a nine-digit code and a structured profile: physical demand level, General Educational Development (GED) rating, Specific Vocational Preparation (SVP) time, and a terse narrative of duties. It was built for a mid-twentieth-century labor market of discrete, physically defined trade and industrial jobs, and it did that job well for decades.

The Department of Labor eventually stopped maintaining the DOT and shifted its occupational-classification investment into a different framework: ONET (the Occupational Information Network), designed to describe work in terms of skills, tasks, and abilities rather than fixed physical-demand codes — a better fit for a service- and knowledge-heavy economy. That transition is a matter of public DOL and ONET program history; if you need the precise sunset date for citation purposes, confirm it against DOL's own archival documentation rather than relying on secondhand summaries, since sources vary in how they characterize the exact cutoff year.

The practical result: the DOT is not being revised, expanded, or corrected. Every code in it describes a job as it existed when the entry was last touched — decades ago for most listings.

Where the DOT Still Shows Up in Practice Today

If the DOT is frozen, why does it keep appearing in current case files? Three reasons drive most of the persistence.

Legal and administrative infrastructure was built around it. Disability-determination frameworks, including Social Security's sequential evaluation process and its medical-vocational grid rules, were written with DOT-style job classifications — exertional level, SVP, transferability language — baked into the regulatory text and decades of case law. Rewriting that infrastructure around a different classification system is a much bigger undertaking than swapping a reference book, so the DOT's vocabulary persists in the rules themselves even though the underlying data source is no longer maintained. The DOT continues to be cited in Social Security disability proceedings on this basis; the exact scope and frequency of that citation in current hearing practice is worth confirming directly against current SSA guidance rather than assumed from older secondary sources.

Workers' compensation systems vary by state and often still reference DOT-style demand levels in their own statutes and forms, independent of what SSA does. This is jurisdiction-specific — never assume one state's reliance on DOT terminology applies to another, and confirm current requirements with the relevant workers' compensation board before citing DOT language in a report headed to that jurisdiction.

Forensic continuity matters. A vocational expert testifying about a job that existed and was classified a particular way years ago may need the DOT specifically because that was the classification in effect when the relevant work occurred — not because it's the best available description of that occupation today.

None of this makes the DOT current. It makes the DOT durable in specific procedural corners even as it becomes less useful as a description of today's labor market.

O*NET: The Intended Successor, and What It Actually Covers

ONET is where the Department of Labor's ongoing classification investment actually lives now. The database currently spans 900 occupation profiles covering more than 55,000 jobs, built and refreshed on an ongoing basis rather than frozen at a single point in time — a structural advantage the DOT can no longer offer, simply because someone is still updating it. (Content includes information from ONET, used under CC BY 4.0; ONET is a trademark of USDOL/ETA.)*

Where the DOT described a job primarily through physical demand and duty narrative, O*NET describes it through skills, abilities, work activities, and — critically for wage work — a direct link to the Standard Occupational Classification (SOC) system, which in turn connects to Bureau of Labor Statistics wage and employment data. That link is what makes a wage-earning-capacity estimate possible from a current occupation description rather than a decades-old one. If you're new to searching the database itself, O*NET Online's occupation search is the practical starting point most practitioners use day to day.

The DOT-to-O*NET/SOC Crosswalk: How Practitioners Bridge the Gap

Neither source alone answers every question a transferable skills analysis or a labor market survey requires. The DOT still carries granular, job-specific physical-demand and duty detail that ONET's broader occupational categories sometimes flatten out. ONET carries the current skills framework and the direct SOC/wage-data connection the DOT can't provide. So practitioners cross-reference: identify the DOT code that matches historical or exertional-classification needs, then cross-walk it to the corresponding O*NET-SOC occupation to pull current skill, task, and wage context.

That crosswalk isn't intuitive to build from scratch — DOT's nine-digit codes and ONET-SOC's alphanumeric codes don't map one-to-one, and a single DOT title sometimes spans or splits across multiple ONET-SOC entries. The mechanics of building that bridge, including where the mapping is clean and where it requires judgment calls, are covered in more depth in how the O*NET-DOT crosswalk works and in a DOT-to-O*NET/SOC crosswalk walkthrough. If you're working from a specific DOT code and need to identify candidates fast, a DOT occupation codes list is the faster reference point than paging through the full dictionary.

What This Means for a Defensible Transferable Skills Analysis

For a report that has to hold up to cross-examination or carrier scrutiny, the discipline is the same regardless of which source you cite: document which source produced which data point, and don't blend DOT-era physical-demand language with O*NET-era skills language without making the crosswalk explicit on the page. A reviewer — opposing counsel, a claims examiner, an administrative law judge — should be able to see exactly why a given occupation was classified the way it was and which source that classification came from.

This is where a structured crosswalk reference earns its place in a firm's standard workflow rather than being reconstructed case by case. Our O*NET/DOT Occupation Crosswalk Reference Workbook gives counselors a working reference for moving between DOT codes and their O*NET-SOC counterparts without rebuilding the mapping from scratch on every file — the kind of estimating and organizing aid meant to support a credentialed practitioner's own analysis and judgment, not substitute for it.

Choosing the Right Source for the Right Task

The short answer to whether the Dictionary of Occupational Titles is still used: yes, in specific procedural and jurisdictional contexts, and no, as a current description of the labor market. Treat it as a historical and regulatory-vocabulary reference, not a live data source, and lean on O*NET — cross-walked deliberately — for anything that needs to reflect today's job requirements or wages. And because workers' comp statutes and SSA procedure both vary by jurisdiction and change over time, confirm current requirements with the relevant board or agency before finalizing which source a given report leans on.

For a broader walkthrough of how transferable skills analysis draws on both sources in practice, see the transferable skills analysis resource hub. And if you want the crosswalk itself sitting in your reference stack rather than rebuilt from memory, download the workbook above.