Documenting Vocational Expert Report Methodology

The deposition question that ends careers before it ends cases

"Walk me through exactly how you got from this file to that number." It sounds like a simple request. For a vocational expert who kept the analysis in their head — a spreadsheet here, a mental note about which O*NET codes felt right, a wage figure pulled from a survey they don't remember running — it's the question that unravels the opinion in real time. Opposing counsel doesn't need to prove the conclusion is wrong. They only need to show the path to it can't be retraced.

Methodology documentation is the difference between an opinion a court can weigh and a guess dressed up in professional language. It's not a formality added after the analysis is done — it's the record of the analysis itself, written contemporaneously enough that a stranger could follow the same steps and land on the same range of outcomes.

This piece walks through what belongs in that record: the data-source trail, the transferable skills analysis steps, the wage math, and the version history that lets you answer "walk me through it" without hesitation. By the end, you'll have a concrete structure for documenting vocational expert report methodology that holds up whether the file sits untouched for eighteen months or goes straight to cross-examination.

What "methodology" actually covers in a vocational expert report

Methodology isn't a single paragraph near the top of the report that cites a professional framework and moves on. It's the cumulative, step-by-step account of every decision that turned raw case facts into a stated opinion. For a forensic vocational expert witness, that typically spans four layers:

• Data intake — what records, depositions, medical opinions, and self-reported history the expert relied on, and what was excluded and why.
• Occupational classification — how job titles, prior work, and residual capacity were mapped to standardized occupational codes.
• Analytic method — the transferable skills analysis (TSA) and/or labor market survey structure applied, including the assumptions built into each.
• Quantification — how wage-earning capacity, labor market access, or vocational disadvantage was calculated from the classification and analytic layers.

No single body sets one fixed methodology standard that every court and jurisdiction applies identically. Some jurisdictions evaluate expert methodology under a Daubert-style reliability framework; others use Frye or a state-specific variant; administrative bodies (workers' comp boards, SSA hearings) often apply their own evidentiary rules entirely. Treat the standard as jurisdiction-specific and confirm the applicable rule with retaining counsel before the report is finalized — never assume the framework that applied in your last case applies in this one. That variability is itself part of why the underlying methodology record has to be strong regardless of which legal test eventually gets applied to it; a Daubert challenge targets the reasoning, not the label you gave it.

Building the data-source trail

Every figure and classification in the report should trace back to a named, dated source. That means logging, at minimum:

• The exact edition or version of the classification system used (O*NET version and release date; DOT if still referenced for legacy comparison).
• The wage survey source and its collection window — a wage figure pulled from a survey with a defined sampling methodology and a stated collection period is a materially different data point than one pulled from an undated listing.
• Which records were reviewed, in what order, and what was still outstanding when the opinion was formed (a gap that later gets filled should trigger a documented addendum, not a silent revision).

ONET itself is a large, versioned system — it currently covers around 900 occupation profiles spanning more than 55,000 job titles — so "I used ONET" is not a methodology statement; "I mapped the claimant's DOT title to O*NET-SOC 43-9199.00 using the [specific] crosswalk, version [x]" is. The same discipline applies to wage data: BLS Occupational Employment and Wage Statistics estimates are built from a probability sample of roughly 1.1 million establishments surveyed in semiannual panels, which is exactly the kind of sampling detail that gives a wage figure its evidentiary weight — and exactly the detail that disappears if you cite "BLS data" without the release date and geographic level you actually pulled.

Documenting the transferable skills analysis step by step

A TSA is where methodology documentation earns or loses its credibility fastest, because it involves professional judgment layered onto data, not just data retrieval. Document each stage separately:

1. Skills identification — the specific skills, tools, and worker functions abstracted from the claimant's past relevant work, tied to the source job description or deposition testimony that supports each one.
2. Residual capacity match — how each identified skill was tested against the claimant's documented physical, cognitive, or vocational restrictions, and which restriction source (IME, treating physician, functional capacity evaluation) governed each judgment call.
3. Crosswalk to candidate occupations — the specific O*NET-SOC codes considered, and — this is the step most often skipped — the codes considered and rejected, with the reason for rejection noted. A defensible TSA shows its negative space, not just its conclusions.
4. Labor market filter — how geography, wage floor, and any other constraint narrowed the candidate list to the occupations named in the final opinion.

Writing this level of detail feels slow the first several times. It stops feeling slow once it's the reason a report survives a motion to exclude instead of becoming one. For a full walkthrough of assembling this into a finished, reader-usable report structure, see how to write a defensible vocational report.

Wage-earning-capacity math: showing the work, not just the number

Wage-earning-capacity analysis compares pre-injury and post-injury earning potential — but "compares" has to mean something specific and checkable on paper. A worked example, using round figures purely to illustrate the mechanics:

• Pre-injury wage anchor: the claimant's documented pre-injury occupation carried a wage of, say, $52,000/year, sourced to a specific wage table entry, not a memory of "what that job usually pays."
• Post-injury candidate set: the TSA identifies three residual-capacity-appropriate occupations, each with its own sourced wage figure — for example $34,000, $38,500, and $41,000 — pulled from the same wage data vintage and geographic level as the pre-injury figure, so the comparison isn't mixing a national average against a local one.
• Resulting band: the wage-earning-capacity loss is expressed as a range across the candidate set, not a single point estimate manufactured by averaging occupations that don't actually resemble each other.

The documentation obligation here is to show which wage source, which geographic level, and which collection period anchor each number in the comparison — and to flag plainly wherever a figure had to be adjusted, interpolated, or estimated rather than pulled directly from a published table. An unlabeled adjustment is the single easiest thing for opposing counsel to turn into a credibility problem on cross-examination. If the wage-earning-capacity opinion also drew on a labor market survey rather than published wage tables alone, the survey's own construction — sample size, employer contact method, response rate — needs the same transparency; see labor market survey methodology for how to document that layer specifically.

The report that survives cross-examination isn't the one with the most confident conclusion. It's the one where every step between the file and the conclusion was written down before anyone asked to see it.

Version control and report reproducibility

Methodology documentation isn't finished when the report is signed — it has to survive the gap between signing and testimony, which can run months or years. That means:

• Locking the data vintage. Note the exact date each wage table, O*NET release, or survey dataset was pulled. If the underlying source updates before trial, the report should say plainly which vintage it relied on rather than leaving the question open to interpretation later.
• Logging revisions with reasons. If a restriction changes, a new record arrives, or a calculation is corrected, the addendum should state what changed, why, and what in the original opinion it affects — not just replace the number silently.
• Preserving the working file, not just the final PDF. The spreadsheet or software output that generated the wage bands and TSA candidate list should be retrievable in the same form it existed in when the opinion was formed. A number that can't be regenerated from its working file is a number that can't be defended when someone asks you to regenerate it.

None of this turns a report into something admissible or compliant by itself — that determination belongs to the court applying its own jurisdiction's standard, and to the credentialed expert's judgment and signature. What structured methodology documentation does is give that judgment a transparent, reproducible record to stand on, which is the most a report can do in its own defense before anyone starts asking questions about it under oath.

Put the structure in place before you need it

Rebuilding a methodology trail after a deposition notice arrives is the wrong time to start — the file should already show its own reasoning. The Forensic Vocational Report Defensibility & Cross-Exam Prep Pack gives you a template structure for documenting data sources, TSA steps, and wage-earning-capacity math in a format built to hold up under exactly this kind of scrutiny. Download the template pack and build the habit into your next report before it's tested in a deposition room.