How to calculate Offer Of Judgment Analyzer in Vermont

Quick takeaways

• Vermont’s offer of judgment cost-shifting rule is in 12 V.S.A. § 5502: if an offer is made, not accepted, and the final judgment obtained by the offeree is less favorable than the offer, the offeror may recover costs.
• DocketMath’s Offer Of Judgment Analyzer helps you compare: (1) your offer amount vs. (2) the judgment amount the offeree ultimately receives.
• Because the jurisdiction rule provided is general/default (no claim-type-specific carve-outs were found), this workflow treats § 5502 as applying across civil actions under the statute’s text.
• The most reliable outputs come from consistent inputs—especially using the same definition for the “judgment amount” you enter as the basis you compare to the offer amount.

Inputs you need

Before you start in DocketMath, gather the items that correspond to what § 5502 is comparing: the offer and the offeree’s final judgment result.

Use this checklist to collect your numbers and labels:

Use this intake checklist as your baseline for Offer Of Judgment Analyzer work in Vermont.

• jurisdiction selection
• key dates and triggering events
• amounts or rates
• any caps or overrides

If any of these inputs are uncertain, document the assumption before you run the tool.

Vermont rule you’ll be applying

Section 12 V.S.A. § 5502 provides the core comparison:

• In a civil action, if a party makes an offer of judgment and it’s not accepted, the offeror may recover costs if the offeree’s judgment is less favorable than the offer.

The decision gate is binary:

• If judgment is less favorable than the offer → costs may be recoverable
• If judgment is equal to or more favorable than the offer → costs generally won’t shift under this rule

Because your instructions specify that no claim-type-specific sub-rule was found, this workflow treats § 5502 as the general/default period and comparison standard for the analyzer’s purpose.

How the calculation works

DocketMath’s Offer Of Judgment Analyzer (US-VT) is built around the statutory logic in 12 V.S.A. § 5502:

1. Verify the offer was not accepted

   • If the offer was accepted, § 5502’s “not accepted” condition is not met for cost recovery under this rule.
   • If not accepted, proceed to the comparison.

2. Compare the offeree’s final judgment vs. the offer

   • The statute triggers when “the judgment obtained by the offeree is less favorable than the offer.”
   • Practically, the analyzer operationalizes this as comparing the final judgment dollar figure to the offer dollar figure using the definition you input (e.g., principal only vs. principal plus tracked additions).

3. Output the result

   • When the analyzer determines the outcome is “less favorable,” it flags that cost recovery is potentially available under § 5502.
   • If you provide a cost basis, it can translate that statutory trigger into an estimated cost impact figure for your internal analysis.

A simple numeric model (what you’re really doing)

Even without claim-type-specific sub-rules, the comparison can be reduced to a straightforward inequality:

• Let O = offer amount
• Let J = offeree’s final judgment amount
• Trigger condition: J < O (judgment less favorable than the offer)

Then:

• If J < O and the offer was not accepted → § 5502 cost recovery may apply
• If J ≥ O and the offer was not accepted → § 5502 cost recovery won’t trigger under the “less favorable” test

Example scenarios (illustrative)

Where DocketMath fits (run the tool)

Use the analyzer here:

• Primary CTA: /tools/offer-of-judgment-analyzer

(If you’re also organizing case milestones and want to align timelines with the offer and judgment, you can use DocketMath’s timeline tool as a companion check: /tools/docket-timeline .)

Quick “run order” inside the analyzer

When you use DocketMath, follow a disciplined order so your comparison is clean:

• Enter **Offer amount (O)
• Set Acceptance status = Not accepted
• Enter Offeree judgment amount (J) using the same definition as the offer
• (Optional) Enter expected costs if you want a cost-impact estimate
• Review the analyzer’s trigger output based on the J vs. O comparison

Common pitfalls

The most frequent mistakes in offer-of-judgment calculations come from mismatched numbers, misunderstanding the default nature of the rule, or skipping the “not accepted” condition.

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

Pitfall checklist

• § 5502 requires that the offer be not accepted to trigger the cost-recovery comparison.

  • If your offer includes one set of components (e.g., principal only) but your judgment figure includes others, the comparison to “less favorable” becomes unreliable.
  • Your Vermont summary identifies the general/default period and provides no claim-type-specific sub-rules. Treat § 5502 as the general standard you’re applying through the analyzer.
  • In the analyzer, “less favorable” is measurable: it depends on your inputs. Make your inputs explicit in your workflow notes.
  • Ensure the judgment amount you enter is the one that represents the offeree’s final judgment obtained for your comparison purpose.

A quick consistency rule

Before you finalize the run:

• Confirm Offer definition = Judgment definition
• Confirm Offer status = Not accepted
• Confirm you’re using J < O (not ≤) for the “less favorable” trigger logic in your comparison model

Sources and references

• 12 V.S.A. § 5502 — Vermont offer of judgment cost recovery standard:
  https://legislature.vermont.gov/statutes/section/12/177/5502
  Key statutory language (summary of the relevant portion): “In any civil action, if a party makes an offer of judgment to another party and that offer is not accepted, the party making the offer shall be entitled to recover costs if the judgment obtained by the offeree is less favorable than the offer.”

Next steps

1. Run the calculation using /tools/offer-of-judgment-analyzer:

   • /tools/offer-of-judgment-analyzer
2. Record the key inputs you used:

   • Offer amount (O)
   • Judgment amount (J)
   • Whether the offer was accepted
   • Your definition of “judgment amount” (principal-only vs. other tracked components)
3. Stress-test with a second pass:

   • Keep acceptance status the same
   • Change only one variable (usually the judgment figure definition) and see whether the comparison flips around the trigger boundary (J < O)
4. Use the DocketMath output for internal budgeting and scenario analysis:

   • If you included a cost basis, compare how cost impact changes when J moves just below versus just above O

Related reading

• Offer of Judgment Analyzer Guide for Alabama
• Offer of Judgment Analyzer Guide for Arizona
• Offer of Judgment Analyzer Guide for Colorado