Why Wage Backpay results differ in West Virginia
4 min read
Published April 15, 2026 • By DocketMath Team
The top 5 reasons results differ
Run this scenario in DocketMath using the Wage Backpay calculator.
When DocketMath calculates wage backpay for West Virginia (US-WV), the output can differ across cases—even when the parties largely agree on the underlying wage loss. Most differences come from jurisdiction-aware assumptions and input choices that change the backpay time window and the amount “should have been paid.”
Below are the top five reasons you may see different results in West Virginia.
Which “lookback” period is applied
- DocketMath uses West Virginia’s general/default statute of limitations baseline of 1 year, based on W. Va. Code §61-11-9.
- Practical effect: if a calculation uses a longer (or different) limitations window, the backpay period expands and total backpay usually increases.
- Important: No claim-type-specific sub-rule was found in the provided jurisdiction data, so the general/default 1-year period is the baseline for US-WV in this context.
Different pay-period boundaries
- Backpay is sensitive to how the start/end dates line up with payroll cycles (e.g., weekly vs. biweekly).
- A small date shift can change how many pay periods are included, which changes the included wages and any time-based adjustments used by the calculator.
Different treatment of “partial” pay periods
- Some inputs effectively include partial pay periods; others behave more like they round to whole pay periods.
- If one run uses dates that reflect calendar-day work and another run was modeled as “about 30 days” without matching exact dates, the included work days/pay periods can differ.
Missing or inconsistent wage components
- Backpay results can change if inputs aren’t identical for components such as:
- hourly vs. salary assumptions,
- regular hours vs. overtime hours,
- included/excluded bonuses or other wage components,
- scheduled shift patterns.
- Even if both runs start from the same job description, two versions of the wage inputs can produce different totals.
**End date mismatches (what “backpay ends” really means)
- Many backpay models stop at a chosen endpoint. If one calculation uses:
- a separation date, another uses
- a reinstatement date, or a later administrative/court date, the covered time span changes and the output follows that change.
Pitfall: Labels like “backpay end date” can be used inconsistently across case documents. Verify the actual entered dates, not just the description.
How to isolate the variable
To determine why two DocketMath outputs differ, change only one input at a time and compare how the total shifts.
Use this sequence:
- Baseline: 1 year under W. Va. Code §61-11-9
- Because no claim-type-specific sub-rule was identified in the provided jurisdiction data, you should not expect an alternate limitations period for the general/default setting.
- Use the same wage rate inputs and assumptions (including whether overtime/bonus components are included).
- Run 1: your standard start/end dates
- Run 2: shift only the start date by 7 days
- Run 3: shift only the end date by 7 days
Quick diagnostic rule of thumb:
| What you change in DocketMath | What you’re likely learning |
|---|---|
| Limitations/window via date span | Whether differences are driven mainly by the covered time period |
| Pay-period alignment | Whether payroll cadence/date alignment changes the paycheck count |
| Wage inputs (rate/hours/OT/bonuses) | Whether differences are driven by wage component assumptions |
| End date | Whether totals scale roughly with additional/removed days |
Next steps
Create three DocketMath scenarios with the same wage numbers:
- Scenario A: current start/end dates
- Scenario B: start date moved earlier by 1 week
- Scenario C: end date moved later by 1 week
Compare totals to see if differences are primarily driven by time window or wage assumptions.
Record inputs in a single “calculation sheet” Capture exactly:
- the start date and end date entered into DocketMath,
- wage inputs (rate/hours; whether overtime/bonuses are included),
- payroll cadence assumptions if applicable to your inputs.
Sanity-check the limitations baseline If someone else’s calculation appears to use something other than the general/default 1-year baseline from W. Va. Code §61-11-9, you’ll likely see systematic differences that won’t be resolved by adjusting wage components alone.
Gentle note: This is for diagnostics and modeling comparison purposes, not legal advice. If you need advice about how statutes apply to a specific claim, consult a qualified professional.