Worked example: Damages Allocation in Georgia

Example inputs

This worked example shows how DocketMath allocates damages across multiple time windows in Georgia using a jurisdiction-aware assumption based on the general statute of limitations (SOL) for civil actions.

Here is a simple illustration for Georgia. These values are for demonstration only and should be replaced with your actual inputs.

• Principal or amount: $100,000
• Rate or cap: 10%
• Start date: 2025-01-15
• End/as-of date: 2025-09-30

Scenario (Georgia)

A plaintiff sues a defendant for damages tied to a continuing dispute that spans these dates:

• Alleged start of harm: January 1, 2023
• Alleged end of harm: December 31, 2024
• Filing date (complaint): January 10, 2025

DocketMath’s damages-allocation calculator is designed to allocate potential damages into:

1. Time within the SOL window (potentially recoverable), and
2. Time outside the SOL window (typically treated as time-barred in the model)

Jurisdiction rule used (Georgia general/default)

Georgia’s general SOL period is 1 year, governed by:

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

Per the provided jurisdiction data, no claim-type-specific sub-rule was found, so this example uses the general/default period as the controlling limitation in the calculator.

Monetary inputs

Assume the plaintiff claims damages that accrue evenly over time:

• Total claimed damages (lump sum): $120,000
• Accrual method: straight-line over the harm period
• Harm period length: Jan 1, 2023 → Dec 31, 2024 (730 days)

DocketMath will translate the SOL window into a fraction of the harm period and allocate the total damages accordingly.

DocketMath inputs (what you’d enter)

Use DocketMath’s /tools/damages-allocation flow like this:

• Jurisdiction: US-GA
• Statute of limitations basis: **General/default (O.C.G.A. § 17-3-1 — 1 year)
• Harm start date: 2023-01-01
• Harm end date: 2024-12-31
• Filing date: 2025-01-10
• Total claimed damages: 120000
• Allocation method: Pro rata by days

You can launch the tool here: /tools/damages-allocation.

Example run

Run the Damages Allocation 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 SOL cutoff date

With a 1-year general SOL under O.C.G.A. § 17-3-1, DocketMath treats the recoverable window as the period beginning:

• Filing date: January 10, 2025
• Start of SOL window: January 10, 2024

So in this model:

• Days on/after 2024-01-10 are considered within the limitations period.
• Days before 2024-01-10 are considered outside it.

Step 2: Translate the window into dates within the harm period

Your harm period runs from:

• Start: 2023-01-01
• End: 2024-12-31

Break it at the SOL start date 2024-01-10.

A) Outside SOL window

• 2023-01-01 through 2024-01-09

B) Within SOL window

• 2024-01-10 through 2024-12-31

Step 3: Allocate by pro rata days

DocketMath uses a days-based proportion.

For clarity, here’s a quick day count (using the ranges above):

• Total harm days: 730
• Days outside SOL:

  • From 2023-01-01 to 2024-01-09 = 374 days
• Days within SOL:

  • From 2024-01-10 to 2024-12-31 = 356 days

Compute the recoverable fraction:

• Recoverable fraction = 356 / 730 ≈ 0.4870
• Time-barred fraction = 374 / 730 ≈ 0.5130

Step 4: Allocate total claimed damages

• Within SOL window recoverable (modeled):
  $120,000 × 0.4870 ≈ $58,440

• Outside SOL window (modeled as time-barred):
  $120,000 × 0.5130 ≈ $61,560

Results table (what the calculator produces conceptually)

How this ties to Georgia law (in this example)

Georgia’s O.C.G.A. § 17-3-1 supplies the 1-year general/default period. Since your dataset indicates no claim-type-specific sub-rule, DocketMath applies that general period to create the modeled allocation window.

Sensitivity check

Small changes in key dates can shift the allocation fraction. DocketMath is particularly useful here because the model updates the SOL cutoff and pro rata fractions immediately.

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 test: filing date moves by 30 days

Keep everything else the same (same harm start/end and total damages), but move the filing date:

• Original filing date: 2025-01-10
• Revised filing date: 2024-12-11 (30 days earlier)

Recompute the SOL window start

• New SOL window start = filing date − 1 year
• New start = 2023-12-11

Now within the harm period, more of the 2023 portion becomes “within SOL” compared to the original run.

Practical effect on allocation (illustrative)

• Earlier filing date → earlier SOL cutoff → larger recoverable window
• That increases the “Within SOL window” share and reduces the time-barred share.

Quick comparison view (directional)

Sensitivity test: harm end date extends 6 months

Now keep the filing date fixed at 2025-01-10, but extend the harm end date:

• New harm end: June 30, 2025 (instead of Dec 31, 2024)

In this model:

• The recoverable window remains capped by the SOL rule relative to the filing date.
• Any harm after the filing date typically won’t increase “suit-timing” value unless you structure your accrual dates accordingly.
• DocketMath will nonetheless change the denominator (the harm period length) used for the pro rata allocation.

What DocketMath changes in this model

• It updates the harm period you supply, which changes pro rata fractions.
• The SOL rule itself is unchanged in this scenario.

Sensitivity checklist (what to vary in DocketMath)

Use these toggles to stress-test your allocation:

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules