Nevada · offer of judgment analyzer

How to run Offer Of Judgment Analyzer in DocketMath for Nevada

By DocketMath TeamJune 4, 20267 min read
Abstract background illustration for How to run Offer Of Judgment Analyzer in DocketMath for Nevada
Partially verified

older_than_packet

Step-by-step

Follow these steps to run DocketMath’s Offer Of Judgment Analyzer for Nevada (US-NV) using jurisdiction-aware rules based on Nev. R. Civ. P. 68 (the Nevada rule governing offers of judgment).

Note: Nevada’s default offer timing under Nev. R. Civ. P. 68(a) applies when an offer is served more than 21 days before trial. No claim-type-specific sub-rule was identified here, so the “more than 21 days before trial” standard is the baseline used in this workflow.

1) Open the analyzer for Nevada

  1. Open the tool here: /tools/offer-of-judgment-analyzer
  2. In the jurisdiction selector, choose:
    • Jurisdiction: US-NV (Nevada)

2) Confirm the rule context (what the analyzer is modeling)

Nevada uses Nev. R. Civ. P. 68, which includes:

  • The Offer (service timing and written terms)
  • Acceptance/allowing judgment
  • Penalties for rejection, including costs and interest consequences if the offeree rejects and then fails to obtain a more favorable judgment

This analyzer is designed to model the financial consequences tied to the outcome comparison: your final result vs. the offer amount.

3) Enter the inputs DocketMath needs

Use the input fields to reflect the scenario you want to analyze. While the exact labels may vary slightly in the UI, the core inputs typically include:

  • Offer amount (the number stated in the Rule 68 offer)
  • Your side (who made the offer vs. who is being analyzed as the offeree)
  • Expected or actual final judgment amount (the comparison point)
  • Costs/fees inputs relevant to the outcome comparison (when applicable in the tool)
  • Interest-related inputs if your workflow includes them

Input accuracy checklist

  • Offer amount matches the document served under Nev. R. Civ. P. 68
  • The judgment comparison number is the one you intend (e.g., total judgment vs. net figure used in your case materials)
  • You’ve chosen the correct “role” (offeror/offeree) so the “penalty for rejection” directionality is correct

Pitfall: The most common mismatch is flipping the role—entering the offeror’s perspective when you mean the offeree’s perspective. That can change how “penalties for rejection” should be expected to apply based on the tool’s modeling.

4) Apply Nevada timing logic (21+ days before trial)

Nev. R. Civ. P. 68(a) states offers may be served “at any time more than 21 days before trial.” In practice, make sure your analysis reflects the timeline when:

  • The offer is served more than 21 days before trial, and
  • You’re comparing consequences triggered by acceptance vs. rejection and the resulting judgment comparison

In DocketMath, timing is usually handled either through a dedicated field (e.g., offer date / trial date) or via a jurisdiction default rule. If there is a date section, enter:

  • Offer service date
  • Trial date

Then verify the analyzer is set to treat the offer timing as satisfying the > 21 days requirement.

5) Run the calculation

  1. Click Analyze (or the tool’s equivalent)
  2. Review the two core outputs:
    • Outcome comparison (whether the judgment is more favorable than the offer)
    • Consequence estimate (based on Nevada’s Rule 68 penalty framework)

6) Interpret results using the “more favorable judgment” trigger

Nevada’s Nev. R. Civ. P. 68(f) focuses on consequences when:

  • The offeree rejects the offer, and
  • Fails to obtain a more favorable judgment than the offer

Use the analyzer results to answer two practical questions:

  • Comparison: Did the offeree end up with a more favorable judgment than the offered amount?
  • Consequence: If not, what financial impact is modeled (often involving costs and/or interest) under the tool’s implementation of the Nevada rule?

7) Iterate for what-if planning (change inputs and watch the threshold move)

After your first run, adjust inputs to test different settlement postures:

Common variables to try:

  • Offer amount (lower vs. higher)
  • Expected judgment amount (use the best estimate you have, or run multiple scenarios)
  • Offeree role selection (confirm you selected the correct role)
  • Costs/interest assumptions (only change these if you have support for the assumptions)

A simple approach:

  • Run a baseline scenario
  • Increase or decrease the offer amount in a reasonable increment (for example, 10%)
  • Re-run and note where the “more favorable” outcome appears to flip
  • Keep the final scenario consistent with how the Rule 68 offer would be drafted and presented

Warning: If your “expected/actual judgment” figure doesn’t match what the judgment will actually include (or how the tool expects to compare it), the “more favorable judgment” comparison may be less reliable.

Common pitfalls

Avoid these issues when running the Offer Of Judgment Analyzer in US-NV.

  1. Offer timing not meeting Nev. R. Civ. P. 68(a)

    • The baseline requirement is an offer served “more than 21 days before trial.”
    • If your dates don’t reflect that window, the modeled consequences may not correspond to what the rule would support.
  2. Using the wrong offer role

    • The penalty framework in Nev. R. Civ. P. 68(f) is tied to the offeree’s rejection and failure to obtain a more favorable judgment.
    • If DocketMath’s perspective is set to the wrong side, results can look “reversed.”
  3. Comparing the wrong number

    • The analyzer depends on whether the final judgment is more favorable than the offer.
    • Be consistent about which judgment figure you enter (and ensure it matches the operative comparison in your materials).
  4. Costs and interest assumptions don’t match your real case

    • Nevada’s Rule 68 includes penalties that can involve costs and interest consequences.
    • If DocketMath requires cost/interest inputs and you leave them blank or inconsistent, the comparison outcome may still appear, but the estimated dollar impact can be misleading.
  5. Forgetting this timing is a default here

    • Use the > 21 days before trial standard as the default workflow requirement under Nev. R. Civ. P. 68(a).
    • No claim-type-specific timing sub-rule was identified for special variations in this guide.

Try it

To test the analyzer quickly in Nevada:

  1. Open /tools/offer-of-judgment-analyzer
  2. Set:
    • Jurisdiction = US-NV
  3. Enter:
    • Offer amount
    • Role (offeror/offeree) (confirm it matches your analysis goal)
    • Expected/actual final judgment amount
    • Any costs/interest inputs the tool requests (if shown)
  4. If the tool includes timing fields, enter:
    • Offer service date
    • Trial date
  5. Click Analyze
  6. Use the results to answer:
    • Comparison: Will the offeree end up with a more favorable judgment than the offer?
    • Consequence: If not, what is the estimated financial impact modeled under Nev. R. Civ. P. 68(f)?

Note: This is for calculation and scenario planning, not legal advice. For any filing, match your actual Rule 68 offer language and your case posture to the rule’s requirements and Nevada law.

If your first run indicates “no more favorable judgment,” try adjusting only one variable at a time—most commonly the offer amount—to find the approximate point where the outcome comparison changes.

Related reading

Additionally, review the text of Nevada’s rule as published by the Nevada Legislature here:


Run the numbers for your matter against the verified rule for this jurisdiction.

Calculate now