How Offer Of Judgment Analyzer rules vary in Virginia

What varies by jurisdiction

Offer-of-judgment rules can look uniform at a high level—“make an offer, and if you beat it, you may shift costs”—but the details vary a lot by jurisdiction and by how (or whether) the state treats “offers” procedurally.

For Virginia (US-VA), the core variation is that Virginia is not a broad, general “Rule 68–style” offer-of-judgment system for all cases. Instead, Virginia’s offer-of-judgment treatment is statutory and tied to Virginia’s specific framework, which is reflected in the Virginia Supreme Court rules as limited and in the need to apply Virginia-specific logic rather than assuming a federal-style model.

Virginia’s core building blocks (and why they matter for the analyzer)

When using DocketMath’s Offer Of Judgment Analyzer for Virginia, the results depend on which Virginia authorities and modeling choices are used. In the verified Virginia configuration:

• Virginia’s offer-of-judgment framework

  • The primary offer-of-judgment statute to anchor the analyzer is Va. Code Ann. § 8.01-271.1.
  • The Virginia Supreme Court procedural rules reference Va. Sup. Ct. Pt. 1, Rule 1:14 (Offer of Judgment) as limited, consistent with the packet’s verified point that Virginia lacks a general offer-of-judgment regime like Fed. R. Civ. P. 68.

• Judgment interest modeling

  • The analyzer’s verified safe facts include a statutory judgment interest rate of 6% per annum, simple, sourced from Va. Code Ann. § 6.2-302.

• Cost shifting inputs

  • The verified configuration indicates:

    • costShifting.costMultiplier = 1
    • costShifting.interest = false
    • comparisonBasis.includeInterest = false

Put simply: in Virginia, even when two scenarios look similar (same offer amount and same eventual judgment), the tool’s “who wins under the offer” comparison can change depending on (1) which Virginia framework is applied and (2) whether interest is included in the comparison basis and/or cost-shifting mechanism.

DocketMath jurisdiction-aware behavior (US-VA)

DocketMath helps keep the analysis aligned to Virginia by using verified rule inputs for US-VA. In the verified configuration:

• Interest inclusion in the comparison basis is off (includeInterest: false)
• The cost-shifting mechanism does not add interest as part of the toggle (costShifting.interest: false)
• The statutory judgment interest rate used is modeled as 6% simple (per the verified safe facts)

As a practical check: if you run the same inputs under a federal-style Rule 68 workflow and your result “feels too federal,” that mismatch is often a signal that the analyzer is using the wrong jurisdiction logic path for Virginia.

If you want to run the Virginia calculator directly, start at /tools/offer-of-judgment-analyzer.

What to verify

Before relying on any Offer Of Judgment Analyzer output, verify the inputs that actually drive the Virginia result. Use the checklist below as a practical, tool-first validation step.

Checklist: Virginia Offer Of Judgment Analyzer inputs

• You selected Virginia (US-VA) as the jurisdiction

  • Confirm the analyzer is using Va. Code Ann. § 8.01-271.1 logic rather than Fed. R. Civ. P. 68 logic.

• The analyzer is aligned to Virginia’s “limited” procedural framing

  • The verified packet ties the procedural rule reference to Va. Sup. Ct. Pt. 1, Rule 1:14 (Offer of Judgment) and notes it as limited. Make sure your scenario is not being evaluated as though Virginia had a broad, general Rule 68–type regime.

• Judgment interest assumptions match the verified rate model

  • The analyzer uses 6% per annum, simple (from Va. Code Ann. § 6.2-302) as the verified safe fact rate.
  • If your output includes or excludes interest, confirm that it matches the verified toggles:

    • comparisonBasis.includeInterest = false
    • costShifting.interest = false

• Cost-shifting multiplier

  • Ensure the configuration reflects costShifting.costMultiplier = 1.

• Pre/post-judgment interest is handled consistently

  • If your case turns on interest timing mechanics beyond the judgment-rate model, Virginia’s interest provisions are governed by Va. Code Ann. § 8.01-382. The analyzer should reflect how it’s modeling interest calculations for your specific scenario.

How outputs can change in Virginia

Use this sensitivity map to interpret differences you see between runs (or between jurisdictions):

Quick workflow suggestion (non-legal, tool-first)

1. Run the Virginia (US-VA) analyzer once with your facts.
2. If the result seems inconsistent with a Virginia-specific approach, re-check whether the tool used Va. Code Ann. § 8.01-271.1 framing rather than a Rule 68 framing.
3. Look at whether interest is being included in the comparison basis (it should be off under the verified Virginia settings).

Related reading

• How to calculate Offer Of Judgment Analyzer in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Offer Of Judgment Analyzer in Philippines — Worked example with real statute citations
• Inputs you need for Offer Of Judgment Analyzer in Philippines — Input checklist with sourcing guidance

Sources and references (verified packet only)

• Va. Sup. Ct. Pt. 1, Rule 1:14 (Offer of Judgment) — limited framing for Virginia (https://www.vacourts.gov/courts/scv/rulesofcourt.pdf)
• Va. Code Ann. § 8.01-271.1 (https://law.lis.virginia.gov/vacode/title8.01/chapter3/section8.01-271.1/)
• Va. Code Ann. § 6.2-302 — judgment interest rate modeling as 6% per annum, simple (https://law.lis.virginia.gov/vacode/title6.2/chapter3/section6.2-302/)
• Va. Code Ann. § 8.01-382 — pre/post-judgment interest (https://law.lis.virginia.gov/vacode/title8.01/chapter3/section8.01-382/)
• Fed. R. Civ. P. 68 — referenced for contrast with Virginia’s limited approach (https://www.law.cornell.edu/rules/frcp/rule_68)