How to run Offer Of Judgment Analyzer in DocketMath for Nebraska

How to run Offer Of Judgment Analyzer in DocketMath for Nebraska

7 min read

Published May 29, 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

Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.

Below is a practical walkthrough for running the Offer Of Judgment Analyzer in DocketMath with Nebraska (US-NE) jurisdiction-aware rules. This guide explains how to operate the tool and interpret its outputs—not whether you should pursue or reject an offer. (This is general information, not legal advice.)

1) Open the analyzer

  1. Go to the primary tool page: /tools/offer-of-judgment-analyzer
  2. Select Nebraska (US-NE) as the jurisdiction (if the interface prompts you).
  3. Confirm you’re on the Offer Of Judgment Analyzer workflow.

2) Gather the exact case inputs the tool needs

DocketMath typically works best when you enter precise amounts and dates tied to the offer/judgment timeline. Before you start, locate:

  • The offer amount
  • The judgment amount recovered (or the figure you want to compare to the offer)
  • The offer date and judgment date (or whichever dates the tool requests)
  • Any costs or fees inputs the tool asks for (often entered as a single number or via categories)

Jurisdiction-aware relevance (Nebraska): Nebraska’s offer-of-judgment cost-shifting rule applies to actions for the recovery of damages where the recovery sought is for personal injury or wrongful death. The governing statute is Neb. Rev. Stat. § 25-1250.

Note: Nebraska’s statute is the default trigger used by the analyzer for the Nebraska jurisdiction. However, the claim must fall within the statute’s scope (personal injury or wrongful death damages recovery) for the cost-shifting framework to be relevant.

3) Enter the timeline that drives the results

In DocketMath, the timeline typically affects outputs such as whether a matching “offer made and not accepted” scenario applies and how the calculator accounts for timing-dependent components.

Use the dates exactly as tied to the relevant procedural events, and make sure:

  • the offer date is earlier than the judgment date
  • you input dates in the format the tool expects

Default-period clarification (general rule)

Nebraska’s analysis uses a general/default period when no claim-type-specific sub-rule is supplied. In this brief, no claim-type-specific sub-rule was found, so treat Neb. Rev. Stat. § 25-1250 as the general/default logic for the Nebraska analyzer unless the UI explicitly shows a more specific branch.

4) Compare “judgment recovered” vs “offer”

The statute’s core decision point is whether the judgment recovered is more favorable than the offer.

Neb. Rev. Stat. § 25-1250 (summary of key logic) centers on this threshold:

  • where an offer of judgment was made and not accepted
  • and the judgment recovered is not more favorable than the offer
  • then the offeree must pay the offeror costs (with additional statutory detail about costs and related components)

In the analyzer:

  1. Enter the offer amount
  2. Enter the judgment amount
  3. Ensure the amounts are comparable in the same terms (for example, damages figure/measurement in the form the tool expects)

What to expect as output changes

As you change the inputs, the tool’s results usually shift in line with the “more favorable” threshold. Common patterns include:

  • If judgment is more favorable than the offer: the analyzer will often show reduced cost-shifting outputs (or none), depending on how it models statutory language and cost components.
  • If judgment is not more favorable than the offer: the analyzer will likely show a cost-shifting consequence consistent with § 25-1250’s trigger.

5) Review the analyzer outputs and assumptions

After you run the calculation, review:

  • the comparison result (offer vs. judgment)
  • any estimated costs/amounts the tool includes
  • any assumptions or rule basis panel (if provided)

Pay special attention to whether the tool is assuming:

  • an offer was made and not accepted
  • the modeled scenario is treated under the Nebraska § 25-1250 framework
  • the general/default logic is being applied (since no claim-type-specific sub-rule was identified in this brief)

6) Export or record the result

If you need to document what you ran:

  • use any download/share/copy/save options available
  • keep your input values (offer amount, judgment amount, and dates) with the output so you can reproduce the run later

7) Validate with a quick sanity check

Before relying on the numbers:

  • Confirm amounts are entered as plain numbers
  • Confirm dates are chronologically consistent
  • Confirm Nebraska (US-NE) is selected

Also be cautious about what the “judgment amount recovered” number represents. If your judgment figure includes or excludes items differently than the offer figure, the “more favorable” comparison can flip—changing outputs under Neb. Rev. Stat. § 25-1250.

Common pitfalls

Here are the most common issues when running DocketMath’s Offer Of Judgment Analyzer for Nebraska (US-NE).

Mis-scoping the statute

Neb. Rev. Stat. § 25-1250 is tied to:

  • actions for the recovery of damages
  • where the recovery sought is personal injury or wrongful death

If your claim doesn’t match that scope, the analyzer may still produce results, but they may not map to the legal reality you’re evaluating.

Getting the “more favorable” comparison wrong

The threshold is whether the judgment is not more favorable than the offer. This often fails due to input comparability issues.

Date confusion

Even if the decision point is primarily amount-based, the tool can still use the timeline.

Assuming special sub-rules that aren’t present

This brief did not identify a claim-type-specific sub-rule. Therefore, use the general/default logic unless the DocketMath UI explicitly provides more specific branches.

Ignoring assumptions in the output panel

Many calculators include internal assumptions.

Try it

Use this quick test to see how the analyzer responds around the statutory threshold.

  1. Open /tools/offer-of-judgment-analyzer
  2. Set jurisdiction to **Nebraska (US-NE)
  3. Enter test inputs:
    • Pick an offer amount (any reasonable number for testing)
    • Pick a judgment amount
    • Enter the offer date and judgment date
  4. Run two scenarios:
    • Run A: judgment amount slightly less than or equal to the offer (so it should be not more favorable)
    • Run B: judgment amount slightly greater than the offer (so it should be more favorable)

Then compare outputs. Your goal is to confirm the tool’s threshold behavior aligns with the statutory concept in Neb. Rev. Stat. § 25-1250: “judgment recovered is not more favorable than the offer” is the trigger for cost-shifting.

For reference while you test, review Neb. Rev. Stat. § 25-1250:
https://nebraskalegislature.gov/laws/statutes.php?statute=25-1250

Quick threshold checklist

Related reading

Step-by-step

  • Select Nebraska in the Offer Of Judgment Analyzer tool.
  • Enter the trigger dates and any caps or rates.
  • Run the calculation and save the output.

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

Common pitfalls

  • missing a required input
  • using a stale rate or rule
  • ignoring calendar or holiday adjustments
  • skipping documentation of assumptions

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

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

Try it

Open the Offer Of Judgment Analyzer calculator and follow the steps above: Run the calculator.

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

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

Related reading