Worked example: Wage Backpay in Colorado
5 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
This worked example walks through wage backpay in Colorado using DocketMath’s wage-backpay calculator (jurisdiction-aware rules for US-CO). The goal is to show how the inputs translate into an estimated backpay range, not to provide legal advice.
Scenario (fictional but realistic)
A Colorado employee is owed unpaid wages after a dispute with an employer. The employee kept records of hours worked and the wage rate. The employer later corrects payroll for the missing period.
We’ll calculate:
- Backpay for hours worked during the claim period
- Less any amount already paid
- Net result using the calculator’s wage-backpay (wages-only) logic
Inputs used in this example
Use these as the exact set of values you would enter into DocketMath → /tools/wage-backpay.
Employment & wage basics
- Jurisdiction: **Colorado (US-CO)
- Pay type: Hourly
- Wage rate: $28.50/hour
- Hours owed per week: 32 hours
- Owed weeks: 18 weeks
- Already paid wages: $2,200 (partial catch-up payment)
Backpay framing
- Calculation basis: “Wages only” (no liquidated damages, benefits, or other extras)
- Excluded items: no tips, no commissions, no incentive pay
- Rounding: calculator default (weekly aggregation)
Quick sanity checks before running
Before hitting calculate, confirm:
- Weekly hours × wage rate matches your payroll records (or timekeeping records).
- Owed weeks matches the specific period you’re targeting (the calculator needs a defined window).
- Already paid wages is only what the employee actually received for the same disputed period—not what the employer says they would have paid under a different scenario.
Note: This example assumes the wage rate and weekly hours are consistent. If hours vary materially week to week, use the calculator with the closest available weekly schedule, or run multiple intervals and add the results.
Example run
Open DocketMath’s wage tool here: /tools/wage-backpay.
Below is a walkthrough-style “run” for the inputs above.
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.
Step 1: Compute gross owed wages for the period
For the specified period, the calculator’s wage-backpay math (wages-only) follows:
- Weekly owed wages = 32 hours/week × $28.50/hour = $912/week
- Gross owed wages = $912/week × 18 weeks = $16,416
Step 2: Subtract wages already paid
Next, subtract payments already received for the same period:
- Already paid wages = $2,200
- Estimated wage backpay = $16,416 − $2,200 = $14,216
Step 3: Present output as the calculator would
A typical DocketMath output for this tool will present:
- Gross wages owed for the defined period
- Less payments already made
- Net wage backpay estimate
Result from this example run
- Estimated wage backpay (wages only): $14,216
To keep expectations realistic, treat this as an estimate based on the inputs you feed the calculator, not a guarantee of the final number in any proceeding.
Pitfall: “Already paid wages” must correspond to the same period you’re calculating backpay for. If you subtract payments tied to different weeks, you may understate the backpay owed for the claim window.
Sensitivity check
Backpay totals can change noticeably with small input updates because the core computation is essentially time × wage, once you’ve set the period and rate. This section shows how the estimate moves when you adjust inputs one at a time.
Sensitivity table (wages only)
Assume the same 18-week period and $2,200 already paid, but vary the hourly wage.
| Hourly wage | Weekly wages (32 hrs × rate) | Gross owed (18 wks) | Net backpay (gross − $2,200) |
|---|---|---|---|
| $27.00 | $864.00 | $15,552.00 | $13,352.00 |
| $28.50 (base) | $912.00 | $16,416.00 | $14,216.00 |
| $30.00 | $960.00 | $17,280.00 | $15,080.00 |
What to learn from this
- A $1.50/hour change affects weekly wages by $1.50 × 32 = $48/week.
- Over 18 weeks, that’s $48 × 18 = $864 change in gross owed.
- After subtracting $2,200 already paid, the net backpay changes by the same $864.
Another sensitivity: period length
Now hold hourly wage at $28.50 and vary owed weeks, keeping already paid wages at $2,200.
| Owed weeks | Gross owed (weekly $912 × weeks) | Net backpay (gross − $2,200) |
|---|---|---|
| 16 | $14,592 | $12,392 |
| 18 (base) | $16,416 | $14,216 |
| 20 | $18,240 | $16,040 |
Period-length takeaway
Each extra week adds:
- $912/week in gross owed, and
- the same increase in net backpay if “already paid wages” does not change.
Warning: If your claim period is contested—e.g., parties disagree on the start or end date—your results can shift by hundreds per week. A practical approach is to run the tool at plausible boundary dates and use the difference to frame a range.
Practical workflow with DocketMath
If you’re unsure about the exact owed weeks boundary, run three scenarios:
- Conservative
- Base
- Aggressive Keep the wage rate constant first, then adjust it only if payroll evidence suggests a different rate.
For example:
- Conservative: 16 weeks
- Base: 18 weeks
- Aggressive: 20 weeks
Estimated net backpay range (wages only):
- $12,392 to $16,040