How to run Settlement Allocator in DocketMath for Virginia

Step-by-step

Run this scenario in DocketMath using the Settlement Allocator calculator.

You can run DocketMath’s Settlement Allocator for Virginia (US-VA) to produce an allocation-style breakdown of settlement amounts using jurisdiction-aware rules. This walkthrough focuses on what to enter, what the outputs mean, and how to sanity-check results so your spreadsheet exports are ready for workflow.

1) Start in the correct tool

1. Open Settlement Allocator: /tools/settlement-allocator
2. Confirm the jurisdiction is set to Virginia (US-VA) (or select it if prompted).

What to look for

• A jurisdiction selector showing US-VA
• Any “jurisdiction-aware rules” toggle or label

2) Choose the allocator mode (if available)

Some setups let you choose between allocation styles (for example, “multi-category” vs. “standard” workflows). If you see a mode selector:

• Select the mode that matches the number of categories your matter tracks internally.
• If you only need a simple split, pick the simplest mode that still captures your required components.

3) Enter settlement totals first

Before allocating anything, input the settlement’s total amount.

Use a single “Total settlement” number so the allocator can distribute across categories.

**Inputs to provide (typical)

• Total settlement amount (e.g., 250000)
• Currency (usually USD)
• Any “already allocated” amounts (only if your DocketMath screen includes that field)

4) Add category amounts or basis values

Settlement Allocator generally needs one of the following:

• Category amounts to allocate (e.g., “pain and suffering,” “medical,” “wage loss”), or
• Basis values/weights that determine how DocketMath computes allocations.

Use whatever your DocketMath screen asks for. The key is consistency:

• If you provide explicit category amounts, keep them aligned to how your case documentation labels damages.
• If you provide weights, ensure the weights are proportional to the evidence you plan to rely on.

**Quick example (basis values/weights approach)

• Total settlement: 250000
• Categories: 3 lines (Medical, Lost wages, Other damages)
• If you enter basis values (e.g., 40000, 60000, 150000), the allocator distributes amounts based on those basis inputs while preserving proportional relationships (subject to rounding).

5) Add any required deductions or exclusions (Virginia workflow)

If the calculator asks for items like:

• Attorneys’ fees (or fee percentage)
• Costs
• Medical liens / reimbursement placeholders
• Prior payments

…enter them using the format the tool expects (amount vs. percentage).

Why this changes outputs

• If you enter deductions, DocketMath will typically allocate the net amount remaining after those deductions, or it may show allocations in both gross and net form depending on what the UI offers.

6) Ensure Virginia-specific rules are enabled (when prompted)

Because you’re using US-VA, DocketMath may apply jurisdiction-aware formatting, grouping logic, or allocation constraints tied to Virginia workflows.

On-screen cues can include:

• “Virginia rules applied”
• A label describing how the tool structures output categories

If there’s a checkbox or dropdown, keep it enabled for US-VA so the output aligns with Virginia-oriented assumptions.

7) Review the allocation table

After clicking Calculate (or similar), review:

• Total settlement vs. total allocated
• Each category line item
• Any computed net totals after deductions

What you should verify

• The allocated sum equals the expected net or gross total (often within rounding)
• No category shows 0 unexpectedly unless that’s intentional
• The tool’s category naming matches what you’ll export to your case management system

Quick checklist

8) Export or copy outputs for your workflow

Many DocketMath tools let you:

• Copy a summary
• Export to CSV/Excel-ready format
• Download a report view

Export only after you confirm totals and category mapping so downstream steps don’t require rework.

Practical workflow tip

• Save a “v1” export before you adjust inputs.
• If you change one input (like fee or lien amounts), re-run and compare totals.

9) Run a sensitivity test (change one input at a time)

To ensure the allocator behaves predictably:

• Change one parameter at a time (for instance, adjust “Total settlement” by 1,000)
• Re-run
• Confirm that category allocations scale as expected

This is especially useful when:

• You entered weights rather than explicit category amounts
• You used percentage-based deductions

Common pitfalls

Settlement allocation workflows most often fail due to mismatched inputs, inconsistent categories, or misunderstandings about whether the tool allocates gross or net amounts. Watch for these issues:

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

Pitfall: Mixing “amounts” with “weights”

If your DocketMath screen offers both approaches, don’t mix them accidentally across categories.

• Example: you enter “Medical = 40000” (amount) but “Lost wages = 0.6” (weight)
• Result: the allocator may interpret numbers literally and skew outputs.

✅ Fix: Use the same input style consistently (all amounts or all weights) as the UI intends.

Pitfall: Entering deductions as both percentage and amount

Some tools accept:

• Fee as a percentage, plus
• Costs as an amount

If you enter costs twice (once directly and once as part of a prior total), allocations may become too small.

✅ Fix: Confirm what DocketMath expects—does it compute deductions automatically from percentages, or do you provide net already?

Pitfall: Category totals not aligned to your settlement breakdown

If your settlement memo says:

• Medical: 55,000
• Lost wages: 30,000
• Non-economic: 165,000

…but DocketMath output is driven by different numbers (weights or alternate categories), you’ll see a mismatch even if the math is internally consistent.

✅ Fix: Align your category labels and the values you enter with the underlying documentation you’re using.

Pitfall: Assuming results are automatically “final”

Allocation outputs are often structured estimates based on inputs. Even with correct tool execution, you may still need internal review because:

• Rounding may differ by line
• Some matters require category mapping rules not present in the tool UI

✅ Fix: Run a sensitivity test and reconcile totals before exporting to a document workflow.

Pitfall: Forgetting the jurisdiction selection

If you accidentally run the tool with a different jurisdiction than US-VA, category structures or rule constraints might not match your expectations.

✅ Fix: Verify the jurisdiction field shows Virginia (US-VA) immediately before calculating.

Try it

1. Open Settlement Allocator: /tools/settlement-allocator
2. Set jurisdiction to Virginia (US-VA).
3. Use a small test dataset first:

   • Total settlement: 25000
   • Add 2–3 categories
   • Enter deductions only if the UI requires them

Then do this quick validation pass:

• ☐ Allocated total equals expected gross/net (within rounding)
• ☐ Categories match the count you entered
• ☐ One-change sensitivity test scales line items predictably

When you’re satisfied, re-run with your real values and export the final output.

Tip: If your first run fails to reconcile totals, don’t keep changing multiple fields. Reset to your “v1” inputs and verify the meaning of each field (amount vs. weight; gross vs. net) in the UI.

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado