Worked example: Wage Backpay in Ohio

Example inputs

Below is a worked example of calculating wage backpay using DocketMath for Ohio (US-OH). This walkthrough uses Ohio’s general statute of limitations for bringing claims, which is tied to Ohio Rev. Code § 2901.13.

Scenario (numbers you can swap)

Assume a wage backpay scenario in Ohio where:

• Alleged discriminatory/withholding event start date: 2022-02-01
• Date the case is filed: 2024-03-15
• Pay rate (assume constant): $22.50/hour
• Weekly hours: 32 hours/week
• Pay frequency: weekly (kept simple; other schedules can be modeled if the tool supports them)
• Workdays actually missed: the tool will translate missed time into backpay using its wage-backpay model (hours × hourly rate × applicable weeks)

SOL window used in Ohio (general/default)

DocketMath uses the general SOL period you provided:

• General SOL Period: 0.5 years

That means, for recoverable wages, the tool looks back 6 months from the filing date—unless you have facts that require applying a different limitation period (this example does not apply a different one because the brief indicates no claim-type-specific sub-rule was found).

Cited law basis for the general approach: Ohio Rev. Code § 2901.13, accessed via the Ohio statutory PDF provided:
https://codes.ohio.gov/assets/laws/revised-code/authenticated/29/2901/2901.13/7-16-2015/2901.13-7-16-2015.pdf

Inputs list (what you’d enter in DocketMath)

Use these as the baseline inputs for the wage-backpay calculator:

• Filing date: 2024-03-15
• Event start date: 2022-02-01 (used to determine how much predates the SOL window)
• Hourly wage: $22.50
• Weekly hours: 32
• SOL lookback: 0.5 years (general/default per § 2901.13)

Optional inputs (only if your DocketMath model includes them):

• Partial weeks or interruptions—leave blank in a basic run

Example run

Let’s walk through what DocketMath would do with the inputs above.

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 recoverable date range

• Filing date: 2024-03-15
• Lookback (general/default): 0.5 years ≈ 6 months
• Tool-window start date (approx.): 2023-09-15

Because the alleged event started on 2022-02-01, most of that earlier period is older than the 6-month SOL-capped window. So for wage-backpay purposes, DocketMath will use:

• Recoverable period: 2023-09-15 through 2024-03-15 (the inclusive/exclusive treatment can depend on the tool’s week/day logic; the key idea is the SOL-capped lookback ends at filing)

Step 2: Convert time in the recoverable window to wages

Total time in the recoverable window is roughly 6 months. In a weekly wage model:

• Weeks in 6 months (approx.): 26 weeks

Weekly earnings (gross wages, before deductions) are computed as:

• Weekly wages = hourly rate × weekly hours
• Weekly wages = $22.50 × 32 = $720 per week

Approximate recoverable backpay:

• Backpay ≈ 26 weeks × $720/week
• Backpay ≈ $18,720

Step 3: Output summary (how to interpret the result)

A DocketMath wage-backpay run typically reflects three things:

• The SOL-limited recoverable window
• The number of weeks (or time units) included in the wage multiplication
• The calculated backpay amount based on wages per included week

So the headline result for this example would be:

• Backpay estimate (SOL-limited): ~$18,720

Why you don’t see more: even though the event started in 2022, the calculation only includes the general SOL lookback period ending at filing (2024-03-15).

Sensitivity check

Use this section to see how the estimate changes when you adjust inputs that affect (a) the SOL window and (b) the wage math.

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.

A) Filing date changes (SOL window shifts)

Keep hourly rate and weekly hours the same, and change the filing date:

• Filed ~30 days earlier:

  • Filing date: ~2024-02-14
  • The lookback window ends sooner → fewer weeks included → backpay decreases roughly with the weeks lost.

• Filed ~30 days later:

  • Filing date: ~2024-04-14
  • The lookback window ends later → more weeks included → backpay increases roughly with the extra weeks gained.

Because the SOL lookback here is a straight 0.5 years, the result is often approximately proportional to the amount of time included (assuming constant pay).

Quick per-week sensitivity using these constants:

• Weekly backpay rate: $720/week
• A change of 4 weeks ≈ $2,880 (4 × $720)

B) Weekly hours change (direct wage multiplier)

Hold dates constant; adjust weekly hours:

Pattern: if weekly hours increase by 8 hours/week, weekly wages increase by:

• $22.50 × 8 = $180/week
• Over 26 weeks: 26 × $180 = $4,680 (approx.)

C) Hourly wage change (another direct multiplier)

Hold dates and hours constant; vary hourly wage:

D) SOL rule assumption (general/default only)

This is the key assumption for this Ohio worked example:

• DocketMath uses the general/default SOL period of 0.5 years tied to Ohio Rev. Code § 2901.13.
• The brief note states no claim-type-specific sub-rule was found, so this example does not switch to a different lookback.

Practical takeaway: if, in your real case, a different limitation period applies based on how the claim is characterized, the recoverable wage window (and therefore the backpay estimate) could change.

Optional next step in DocketMath

If you want a more realistic model, update one input at a time (hours, hourly rate, and/or date) and re-run. For quick access, start here: Wage Backpay calculator.

Related reading

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