By Rovaryn Digital · May 24, 2026 · 7 min read
The Spreadsheet That Fell Apart on Cross-Examination
A vocational counselor built a wage comparison in a spreadsheet three years ago and has been copying the same tabs into every new case since. It works — until opposing counsel asks where the post-injury wage figure came from, and the counselor has to reconstruct, from memory, which OES release year a cell was pulled from and whether it was updated when BLS refreshed the data. The number in the report is right. The paper trail behind it is not. That gap is what turns a routine wage-earning-capacity calculation into an afternoon of hostile questioning — and it's exactly what a purpose-built calculator is supposed to prevent. By the end of this piece, you'll know what a defensible wage-earning-capacity calculator actually needs to hold up: which cells require a citation, how pre-injury and post-injury comparisons should be structured, and where to draw the line between what a tool computes and what a credentialed practitioner signs.
What a Wage-Earning-Capacity Calculator Actually Computes
A wage-earning-capacity calculator is not a black box that produces a settlement number. It's an organizing structure for a comparison that already exists in workers' comp, LTD, and personal-injury practice: what did this worker earn before the injury, and what can they reasonably earn now, given their residual capacity and the labor market available to them. The calculator's job is to hold both sides of that comparison — inputs the practitioner supplies, wage data the practitioner sources — and compute the resulting gap consistently, case after case, without re-deriving the arithmetic by hand each time.
That distinction matters because it sets the boundary of what the tool can claim. The calculator computes from the practitioner's own inputs. It does not determine capacity, does not select the comparison occupations, and does not decide whether a result is admissible in a given jurisdiction. Those are judgment calls that belong to the certified counselor or vocational expert whose name goes on the report. If you want the underlying concept explained before you build or buy a tool, wage-earning capacity as a concept is worth reading first — the calculator only works if the person using it understands what the number represents.
The Wage Cells: Where Sourcing Breaks Down
Every wage-earning-capacity calculator has, at minimum, two wage cells: a pre-injury wage and a post-injury (or residual) wage. In practice, most calculations need several post-injury wage cells, one for each occupation identified as suitable given the worker's residual physical and vocational capacity. This is where most homegrown spreadsheets quietly become indefensible: the pre-injury wage usually traces cleanly to payroll records or a wage statement, but the post-injury wage cells are often pulled from a labor market survey or a BLS Occupational Employment and Wage Statistics (OEWS) query done months earlier, then hand-copied into the workbook with no record of the release date, the geographic area, or the percentile used.
A defensible calculator treats each post-injury wage cell as a citation, not just a number. At minimum that means recording the SOC code, the geographic area (national, state, or metro), the OEWS release date, and the wage percentile selected (median is common, but not universal). OEWS estimates themselves are built from a large sample — BLS constructs the survey from a probability sample of about 1.1 million establishments, sampled in semiannual panels of roughly 186,000 to 189,000 each — which is part of why the data is trusted as a citation source in the first place, but the trust doesn't transfer if the calculator loses track of which release the number came from. For a deeper walkthrough of pulling the right cell by SOC code, see how to work with BLS OEWS wage data by SOC code.
Pre-Injury vs. Post-Injury: Structuring the Comparison
Once the wage cells are sourced, the comparison itself is straightforward arithmetic — but the structure around it is what makes the output usable in a report. A clean pre-injury vs. post-injury comparison typically lays out:
- The pre-injury wage, with its source (payroll record, wage statement, or prior earnings history) and the period it covers.
- Each candidate post-injury occupation, identified by SOC code and title, with its sourced wage cell.
- The resulting wage gap, expressed both as a dollar figure and as a percentage of the pre-injury wage.
- A note on which occupations were included or excluded, and why — this is where the practitioner's transferable-skills judgment enters the calculation, not the tool's.
Worked as a simple example: a pre-injury wage of $52,000 a year compared against a sourced post-injury median of $39,000 for the best-matching occupation produces a $13,000 gap, or roughly a 25% wage loss. That's a worked illustration to show the mechanics, not a claim about any real case — the actual inputs, occupation selection, and percentage-loss threshold that matters in a given filing depend entirely on the jurisdiction and the facts of the case. For a fuller treatment of building this comparison correctly, pre-injury vs. post-injury wage comparison methodology walks through common mistakes, including comparing against occupations the worker isn't actually qualified for.
From Wage Gap to Percentage Loss — and Why Jurisdiction Changes the Math That Follows
A calculator can compute a wage gap and a percentage-loss figure reliably. What happens to that percentage next — whether it maps to a specific disability rating, a benefit duration, or a voucher amount — is governed entirely by the jurisdiction, and generalizing across states or provinces is one of the fastest ways to produce an unreliable report. In California workers' compensation, for example, injured workers who cannot return to long-term work due to permanent disability may qualify for the Supplemental Job Displacement Benefit, a $6,000 voucher for education and retraining — a figure specific to California and not representative of any other state's scheme. A calculator's job is to get the wage-loss percentage right and sourced; what a practitioner or claims examiner does with that percentage afterward depends on rules that a wage-earning-capacity tool should never hardcode.
This is also where the stakes of getting the calculation right connect to the broader disability employment picture the counselor is working within. In 2024, the employment-population ratio was 22.7% among people with a disability compared with 65.5% among those without — a gap that underscores why an accurate residual-capacity wage figure, not just a defensible-looking one, matters to the worker on the other end of the report. Confirm the current voucher amounts, percentage-loss thresholds, and formula requirements with the relevant workers' comp board before finalizing any report — those specifics change by jurisdiction and by year, and a calculator that hardcodes last year's rule is worse than no calculator at all.
If you want the general mechanics of turning a wage gap into a wage-loss claim laid out end to end, wage loss calculation for workers' comp covers the full sequence from wage gap to claim documentation.
Building One vs. Using One That's Already Sourced
Practices weighing whether to build their own wage-earning-capacity calculator in a spreadsheet or adopt one already built face a real tradeoff. A spreadsheet is flexible and free to start, but every wage cell's sourcing lives in someone's memory or a scattered set of saved PDFs, and it doesn't scale past a handful of counselors without someone eventually losing track of a citation. A structured calculator — whether a standalone workbook or a module inside broader case-management software — bakes the citation fields into the input process itself, so a wage cell can't be entered without a SOC code, source, and date attached.
For practices not ready to move off spreadsheets entirely, a structured starting point is often the more practical first step than building the sourcing discipline from scratch. The Wage-Earning-Capacity Calculator Workbook gives you that structure — sourced wage-cell fields, a built-in pre-injury/post-injury comparison layout, and a percentage-loss output — without requiring a full platform switch.
If your caseload has outgrown a workbook, or you're already juggling wage comparisons across a dozen open files alongside deadline tracking and billing, it may be worth seeing how the calculation fits into a full practice workflow rather than a standalone tool. See a demo of how sourced wage data, scenario comparison, and report drafting work together in one system, built for practices that bill against fee schedules rather than run analytics as a side project.