Inputs you need for Damages Allocation in Oregon

Inputs you will need

Damages allocation in Oregon (US-OR) often turns on who caused what, when it happened, and whether any amounts are offset or apportioned. With DocketMath’s damages-allocation calculator, you’ll get the cleanest, most defensible allocation result when your inputs are complete, consistent, and easy to audit.

Before you run anything, gather the categories of information below. Think of them as the “minimum viable” inputs for allocation logic.

1) Parties and role mapping

You’ll need a clear mapping of participants so the tool can assign damages to the right places.

• Defendant(s) you want damages allocated against (names or identifiers you can match to other documents)
• Claimant / plaintiff / payee
• Role of each party, such as:

  • directly responsible party
  • contributor / other party whose conduct affects allocation
  • insurer or reimbursement recipient (if your workflow models those items)

2) Timing data (dates and periods)

Allocation is usually more reliable when you can break damages into periods that correspond to changes in conduct, responsibility, or measurable harm.

Gather:

• Date of injury / event start
• Date of event end (if there is a defined period)
• Key milestone dates that split damages into time-based buckets, for example:

  • repair or replacement start/end
  • contract termination
  • project completion
  • continuing harm vs. discrete events
• Notice dates (if your allocation approach treats notice as a turning point)

3) Damages components (line items)

Enter each damages “bucket” as its own line item so the calculator can apply the correct allocation treatment.

Common Oregon-focused component categories include:

• Economic damages

  • past lost income / wages
  • future lost income (use a defined projection period)
  • medical expenses / care costs
  • property damage or repair costs
• Non-economic damages

  • pain and suffering (only if your model or framework includes a non-economic component)
• Equitable or other categories

  • only if your workflow uses them
• Litigation costs

  • only if your allocation approach includes recoverable costs

For each component, capture:

• Total amount for the component
• Date range the component covers (when applicable)
• Any exclusions you intentionally leave out (so you don’t accidentally double count)

4) Causation / allocation drivers

To allocate, DocketMath needs factors that map to your jurisdiction-aware rules and your case narrative.

Gather:

• Causation allocation basis, such as:

  • percentage responsibility / fault
  • phase-based conduct (what happened in each phase)
  • direct vs. indirect causation split
• Evidence-backed inputs you already have (for example, an allocation table from an expert, or a breakdown by time period)
• Whether a damages component is:

  • single-source (tied to one conduct period/party), or
  • divisible (can be split across parties or time)

5) Offsets, credits, and recoveries (if used)

If your goal is net damages, you’ll need to model offsets so the calculator can reflect net recovery.

Gather:

• Prior payments (amount and date)
• Insurance or reimbursement amounts you plan to treat as offsets
• Settlements you plan to include or exclude (and how you intend to characterize their scope)
• Interest policy settings (if your workflow includes interest)

Where to find each input

DocketMath works best when you paste values from structured notes or documents you already have. Here’s a practical “where to look” guide for each input type.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

Parties and role mapping

• Complaint / answer: identifies who is alleged to have done what
• Discovery responses: often clarify roles (e.g., installer vs. designer)
• Settlement documents / stipulations: clarifies what is included in any settlement payments

Timing data

• Chronology section of briefs or case summaries
• Treatment records / repair invoices: helpful for medical or property timelines
• Contract milestones / project logs: helpful for construction or service timelines
• Notice letters and response dates

Damages components

• Damages spreadsheet (your existing model, if you have one)
• Expert reports (amounts and time windows)
• Billing records and invoices (repair/medical/care costs)
• Payroll or employment records (wage/lost income inputs)

Causation / allocation drivers

• Expert causation exhibits (often show allocation by period or mechanism)
• Deposition summaries (actions and timing)
• Fault allocation tables you already have

Offsets / credits / recoveries

• Payment history (bank records, claim logs)
• Insurance communications and remittance summaries
• Settlement agreements (amounts and release scope; whether payments are intended as credits)

For the fastest path, open the tool here: /tools/damages-allocation.

Run it

Now translate your inputs into the DocketMath damages-allocation calculator workflow (US-OR).

Enter the inputs in DocketMath and run the Damages Allocation calculation to generate a clean breakdown: Run the calculator.

Capture the source for each input so another team member can verify the same result quickly.

Step-by-step checklist (input-checklist approach)

What the outputs will typically show you

When you run the calculator, expect results that are easier to audit and adjust.

Quick “sanity test” before you finalize

After results generate:

• Compare sum of allocated components to your gross total (or net total if offsets are enabled)
• Confirm that single-source damages components weren’t forced into time/party splits
• Re-run after one intentional change (example: adjust a percentage driver by a few points) to see if the result behaves predictably

When you’re ready, run the final set of inputs again: /tools/damages-allocation.

Gentle reminder: this tool and checklist are meant to support organization and repeatable calculations. They are not legal advice, and you should ensure your inputs and assumptions match your specific matter and evidence.

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