How to run Offer Of Judgment Analyzer in DocketMath for North Carolina

How to run Offer Of Judgment Analyzer in DocketMath for North Carolina

8 min read

Published April 2, 2026 • 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

This is a practical walkthrough for running DocketMath’s Offer Of Judgment Analyzer for North Carolina (US-NC) using jurisdiction-aware timing logic tied to N.C. Gen. Stat. § 1A-1, Rule 68.

Note: DocketMath helps you calculate and organize outcomes—it does not provide legal advice. Use the results as decision support and verify the specifics against N.C. Gen. Stat. § 1A-1, Rule 68 and your case’s procedural posture.

1) Open the correct tool

  1. Open the analyzer here: **/tools/offer-of-judgment-analyzer
  2. Confirm the jurisdiction selector is set to North Carolina (US-NC).

If your interface does not auto-select the jurisdiction, set it before entering any numbers. Timing outcomes and rule assumptions should match the selected jurisdiction.

2) Understand the Rule 68 timing rule DocketMath uses (NC)

North Carolina’s offer mechanism is found in N.C. Gen. Stat. § 1A-1, Rule 68. The key baseline timing rule (the only one cited for this analyzer logic) is:

  • At any time more than 10 days before the trial begins, a party may serve an offer allowing judgment to be taken against the offeror for the money or property claimed.

Because no claim-type-specific sub-rule was found for this workflow, the analyzer uses this general/default “more than 10 days before trial begins” rule when your inputs don’t trigger a more specific timing window.

Statute reference:

3) Enter the offer details

In the tool, fill out the offer-related fields (labels may vary slightly). At minimum, provide:

  • Offer amount (the dollar amount or property value, based on what your case is claiming)
  • Offer service date (the date the offer was served)
  • Trial start date (the date the trial begins, using the schedule reflected in your case)

If DocketMath requests additional dates (e.g., judgment/acceptance-related dates), enter them if you have them. If the tool allows blanks, you can leave fields empty only when it explicitly permits that.

4) Enter the judgment outcome used for comparison

Offer-of-judgment analysis depends on comparing the offer to what the parties ultimately achieve at judgment.

Provide inputs that represent the final outcome the tool expects to compare—typically:

  • Final judgment amount (or your best estimate of the money awarded)

If the tool separates the comparison by perspective (for example, offeror vs. offeree), enter the award relevant to the perspective the tool asks for.

How outputs change based on your inputs

These relationships generally drive what you see in the results:

  • Earlier vs. later offer service: If your offer service date is not “more than 10 days before trial begins,” the analyzer will flag timing risk under the statutory baseline.
  • Offer amount vs. eventual judgment: The incentive direction changes depending on whether the offer is more or less favorable than the eventual judgment amount from the relevant perspective.

5) Review the timing check section first

Before focusing on cost/benefit numbers, look at whether DocketMath confirms the offer meets the Rule 68 timing requirement:

  • “More than 10 days before the trial begins” (baseline from N.C. Gen. Stat. § 1A-1, Rule 68)

If the tool indicates the offer was served 10 days or fewer before the trial begins, treat that as a red flag that the statutory baseline threshold may not be met. That’s not the same as a definitive conclusion about enforceability in every situation—just a timing mismatch against the baseline rule used by the analyzer.

6) Run the analyzer and interpret the results

After running the tool, DocketMath typically provides results in a few parts, such as:

  • A timing compliance indicator (based on offer service date vs. trial start date)
  • A comparison showing how the offer amount relates to the judgment amount
  • A cost/benefit summary computed from your inputs

Read them in this order:

  1. Timing compliance (does the offer fit the baseline “more than 10 days before trial begins” rule?)
  2. Offer vs. judgment comparison (did the outcome land above/below the offer from the relevant perspective the tool uses?)
  3. Cost estimate summary (use as a computed result from your entries, not as a prediction of how all procedural nuances will play out)

7) Export or save your inputs (if available)

If DocketMath supports saving:

  • Save the run so you can revisit it after trial dates or judgment figures change.
  • Keep the saved version tied to the exact dates you entered—changing a single date can change the timing compliance outcome.

8) Cross-check the critical dates

Even with analyzer support, verify the dates you entered:

  • Offer service date vs. trial start date
  • Any docket facts that might affect what “trial begins” means for the purposes of your record

Warning: Rule 68 timing is date-driven. Entering a “draft” date instead of the actual served date can flip the timing check and alter the analyzer’s conclusions.

Common pitfalls

Below are recurring mistakes when running Offer Of Judgment Analyzer in North Carolina with Rule 68 timing logic.

Pitfall: Using a “trial scheduled” date when “trial begins” differs

If your calendar reflects a scheduled start that later changes—or if proceedings occur in segments—the date you choose for “trial begins” may not match the meaning assumed in the tool.

  • Fix: Use the date that best reflects when the trial began in your procedural record, then re-run.

Pitfall: Confusing “more than 10 days” with “10 days”

The baseline rule is more than 10 days before the trial begins (not “10 days or fewer”).

  • Practical effect:
    • 10 days or fewer before trial start may fail the baseline threshold.
    • 11+ days before trial start generally aligns with the baseline timing requirement used by the analyzer.

Pitfall: Assuming a claim-type-specific sub-rule is applied

This workflow is using the statute’s general/default timing window because no claim-type-specific sub-rule was identified for this jurisdiction-aware logic.

  • Fix: Run the analyzer using the baseline. If you believe a different rule applies due to the claim type or procedural posture, verify that applicability and treat the analyzer output as baseline-computed rather than conclusive.

Pitfall: Entering inconsistent money amounts

The analyzer relies on consistent monetary framing.

Common mismatches:

  • Entering net damages in one field and gross award in the other

  • Swapping the amount relevant to the offeror vs. the recipient if the tool expects a specific perspective

  • Fix: Check the field labels (e.g., “offer amount” vs. “final judgment amount”) and enter figures that match the tool’s intended framing.

Pitfall: Running with incomplete or approximate dates

If the tool accepts partial inputs, it may still compute something—but timing confidence can drop.

  • Fix: Provide at least:
    • Offer service date
    • Trial start date

These dates power the timing compliance indicator.

Try it

Ready to run the North Carolina analysis?

  1. Select North Carolina (US-NC).
  2. Enter:
    • Offer amount
    • Offer service date
    • Trial start date
    • Final judgment amount (the amount the tool uses for comparison)

Then review results in this checklist order:

Testing tip: change one variable at a time (for example, move the offer service date by 2–3 days) to see how the timing indicator responds. This is the fastest way to build confidence in the analyzer’s Rule 68 baseline timing logic for US-NC.

Related reading

Step-by-step

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

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

Common pitfalls

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

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

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Try it

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

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

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Related reading