Spreadsheet checks before running Damages Allocation in Oregon

What the checker catches

Running a Damages Allocation in Oregon usually fails for one of three reasons: (1) the spreadsheet is internally inconsistent, (2) the inputs don’t match the calculation logic you intend, or (3) the Oregon-specific assumptions embedded in the tool don’t line up with how your case’s claims actually flow.

DocketMath’s spreadsheet-checker for Damages Allocation (US-OR) is designed to catch those issues before you generate allocations. It focuses on the most common spreadsheet problems that cause downstream allocation results to be wrong or unstable.

1) Missing or mismatched charge components

If your spreadsheet includes columns for typical damages components—such as economic damages, non-economic damages, interest, attorney fees, or costs—the checker verifies that:

• every required component has a value (or is clearly marked as intentionally zero/omitted),
• totals reconcile to the underlying line items,
• units and formats are consistent (for example, not mixing dollars and percentages in the same field).

2) Arithmetic and aggregation errors

The checker looks for internal math faults, including:

• totals that don’t equal the sum of line items,
• negative values where they usually shouldn’t appear in allocation inputs,
• double-counting—when the same figure appears both as a component and again as a subtotal.

3) Timeline and rate inputs that can’t support an allocation

Damages allocation workflows often depend on timing inputs (for example, when damages began and ended, and what rate applies). The checker verifies that:

• dates are valid calendar dates,
• date order is logical (start ≤ end),
• rate fields are numeric and in an expected usable range,
• day-count logic is consistent across rows (so the same basis is applied where it should be).

4) Oregon jurisdiction-aware rule alignment (US-OR mapping)

DocketMath applies US-OR jurisdiction-aware checks to help ensure your spreadsheet structure aligns with the Oregon Damages Allocation workflow you selected. This includes verifying that your inputs map cleanly to the tool’s allocation schema—for example:

• the sheet includes the expected claim/damages categories,
• the allocation driver columns are present and positioned in a way the tool can read.

5) Output risk indicators (stability checks before you commit)

Even before running the full allocation, the checker can warn when inputs are likely to produce unstable results, such as:

• allocation bases that sum to zero,
• extreme ratios (for example, one bucket at ~99.9% with others near zero),
• inconsistent number formatting that can cause the tool to misread values.

Below is a quick checklist of the kinds of issues the checker typically flags:

When to run it

Run the spreadsheet-checker at specific points in your workflow—because the goal is to prevent avoidable errors from flowing into allocation results you may later need to explain or revise.

Run the checker before importing a spreadsheet into the Damages Allocation workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.

Run it:

• After you enter or import damages line items, before you start relying on totals.
• After you revise dates or rates, especially if you copy/paste rows across damages buckets.
• Before generating the final allocation you plan to submit, file, or circulate.

Avoid running it only at the end if:

• you suspect arithmetic issues,
• you performed any manual copy/paste,
• you adjusted assumptions multiple times (timeline, rate basis, or categories).

Try the checker

You can try the workflow in DocketMath using the jurisdiction-aware Damages Allocation (US-OR) tool. The checker step validates structure, math, and mapping without generating allocations right away.

Upload the spreadsheet, review the warnings, and then run the calculation once the inputs are clean: Try the checker.

Step-by-step (practical workflow)

1. Open DocketMath and navigate to the Damages Allocation checker.
2. Select jurisdiction: US-OR.
3. Upload or paste your spreadsheet used for damages allocation.
4. Run the spreadsheet-checker (validation runs first; allocations come later).
5. Review the flagged items and apply fixes:

   • add missing values (or confirm intentional zeros),
   • correct totals that don’t reconcile,
   • fix date order and rate formats,
   • adjust category mapping if the tool can’t match your columns.
6. Re-run the checker until you clear major warnings.
7. Only then run Damages Allocation.

Inputs that change outputs (what to watch)

Re-run the checker whenever you change any of the following, because they directly affect allocation results:

• Start/end dates (time-based calculations),
• rate fields (anything interest-like or time-based),
• damages category amounts (allocation proportions),
• any driver columns that determine how amounts allocate across parties or buckets.

What to expect from the output

After you clear checker issues, allocation results should be more stable and internally consistent. You’ll also get improved traceability between:

• line-item inputs,
• intermediate totals,
• final allocation outputs.

Primary CTA

Use DocketMath here: **/tools/damages-allocation

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