How to run Settlement Allocator in DocketMath for Alabama

Step-by-step

Run this scenario in DocketMath using the Settlement Allocator calculator.

Follow these steps to run Settlement Allocator in DocketMath for Alabama (US-AL) using jurisdiction-aware rules. This guide focuses on operational setup—what to enter, what to expect, and how to validate results. (This is not legal advice; it’s a workflow for using the calculator.)

1) Open the correct tool

1. Go to /tools/settlement-allocator.
2. Confirm the jurisdiction is set to Alabama (US-AL).

   • If the UI offers jurisdiction selection, choose US-AL before entering any amounts.

2) Identify the settlement components you need to allocate

Settlement Allocator is designed for allocating a single settlement amount across buckets that can be important for reporting and downstream calculations (for example, different payment types or claim categories, depending on what the tool supports).

Before you start typing numbers, create a quick internal list of what the settlement should represent in your case file. Typical buckets you might see or use include:

• Bodily injury / personal injury
• Property damage
• Medical expenses
• Lost wages
• Other damages
• Attorneys’ fees and costs (if the tool supports separate treatment)
• Interest (if the tool supports it)

If you’re unsure which bucket maps to your agreement language, use your settlement agreement’s headings and payment breakdown (if any) as the source of truth for category intent.

3) Enter the settlement amount and inputs

In DocketMath’s Settlement Allocator UI:

1. Enter the total settlement amount (the gross amount before any internal allocation).
2. Add the allocation basis inputs the tool requests. Common patterns include:

   • Known amounts per category (if the settlement agreement or demand provides numbers)
   • Or percentage allocations (if you only have proportions)
   • Or evidentiary weights / ratios (if the tool supports an evidence-based approach)

Use the direction implied by the calculator fields:

• If the form asks for amounts, input dollar figures per bucket.
• If it asks for percentages, make sure they sum to 100% (or the UI will show a validation warning).
• If there are optional categories (like interest or “other damages”), include them only when they materially exist in your agreement or your internal allocation memo.

4) Confirm Alabama jurisdiction-aware logic is active

Because this is for US-AL, verify that:

• The tool displays “Alabama (US-AL)” (or equivalent).
• Any toggle labeled something like jurisdiction rules or US-AL treatment is enabled.

If your results look inconsistent, the first thing to check is not the math—it’s whether the jurisdiction-aware rule set switched to the wrong state.

5) Review the allocation outputs

After you submit (or after you finish entering inputs, depending on the tool UX), Settlement Allocator generates outputs such as:

• Allocated amounts per bucket
• Residual / remainder handling (how rounding or “unassigned” portions are distributed)
• Totals check (ensuring allocations reconcile back to your settlement total)

You should validate at least three things:

1. Reconciliation

   • Do the bucket totals add up to the settlement total (within rounding tolerance)?
2. Rounding

   • Does the tool display rounding behavior (e.g., to the nearest cent)?
3. Category completeness

   • Are there categories left at $0 because you didn’t include them—or because you didn’t have inputs?

6) Export or copy the results for your workflow

If DocketMath provides export/copy options (PDF, CSV, or a structured table you can copy), do this before making edits. That way you can compare “before vs. after” when you refine inputs.

A practical approach:

• Run once with your best estimate.
• Save/copy the output.
• Adjust inputs only where the tool indicates validation issues or where the agreement language clearly supports a different allocation.

7) Perform a quick sanity check before relying on outputs

Even when the UI validates totals, still do a human check:

• Does the largest bucket align with the biggest claimed damages category in your documents?
• Are attorneys’ fees/costs treated in the way your agreement indicates (if applicable)?
• Do you see a meaningful amount in “interest” only if your settlement explicitly includes it?

Common pitfalls

Settlement Allocator is fast, but jurisdiction-aware behavior means small input mistakes can produce large output changes. Use this checklist before finalizing:

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

Input & math pitfalls

• Example: entering fees both as their own bucket and also embedding them in a “gross settlement” assumption

  • If you enter values with more than two decimals, the tool may round bucket outputs and shift pennies to residual handling

Agreement mapping pitfalls

• Payment language matters: “settlement of claims” isn’t always equivalent to “payment for medical expenses” for allocation purposes.

  • If your only information is “total settlement,” you may need to choose an allocation basis supported by your agreement or internal documentation.

Validation pitfalls

• If the UI flags totals mismatch or category gaps, fix those before exporting.

Try it

Here’s a quick way to test the workflow with a realistic “first run” approach. You can use approximate numbers to validate behavior before using your final figures.

1. Open /tools/settlement-allocator.
2. Set Alabama (US-AL).
3. Enter a total settlement amount.
4. Add 2–4 core buckets first (for example: medical expenses, lost wages, other damages, and property damage if relevant).
5. Leave optional categories off initially (like interest) unless you know they apply.
6. Run the allocation and review:

   • Bucket totals
   • Any remainder handling
   • Whether the UI reports any mismatches

Once the tool behaves as expected:

• Re-run using your actual figures.
• Copy/export the final output.

If you want to iterate efficiently, use this ordering:

• Fix jurisdiction selection first (US-AL).
• Fix allocation type next (amount vs. percentage).
• Then adjust only the buckets that conflict with your settlement paperwork.

Related reading

• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado
• Settlement Allocator Guide for Connecticut