Inputs you need for Wage Backpay in Delaware
4 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
If you’re trying to calculate wage backpay exposure in Delaware with DocketMath (wage-backpay), you’ll get the most reliable results when you enter the right “inputs” up front. Delaware uses a general/default statute of limitations (SOL) of 2 years for the backpay window in this workflow, based on 11 Del. C. § 205(b)(3). No claim-type-specific sub-rule was found in the available guidance for extending or shortening that period for this specific setup—so treat 2 years as the default.
Use the checklist below as your capture sheet before you run the calculator:
Note: DocketMath’s output depends heavily on whether your inputs match the actual wage pattern during the backpay window—especially hours worked and any already-paid amounts.
Delaware SOL effect you should expect
In this DocketMath workflow, the calculation uses the 2-year default SOL derived from 11 Del. C. § 205(b)(3). In practice, that means the tool typically limits the backpay “window” to the unpaid wages that fall within the two years before the relevant filing/trigger date you use in the tool.
- If your entered dates cover more than 2 years, expect DocketMath to truncate the calculation period to the SOL window.
- If your entered start date moves within the last 2 years, the backpay result should generally change because different numbers of pay periods fall inside (or outside) the SOL-limited period.
(Avoiding legal advice disclaimer: this is a practical math workflow and general SOL information, not a determination of legal rights.)
Where to find each input
To keep this actionable, here’s where you can usually pull each item quickly:
| Input | Where to find it | What to look for |
|---|---|---|
| Employment start date | Offer letter, onboarding emails, HR records, employment agreement | “Start date,” “effective date,” or first day worked |
| Employment end date | Termination letter, resignation email, HR confirmation | Final day worked or last paid date—align with the tool’s definition |
| Pay period frequency | Pay stubs, payroll portal settings | Weekly / biweekly / semi-monthly / monthly |
| Pay rate(s) | Pay stubs, offer letter, wage change notices | Base hourly rate; document any wage changes |
| Regular hours per pay period | Timesheets, scheduling logs, calendar entries | Total hours per pay period you want DocketMath to model |
| Overtime hours | Timesheets, payroll reports | Overtime totals and the dates they occurred |
| Amounts already paid | Pay stubs and adjustment statements | “Backpay,” “catch-up,” adjusted wages, or partial payments |
| Verification documents | Your document set | Timekeeping records + wage statements for cross-checking |
Document discipline that makes the math faster
Before you start entering numbers, gather:
- One pay stub that shows the “normal” wage structure, and
- Any pay stubs that show changes (raise, hours/schedule changes, overtime pattern changes, or catch-up payments).
This reduces the most common input mismatch—entering one pay rate or one hours figure when the pay history shows multiple patterns.
Warning: If your hours varied significantly across pay periods, using one averaged “regular hours” number can materially change the result. Whenever possible, mirror the pattern from your time records (or use the best approximation your documents support).
Run it
Now you’ll plug the inputs into DocketMath → wage-backpay and use the tool to do two main things:
**Apply the Delaware default SOL window (2 years)
- Default period used in this workflow: 2 years
- General statutory citation: **11 Del. C. § 205(b)(3)
- Default only: no claim-type-specific sub-rule found to change that period in this setup
Calculate unpaid wage totals
- Uses your **pay rate(s)
- Uses your regular hours and any overtime inputs you enter
- Nets out amounts already paid (partial payments/catch-up) so the output reflects unpaid backpay rather than double-counting
How output changes when you adjust inputs
- Changing the start date earlier than the SOL window
- Expect the output to not expand beyond the SOL-limited period. DocketMath will generally ignore unpaid periods outside the 2-year default window.
- Changing the start date within the SOL window
- Expect the backpay amount to increase or decrease as more (or fewer) pay periods are included.
- Adjusting regular hours upward
- Expect the backpay amount to increase. If the tool includes overtime logic, increasing hours may also affect overtime calculations.
- Adding amounts already paid
- Expect the backpay output to drop, because DocketMath nets the unpaid portion against what you were already compensated for.
When you’re ready, run the calculation here: **Run Wage Backpay in DocketMath