Worked example: Wage Backpay in New York

Example inputs

Run this scenario in DocketMath using the Wage Backpay calculator.

This worked example shows how to estimate wage backpay for a New York matter using DocketMath’s Wage Backpay calculator with jurisdiction-aware time limits.

Because this is an example (not legal advice), treat the numbers as placeholders for how the calculation works. The calculator’s job is to translate your inputs into a backpay window and a payout estimate based on the assumptions you select.

If you want to follow along, open the calculator here: /tools/wage-backpay.

Statute-based backpay window (New York)

For New York, DocketMath applies the general/default limitations period of 5 years. The relevant source is:

• N.Y. Crim. Proc. Law § 30.10(2)(c)
  Source: https://www.nysenate.gov/legislation/laws/CPL/30.10

No claim-type-specific sub-rule was found in the jurisdiction data you provided. So the calculator uses the general/default period as the governing lookback window for this example (i.e., there is not a different, shorter/longer window for a specific wage-backpay claim type here).

Input assumptions for the example

In a wage backpay scenario, you typically need:

• Last date wages were paid / last worked date (sets the end of the backpay period because wages generally can’t be “lost” after the person returns to paid work)
• Filing date (or effective claim date) (anchors the limitations lookback window)
• Pay rate (hourly or salary—salary may be converted depending on the calculator’s settings)
• Hours per week (drives weekly wage totals)
• Work schedule assumptions (often a “full-time” default; the exact proration can affect partial weeks)
• Wage-only mode vs. including other components (for this example, we focus on wages)

Below are the example inputs used to run the calculator:

Example run

Now let’s run the example in DocketMath using the Wage Backpay calculator.

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: Determine the 5-year lookback window (default rule)

Using the general/default 5-year period, DocketMath computes a backpay start date from the chosen effective/filing date.

For this example:

• Claim/effective date: 2026-04-10
• Lookback period: 5 years
• Approximate backpay start: 2021-04-10
  (The exact start day can vary slightly based on the calculator’s date-handling convention.)

Then the calculator applies the practical constraint that the backpay period should not extend past when wages actually stopped. With:

• Last worked date: 2021-06-15

…the effective backpay window becomes:

• Start: 2021-04-10
• End: 2021-06-15

That is about 9 weeks (the calculator will compute the precise number of days/weeks using its internal schedule logic).

Effective backpay window (for this example):

• Start: 2021-04-10
• End: 2021-06-15

Step 2: Compute weekly lost wages

Weekly wages in this example are:

• Hourly rate: $30.00
• Hours per week: 40
• Weekly wages: $30.00 × 40 = $1,200

Step 3: Multiply by the number of weeks in the period

DocketMath multiplies weekly wages by the computed duration of the backpay window.

If the duration is ~9.0 weeks:

• Backpay ≈ $1,200 × 9.0 = $10,800

Example output (estimate)

For this specific run, the calculator’s wage backpay estimate would be approximately:

• Estimated wage backpay: $10,800

You should expect small differences depending on:

• how partial weeks are prorated (day-based vs week-based),
• rounding behavior (for duration),
• and whether the schedule inputs match a standard 5-day workweek or a custom schedule.

For clarity, here’s the same result broken into pieces:

Sensitivity check

Backpay totals change quickly when you adjust inputs that affect (1) the date window or (2) weekly wages. Below are targeted “one-change-at-a-time” checks.

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.

Sensitivity 1: Filing/effective date by +30 days

Keep pay rate, hours/week, and last worked date the same, but assume the filing date moves from:

• 2026-04-10 → 2026-05-10

A later filing date can shift the computed 5-year lookback window and change the overlap between the lookback period and the “before last worked” period.

Directional estimate for this example:

• $1,200 per week
• 30 days ≈ 4.3 weeks
• Potential swing ≈ $1,200 × 4.3 ≈ $5,160

So the total could plausibly move by an amount on the order of ~$5,000, depending on how proration lands.

Sensitivity 2: Hourly rate increases from $30/hour to $35/hour

Keep dates constant; change only the hourly rate:

• Original weekly: $30 × 40 = $1,200
• New weekly: $35 × 40 = $1,400
• Increase: $200/week

With ~9 weeks:

• Increase ≈ $200 × 9 = $1,800

Sensitivity 3: Hours per week decreases from 40 → 35

Keep dates and hourly rate constant; reduce hours:

• Original weekly: $30 × 40 = $1,200
• New weekly: $30 × 35 = $1,050
• Weekly reduction: $150/week

Over ~9 weeks:

• Reduction ≈ $150 × 9 = $1,350

Quick comparison table

Using the same approximate ~9-week backpay duration as a baseline:

Related reading

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