How to run Damages Allocation in DocketMath for Oregon

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide walks you through running Damages Allocation in DocketMath for Oregon (US-OR) using jurisdiction-aware rules. You’ll set up the calculator, confirm the allocation approach matches an Oregon workflow, and review the output so you can carry it into your docketing or case notes.

1) Open the correct tool

1. Go to /tools/damages-allocation
2. Select Oregon (US-OR) in the jurisdiction selector (if shown on the page).
3. Confirm you’re using the Damages Allocation calculator (template: damages-allocation).

2) Confirm what the calculator expects as inputs

Before entering numbers, scan the input panel for these typical categories (names may vary slightly):

• Total claimed damages (or a comparable “overall” amount)
• Categories to allocate (e.g., principal-like vs. other components, or harm components depending on your template)
• Allocation rules (the calculator’s Oregon-aware configuration)
• Timing-related inputs (if the tool includes any interest/period/date logic)
• Evidence weighting / percentages (if the model uses distribution logic)

If the UI shows toggles for allocation methodology, choose the one that best fits your Oregon workflow as reflected by the jurisdiction-aware rules in the tool.

3) Enter your totals and category amounts

For each damages category the tool lists:

• Enter the amount (numeric)
• Ensure the unit matches the calculator’s expectation (typically currency)
• If the calculator uses percentages instead of amounts:

  • Enter percentages that sum to 100%
  • Avoid rounding to whole numbers unless the tool allows tolerance

Quick consistency check

• If the UI asks for a “total” plus category splits: the tool should reconcile to the total.
• If it asks only for categories: verify the sum equals the total you plan to report.

4) Set Oregon jurisdiction-aware options

In Oregon mode (US-OR), DocketMath may apply allocation logic that differs from other jurisdictions. Look for:

• A jurisdiction label confirming **Oregon (US-OR)
• An Oregon-specific allocation rule description (often shown near a methodology dropdown)
• Any additional Oregon-specific fields (e.g., if the tool uses a period or rate input only in Oregon mode)

Adjust only the fields the UI provides for Oregon. If the tool hides fields based on jurisdiction, leave those hidden fields untouched—DocketMath is using the Oregon rule set behind the scenes.

5) Add date/timing details (only if requested by the interface)

If the calculator includes date fields (for example, a start date, an end date, or an event date):

• Use the earliest date that your docketing record recognizes as the relevant start for computation
• Use the end date tied to the event the allocation is intended to reflect (often judgment date, settlement date, or an as-of date)

Why this matters in the output: date fields can change how DocketMath computes time-based components and therefore change the category totals and the final allocation distribution.

6) Run the calculation and review outputs

Click Calculate (or the tool’s equivalent button). Then review:

• Allocated amounts by category
• Allocation percentages by category (if shown)
• Reconciliation values (e.g., “allocated total” vs. “entered total”)
• Any warnings produced by the calculator (common ones include totals mismatch or missing required fields)

If the tool provides a breakdown table, use it to validate:

• Does each category look reasonable?
• Do percentages align with the category amounts?
• Do the “allocated total” and your entered total match (or differ within any documented tolerance)?

7) Adjust inputs based on the reconciliation results

If the output shows a mismatch:

• Re-check category sums
• Re-check total vs. category reconciliation
• Correct rounding issues (e.g., $0.01 drift from percentage rounding)

A practical workflow is:

• Fix the smallest discrepancy first (usually a rounding or transposition error)
• Re-run immediately to confirm the allocator now reconciles

8) Export or copy the results for docket use

When the calculator displays results:

• Copy the final allocated amounts
• Capture any date-driven computed components
• If the interface supports download/export, save the output with a descriptive filename (e.g., OR-damages-allocation-2026-04-15)

Common pitfalls

These are recurring issues when running Damages Allocation in DocketMath for Oregon (US-OR). Watch for them before you finalize anything.

• Category totals don’t reconcile to the overall total

  • Symptom: the output shows an “allocated total” that doesn’t equal what you entered.
  • Fix: adjust category amounts or ensure percentages sum to 100%.

• Percent-based allocations rounded too aggressively

  • Symptom: small drift that grows into larger differences when scaled.
  • Fix: use the decimal precision the tool recommends (or the closest option it allows) and re-run.

• Wrong jurisdiction mode

  • Symptom: the tool displays rule text or computed fields that don’t align with Oregon expectations.
  • Fix: explicitly confirm Oregon (US-OR) is selected before running.

• Missing required timing fields

  • Symptom: the tool either blocks calculation or silently switches methodology.
  • Fix: fill date fields exactly as the interface requests, then rerun.

• Entering both “total” and category splits that conflict

  • Symptom: DocketMath uses one as the source of truth and adjusts the other.
  • Fix: decide which field should be authoritative; align both or let the tool’s reconciliation guide you.

• Not capturing the calculator’s methodology choice

  • Symptom: someone later can’t reproduce your numbers.
  • Fix: record the selected method/mode from the UI when exporting or copying results.

Try it

You can run Damages Allocation right now using DocketMath’s tool page:

• /tools/damages-allocation

To make your first run successful in Oregon (US-OR), use this quick checklist:

If you want to stress-test your setup without risking real case numbers, try a small test case:

• Use a clean round total (e.g., 10000)
• Allocate across 2–4 categories
• Use dates that are within the same month to reduce time-based complexity
• Confirm the output breakdown matches the proportional logic you expect

Once it behaves correctly with test inputs, repeat with your actual Oregon damages inputs.

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