Why Wage Backpay results differ in Delaware

The top 5 reasons results differ

If you run DocketMath’s Wage Backpay calculator for Delaware (US-DE) and see different outputs across runs, the most common cause is that the calculator’s results are sensitive to jurisdiction-aware inputs—especially the Delaware general 2-year lookback.

Delaware’s general limitation period is 2 years under 11 Del. C. § 205(b)(3). No claim-type-specific sub-rule was found in the jurisdiction data you provided, so this article treats 11 Del. C. § 205(b)(3) as the default rule.

Here are the top 5 reasons Wage Backpay results may differ in Delaware:

1. **Lookback window cutoffs (2-year SOL)

   • The calculation will effectively include only pay/work periods that fall within the 2-year general period tied to 11 Del. C. § 205(b)(3).
   • If your as-of date or filing date input shifts by even a small amount (weeks can matter), the earliest included wage period changes—often changing the total more than other adjustments.

2. Pay period boundaries vs. partial periods

   • Backpay totals depend on how the tool maps work time into pay periods (weekly/biweekly) and how the cutoff interacts with those boundaries.
   • Two runs that look similar can produce different totals if the cutoff lands on different sides of a pay-period boundary or if the tool allocates partial coverage differently near the edge.

3. Hours interpretation: scheduled vs. worked vs. credited

   • Wage backpay is driven by the relationship between hours and wage rate. If you enter or model hours differently (e.g., using hours scheduled as a proxy instead of hours worked), results can diverge.
   • This effect can be amplified when the 2-year window excludes some weeks but includes others, making definitions near the cutoff especially influential.

4. Wage rate and rate changes

   • If you include multiple wage rates (raises, promotions, role changes), the calculator needs consistent rate-by-effective-date inputs.
   • A mismatch can happen when a higher rate is applied to dates that should be excluded (or vice versa), leading to different totals even if your date range is the same.

5. Offset items and netting assumptions

   • Some calculations depend on whether the run is modeled as gross wages versus net wages after offsets (for example, mitigation or other earnings, depending on how the tool is configured).
   • If you enter offsets in one run but not the other—or categorize them differently—you can see materially different totals even when dates match.

Pitfall to watch: If your “as-of” or filing date input moves, you can change which weeks fall inside the 2-year lookback under 11 Del. C. § 205(b)(3). That single change can dominate the result.

How to isolate the variable

To pinpoint what caused the difference between two US-DE DocketMath runs, use this step-by-step checklist:

• Compare the run’s as-of date / filing date / start date inputs (whichever your workflow uses).

• Keep everything identical except the one date you’re testing.

• If you can, keep the pay-period structure the same across runs (e.g., weekly vs. biweekly).

• Pay special attention to whether the cutoff date lands near a pay-period boundary.

• Ensure each run uses the same:

  • wage rate amounts
  • effective dates for each rate

• If effective dates differ (even subtly), the result can shift.

• Use one consistent definition across both runs (for example, hours worked rather than hours scheduled, if that’s what you intended).

• Consistency matters most for weeks near the 2-year boundary.

• Check whether one run includes offset/mitigation values and the other does not.

• Also confirm you’re entering them in the same category/format each time.

Fast workflow tip: Start with a baseline run via /tools/wage-backpay, save the output, and then change only one input at a time. As you adjust inputs, watch for changes in both (1) the included date range and (2) the resulting total.

• Open: **/tools/wage-backpay

Friendly reminder: This is a practical explanation of common calculation sensitivities, not legal advice.

Next steps

1. Validate the date window first

   • Before tweaking wages or offsets, verify the included periods align with the general 2-year rule under 11 Del. C. § 205(b)(3) (the default approach here, since no claim-type-specific sub-rule was found).

2. Run a two-scenario test

   • Scenario A: slightly earlier cutoff date
   • Scenario B: slightly later cutoff date
     This quickly shows whether the discrepancy is mainly driven by which weeks are inside vs. outside the lookback.

3. Document assumptions

   • Write down what you used for each run:

     • wage rate effective dates
     • hours definition (worked vs. scheduled, etc.)
     • how offsets/netting were entered
       This makes it much easier to explain the difference and reproduce the result later.

4. Keep scope consistent with the calculator’s default

   • Since no claim-type-specific sub-rule was identified in the provided jurisdiction data, Delaware behavior here should be treated as driven by the general/default 2-year limitation in 11 Del. C. § 205(b)(3).

If you share the two sets of inputs you used (especially the dates, wage rates, hours method, and any offsets), I can help you identify the most likely cause—without providing legal advice.

Related reading

• Wage & Backpay Calculator Guide for Alabama
• Wage & Backpay Calculator Guide for Arizona
• Wage & Backpay Calculator Guide for Colorado