How Offer Of Judgment Analyzer rules vary in North Carolina

6 min read

Published June 4, 2026 • By DocketMath Team

Partially verified

older_than_packet

Open the live calculator View on primary source

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

What varies by jurisdiction

In North Carolina, DocketMath’s Offer Of Judgment Analyzer depends on applying the state’s Rule 68 framework found in N.C. Gen. Stat. § 1A-1, Rule 68. The general concept is familiar in many places: a party makes an offer of judgment, and if the other side does not do better at trial, cost consequences may follow.

However, the part that varies by jurisdiction isn’t “whether Offer of Judgment exists”—it’s the inputs that drive the analysis, especially:

Timing window for the offer
- Rule 68 uses a specific trigger tied to the trial date.
Who serves the offer (and upon whom)
- The rule is structured for the defending party serving on the adverse party.
What the offer may cover
- North Carolina expressly includes offers for money or property (or an offer “to the effect specified”).
How the statute treats costs after the final judgment
- The penalty/cost-shifting language is applied based on what happens at the end of the case, so the analyzer must align to the statute’s mechanics.

North Carolina uses a default Rule 68 timing rule (no claim-type special case found)

Per the jurisdiction data you provided, no claim-type-specific sub-rule was found. That means for North Carolina, treat Rule 68 as using the general/default timing language, not a special claim-category override—unless you later confirm an additional controlling subsection or interpretation.

If your analyzer has a “claim type” special-case toggle, do not enable it for North Carolina unless you confirm additional Rule 68 authority that changes timing or the cost effect for a specific claim type.

Practical mapping: how DocketMath inputs should reflect Rule 68 (US-NC)

DocketMath translates jurisdiction rules into calculator logic. For US-NC, align your inputs to the Rule 68 structure:

Offer date (date served)
Trial start date (or your system’s “trial begins” date field)
Offer terms
- At minimum: the money or property amount the offer is intended to cover
- If your intake supports non-monetary outcomes: you may need to capture the “effect specified” concept as well
Costs accrued at the time of offer
- Rule 68 references offers made “with costs then accrued,” so costs-by-date matters to expected outcome calculations
Trial outcome vs. offer
- The analyzer needs a way to compare the plaintiff’s trial result (e.g., net judgment/award relative to the offer) so it can determine whether the plaintiff “did better” and avoid the statute’s adverse cost result

If you accidentally apply timing logic from another jurisdiction (or round the timing window differently), the analyzer output can change substantially—particularly because North Carolina’s trigger is stated in days relative to trial.

What to verify

Before relying on DocketMath’s Offer Of Judgment Analyzer for a North Carolina case, verify these items directly against N.C. Gen. Stat. § 1A-1, Rule 68:

Timing: “more than 10 days before the trial begins”
- The statute provides:
  “At any time more than 10 days before the trial begins…”
- Verification points for your workflow:
  
  The rule requires strictly more than 10 days.
  
  An offer served exactly 10 days before trial begins should not satisfy “more than 10 days.”
  
  In date math, ensure your analyzer logic reflects this strictness (e.g., if your system uses day counts, “> 10” not “≥ 10”).
Party posture: defending party to adverse party
- Rule 68 is framed so that a party defending against a claim may serve the offer on the adverse party.
- Verification point: confirm your intake labels the “offer maker” and “offer recipient” consistently with that posture.
Offer scope: money/property and “to the effect specified”
- North Carolina’s text allows an offer “for the money or property or to the effect specified in his offer…”
- Verification point: ensure DocketMath is configured to treat the offer as covering the correct category (money/property, and any “effect specified” mechanism your tool supports).
Costs at the time of service: “with costs then accrued”
- The statute explicitly ties the offer to costs then accrued.
- Verification point:
  
  Make sure “costs accrued” in your inputs correspond to costs accrued as of the offer service date (not as of filing, not as of trial, unless your data source supports that distinction).
Final-judgment cost/penalty mechanics
- Your draft excerpt ends at: “If the judgment finally obt…”
- Verification point:
  
  Do not finalize the analyzer’s interpretation until you confirm the complete Rule 68 text in the statute link, because the exact cost-shifting/penalty consequences after final judgment determine the analyzer’s “expected outcome.”
  
  If any clause defines who pays costs (and under what scenario), the calculator rules must match it.

Checklist: North Carolina Rule 68 setup (US-NC)

Offer served by the defending party
Offer served more than 10 days before the trial begins (not exactly 10)
Offer terms captured as money/property (and “effect specified” if your workflow supports it)
Costs then accrued entered using the correct offer-service-date basis
Final judgment cost consequences configured to match the complete statute language exactly

Friendly reminder: this content is for general guidance on how a calculator should be configured—not legal advice. If you need outcome-specific advice for a particular case, consult a qualified attorney.

Use the North Carolina calculator path

To run the analysis using DocketMath with North Carolina rules, start here: /tools/offer-of-judgment-analyzer.

When entering dates, double-check that your system’s date math treats “more than 10 days” as strictly greater than 10, not “10 or more.”