A Defensible Labor Market Survey Methodology

The Cross-Examination That Started With a Missing Date

The report looked fine on paper. Six employers, six job openings consistent with the claimant's transferable skills, wages that lined up with the vocational expert's earning-capacity opinion. Then opposing counsel asked a simple question: "What date did you contact Employer 3?" The counselor's file had a name and a phone number. It did not have a date, a time, or a note on what was actually said. One missing field, and the entire survey's credibility came under question — not because the underlying labor market conclusion was wrong, but because nothing in the file let anyone check it.

That scenario repeats across deposition rooms and hearing offices in every jurisdiction that permits vocational testimony. The survey itself is rarely the problem. The documentation trail behind it is. A labor market survey methodology earns the word "defensible" not by using better judgment than the next expert, but by leaving a record precise enough that another qualified evaluator — or a skeptical attorney — could retrace every step and land in the same place.

By the end of this piece, you'll have a concrete framework for building that record into your labor market survey process from the first sampling decision through the final wage citation, so the next missing-date question never gets a shrug for an answer.

What "Defensible" Actually Means in a Labor Market Survey

"Defensible" gets used loosely in vocational rehabilitation, often as a synonym for "well-written." It means something narrower and more useful: a methodology is defensible when its parameters were set before the search began, applied consistently, and documented well enough that someone other than the author could reproduce the same universe of jobs from the same file.

That definition deliberately avoids court-specific language. Admissibility standards for expert testimony vary by jurisdiction — some follow a Daubert-style reliability inquiry, others a Frye-style general-acceptance test, and many have their own statutory or administrative variants for workers' compensation, Social Security, or long-term disability proceedings. Which standard applies, and what it requires, is a legal question for the attorney of record and the forum's own rules — not something a methodology write-up should presume to answer, and not something any software can certify on your behalf. What a sound labor market survey methodology can do is give whichever standard applies something solid to test.

In practice, defensibility rests on four things happening in a specific order and staying on the record:

• The search parameters (geography, occupational codes, wage range, date window) were fixed before contacts began, not adjusted after seeing results.
• The sampling approach was applied evenly across all candidate employers, not selectively to favor a conclusion.
• Every contact attempt — successful or not — was logged with enough detail to reconstruct it.
• The wage and job-availability data cited trace to a named, checkable source.

Each of those is a discipline problem before it's a writing problem. Get the underlying labor market survey process right, and the report write-up mostly narrates decisions that were already made on the record.

Building a Reproducible Sampling Frame

A sampling frame is the boundary you draw before you start calling employers: which occupational titles qualify, what geographic radius counts as the relevant labor market, and what date range the postings or contacts must fall within. Set it after you've already seen a few promising job orders, and you've built the frame around the conclusion rather than the other way around — the single most common vulnerability in a challenged survey.

Occupational identification usually starts from a DOT-to-ONET/SOC crosswalk tied to the claimant's transferable skills analysis. The ONET database itself covers 900 occupation profiles and more than 55,000 constituent jobs, which gives most evaluators a wide enough net to find several viable SOC codes rather than forcing a single title. Document which codes you used and why — restrictions ruled out, physical demand levels considered, skill-transfer logic applied — before a single employer contact is made.

Geography deserves the same up-front discipline. "Reasonable commuting distance" is not a fixed number; it depends on the claimant's location, transportation access, and local labor market norms, and different fora weigh it differently. Pick a radius, write down the reasoning, and hold it constant across every occupation surveyed in that report. If a later step forces a deviation — say, a specialized occupation with no local employers — note the deviation and the reason at the time, not after the fact when someone asks about it. For a fuller walkthrough of frame construction step by step, see how to conduct a labor market survey.

Documenting Employer Contacts as They Happen

This is where most surveys lose defensibility, and it's almost always a discipline failure rather than a knowledge failure. Every evaluator knows they should log employer contacts. Fewer actually log them in the moment, with enough granularity to survive a cross-examination question asked eighteen months later.

A usable employer contact log needs, at minimum: the employer name, contact name and title, date and time of contact, method (phone, email, in-person, job posting review), the specific question asked, the response received verbatim or closely paraphrased, and whether the position was open, the wage offered or range, and any qualifying requirements mentioned. Missing any one of those fields turns a contact from evidence into an assertion.

If another expert can't reproduce your survey from your file, it isn't a methodology — it's an opinion with extra steps.

The failure mode isn't usually dishonesty. It's sequencing — the counselor makes six calls in an afternoon, writes the report from memory two weeks later, and reconstructs details that felt obvious at the time but aren't verifiable now. Building the log at the moment of contact, not after, is the single highest-leverage habit in this entire methodology. A structured employer contact log format — the same fields, the same order, every time — makes that habit close to automatic instead of something you have to remember to do under deadline pressure.

Wage Data: Anchoring Estimates to a Named Source

A labor market survey that reports wages without naming where they came from invites exactly the follow-up question that sank the opening scenario. Every wage figure in the report should trace to one of two places: a direct employer statement, logged with the contact detail above, or a published labor statistics source, cited by name and vintage.

For published data, the BLS Occupational Employment and Wage Statistics program is the standard reference most evaluators lean on for wage bands by occupation and area. It's worth understanding, and disclosing, what that data actually represents: OEWS estimates are built from a probability sample of roughly 1.1 million establishments, drawn in semiannual panels of about 186,000 to 189,000 each. That's a real, well-documented sampling methodology behind the number — which is exactly why citing "BLS OES" with a date and geographic level is more defensible than citing a remembered wage figure with no source at all. When employer-reported wages and published statistics diverge, note the divergence and explain which one anchors your opinion and why, rather than picking silently.

Whichever source you cite, keep the citation specific: program name, geographic area, occupational code, and publication date. "According to BLS OEWS data" is weaker than "According to BLS OEWS, May 2024, [area], SOC [code]." The second version is the one that survives a follow-up question about currency or geographic fit.

Where Labor Market Surveys Fall Apart Under Cross-Examination

Across depositions and hearings, the same handful of gaps recur:

• Undated or backfilled contact logs — the scenario that opened this piece.
• Shifting sampling criteria mid-survey — expanding the radius or relaxing wage thresholds once early results look thin, without documenting the change.
• Uncited wage figures — a number in the report with no traceable source, employer or published.
• Inconsistent occupational logic — SOC codes chosen that don't clearly map back to the transferable skills analysis or the physical/vocational restrictions on record.
• No reproducibility trail — a report that reads well but couldn't be rebuilt by a second evaluator working from the same file.

None of these require bad faith to produce. They're what happens when a sound methodology exists in an evaluator's head but not in the file. The fix is the same one that runs through every section above: write the parameters down before you search, log contacts as they happen, cite sources by name, and keep the whole record in one place so it can be handed over, intact, whenever it's asked for.

A full vocational expert report methodology — the write-up that sits on top of the survey itself — inherits its credibility from exactly this groundwork. And because the survey is only one piece of what a forensic vocational expert witness is asked to defend, the same documentation discipline should extend to the transferable skills analysis and wage-earning-capacity opinion that sit alongside it in the file.

If you want the underlying structure — sampling frame worksheet, employer contact log template, and wage-citation checklist — in a ready-to-use format rather than building it from scratch, the Forensic Vocational Report Defensibility & Cross-Exam Prep Pack packages these into templates built for exactly this kind of scrutiny. It won't make a survey admissible on its own — that determination belongs to the forum and the attorney of record — but it will make the file behind it much harder to pick apart one missing date at a time.