Inputs you need for Wage Backpay in Colorado
6 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
To calculate wage backpay in Colorado using DocketMath (the wage-backpay tool), collect the inputs that let the calculator estimate what wages were owed, the backpay period, and any relevant time-based adjustments. In practice, the final number is driven by the same core factors in most wage disputes: the dates, the rate of pay, and how your worked time translates into the wage basis you’re claiming.
Use this checklist to gather the minimum information you’ll need for a solid first run:
- The date you want the backpay calculation to begin from (often tied to when the underpayment began or when a protected/pay-relevant period started, depending on your situation).
- The last date to include in the backpay period.
- Weekly or biweekly totals are usually easiest.
- If hours varied, keep one of the following:
- Choose what best matches what happened:
- If you’re claiming overtime or a premium-rate difference, provide:
- Include wages already paid that overlap the same time window to avoid double-counting:
- Provide how you want leave/time off treated in the calculation:
Warning (practical, not legal advice): Backpay inputs are only as accurate as your underlying records. If your start/end dates, pay rate, or hours are off—even by a few weeks—the output can move meaningfully.
Quick reference table: “Input → Why it matters”
| Input | What DocketMath needs it for | How it changes the output |
|---|---|---|
| Backpay start/end dates | Defines the number of workdays/pay periods included | Longer period can increase potential backpay |
| Pay rate(s) | Sets the baseline “what should have been paid” | Higher rate typically increases per-hour backpay |
| Hours worked | Determines the wage base | More hours generally increases amounts at issue |
| Wage gap type | Tells the tool how to compute differences | “Unpaid hours” vs “underpaid per hour” can produce different totals |
| Prior payments | Prevents counting money twice | More prior payments usually reduces remaining backpay |
| Deductions/time-off handling | Adjusts which portions are included/excluded | Different inclusion choices can shift totals |
Where to find each input
Most of what you need comes from a small set of documents. Here’s a practical mapping from record to input:
Backpay start date / end date
- Payroll calendar and employment records
- Offer letters, HR/role change documents, or communications showing when the pay issue began/ended
- Termination paperwork (if applicable) and your final payroll date
**Pay rate(s)
- Most recent offer letter and any pay change notices
- Pay history sections on payroll portals
- Pay stubs (often the fastest way to confirm what you actually received during each pay period)
Hours worked
- Timekeeping system exports (weekly timesheets are usually easiest)
- Payroll history by pay period (hours shown on pay stubs)
- If timekeeping is incomplete, reconcile:
**Wage gap type (unpaid hours vs. underpaid rate)
- Compare scheduled/recorded work against what appears on pay stubs for the same pay periods
- If the issue is classification-related (such as overtime treatment), keep a time breakdown by day/week showing why the hours should be treated differently
Prior payments already made
- Pay stubs and payroll ledger
- Retro pay or corrected payroll adjustments
- Written confirmations tied to the same time window (if you have them)
Deductions and time-off
- Pay stub line items (especially “deductions” and leave categories)
- Company policy documents only if you need help interpreting how leave/deductions functioned in your situation
If you want to enter everything in the same order you’ll use it in the calculator, open the tool here: ** /tools/wage-backpay
Run it
After you’ve collected your inputs, you’re ready to run DocketMath’s wage-backpay calculator.
Set the backpay period
- Enter the start date and end date you want included.
- If you only have a probable start date, start with the earliest solid record date you can document, then refine after you verify more payroll evidence.
**Enter pay rate(s)
- Provide the hourly rate (or the equivalent hourly basis used for salaried pay).
- If your pay changed, add the rate changes so the calculation reflects each sub-period accurately.
Enter hours and select the wage gap type
- Choose the method that matches what happened:
- unpaid hours, or
- underpaid per hour, or
- (if your workflow supports it) a combination approach.
- Add the hours worked per pay period, or the best-supported breakdown you have.
Account for payments already made
- If you received any overlapping wages during the period, input them so DocketMath can reduce double-counting.
Review the output categories
- DocketMath’s results typically reflect the totals tied to the wage gap method you selected.
- If the result seems dramatically high/low versus your own estimate, check in this order:
- dates
- hours
- rate changes
Pitfall to avoid: People often enter the correct end date but use the wrong start date (for example, starting from a notice/filing date rather than the first pay period they can actually document). That can understate or inflate backpay by weeks.
What to sanity-check (quick sensitivity checks)
Use these to catch obvious input mistakes before you finalize:
- If you increase the hourly rate by $1, backpay often changes by roughly:
- (hours at issue) × $1, depending on which wage gap method you selected.
- If you shift the start date by 2 pay periods, backpay often changes by:
- (average wages per pay period) × 2, assuming the wage gap persists.
- If you change hours worked by 10 hours, backpay often changes by:
- (rate difference / unpaid amount per hour) × 10
If you want a safe iteration approach, run two versions:
- Run A: using your best estimate for the start date
- Run B: using the earliest verifiable start date from pay stubs/timekeeping
Then keep the version that best matches your records.