SVP: Specific Vocational Preparation Levels Explained

When the wrong SVP number gets read into the record

A vocational expert is on the stand at an SSDI hearing. Opposing counsel asks her to explain why the labor market survey lists a machine-tender occupation as "unskilled" when its DOT entry carries an SVP of 3. She hesitates — the report was built from a spreadsheet lookup that treated "low skill" and "SVP 2 or below" as interchangeable. They are not. The hesitation costs her credibility for the rest of the testimony, and the claimant's counsel notices.

This is a small classification error with an outsized consequence, and it happens because SVP looks simpler than it is: a single-digit number bolted onto a DOT code, easy to glance at and easy to misread. By the end of this article you'll be able to state exactly what SVP measures, walk through all nine levels without hedging, and correctly use SVP — distinct from skill level and distinct from exertion — to filter occupations in a defensible transferable skills analysis.

What SVP actually measures (and what it doesn't)

Specific Vocational Preparation is a classification the U.S. Department of Labor built into the Dictionary of Occupational Titles to capture one specific variable: how much time a typical worker needs to reach average performance in a given occupation. The DOT's own Appendix C frames SVP as the amount of lapsed time required to learn the techniques, acquire the information, and develop the facility needed for average performance in a specific job-worker situation.

That framing matters because of what it excludes. SVP is not a measure of physical demand — that's exertion level, tracked separately. It is not a measure of intelligence, aptitude, or general educational development, which the DOT tracks under its own GED scale. And it is not identical to "skill level," a related but distinct three-bucket classification (unskilled, semiskilled, skilled) used heavily in disability adjudication. SVP is preparation time, full stop — training, vocational education, apprenticeship, in-plant experience, essential on-the-job learning, and the time spent in a like occupation, all added together.

The nine SVP levels, defined

The DOT scale runs from 1 to 9, each level a band of lapsed time:

• SVP 1 — short demonstration only
• SVP 2 — anything beyond short demonstration up to and including 1 month
• SVP 3 — over 1 month up to and including 3 months
• SVP 4 — over 3 months up to and including 6 months
• SVP 5 — over 6 months up to and including 1 year
• SVP 6 — over 1 year up to and including 2 years
• SVP 7 — over 2 years up to and including 4 years
• SVP 8 — over 4 years up to and including 10 years
• SVP 9 — over 10 years

Every DOT occupation code carries one of these nine values as part of its occupational definition. It is worth saying plainly that the DOT itself was last revised in 1991 and is no longer maintained as a live database — practitioners now typically cross-reference SVP against the Occupational Information Network (O*NET) crosswalk rather than a printed DOT volume, a topic covered in depth in our O*NET-DOT crosswalk explainer. The SVP values themselves, however, remain the reference point most fee schedules, disability examiners, and vocational experts still cite.

SVP vs. skill level: why the distinction matters in disability claims

This is where the courtroom example above goes wrong most often. Social Security disability adjudication groups occupations into three skill-level buckets, and those buckets are built directly on SVP ranges: unskilled work generally corresponds to SVP 1–2, semiskilled to SVP 3–4, and skilled work to SVP 5 and above. Because this mapping does real work in a disability decision — it affects whether a claimant's past relevant work counts as unskilled and whether alternative occupations are within reach — a report that states a skill-level conclusion needs to show the SVP number underneath it, not the other way around.

Practitioners should treat the SVP-to-skill-level mapping as adjudicative guidance rather than a fixed constant baked into the DOT itself, and confirm the current thresholds directly with the Social Security Administration before relying on them in a report, since agency guidance can be revised. The SVP number is a DOT classification; the unskilled/semiskilled/skilled label is a policy overlay applied on top of it.

SVP measures how long it takes to learn a job. Skill level is a policy bucket built from that number. Confusing the two — or worse, using them interchangeably in a report — is one of the fastest ways to lose credibility under cross-examination.

Where SVP fits in a DOT-to-O*NET crosswalk

Because the DOT is frozen and ONET is the live successor database, most current transferable skills analysis work runs through a crosswalk between the two systems. ONET does not publish SVP directly; instead it uses Job Zones, a five-tier scheme correlated to — but not identical to — SVP and GED. The O*NET database itself spans roughly 900 occupation profiles covering more than 55,000 jobs, a far coarser occupational grain than the DOT's tens of thousands of six-digit codes, which is exactly why crosswalk work requires care rather than a simple lookup table.

(Includes information from ONET, used under CC BY 4.0; ONET is a trademark of USDOL/ETA.)

When a practitioner needs the specific SVP value for a legacy DOT code — the number a fee schedule, a state agency, or an ALJ actually expects to see cited — pulling it straight from the DOT occupation codes list rather than approximating it from an O*NET Job Zone keeps the report anchored to the classification the record is asking about. Our O*NET-DOT crosswalk explainer walks through that mapping step by step.

Using SVP to filter occupations in a transferable skills analysis

Inside a transferable skills analysis, SVP does one specific job: it caps the universe of occupations a client can realistically be found capable of performing, given how much of their prior preparation time is transferable. A claimant whose only work history sits at SVP 6 has accumulated skills that took one to two years to build; a TSA that surfaces SVP 8 occupations as "transferable" without a bridge explanation for the gap is inviting exactly the kind of cross-examination moment described at the top of this article.

In practice, SVP is one filter among several — alongside exertion level and the transferability of the underlying skills themselves — that narrows a full occupational universe down to a defensible candidate list. Our guide on exertion, SVP, and skill-level occupation filtering covers how these three variables interact, and the foundational transferable skills analysis explainer covers where SVP fits in the broader TSA methodology. For the step-by-step mechanics of building the analysis itself, see how to perform a transferable skills analysis.

Common SVP mistakes that undermine a report

A few errors recur often enough to name directly:

• Treating SVP and skill level as synonyms. They're related, not identical — always show the SVP number, not just the bucket label.
• Pulling SVP from a stale or mismatched source. A crosswalk error between a DOT code and an O*NET Job Zone can silently shift the reported preparation time.
• Ignoring accumulated SVP from combined work history. SVP attaches to a single occupation's learning curve; a claimant's transferable skill set may draw on preparation time from more than one prior job, and the analysis should say so explicitly rather than defaulting to the highest single SVP on record.
• Failing to state the source. A report that cites an SVP level without naming where it came from — the DOT itself, a specific crosswalk, a specific edition — is harder to defend when challenged.

Building an SVP-literate TSA workflow

None of this requires memorizing nine time bands under pressure. What it requires is a workflow that pulls the SVP value from a defensible source every time, applies it consistently against exertion and skill-level filters, and documents where that number came from in the finished report — the same discipline that governs the DOT-to-O*NET crosswalk work covered in our resource hub.

If your current process still involves cross-referencing a printed DOT appendix against a separate O*NET lookup by hand, the TSA Worksheet Pack gives you a structured, pre-built worksheet for capturing SVP, exertion, and skill-level filters in one pass, so the number that ends up in the report is the same number you can point to under questioning.

Download the TSA Worksheet Pack and standardize how your practice documents SVP on every transferable skills analysis.