Worked example: Damages Allocation in Alabama

Example inputs

This is a worked example of damages allocation in Alabama using DocketMath and jurisdiction-aware rules (jurisdiction code US-AL). It’s meant to be practical and actionable: you can see how to structure inputs for the damages-allocation calculator and how allocation outcomes change when you toggle assumptions.

Scenario

A plaintiff sues an Alabama company after a workplace incident. The complaint alleges:

• Compensatory damages for economic loss (medical bills, lost wages)
• Compensatory damages for non-economic harm (pain and suffering)
• Punitive damages (based on alleged wantonness / recklessness)

The jury returns verdicts that include both compensatory and punitive components. This example allocates the total damages into category totals you can use for downstream tasks (like reporting, offsets/credits modeling, or structured summaries).

Key numbers used in this example

We’ll assume the jury awarded:

• Economic compensatory: $120,000
• Non-economic compensatory: $80,000
• Punitive damages: $60,000
• Total before allocation: $260,000

Allocation categories in the calculator

DocketMath’s damages-allocation flow typically expects inputs you can map to major buckets, such as:

• Economic compensatory (compensatory bucket)
• Non-economic compensatory (compensatory bucket)
• Punitive damages (separate bucket)
• Optional modifiers that can affect net allocation:

  • Offsets / credits
  • Pre-judgment interest (if enabled)

For this baseline run, we keep the setup focused and include only category allocation—no offsets/credits and no interest—so you can see the “pure” category split first.

Checkbox inputs (what you would toggle in DocketMath)

Use this as a checklist for entering the same scenario:

• Economic compensatory = $120,000
• Non-economic compensatory = $80,000
• Punitive damages = $60,000

Alabama jurisdiction-aware note (why jurisdiction matters)

Alabama rules can affect how courts treat punitive damages versus compensatory damages—particularly in how punitive awards are reviewed and handled in judgment-related contexts. A jurisdiction-aware tool keeps punitive as a separate category so results remain clean, auditable, and usable for later steps (for example, reporting how much is compensatory vs. punitive).

Example run

You can replicate the baseline scenario by starting at the tool here: DocketMath Damages Allocation.

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-by-step inputs

In DocketMath (US-AL), enter the damages components like this:

After you run the calculator, DocketMath computes allocation totals by category. Those totals are what you’ll reference for reporting or next-stage calculations.

Expected allocation output (category totals)

With no offsets/interest enabled, the allocation is straightforward: the category totals should sum to $260,000.

“Jurisdiction-aware” behavior to watch

Even for a simple run, the jurisdiction-aware separation matters: punitive damages remain distinct from compensatory totals. That separation is useful if you later compute or document things like:

• How much of the judgment is compensatory vs. punitive
• Whether post-trial review logic (tool-side or workflow-side) applies to punitive portions
• How settlement credits might be allocated if you choose to model them

Pitfall to avoid: If you combine punitive and compensatory into a single “total damages” number before allocation, you lose the category granularity that Alabama-focused downstream checks often rely on.

Sensitivity check

Now test small changes to confirm your inputs map correctly to the outputs you need. Sensitivity checks are one of the fastest ways to validate whether your toggles (offsets/credits, interest, punitive) are behaving as expected.

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 A: Add a settlement credit (offsets/credits enabled)

Assume you learn there was a settlement credit of $25,000 attributable to compensatory exposure (illustration).

Change only this toggle/input:

• Include offsets/credits
• Settlement credit = $25,000
• Apply credit to: compensatory buckets (not punitive)

Expected behavior pattern

If punitive remains a separate bucket (typical in category-aware allocation), then a compensatory-only credit should reduce compensatory totals first, leaving the punitive category unchanged unless you explicitly configure otherwise.

Why this split often stays proportional: when the credit is applied only within compensatory exposure and no additional allocation instructions are provided, tools frequently maintain the original ratio between economic and non-economic compensatory.

Sensitivity B: Turn on pre-judgment interest

Suppose the tool allows adding a pre-judgment interest component and you enable it.

Example inputs (illustration):

• Include pre-judgment interest
• Pre-judgment interest amount computed by tool: $18,000

Expected output pattern

DocketMath may treat interest as either:

• its own line item, or
• a modifier applied to certain compensatory categories.

In a robust allocation workflow, punitive should remain separate even when interest is included.

Illustrative result:

Sensitivity C: Change punitive amount only

Keep compensatory fixed and change punitive to see how the total composition shifts.

Assume a new punitive figure:

• Punitive damages: $75,000 (instead of $60,000)
• Everything else unchanged

What to look for:

• The tool should not move compensatory values when punitive changes.
• Category percentages should update accordingly:

  • Punitive share rises from 23.08% ($60,000 / $260,000) to 27.27% ($75,000 / $275,000)

Quick validation checklist (before relying on outputs)

Related reading

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