How to run Offer Of Judgment Analyzer in DocketMath for Oregon

Step-by-step

Here’s how to run Offer Of Judgment Analyzer in DocketMath for Oregon (US-OR), using jurisdiction-aware rules tied to ORS § 18.080.

1) Open the Oregon Offer Of Judgment Analyzer

1. Go to Offer Of Judgment Analyzer.
2. Confirm the jurisdiction context is set to:

   • Jurisdiction code: US-OR
3. If the tool shows a jurisdiction selector, choose Oregon (US-OR).

2) Gather the Oregon-specific figures you’ll need

ORS § 18.080 is the jurisdiction anchor for costs and disbursements tied to offers in civil actions (see the Oregon Legislature link below for the statute text). In practice, you’ll generally need to provide inputs that correspond to:

• Judgment amount: the amount you’re treating as the relevant money judgment for the comparison (often “final judgment” or the amount the plaintiff recovers—use whatever judgment figure the analyzer expects you to model).
• Offer amount: the dollar amount stated in the offer of judgment.
• Timing inputs (if requested by the tool): some workflows model whether the offer falls within a timing framework.
• Costs and disbursements inputs (if requested): if the tool supports entering them, provide estimated costs/disbursements so the tool can estimate the modeled impact.

Important: If your case has multiple components (damages vs. fees vs. costs), the analyzer can only compute what you enter. Decide which number you want to use as the “judgment amount” basis for your scenario.

3) Enter the offer and judgment amounts

In DocketMath, enter:

• Offer amount = the offer amount you want to evaluate.
• Judgment amount = the judgment figure to compare against.

How outputs change:
Most offer-of-judgment analyses pivot on where the offer falls relative to the judgment. In many setups, small input changes can flip the result from “favorable” to “unfavorable” (because the cost-shifting threshold can be sensitive to the offer/judgment relationship).

4) Provide the timing inputs using the “general/default” period

If the tool asks for a timing period or timing framework, this runbook uses the general/default period approach.

Here’s the key detail for this guide:

• No claim-type-specific sub-rule was found.
• Therefore, use the general/default period as the analyzer’s baseline in this run.

Why this matters:
If you pick a special timing category without a clear basis, you could be modeling a different framework than the one this runbook intends to apply.

5) Enter costs/disbursements only if the tool provides fields for them

If DocketMath includes fields for costs and disbursements, you can fill them in using your best estimates.

• If you have reasonable cost/disbursement estimates: enter them to get a more informative modeled cost impact.
• If you don’t: you can still run the analysis if the tool allows it, but the output may be comparison-only (offer vs. judgment threshold) rather than a full cost impact estimate.

How outputs change:

• With costs/disbursements entered, the tool can estimate the modeled difference (e.g., a cost shift vs. no shift).
• Without those numbers, you’ll likely get less granularity on the dollar impact.

6) Select the correct side (if your UI supports it)

Some Offer Of Judgment Analyzer workflows ask you to specify whose perspective you want to model (for example, offeror vs. offeree or plaintiff vs. defendant).

Choose the option that matches the question you’re trying to answer:

• If you’re evaluating the expected position of the offeror, select the offeror-oriented mode.
• If you’re evaluating the expected position of the offeree, select the offeree-oriented mode.

How outputs change:
Depending on how the tool defines “your offer” and “your outcome,” the same dollar inputs can produce a different “favorable/unfavorable” direction. Perspective toggles are a common reason results look “reversed.”

7) Run the analysis and review the results

1. Click Analyze (or the tool’s equivalent button).
2. Review:

   • The offer vs. judgment comparison
   • Any modeled cost/disbursement outcome (if you entered cost inputs)
   • Any timing compliance or timing-related result (if timing fields were provided)

Use the results to generate follow-up questions, such as:

• “How sensitive is the result to the judgment amount?”
• “What happens if my cost estimates are higher or lower?”
• “Did the timing inputs land inside the tool’s general/default period assumption?”

8) Iterate: run scenario variations

A practical way to use the tool is to run multiple scenarios and compare them.

Example scenario approach:

• Scenario A: conservative costs/disbursements
• Scenario B: middle/expected costs/disbursements
• Scenario C: higher costs/disbursements
• If judgment is uncertain, also test alternate judgment assumptions

If the tool supports it, save runs or keep notes so you can compare outputs side-by-side.

Quick scenario tracking table (example template)

Common pitfalls

Avoid these issues when running the Oregon analysis in DocketMath:

• Mixing up “offer amount” and “judgment amount.”
  If you reverse these inputs, the comparison logic can produce an outcome that doesn’t match reality.

• Using a timing category that isn’t supported by the runbook’s “general/default” assumption.
  This guide explicitly uses the general/default period because no claim-type-specific sub-rule was found for this run.

• Entering costs/disbursements that the tool isn’t actually modeling.
  If the analyzer’s cost fields are specific or structured, avoid treating them as an all-purpose “everything” container.

• Not matching perspective/side selection to your objective.
  If the UI offers offeror/offeree (or plaintiff/defendant) toggles, selecting the wrong one can make results appear “backwards.”

• Assuming Oregon law details automatically map 1:1 to every cost line item.
  While ORS § 18.080 provides the general statutory framework, the analyzer can only calculate based on the input fields it exposes. Make sure the numbers you enter correspond to what the tool expects.

Oregon rule anchor (for context)

ORS § 18.080 addresses the court’s authority to award costs and disbursements in civil actions under statutory provisions, including offer-related cost consequences. The statute text begins broadly and then works through the offer framework.

• Source: https://www.oregonlegislature.gov/bills_laws/ors/ors018.html

Try it

1. Open Offer Of Judgment Analyzer.
2. Set jurisdiction to US-OR (Oregon).
3. Enter:

   • Offer amount
   • Judgment amount
   • Timing fields using the tool’s general/default period behavior (no claim-type-specific sub-rule is being applied in this runbook)
   • Costs/disbursements only if the tool asks for them and you have reasonable estimates
4. Click Analyze.
5. Run 2–3 quick scenarios by adjusting:

   • the judgment amount (if uncertain)
   • the costs/disbursements (if you can model a low/medium/high range)

Quick sanity check: Before relying on the numeric output, do a plain-English check (e.g., “offer is below/near/above the judgment basis”). Then confirm the tool’s direction matches that expectation. If it doesn’t, re-check:

• offer vs. judgment fields
• any side/perspective toggle
• timing inputs

Related reading

• Offer of Judgment Analyzer Guide for Alabama
• Offer of Judgment Analyzer Guide for Arizona
• Offer of Judgment Analyzer Guide for Colorado