Worked example: Wage Backpay in Virginia
7 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
Below is a worked example for wage backpay in Virginia using DocketMath (jurisdiction-aware rules for US-VA). This example is designed to show how the calculator behaves with common wage-backpay inputs—not to provide legal advice.
Here is a simple illustration for Virginia. These values are for demonstration only and should be replaced with your actual inputs.
- Principal or amount: $100,000
- Rate or cap: 10%
- Start date: 2025-01-15
- End/as-of date: 2025-09-30
Scenario (Virginia)
A retail employee worked for 10 weeks and was paid late and at an incorrect hourly rate after being scheduled for full-time hours. The employee alleges backpay for the period starting Monday, January 8, 2024 through Friday, March 15, 2024 (inclusive). The employee was expected to work 40 hours per week.
To keep math transparent, assume the employer’s incorrect pay happened consistently across the entire period.
Inputs you would enter into DocketMath (wage-backpay)
Use the same units DocketMath expects (hours, dollars, and dates). The example values:
| Input | Example value | Why it matters |
|---|---|---|
| Jurisdiction | US-VA | Switches Virginia-specific wage-backpay assumptions and how the tool computes the period |
| Backpay period start | 2024-01-08 | Determines which pay dates/hours fall inside the window |
| Backpay period end | 2024-03-15 | Caps the computation at the end date |
| Expected hours per week | 40 | Drives total hours owed |
| Actual hours worked per week | 40 | If identical, the backpay comes from the rate difference, not missed hours |
| Expected hourly rate | $22.00 | What the employee should have earned |
| Actual hourly rate paid | $18.50 | What the employee was paid |
| Overtime assumption | Straight time only | Keeps the example focused on wage rate backpay; overtime logic can change totals |
| Pay timing | Not modeled | DocketMath focuses on wages/backpay totals; penalties/interest may be computed separately or treated differently depending on the tool settings |
Quick math behind the example (so you can sanity-check)
- Weeks in the period: 10 weeks (Jan 8 → Mar 15 inclusive)
- Expected total hours: 10 × 40 = 400 hours
- Hourly wage gap: $22.00 − $18.50 = $3.50 per hour
- Backpay before any special adjustments: 400 × $3.50 = $1,400
That $1,400 is the baseline outcome the calculator should produce when overtime and other adjustments are not applied.
Note: Backpay disputes can include tipped wages, overtime calculations, bonuses, chargebacks, or deductions. If your case includes any of those, adjust the calculator inputs so the hours and rate fields reflect the actual disputed components.
Example run
You can follow this run as a “dry run” to verify your own inputs. Start by opening DocketMath’s wage backpay tool: /tools/wage-backpay.
Run the Wage Backpay calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.
Run settings (US-VA)
- Select jurisdiction: **Virginia (US-VA)
- Enter:
- Start date: 2024-01-08
- End date: 2024-03-15
- Expected hours/week: 40
- Actual hourly rate: $18.50
- Expected hourly rate: $22.00
- Set overtime handling to match the scenario:
- For this example: straight time only
- Ensure the tool is set to compute wage backpay (not damages beyond backpay).
Expected output for this scenario
With the inputs above, the calculation should align with the baseline math:
- Total hours (expected): 400
- Rate difference: $3.50
- Wage backpay total: $1,400
In practice, DocketMath may also show:
- A detailed breakdown by week (showing the constant gap each week)
- A summary section indicating which components were included (hours, rate difference, and whether overtime adjustments were excluded)
What each output line means (practical reading)
If DocketMath presents a breakdown, interpret it like this:
- Hours included: confirms the date window correctly covers 10 weeks (400 hours).
- Wage gap: expected rate minus actual rate ($22.00 − $18.50 = $3.50/hour).
- Backpay per week: hourly gap × expected hours/week ($3.50 × 40 = $140/week).
- Backpay total: weekly backpay × number of weeks ($140 × 10 = $1,400).
To reconcile the tool’s number with your own math:
- Multiply DocketMath’s “rate gap” by its “total hours.”
- If you see a different number, inspect whether:
- the tool used a different effective week count for partial weeks,
- overtime logic was enabled, or
- hours/week differs from your assumption.
Pitfall: Off-by-one date errors are common. If you accidentally end on 2024-03-14 instead of 2024-03-15, you may reduce the week count or exclude hours the tool assumes were worked—changing the total even if the hourly rate inputs are correct.
Sensitivity check
Once the baseline run matches your hand math, test how sensitive the result is to realistic input changes. This is where DocketMath’s practical value shows up: you can see which facts move the number most.
To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.
Sensitivity 1: Changing the end date by 1 week
Assume everything stays the same except the end date becomes 2024-03-22 (adds one more week of similar work).
- New weeks: 11 weeks
- New hours: 11 × 40 = 440
- Backpay: 440 × $3.50 = $1,540
- Increase from baseline: $1,540 − $1,400 = $140
Takeaway: With constant hours/week and constant rate gap, weekly increments are linear. Each added week at 40 hours adds:
- $3.50 × 40 = $140.
Sensitivity 2: Changing the paid hourly rate
Keep the date window the same, but suppose the actual paid hourly rate was $19.25 instead of $18.50.
- New gap: $22.00 − $19.25 = $2.75
- Backpay: 400 × $2.75 = $1,100
- Change: $1,100 − $1,400 = −$300
Takeaway: Rate inputs dominate the result. A $0.75/hour difference changes:
- Weekly backpay by: $0.75 × 40 = $30/week
- Over 10 weeks by: $30 × 10 = $300
Sensitivity 3: Hours/week differs from “expected”
Suppose the employee actually worked 35 hours/week instead of 40, still within the same dates. Keep rates the same.
- Total hours: 10 × 35 = 350
- Backpay: 350 × $3.50 = $1,225
- Change: $1,225 − $1,400 = −$175
Takeaway: If hours are disputed, that’s the second-largest driver after the hourly rate gap (in scenarios like this with constant weekly pay).
Quick comparison table (baseline vs. variations)
| Variation | Hours/week | Paid rate | End date | Expected backpay |
|---|---|---|---|---|
| Baseline | 40 | $18.50 | 2024-03-15 | $1,400 |
| Add 1 week | 40 | $18.50 | 2024-03-22 | $1,540 |
| Paid rate higher | 40 | $19.25 | 2024-03-15 | $1,100 |
| Fewer hours | 35 | $18.50 | 2024-03-15 | $1,225 |
Warning: These sensitivities assume overtime is not part of the calculation. If your disputed period includes weeks over 40 hours and overtime should apply, totals can change nonlinearly because overtime rates often don’t match straight-time rates.