Worked example: Wage Backpay in Georgia

Example inputs

Run this scenario in DocketMath using the Wage Backpay calculator.

This worked example shows how to estimate wage backpay using DocketMath with Georgia (US-GA) jurisdiction-aware rules.

Primary tool link: /tools/wage-backpay

Before you run the calculator, confirm what you’re measuring. Wage backpay estimates are typically limited by the applicable statute of limitations (SOL) for bringing a claim for unpaid wages. For this example, we use Georgia’s general/default SOL period because no claim-type-specific sub-rule was found in the jurisdiction data provided.

Georgia SOL used in this example (default/general)

• General SOL Period: 1 year
• General Statute: O.C.G.A. § 17-3-1
  Source: https://law.justia.com/codes/georgia/2021/title-17/chapter-3/section-17-3-1/?utm_source=openai

Important note (how this example treats the law): No claim-type-specific sub-rule was found for this calculator run, so this example uses the general/default 1-year SOL referenced in O.C.G.A. § 17-3-1. If your situation involves a different governing rule, the eligible backpay window could change.

Inputs you’ll enter in DocketMath (wage-backpay)

Use these values as an example set. You can swap numbers later—what matters most is how the SOL window changes which dates’ wages are included.

Assumptions for this example

• The worker was not paid for the missed hours for the claimed period.
• No interim wage payments were received (offsets are $0).
• Wages are modeled simply as: hours per week × hourly rate for each included week.

If your scenario involves variable hours, multiple employers, or different pay rates over time, you can still use the tool—often by running multiple scenarios and comparing results.

Example run

Now let’s run the example using DocketMath’s wage-backpay calculator logic with the Georgia default SOL approach (1-year lookback under O.C.G.A. § 17-3-1).

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: Compute the weekly wage loss

• Hourly rate: $22.50
• Hours per week: 15

Weekly loss = $22.50 × 15 = $337.50

Step 2: Determine the SOL window (Georgia default/general: 1 year)

Georgia’s default/general SOL is 1 year under O.C.G.A. § 17-3-1, so DocketMath limits included wages to those attributable to a 1-year lookback ending at the claim filing reference date.

• Work stopped (start): 2024-01-15
• Claim filed (end reference): 2025-02-10

A 1-year lookback from 2025-02-10 reaches back to 2024-02-10.

SOL-eligible time range (by date): approximately 2024-02-10 through 2025-02-10.
Wages attributable to time before 2024-02-10 would be excluded in this default SOL calculation.

Warning (boundary effect): This worked example uses the general/default 1-year SOL from O.C.G.A. § 17-3-1 because no claim-type-specific sub-rule was found in the jurisdiction data. If a different SOL applies, your eligible window could be different.

Step 3: Overlap the SOL window with the claimed period

Your inputs include:

• Weeks of backpay claimed: 40
• Claimed start date: 2024-01-15
• Claimed duration: 40 weeks

So the tool effectively estimates a claimed date range beginning 2024-01-15 and covering those 40 weeks, then includes only the portion of that claimed range that falls inside the SOL-eligible lookback window.

In this example, the first part of the claimed period (from 2024-01-15 up to 2024-02-10) falls outside the 1-year lookback start, so only the remainder is SOL-eligible.

A practical way to estimate the overlap (consistent with the example’s provided numbers) is:

• Excluded early period: about 4 weeks
• Therefore eligible overlap: 40 − 4 = 36 weeks

Step 4: Convert eligible weeks to an estimated backpay amount

Included backpay = weekly loss × eligible weeks
= $337.50 × 36
= $12,150.00

Step 5: Apply offsets (if any)

• Interim payments / offsets: $0

Net estimated wage backpay = $12,150.00

Output summary (example result)

• Estimated wage backpay (Georgia default SOL, 1-year window): $12,150.00

Gentle reminder: This is a worked estimate, not legal advice. Real backpay calculations can involve additional factors (proof of time worked, specific wage components, and how the facts map to the governing legal rules).

Sensitivity check

Backpay estimates can change meaningfully when you move dates around the edges of the SOL window, even if your wage rate stays the same—because the result is driven by overlap, not just arithmetic.

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.

What to vary and what to watch

Use these “what-if” changes to see how sensitive the estimate is:

Date variations (most sensitive near the boundary)

• Move the claim reference date forward (shifts the lookback window later)
• Move the claim reference date backward (shifts the lookback window earlier)
• Keep your start date and weeks of backpay claimed consistent; inconsistent inputs can create a mismatch between the claimed timeframe and the SOL overlap.

Wage variations (more predictable)

• Increase hours/week → increases backpay linearly within the same eligible-week count
• Increase hourly rate → increases backpay linearly within the same eligible-week count
• Add offsets → decreases net backpay by the offset amount (within the tool’s handling)

Quick quantitative sensitivity (using the same 36 eligible weeks overlap)

Baseline:

• Weekly loss: $337.50
• Eligible weeks: 36
• Baseline backpay: $337.50 × 36 = $12,150.00

If hourly wage increases from $22.50 → $25.00:

• New weekly loss = $25.00 × 15 = $375.00
• New backpay = $375.00 × 36 = $13,500.00
• Change = +$1,350.00

If hours/week increases from 15 → 18:

• New weekly loss = $22.50 × 18 = $405.00
• New backpay = $405.00 × 36 = $14,580.00
• Change = +$2,430.00

Date sensitivity is overlap-based (not linear)

Even small date moves can:

• bring additional weeks into the 1-year window, or
• push weeks out of the window.

Practical approach: run at least 2–3 date variants:

• the date you intend to use, plus
• a variant a few weeks earlier and a few weeks later

Then compare results to understand how close you are to the SOL boundary.

Related reading

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