How to run Damages Allocation in DocketMath for Georgia

Step-by-step

This guide walks you through running Damages Allocation in DocketMath for Georgia (US-GA) using jurisdiction-aware rules. The goal is to help you generate an allocation workflow you can review, not to provide legal advice.

• Select Georgia in the Damages Allocation tool.
• Enter the trigger dates and any caps or rates.
• Run the calculation and save the output.

1) Open the calculator for the correct tool

Go to the DocketMath calculator:

• Primary CTA: **/tools/damages-allocation

If you’re navigating from the site, you can also reach it by selecting the Damages Allocation calculator in the tools area.

2) Confirm the jurisdiction setting is Georgia

Inside the calculator, make sure the jurisdiction is set to:

• **Georgia (US-GA)

Why this matters: DocketMath applies Georgia-specific assumptions, especially around timing concepts like limitation periods. That helps your output align with O.C.G.A. § 17-3-1 rather than a different state’s rule set.

3) Enter the core damages inputs

Damages allocation depends on the damages components you’re allocating and the time basis you want reflected in the scenario. Use the calculator’s input fields to provide the amounts relevant to your situation.

Depending on the calculator UI version, you may see fields such as:

• Total claimed damages (if the tool supports a single total)
• Component amounts (damage categories you want allocated)
• Allocation basis/parameters (for example, a time window or structured criteria)

Practical approach if you’re unsure: start with the broadest inputs the tool allows (such as a total plus any allocation drivers). Then refine by adding component-level amounts only if the calculator supports them.

4) Use the Georgia timing rule for limitation period context

For Georgia, DocketMath’s configuration uses the general/default statute of limitations from O.C.G.A. § 17-3-1.

• General SOL Period (default): 1 years
• Georgia 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 clarification (per the tool’s current setup): the configuration uses only the general/default period.
No claim-type-specific sub-rule was found, so the calculator will not automatically switch to a different limitations rule based on claim category.

Warning (scope note): If your situation involves a claim type with a limitations rule different from the general default in O.C.G.A. § 17-3-1, the Georgia SOL context in DocketMath may not reflect that nuance because the current ruleset is default-only.

5) Choose allocation parameters required by “Damages Allocation”

Depending on the calculator version, you may be asked to supply inputs such as:

• A date or time horizon that determines whether damages fall inside/outside the allocation window
• Weighting factors that distribute totals across categories
• Whether you want outputs for one scenario or multiple scenarios

How to keep it accurate:

• If the tool uses a date range, double-check the start and end dates match the period you want to analyze.
• If you’re comparing alternatives (e.g., two possible windows), rerun the calculator with updated inputs rather than trying to “adjust” only one part of the output.

6) Review the outputs and verify internal consistency

After you run the calculation, DocketMath will produce an allocation breakdown. Review it for internal consistency, such as:

• Totals reconciliation: if the tool shows a total, confirm allocated components sum correctly.
• Timing logic: confirm the time-window behavior matches the 1-year general/default limitation context under O.C.G.A. § 17-3-1.
• Scenario labeling: if multiple scenarios are enabled, ensure you’re reading the scenario you intended.

Treat the results as a draft calculation/workflow based on the inputs you entered, then reconcile with your own understanding of the matter.

7) Iterate: rerun with one change at a time

If results look unexpected, the cause is often an input mismatch. A helpful debugging workflow is:

1. Change one input (for example, adjust a date or update one component amount)
2. Rerun
3. Compare the new output to the prior output

This makes it easier to identify what actually drove the difference (date range shift vs. weight vs. missing component).

Common pitfalls

Below are common issues that can cause Damages Allocation results to diverge from expectations when using Georgia settings in DocketMath.

The Georgia setup here uses the general/default period from O.C.G.A. § 17-3-1 (1 years).
No claim-type-specific sub-rule was found, so the tool won’t automatically swap limitation periods based on claim category.

If allocation depends on a date range, swapping start/end dates or using the wrong boundaries can change results dramatically.

If the tool expects components to add up to a total (when both are provided), make sure your component inputs align.

If you modify several inputs at once, it becomes hard to tell which change caused the output shift.

If the interface supports multiple scenarios, confirm you’re reviewing the correct scenario output.

Pitfall reminder: If you need a limitations rule different from the general default in O.C.G.A. § 17-3-1, the Georgia SOL context in DocketMath may not match your analysis because the current ruleset is default-only.

Try it

You can run the calculation right away using the Georgia configuration:

1. Open **/tools/damages-allocation
2. Set jurisdiction to **Georgia (US-GA)
3. Enter your damages inputs and any required time/allocation parameters
4. Run the calculation
5. Review:

   • The allocation breakdown
   • Any total reconciliation shown by the tool (if applicable)
   • The timing context tied to O.C.G.A. § 17-3-1’s general/default SOL of 1 years

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