Worked example: Wage Backpay in Nebraska
6 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
Run this scenario in DocketMath using the Wage Backpay calculator.
This worked example shows how DocketMath calculates wage backpay using Nebraska’s general limitations period.
Because Nebraska does not appear (based on the jurisdiction data you provided) to have a distinct, claim-type-specific wage backpay limitations rule for this scenario, we use the general/default period:
- General SOL period: 0.5 years
- General statute: Neb. Rev. Stat. § 13-919
- Statutory source: https://law.justia.com/codes/nebraska/chapter-13/statute-13-919/
Note: No claim-type-specific sub-rule was found in the provided jurisdiction data. This example therefore uses Nebraska’s general/default limitations period under Neb. Rev. Stat. § 13-919.
Inputs used in this example
Assume the following hypothetical facts for a Nebraska wage backpay calculation:
- Wage loss date (or last date the wage loss was sustained / “injury/violation date”): 2024-03-15
- Filing date (when the claim is filed): 2024-09-30
- Weekly wages at issue: $1,200 per week
- Reduced earnings pattern: none (assume full-time equivalent at the weekly rate)
- Backpay start alignment: begin counting backpay from the first pay period after the wage loss date (if your real-world facts use a different anchor—like first missed paycheck or last worked day—enter the dates accordingly)
What DocketMath needs for a wage-backpay run
In practice, wage backpay calculators generally need enough information to establish:
- A date range (or two dates) that defines the lookback period
- A wage rate (here, weekly wages)
- A work/pay-period assumption so the tool can translate calendar time into covered compensation periods
In this example, the key inputs are the injury/violation date (2024-03-15), the filing date (2024-09-30), and the weekly wage ($1,200/week). DocketMath then applies the jurisdiction-aware limitations window to decide which portion of the date range is covered.
Default limitations window applied in this example
Using the provided rule:
- 0.5 years = 6 months
- Nebraska general limitations basis: Neb. Rev. Stat. § 13-919
So, DocketMath applies a ~6-month lookback from the filing date as the default cap. Unless you structure your worksheet to use an alternative anchor (for example, a “last paycheck” date rather than “filing date”), the covered backpay window will be the portion that falls within that ~6-month period.
Example run
Below is a practical “how the run works” walkthrough for Nebraska (US-NE) using DocketMath and the general/default limitations period.
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: Apply Nebraska’s general limitations period
- Filing date: 2024-09-30
- Lookback period: 0.5 years (general/default) under Neb. Rev. Stat. § 13-919
- Backpay earliest allowable date: approximately 2024-03-30 (about six months before 2024-09-30)
Because the wage loss date in this hypothetical is 2024-03-15, the portion of wages before ~2024-03-30 is outside the default limitations window. Therefore, only wages on/after ~2024-03-30 are covered under the general/default SOL in this example.
Pitfall to watch: Backpay calculations often turn on the exact date the tool starts counting covered pay periods. If your first unpaid paycheck corresponds to a different date than the “injury/violation date,” you may need to adjust the date inputs to reflect the pay-period reality in your case.
Step 2: Determine the covered weeks (weekly wage assumption)
Assume wage backpay is calculated in weekly increments at $1,200/week.
- Backpay period start (covered): ~2024-03-30
- Backpay period end (anchor used in this example): 2024-09-30
From ~2024-03-30 to 2024-09-30 is roughly 6 months, which is about 26 weeks (using the typical “months-to-weeks” approximation for a worked example).
To keep the worksheet consistent with a weekly wage input, DocketMath treats the covered window as ~26 covered weeks.
Step 3: Multiply covered time by the weekly wage rate
- Weekly wages: $1,200/week
- Covered weeks: 26
- Estimated backpay (principal):
- $1,200 × 26 = $31,200
Summary of this example output
| Input | Value |
|---|---|
| Jurisdiction | Nebraska (US-NE) |
| SOL basis | Neb. Rev. Stat. § 13-919 (general/default) |
| Lookback window | 0.5 years (6 months) |
| Filing date | 2024-09-30 |
| Backpay start used | ~2024-03-30 |
| Weekly wages | $1,200 |
| Covered weeks | 26 |
| Estimated wage backpay (principal) | $31,200 |
DocketMath CTA:
- Use the tool here: /tools/wage-backpay
Friendly note: This is a worked example for illustration. Wage backpay outcomes depend heavily on the exact pay schedule and how the “covered period” is aligned to actual pay periods.
Sensitivity check
Small changes in inputs can shift the covered date range, changing the total backpay. Here are three quick “what if” checks you can mirror in DocketMath.
To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.
1) Filing date moves forward by ~30 days
If the filing date were 2024-10-30 instead of 2024-09-30:
- The ~6-month lookback would shift forward
- The covered window could shrink slightly depending on pay-period alignment
Approximate impact (illustrative):
- If covered weeks drop from ~26 to ~25:
- $1,200 × 25 = $30,000
- Change vs. base case ($31,200): -$1,200
2) Wage loss date moves later (but filing date stays fixed)
If the relevant wage loss began later (e.g., 2024-04-10 instead of 2024-03-15), then less of the covered window may actually represent lost wages.
Illustrative assumption:
- Covered weeks drop from ~26 to ~25
- $1,200 × 25 = $30,000
- Change vs. base case: -$1,200
3) Weekly wage rate increases by 10%
If weekly wages rise by 10% while covered weeks remain ~26:
- New weekly wages: $1,200 × 1.10 = $1,320
- Backpay: $1,320 × 26 = $34,320
- Change vs. base case: $34,320 − $31,200 = +$3,120
Sensitivity results at a glance
| Change | Covered weeks (approx.) | Weekly wage | Backpay (principal) | Change vs. $31,200 |
|---|---|---|---|---|
| Base case | 26 | $1,200 | $31,200 | — |
| Filing +30 days (possible ~1 week less) | 25 | $1,200 | $30,000 | -$1,200 |
| Wage loss starts later (possible ~1 week less) | 25 | $1,200 | $30,000 | -$1,200 |
| Weekly wage +10% | 26 | $1,320 | $34,320 | +$3,120 |
Warning: Sensitivity checks are not substitutes for pay-period-accurate schedules. If you’re paid biweekly or monthly, “weeks covered” should be translated to match the actual pay cadence (or use the tool’s frequency inputs).
