How to Calculate Lost Wages for a Personal Injury Claim

Quick takeaways

Run this scenario in DocketMath using the tools directory.

• In a personal injury claim, lost wages typically track your net (take-home) earnings, but what counts as “lost” depends on your pay setup (hourly vs. salary), your pay cadence, and any benefits you received while out (like sick pay or short-term disability).
• To calculate lost wages defensibly, DocketMath starts with the exact dates you missed work, your usual earnings, and any income you actually received during the missed period.
• If you’re a W-2 employee, the most defensible baseline is usually your recent pay history (often the prior 4–13 weeks, or an average when pay varies).
• If you’re self-employed, use tax records and profit evidence—avoid guessing.
• DocketMath also helps account for offsets (wage-replacement amounts) and work resumption patterns (partial days, modified duty, reduced hours).

Inputs you need

Before you run lost-wage numbers in DocketMath, gather records that match how you were actually paid. The more your documents mirror your payroll reality, the more defensible your result.

Use this intake checklist as your baseline for N/A work in this jurisdiction.

• jurisdiction selection
• key dates and triggering events
• amounts or rates
• any caps or overrides

If any of these inputs are uncertain, document the assumption before you run the tool.

1) Work-loss timeline (the backbone)

Collect:

• Injury start date / disability start date (when your work capacity changed)
• First missed workday and last missed workday
• Days missed vs. partial days (e.g., “worked 3 hours instead of 8”)
• Any return-to-work dates, including:

  • light duty / restricted hours
  • intermittent absences
  • final workday before you changed jobs

Useful evidence examples:

• employer attendance records
• HR emails approving modified duty
• timecards
• calendars tied to medical restriction notes

2) Your normal earnings (how you were paid)

Pick the category that matches you.

Hourly (W-2 or 1099 equivalent):

• hourly rate(s)
• overtime rate(s), if applicable
• typical scheduled hours per week

Salary (W-2):

• annual salary
• how your employer converts salary to paychecks (weekly/biweekly)
• whether salary was reduced during the absence

Commission / bonus:

• typical commission range
• bonus schedule (quarterly/annual) and whether it was actually paid during the absence

Self-employed / contractor:

• tax returns (profit baseline)
• banking records showing deposits
• invoices and recurring contracts that were interrupted

3) Proof of paid earnings during the missed period

Gather what actually showed up in your bank and/or pay stubs:

• paychecks for any hours you worked while “out”
• employer-paid sick leave / PTO
• short-term disability or long-term disability payments
• unemployment benefits (if any)
• workers’ comp wage replacement (if applicable)
• Social Security disability payments (if applicable)

DocketMath can’t treat “someone might have paid you” as evidence—enter only amounts you can document.

4) Taxes vs. “gross” numbers (choose your baseline)

Lost wage presentations often use net wage loss (after applicable withholding), but the worksheet needs consistency:

• Do you want to compute gross wages missed, then convert to net using an agreed approach?
• Or do you want to rely on take-home pay evidence (pay stubs) directly?

Whatever method you choose, keep it consistent across the entire wage-loss window.

5) Offsets you plan to include

Offsets typically reduce wage-loss damages where the payment is meant to replace wages (depending on the payment source and jurisdictional rules). DocketMath’s wage replacement & offsets workflow helps you capture:

• PTO/sick time paid
• disability benefits
• other wage-replacement streams
• possible duplication concerns (different sources paying for the same time)

How the calculation works

DocketMath’s logic is essentially (missed work units × baseline earnings), then adjusting for offsets and any partial work time you document. The goal is to turn real-world absences into an evidence-backed model.

DocketMath applies the this jurisdiction rule set to the inputs, then runs the calculation in ordered steps. It validates the trigger date, applies rate or cap logic, and produces a breakdown you can audit. If you change any one variable, the tool recalculates the downstream outputs immediately.

Step 1: Break the wage-loss period into work units

Instead of a single lump sum, split the period by:

• missed full days
• partial days (e.g., 5 hours missed)
• weeks with variable schedules

Common unit choices:

• daily missed hours (hourly workers)
• missed salary equivalents (salary workers)
• weekly missed hours (when the schedule pattern is clear)

Step 2: Calculate baseline earnings for each unit

Hourly (illustrative):

• baseline hourly rate × missed hours
• if overtime is part of the typical schedule, apply the appropriate rate(s)

Salary (illustrative):

• annual salary ÷ typical workdays per year (or ÷ workweeks)
• multiply by missed days, or by missed workday equivalents

Commission/bonus (illustrative):

• use a documented average (e.g., last 6–12 months) if commissions fluctuate
• apply the average proportionally to the missed period

DocketMath lets you align baseline earnings with your pay-stub reality, including shifts/differentials/scheduled overtime when supported by records.

Step 3: Subtract documented wage-replacement amounts (offsets)

After calculating “earnings lost,” DocketMath subtracts amounts you entered that are wage-replacement in nature, based on your evidence.

Common offset categories:

• PTO/sick leave that replaced wages
• short-term disability payments
• long-term disability payments
• workers’ comp wage replacement (if relevant)

If you were paid for some workdays, those days should already reduce the missed unit count. Then enter offsets carefully to avoid double counting.

Common double-counting: both (a) reducing missed hours because you actually worked some hours and (b) subtracting a benefit that was triggered by that same worked time.

Step 4: Apply the timeline logic consistently

Real schedules change. Your calculation is more defensible when it reflects changes tied to dates:

• you may return for a week, then miss again due to flare-ups
• restrictions may shift from “no work” to limited hours
• pay structures may change (like a raise between injury and the missed period)

Step 5: Produce totals you can justify

Your outputs typically include:

• Gross wages lost (earnings based on missed time)
• Offset / replacement amounts
• Net wage loss after offsets
• optional breakdown by:

  • week or month
  • full vs. partial missed time

That structure matters in real claim documentation—adjusters often want proof the number came from dates and documents, not a guess.

Common pitfalls

These are the most common reasons wage calculations get challenged. DocketMath helps by structuring inputs, but you still need accurate records.

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

Pitfall checklist

• Using an hourly rate that doesn’t match the period you missed (e.g., an old rate)
• Treating salary as a fixed weekly amount when you were paid biweekly (or when pay deductions changed take-home pay)
• Listing missed work as an estimate (“about a week”) instead of the actual dates/timecards
• Including commissions/bonuses without pay history or a documented averaging method
• Subtracting an offset that doesn’t replace wages for the missed period
• Double-counting offsets (subtracting disability and also reducing missed time in a way that already accounts for the same absence)
• Forgetting partial days and modified duty (often the largest dispute area)
• Mixing cash payments and payroll without reconciling deposits to payroll records

Sources and references

DocketMath uses general wage-loss organization principles. Exact measures of damages and how offsets are treated can vary by jurisdiction and case facts. These references can help with terminology, especially around wage and withholding concepts:

• Fair Labor Standards Act (FLSA), 29 U.S.C. § 201 et seq. (federal wage and overtime concepts that often inform how baseline pay is evidenced)
• IRS Publication 15-T (withholding guidance—relevant when converting gross wage loss to net using documented withholding)
• IRS W-2 / reporting concepts (relevant to distinguishing employee earnings baselines vs. contractor profit concepts)

For a claim submission, align your DocketMath outputs to your supporting documents (pay stubs, time records, and benefit statements). This guide is educational and not legal advice.

Next steps

1. Open DocketMath and start with the wage-loss timeline. Enter missed dates with partial-day precision where possible.
2. Build your baseline earnings from the same period your pay stubs cover (avoid mixing “before injury assumptions” with “during injury pay patterns”).
3. Enter offsets you can prove (PTO, disability, workers’ comp wage replacement, etc.).
4. Generate a breakdown (week-by-week or by missed-day type) so your total is easier to defend.
5. Reconcile your totals to bank/pay stubs and ensure the worksheet matches what you were actually paid.

If you’re using the offset workflow, you can start here: /tools.

Related reading

• DocketMath Help: Lost Wages Calculator Overview
• DocketMath Tools: Wage Replacement & Offsets Worksheet
• DocketMath Blog: How to Document Missed Work for Wage Loss