How to run Settlement Allocator in DocketMath for Oregon

How to run Settlement Allocator in DocketMath for Oregon

6 min read

Published April 27, 2025 • Updated April 23, 2026 • By DocketMath Team

Article claim inventory in progress

Trust release 4

This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.

Step-by-step

This guide walks you through running Settlement Allocator in DocketMath for Oregon (US-OR). The focus is practical: what to enter, what to expect, and how Oregon jurisdiction settings affect the output. (This is not legal advice—think of it as a workflow for producing a structured allocation draft you can review.)

1) Open the tool

  1. Go to Settlement Allocator in DocketMath:
    Primary CTA: /tools/settlement-allocator
  2. Confirm the jurisdiction selector is set to Oregon (US-OR).
    • If your page uses a jurisdiction picker, select US-OR before inputting numbers.

2) Gather the allocation inputs you’ll need

Most settlement allocation workflows require four categories of information:

  • Total settlement amount (the gross settlement figure you want allocated)
  • Number of claimants (if more than one person/entity shares the settlement)
  • Allocation basis (how you want to weight the split—commonly via fixed amounts or proportions)
  • Any constraints or special categories (for example, separate treatment inputs you want the allocator to reflect)

Before you start typing, collect the terms that control how the settlement should be split. If you’re working from a proposed settlement agreement, pull the amounts and labeling exactly as written so your allocations are consistent.

3) Enter the case allocation structure

In the Settlement Allocator UI, you’ll typically do the following:

  • Step A: Total
    Enter the total settlement amount you want allocated across categories/claimants.

  • Step B: Claimants or allocation buckets
    Add each claimant (e.g., Plaintiff A, Plaintiff B) or each allocation bucket (e.g., damages categories) depending on how the tool is configured for your workflow.

  • Step C: Allocation method
    Choose the method that matches how you plan to justify the split:

    • Fixed amounts (you type each bucket/claimant amount)
    • Percent/proportion-based (you enter percentages or relative weights)
    • Hybrid (a mix, if supported)

If the tool supports both “percent” and “amount” entry, prefer amounts when your agreement already contains them; prefer percentages when you only have relative proportions.

4) Use Oregon jurisdiction-aware rules (US-OR)

DocketMath’s jurisdiction-aware configuration is designed to apply Oregon-specific labeling and rule mapping relevant to the allocator. The main effect you’ll notice is in how the tool organizes output and which categories it expects you to supply.

To make this concrete, watch for these behaviors after selecting US-OR:

  • The tool may display Oregon-oriented category options (or adjust which categories are preselected).
  • Validation rules may change (for example, required fields count, how totals must reconcile).
  • The output sections may use Oregon-tailored phrasing for the allocation breakdown.

If the UI shows rule toggles, keep US-OR enabled and only change toggles when your settlement agreement explicitly requires a different structure.

Note: If the allocator flags “totals don’t reconcile,” switch your approach: use one source of truth (either fixed amounts that sum to the total, or percentages that multiply to the total). Mixing can produce rounding drift.

5) Reconcile totals and rounding

After entering claimants/buckets:

  • Verify that allocated totals = settlement total (within any rounding tolerance the tool reports).
  • If you see a “difference” or “unallocated remainder,” decide how you want it handled:
    • Increase a bucket amount
    • Adjust a percentage
    • Add a designated “remainder” bucket (if the tool offers it)

DocketMath’s allocator output usually recalculates instantly. Use that feedback loop to converge on a clean reconciliation.

6) Review output and export

Once inputs validate:

  1. Review the allocation table the tool generates.
  2. Confirm each claimant/bucket line includes:
    • The allocated amount
    • The percentage (if applicable)
    • Any category mapping relevant to the Oregon workflow
  3. Check for summary totals at the bottom of the results.

Then, export or copy the output if your workflow supports it. Even if you don’t generate a formal document, keep the allocator output as a calculation record for your internal review.

7) Sanity-check the results against the settlement terms

Before you treat the output as final for a draft, do a quick consistency check:

  • Does the output reflect the same labels as the settlement agreement?
  • Are you assigning the right amounts to the correct parties?
  • Do the categories reflect the intent (for example, separate treatment where the agreement distinguishes them)?

This step prevents a common scenario: the math is correct, but the category mapping doesn’t match the parties’ agreement.

Common pitfalls

Avoid these issues—each one can change the numbers you rely on:

  • Entering both amounts and percentages without controlling rounding

    • Result: allocated totals may drift from the settlement total.
    • Fix: pick a primary method (amounts or percentages), then adjust the other method only if the UI allows precise alignment.
  • Leaving US-OR selected after switching tabs or templates

    • Result: output may reflect the wrong rule set or category expectations.
    • Fix: confirm Oregon (US-OR) before final entry.
  • Forgetting a claimant/bucket

    • Result: the allocator reallocates the missing share across remaining categories (or produces an “unallocated remainder”).
    • Fix: add all parties/categories that appear in the settlement terms.
  • Using mismatched total figures

    • Example: settlement agreement says $50,000, but you enter net payment or a different gross number.
    • Result: every allocation line is proportionally wrong.
    • Fix: ensure the “total settlement amount” matches the figure you intend to allocate.
  • Category label mismatch

    • Even when totals reconcile, wrong labeling can create downstream inconsistencies.
    • Fix: align DocketMath bucket names to the settlement agreement categories.

Warning: Rounding is not cosmetic. If the tool rounds at the line level and again at the summary level, small differences can appear—especially with percentages across multiple claimants. Treat reconciliation as part of the workflow, not an afterthought.

Try it

Ready to run your Oregon allocation draft in DocketMath?

  1. Open Settlement Allocator: ** /tools/settlement-allocator
  2. Set Jurisdiction: Oregon (US-OR).
  3. Enter:
    • Total settlement amount
    • All claimants or allocation buckets
    • Your chosen allocation method (fixed amounts vs proportions)
  4. Use the results table to verify:
    • Allocated totals match the settlement total
    • Each party/bucket appears once
    • Oregon-specific category mapping looks consistent with your settlement language

If your output shows an “unallocated remainder” or “difference,” adjust inputs until the reconciliation summary is clean—then save/export the results for review.

Related reading