Pre/Post-Offer Damages Split Guide for Georgia
8 min read
Published April 8, 2026 • By DocketMath Team
What this calculator does
Run this scenario in DocketMath using the Pre Post Offer Damages calculator.
DocketMath’s Pre/Post-Offer Damages Split calculator helps you divide a damages total into two time-based components for Georgia:
- Pre-offer damages: damages incurred before a qualifying offer date
- Post-offer damages: damages incurred on/after that offer date
This split is commonly used in litigation workflows where later-period amounts may be treated differently than earlier-period amounts, especially in disputes involving offers and related post-offer computations.
Georgia timing rule used in this guide
Georgia’s general statute of limitations (SOL) period is:
- 1 year under 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 default: No claim-type-specific sub-rule was identified in the prompt beyond the general rule. That means this guide uses the general/default 1-year SOL as the baseline timing concept—not a specialized SOL for particular causes of action.
Note: This guide is about how to split damages around an offer date and how Georgia’s general 1-year SOL (O.C.G.A. § 17-3-1) fits into timeline planning. It is not legal advice.
When to use it
Use the DocketMath pre-post-offer-damages tool when you have all (or most) of the following:
- A specific offer date you are anchoring the calculation to (e.g., the date the offer was served/accepted/extended, depending on your case workflow)
- A damages figure that accrues over time (or that you can reasonably allocate across time)
- A need to estimate or document how much of total damages is associated with:
- the period before the offer, versus
- the period after the offer
Practical use cases (non-exhaustive)
Damages with a time component
Examples include damages that accrue daily/weekly/monthly and can be expressed as an amount over a date range.Time-window documentation
You might need a clean ledger of what portion of damages falls within (or outside) a lookback window tied to SOL concepts—especially when comparing event dates to filing dates.Settlement/offer analysis workflows
Many civil practice workflows track “what changed after the offer” even when the legal standard depends on case posture. This tool supports the accounting split—not the legal conclusion.
Step-by-step example
Below is a concrete walk-through using DocketMath and Georgia’s general 1-year SOL framework as a timing reference point.
You can run the calculator directly here: /tools/pre-post-offer-damages.
Example inputs
Assume the following facts for a damages-accrual period:
- Offer date: March 15, 2025
- Damages accrue evenly over time
- Total damages period you’re analyzing: January 1, 2025 → May 15, 2025
- Total damages for the full period: $12,000
We’ll split the $12,000 into:
- pre-offer: January 1, 2025 → March 14, 2025
- post-offer: March 15, 2025 → May 15, 2025
Step 1: Establish your analysis date range
Make sure your “full period” is clearly defined:
- Start date (left boundary)
- End date (right boundary)
- Whether the offer date counts in pre or post (the tool generally treats the offer date as belonging to the post side based on the “on/after” framing—confirm the tool’s exact convention in your run)
Step 2: Convert the full time window into day counts
For even accrual, a day-based split is typical:
- Pre-offer window: Jan 1 to Mar 14, 2025
- Post-offer window: Mar 15 to May 15, 2025
Once you have day counts, you can allocate damages proportionally.
Step 3: Allocate damages by time proportion
Let:
- TotalDays = days in the full period
- PreDays = days before the offer
- PostDays = days from the offer through the end of the period
Then:
- Pre-offer damages = Total damages × (PreDays / TotalDays)
- Post-offer damages = Total damages × (PostDays / TotalDays)
Example calculation (illustrative)
If the full period were 135 total days, with:
- PreDays = 73 days
- PostDays = 62 days
Then:
- Pre-offer damages = $12,000 × (73/135) ≈ $6,489
- Post-offer damages = $12,000 × (62/135) ≈ $5,511
Step 4: Check SOL timing logic using Georgia’s general rule
Georgia’s general SOL is 1 year under O.C.G.A. § 17-3-1.
So if you are assessing whether damages tied to an older time segment fall outside a typical 1-year lookback window (for SOL planning), you’d compare:
- the event/accrual dates you are splitting, and
- the relevant filing date (or other milestone tied to SOL analysis in your workflow)
Because this guide uses the general/default period (not a claim-specific rule), treat it as a baseline timing screen.
Warning: A SOL framework can affect which damages time periods are recoverable, but this tool’s job is to compute an allocation split. Whether portions are recoverable depends on claim-specific legal elements you should confirm in your case materials.
Step 5: Validate results against your damages model
Even accrual assumptions can be wrong. If your damages accrue unevenly (e.g., higher in some months), you’ll need either:
- a more granular time series input, or
- an adjusted method that matches how your damages were actually calculated.
Common scenarios
These are patterns you’ll likely encounter when using the pre/post split in Georgia workflows.
Scenario 1: Even monthly accrual, one offer date
Facts
- Damages calculated on a steady monthly schedule
- One offer date divides the timeline
How to approach
- Use day counts or month-by-month approximations consistently
- Ensure the offer date is assigned to post (or pre) consistently with the tool
Output you expect
- Two totals that sum to your original total (or very close, depending on rounding rules)
Scenario 2: Irregular accrual (step changes)
Facts
- Damages increase after a certain event (not just after the offer)
How to approach
- Split your damages timeline into “rate segments”
- Run the calculator separately per segment, or input dates in a way that reflects the segment changes
Output you expect
- A pre/post split that reflects both:
- rate changes, and
- the offer-date boundary
Scenario 3: Offer date outside the damages window
Facts
- Your damages period ends before the offer date, or begins after it
How to approach
- If the offer date is after your damages end: expect all damages to land in pre-offer
- If the offer date is before your damages start: expect all damages to land in post-offer
Output you expect
- One side likely becomes $0 (subject to rounding)
Scenario 4: SOL-aware timeline review
Facts
- You want to compare your accrual period against Georgia’s 1-year baseline in O.C.G.A. § 17-3-1
How to approach
- Use your split to identify how much of the total is older/newer relative to your relevant SOL window
- Then decide what portions you want to keep in your model or exhibits
Output you expect
- A split that helps you label “older vs newer” damages with clarity
Pitfall: Using the general 1-year SOL (O.C.G.A. § 17-3-1) as a substitute for claim-specific SOL analysis can lead to overinclusive damages periods. The calculator can still be useful for allocation, but SOL recoverability can differ by cause of action.
Tips for accuracy
A good split depends less on math gymnastics and more on consistent, auditable inputs.
1) Confirm the offer-date boundary rule you’re using
Decide whether:
- damages accrued on the offer date count as post-offer, or
- they count as pre-offer
Run everything using the same boundary rule so your totals remain internally consistent.
- If the tool uses a specific convention, follow it for your case documentation.
- If you compute day counts externally, mirror the same convention.
2) Use consistent date granularity
Pick one:
- day-based allocation (common for time windows)
- month-based allocation (common for billing cycles)
Mixing granularities (e.g., day-based for one dataset and month-based for another) can create small but annoying reconciliation differences.
3) Check for rounding and reconciliation
When you allocate by time proportions:
- fractional pennies can appear
- sums may not equal the stated total exactly
To prevent downstream confusion:
- keep more precision during calculation, then
- round only at the end (or match the calculator’s rounding output)
4) Keep an audit trail of assumptions
Your workpapers should reflect at least these items:
- offer date: ____________
- damages period start/end: ____________
- total damages model: (even accrual / step changes / monthly schedule)
- allocation method: (day-based / month-based / segment-based)
- rounding method: ____________
If you’re presenting this in a spreadsheet, label the columns with date ranges used for pre and post.
5) Use Georgia’s SOL rule as a baseline timeline screen
Georgia’s general SOL is 1 year under O.C.G.A. § 17-3-1. Use it to:
- sanity-check whether your damages lookback extends beyond a 12-month period relative to your filing milestone
- organize exhibits by “
