By Rovaryn Digital · July 6, 2026 · 8 min read
The report doesn't defend itself
Opposing counsel is holding your report. She flips to page four, taps the labor market survey table, and asks: "How many of these employers did you speak with personally?" It's a fair question, and if your file doesn't have a clean answer sitting three seconds away, the pause before you find it is the testimony. Cross-examination doesn't usually attack your conclusion head-on. It attacks the joints — the places where a number, a source, or a judgment call connects to the next one. If any joint is loose, that's where the questioning goes.
This is the gap between writing a report and defending one. A well-organized file can still fall apart on the stand if the expert hasn't rehearsed the specific sequence of questions designed to expose an unsupported step. Vocational expert cross-examination is not a test of your overall competence — it's a test of whether you can trace, out loud and under time pressure, exactly how you got from the claimant's file to the number in your conclusion.
By the end of this piece, you'll have a working framework for anticipating the three places cross-examination attacks a vocational opinion, and a way to rehearse your defense before you're the one in the chair.
Where cross-examination actually attacks: data, method, reasoning
Effective cross-examination of a vocational expert almost always targets one of three layers, and knowing which layer a question is aimed at helps you answer at the right level of detail instead of over- or under-explaining.
Data. Where did the wage figure, the job count, or the transferable-skills list come from? Was the source current at the time of the opinion? Did you rely on a single source or triangulate? This is the layer where questions about OEWS wage percentiles, O*NET occupation codes, or employer-contact logs live.
Method. How did you get from raw data to a conclusion? What transferable skills analysis process did you follow? Why this occupational crosswalk and not another? Why five comparable jobs surveyed instead of fifteen? This is the layer a Daubert-style challenge is built to probe — not "is the number right" but "is the process that produced the number sound and repeatable."
Reasoning. Why did you weight vocational factors the way you did? Why did you conclude the claimant could perform sedentary work rather than light work? This is the most personal layer, and the hardest to script, because it's where your professional judgment — not a database — is doing the work.
Most experts over-prepare for reasoning questions and under-prepare for data and method questions, because reasoning feels like the "real" opinion. But data and method are where cross-examination does the most damage, because they're checkable in real time against your own file.
Building a record that survives scrutiny before you're ever deposed
The best cross-examination preparation happens months before the deposition, at the point the report is drafted. If your report methodology is documented as you go — which source you pulled each wage figure from, which O*NET occupation codes you crosswalked from the claimant's DOT-coded work history, why you selected a given radius or sample size for a labor market survey — you're not reconstructing your reasoning under pressure later. You're reading it back.
A defensible labor market survey keeps a record of every employer contacted, every job order or posting reviewed, the date of contact, and the outcome — not just the jobs that supported your conclusion. Opposing counsel's favorite question is some version of "did you exclude any employers that didn't fit?" If the honest answer is no, and you can show the full contact log to prove it, that's a five-second answer instead of a credibility problem.
The same discipline applies to wage-earning-capacity math. The Occupational Employment and Wage Statistics program that underlies most wage benchmarking is built from a large, standardized federal sample — a detail worth knowing not because you'll recite it verbatim on the stand, but because you should be able to say, plainly, that your wage figures came from a nationally recognized government survey rather than an ad hoc estimate, and point to exactly which release and occupation code you used. Vague sourcing invites the next question. Specific sourcing usually ends the line of inquiry.
Anticipating the standard attack lines
Certain cross-examination sequences recur often enough across jurisdictions and case types that you can rehearse them almost verbatim, adjusting only for the facts of the case.
"You didn't consider X." The fix isn't defensiveness — it's documentation. If your file shows you considered a factor and had a reasoned basis for weighting or excluding it, say so plainly. If you genuinely didn't consider it, say that too, and explain whether it would change the opinion. Experts lose credibility by overclaiming completeness, not by acknowledging limits.
"Your survey only found five jobs." This is a sample-size challenge aimed at the method layer. The defense is explaining your selection criteria — geographic radius, SOC code match, recency of postings — rather than the raw count. A small, well-justified sample survives; a large, poorly justified one doesn't.
"You're not a doctor / vocational counselor / labor economist." A scope-of-expertise challenge. The answer is precise: state exactly what you are credentialed to opine on (transferable skills, labor market access, wage-earning capacity) and what you relied on others' opinions for (medical restrictions, diagnosis). Blurring that line is where experts get into real trouble; drawing it cleanly is a strength, not an admission of weakness.
"Isn't this all just an estimate?" Yes — and saying so, calmly, is often the safest answer. A vocational opinion is a professional estimate built from a stated methodology applied to the available record, not a certified prediction of outcome. Overclaiming certainty is a bigger risk than acknowledging that reasonable experts working from the same file might reach adjacent conclusions.
"Have you testified for this attorney/carrier before?" A bias challenge. Have your case history — how many times you've testified for plaintiffs versus defendants, roughly, and any pattern in outcomes — ready before you're asked, not assembled on the stand.
The goal of cross-examination preparation isn't to have a clever answer for every question. It's to never be surprised by a question you should have already asked yourself.
Rehearsing the defense before you're in the chair
Reading your report the night before a deposition is not preparation — it's familiarization. Actual preparation means having someone else, ideally another vocational professional or the retaining attorney, cross-examine you using the attack lines above before the real thing happens. Two things happen in a mock cross-examination that never happen in a solo review: you discover which of your own explanations sound weaker out loud than they did on paper, and you discover which pieces of your file you can't find quickly.
If your file takes more than a few seconds to produce the source for any given number in your report, that's worth fixing before the deposition, not during it. This is less about memorizing figures and more about knowing exactly where each one lives in your own documentation — the specific survey page, the specific database export, the specific date you pulled a wage table — so a challenge to your data becomes a retrieval task, not a memory test.
Documentation habits that make cross-examination easier, not harder
A few habits consistently separate experts who handle vocational expert cross-examination comfortably from those who struggle:
- Version control on drafts. If your report went through revisions, know why each change was made and be able to explain it as normal professional refinement, not concealment.
- A visible chain from file to opinion. Every number in the conclusion should trace to a specific document, source, or calculation in the file — not to memory or a general sense of the labor market.
- Consistent terminology. If your report calls something a "transferable skills analysis" using O*NET and DOT crosswalks, use that same language in testimony rather than switching terms that sound like they describe a different, less rigorous process.
- A clear statement of limitations. Reports and testimony that acknowledge what the analysis does not cover — clinical diagnosis, legal conclusions, guaranteed job placement — read as more credible, not less, because they show the expert understands the boundary of the opinion.
None of this makes an opinion immune to challenge. No preparation does. What it does is make sure that when a challenge lands, it lands on the substance of a professional judgment call — the layer where your credentials and experience are the answer — rather than on a gap in your own file that had nothing to do with the merits.
Building your own cross-examination file
Every vocational expert eventually develops a personal system for organizing source documentation, survey logs, and methodology notes so they're retrievable under pressure. Building that system from scratch, case by case, is exactly the kind of task that eats hours you'd rather spend on analysis. A structured checklist — the kind that walks through data sourcing, method documentation, and anticipated attack lines before a deposition, rather than the night before — turns this from an ad hoc scramble into a repeatable part of case prep.
For more on the surrounding forensic role and process, see how a forensic vocational expert witness fits into a case team, how to prepare for vocational expert testimony more broadly, and what a Daubert-style challenge specifically targets. If you want the checklist version of everything above — a working document you can run through before your next deposition — the Forensic Vocational Report Defensibility & Cross-Exam Prep Pack is built for exactly that use.
Cross-examination will always test your reasoning in real time. The preparation happens long before you sit down.