Inputs you need for Wage Backpay in Oregon
5 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Run this scenario in DocketMath using the Wage Backpay calculator.
To run a wage backpay calculation in Oregon using DocketMath (jurisdiction US-OR), gather the inputs below first. The goal is to capture (1) what you were owed, (2) what you actually earned/received during the backpay period, and (3) the dates that define the calculation window.
Before you start: this walkthrough is not legal advice—it’s a practical inputs checklist to help your numbers match what DocketMath is designed to calculate.
Core inputs (usually required)
- ☐ **Start date of backpay period (YYYY-MM-DD)
- ☐ **End date of backpay period (YYYY-MM-DD)
- ☐ Pay rate type
- ☐ Hourly rate (e.g., $24.50/hour)
- ☐ Salaried amount (annual salary converted to an hourly equivalent, as DocketMath requires)
- ☐ Commission/bonus (if you want them included, you’ll need a reporting method that fits your dataset)
- ☐ Pay rate amount
- ☐ Scheduled/expected hours per week (or weekly schedule)
- ☐ Actual work hours (if partially worked) or confirm you should treat the period as “not worked”
- ☐ Mitigation income received during the period (what you earned elsewhere during the same dates that may reduce backpay in the calculation model)
- If none: enter $0 (and keep a record showing no mitigation income)
- ☐ Any wage-related benefits you want included or excluded (only if DocketMath supports them in your setup and you want them reflected consistently in your dataset)
Inputs that affect the result even when “wages” seem simple
- ☐ Overtime rules handling
- If overtime was part of the job you were denied, confirm whether your hours include overtime or should be treated as straight-time hours.
- ☐ Different pay rates over time
- If your pay changed (raises, role changes), you’ll need separate segments OR a weighted approach that matches your timeline.
- ☐ Breaks in employment / non-contiguous periods
- If the denial wasn’t continuous, you’ll either split the period or reflect the exact dates DocketMath uses for the backpay window.
Optional inputs (depending on your dataset)
- ☐ Stipends/allowances you treated as wages
- ☐ Tips (if you have documentation and you’re treating them as wage components)
- ☐ One-time wage payments that belong inside the backpay window
Pitfall: A very common reason backpay outputs don’t match expectations is using a calendar date range that doesn’t match the backpay period you’re trying to model. Define the window first, then fill in rates and hours.
Where to find each input
Use your own records first. DocketMath works best when you feed it values you can verify quickly.
Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.
Dates
- Start date: the first date you claim you were entitled to wages but didn’t receive them.
- Common sources: offer/contract start date, pay stub coverage start, termination/denial date documents.
- End date: the last date you’re modeling.
- Common sources: reinstatement/settlement date you’re modeling, final pay date, or the date you started replacement work.
Recommended workflow
- Pull the timeline from the same document set you’ll use for your backpay story.
- If you’re splitting pay rate segments, keep date boundaries consistent (e.g., every raise effective date).
Pay rate, hours, and wage components
- Pay rate amount
- Source: recent pay stubs, offer letter, salary agreement.
- Hours per week
- Source: schedule history, handbook expectations, timekeeping records.
- Actual work vs. not worked
- Source: time records (if you worked elsewhere during the same general scenario), or your attendance records if the wage denial prevented work.
Mitigation income (earnings elsewhere)
- Mitigation income during the period
- Source: pay stubs from the other job, quarterly earnings summaries, or employer payroll statements.
- If mitigation income varies weekly, choose one approach:
- weekly values (more precise), or
- total amount for the full period (simpler, less granular)
Overtime and pay changes
- Overtime
- Source: job classification and historical pay stub patterns.
- Different pay rates
- Source: each pay rate change date and evidence (e.g., raise effective date).
Run it
Once your inputs are collected, you’re ready to run the wage-backpay calculator in DocketMath for Oregon (US-OR).
Enter the inputs in DocketMath and run the Wage Backpay calculation to generate a clean breakdown: Run the calculator.
Step-by-step checklist
How outputs change when you change inputs
Use these “knobs” to understand why a number moves:
| Input you change | What typically happens to the backpay estimate |
|---|---|
| Start date moves earlier by 7 days | Backpay window expands; net backpay usually increases proportionally (depending on hours/week and pay rate) |
| Scheduled hours per week increase | Higher gross wage backpay; net backpay increases unless mitigation offsets rise similarly |
| Pay rate increases (e.g., raise or higher classification) | Gross wage backpay increases for the affected segment(s) |
| Mitigation income increases | Net backpay usually decreases because mitigation is offset against gross backpay |
| You enter $0 mitigation income | Net backpay stays closer to gross wage backpay |
Warning: If you enter mitigation income that overlaps dates you didn’t intend, you can understate the net backpay. Keep mitigation income date boundaries aligned with your backpay start/end dates.