How to run Wrongful Death Damages in DocketMath for Georgia
6 min read
Published March 26, 2026 • Updated April 23, 2026 • By DocketMath Team
Trust release 4
This page includes a legal claim or source that failed the current primary-source review.
Step-by-step
This guide walks you through running Wrongful Death Damages in DocketMath for Georgia (US-GA) using jurisdiction-aware rules. It focuses on how to set up inputs and interpret outputs so you can model damages consistently in your workflow. (This is not legal advice; treat the results as an analysis aid.)
1) Start the correct DocketMath calculator
- Open the Wrongful Death Damages tool:
- Primary CTA: Wrongful Death Damages
- Confirm the jurisdiction is set to Georgia (US-GA).
- If the interface asks for jurisdiction, select Georgia.
2) Enter the core wrongful-death damages inputs
In DocketMath’s wrongful-death-damages workflow, you’ll typically supply items such as:
- Decedent details (e.g., age at death, or other demographic inputs the calculator requests)
- Economic loss inputs (often income-related figures, employment status, or earnings assumptions)
- Benefits / household contributions (if prompted)
- Loss duration / horizon (if prompted—sometimes tied to life expectancy or an assumed future period)
- Adjustment factors the calculator supports (for example, growth rates, discounting, or similar modeling parameters)
Because wrongful-death modeling is math-heavy, your goal is accuracy in the numbers you control. For example, if you input:
- a higher assumed future income, economic damages outputs generally increase
- a longer modeled period/horizon, total present-value losses generally increase
- different discounting/growth settings, outputs can shift meaningfully
3) Set the statute of limitations (SOL) context using Georgia’s general period
DocketMath’s jurisdiction-aware rules include timing constraints. For Georgia, use the general/default SOL period:
- General SOL Period: 1 year
- General Statute: O.C.G.A. § 17-3-1
Key clarity (important): No wrongful-death-specific sub-rule was found in the provided jurisdiction data. That means you should treat the SOL guidance as the general default period for this setup.
Note: Georgia’s general SOL period of 1 year is sourced from O.C.G.A. § 17-3-1. Based on the provided data, there isn’t a claim-type-specific override applied. When DocketMath uses this timing rule, it should reflect that “default” assumption rather than a wrongful-death-tailored period.
Practical effect in the calculator:
If DocketMath offers a “timing / filing window” input, you’ll likely see outcomes or flags that depend on whether a filing date is within a 1-year window under the general O.C.G.A. § 17-3-1 assumption.
4) Verify dates and calculate whether the matter is “within the window”
To make the SOL modeling actionable:
- Enter the relevant trigger date that the calculator expects (commonly the date of death, depending on how the tool is structured).
- Enter your planned filing date (or “as-of” date), based on how the interface frames it.
Then review how DocketMath responds:
- If the filing date is within 1 year, the tool typically shows a “timely” indicator (wording varies by UI).
- If it’s after 1 year, you may see warnings, timing notes, or a less favorable timing status.
If the output includes a status alongside the damages results, don’t ignore it. Timing indicators can affect how someone summarizes case risk, even when the damages math produces large numbers.
5) Review outputs: damages breakdown and sensitivity points
After you run the calculation, examine:
- Total wrongful-death damages (present value) (or equivalent summary)
- Any economic components (if separated)
- Any time-based/rate-based components (growth/discount assumptions and/or modeled horizon)
A practical validation approach is to run quick “what-if” checks:
- Increase/decrease income by a known percentage (e.g., ±10%)
- Shift the modeled duration/horizon (e.g., shorten/extend by 1 year)
- Change growth/discount assumptions if the tool allows it
Expected directional behavior (typical modeling):
- Higher earnings → higher economic damages
- Longer horizon → higher totals (subject to discounting)
- Higher growth rates (if applied) → higher future value streams, typically increasing present value
6) Save, export, or capture results for your workflow
If DocketMath provides export/download or copyable outputs:
- Capture the jurisdiction label (US-GA), the SOL assumption (O.C.G.A. § 17-3-1), and the inputs used.
- Keep a record of your assumptions (income, dates, and any rates), especially if you’ll rerun the model with updated facts.
This makes it easier to explain changes between runs and to maintain consistent Georgia default timing assumptions (the 1-year general period from O.C.G.A. § 17-3-1) across your workflow.
Common pitfalls
Wrongful death damage modeling fails most often due to inconsistent assumptions rather than errors in the arithmetic. Watch for these issues in DocketMath runs for Georgia (US-GA):
- Ensure the tool is applying 1 year from O.C.G.A. § 17-3-1 as the general default period (since no claim-type-specific override is included in the provided jurisdiction data).
- If the tool asks for a date, use the date type it expects (for example, date of death vs. another milestone date). A mismatch can flip whether results appear “within the window.”
- If you rerun the calculator, record what changed (income, duration, growth/discount, or dates). Without this, it’s hard to tell why totals changed.
- Small changes to income, growth, or horizon can produce large swings in present-value totals.
- A calculation can produce large numbers while still showing timing concerns under O.C.G.A. § 17-3-1 (1 year) when using the default assumption.
Warning: If a case involves dates just over the 1-year default window under O.C.G.A. § 17-3-1, DocketMath may flag timing status—even if damages inputs produce high totals. Treat timing indicators as a separate risk dimension from damages math.
Try it
Follow this quick run checklist to get a clean first pass in DocketMath for US-GA:
- totals
- breakdowns
- any SOL/timing indicators
If you want a faster sanity check, do one controlled sensitivity adjustment:
- Run #1 with your best estimate inputs
- Run #2 with income adjusted by a small percentage (e.g., ±10%)
- Compare how the total changes
Here’s a simple interpretation table you can use while testing:
| Change you make | Typical effect on damages output |
|---|---|
| Increase assumed future income | Total damages increases |
| Shorten modeled duration/horizon | Total damages decreases |
| Move filing date beyond 1 year from the trigger date | Timing/status output shifts to “outside default SOL window” under O.C.G.A. § 17-3-1 |
| Update growth/discount assumptions (if available) | Output total shifts (direction depends on parameter direction) |
Once the model behaves as expected, iterate with updated facts (income updates, revised dates, or different horizon assumptions) while keeping the Georgia default timing framework consistent in each run.
