How to run Offer Of Judgment Analyzer in DocketMath for Vermont

Step-by-step

Follow these steps to run Offer Of Judgment Analyzer in DocketMath for Vermont (US-VT). This walkthrough focuses on how to set jurisdiction-aware options and interpret the results. It’s not legal advice; it’s a practical way to model the cost-shifting concept described in 12 V.S.A. § 5502.

1) Open the analyzer from the primary call to action

Start here: **/tools/offer-of-judgment-analyzer

On the tool page, make sure you select:

• Calculator: Offer Of Judgment Analyzer
• Jurisdiction: Vermont (US-VT)

This selection ensures DocketMath applies Vermont’s offer-of-judgment rule framework, anchored to 12 V.S.A. § 5502.

2) Enter the parties and key monetary numbers

You’ll typically be prompted for values like:

• Offer amount (the dollar value of the offer of judgment)
• Judgment amount (what the offeree ultimately receives at judgment)
• Costs modeled (often estimated costs or categories you want included)

If you see fields for “offer rejected” or similar status flags, keep them consistent with the scenario you’re analyzing:

• Offer not accepted → enables the cost-recovery comparison feature under the Vermont rule logic.

Input tip: Treat your Offer amount and Judgment amount as comparable dollar totals (for example, both gross totals or both net totals) so the comparison is consistent.

3) Use the comparison logic correctly: “less favorable” outcome

Under 12 V.S.A. § 5502, the core trigger is comparative. The statute provides that in any civil action where:

• an offer of judgment is made, and
• the offer is not accepted, then
• the offeror may recover costs if the judgment obtained by the offeree is less favorable than the offer.

So DocketMath’s analysis should compare:

• Judgment outcome vs. Offer amount

In practice, your inputs should reflect the same units of measurement (usually total dollar amounts). If your judgment number is net of offsets/credits, use the same convention for the offer amount so the “less favorable” comparison is apples-to-apples.

4) Confirm whether the tool expects “costs” as additional inputs

Many offer-of-judgment analyzers show results in a way that depends on whether you include costs. If the DocketMath interface includes fields such as:

• Estimated costs for the offeror, and/or
• a toggle like model costs recovery,

then your outputs will change with how you fill those values.

A practical workflow:

• Run one scenario with costs = $0 to isolate whether the tool determines the “less favorable” threshold.
• Run a second scenario with your estimated costs to approximate the potential cost recovery amount.

5) Review jurisdiction-aware rule messaging for Vermont

Because the Vermont statute provided here is a general/default rule (no claim-type-specific sub-rule was found in the supplied material), the rule should apply broadly.

Use this guiding interpretation while reviewing DocketMath’s jurisdiction messaging:

• Vermont’s 12 V.S.A. § 5502 applies to “any civil action.”
• Based on the provided statute text, there’s no claim-type branching indicated—so if DocketMath offers only one Vermont option, that generally aligns with the statute’s default framework.

(Gentle reminder: tool outputs are only as accurate as the inputs and the selected rule framework; if anything looks off, double-check the amounts and the jurisdiction selection.)

6) Run the analysis and read the outputs

After inputs are set, click Calculate / Run analysis.

Typical outputs you should look for:

• Whether the tool determines the judgment is less favorable than the offer
• Whether cost recovery is indicated (often tied to the comparison outcome)
• An estimated amount of costs potentially recoverable (if costs are included)
• A summary you can copy/export for internal notes

Because the statute’s trigger is fundamentally comparative, the most important output is usually:

• Judgment < Offer (less favorable) vs.
• Judgment ≥ Offer (not less favorable)

7) Iterate with scenario testing

To see how sensitive the result is, rerun the analyzer with controlled changes.

Recommended scenario iterations:

• Offer higher by $10,000 (to see if cost recovery becomes more likely)
• Judgment lower by $5,000 (to confirm the comparison threshold)
• Costs higher/lower (to see how estimated cost recovery changes)

You’ll typically see changes in two areas:

1. The binary trigger (less favorable vs. not)
2. The estimated cost recovery number (if the tool models costs)

Common pitfalls

A few issues commonly trip up Vermont offer-of-judgment modeling in tools like DocketMath:

• Using inconsistent figures for “offer” vs. “judgment”

  • If your judgment is “after offsets” but your offer is “gross,” the tool may determine “less favorable” incorrectly.
• Forgetting the rule is comparative

  • The statute’s trigger depends on whether the judgment is less favorable than the offer, not just whether the offer was rejected.
• Assuming a claim-type-specific rule exists

  • Based on the provided statute language, 12 V.S.A. § 5502 is framed as a general/default rule for “any civil action.” The supplied material does not indicate claim-type branching.
• Leaving costs undefined when you want cost-recovery estimates

  • If you don’t enter costs (or you enter $0), the tool may still indicate whether the threshold is met, but it may show $0 or a reduced estimate for recoverable costs.
• Not running “what-if” variations

  • Small dollar changes can flip the comparison. Without scenario testing, it’s easy to miss how close the outcome is.

Quick check: If the tool says “judgment is less favorable,” confirm the offer amount and judgment amount are in the same measurement basis (total vs. net; before vs. after credits).

Try it

Use this controlled hypothetical workflow to validate how the tool behaves. These numbers are meant to test behavior—not to predict any real case outcome.

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

Suggested scenario set (3 runs)

Check how the output changes when you adjust the relationship between judgment and offer.

• Run A (baseline):

  • Offer amount: $50,000
  • Judgment amount: $45,000
  • Costs: $7,500
• Run B (close call):

  • Offer amount: $50,000
  • Judgment amount: $50,000
  • Costs: $7,500
• Run C (reversed outcome):

  • Offer amount: $50,000
  • Judgment amount: $60,000
  • Costs: $7,500

What to expect under 12 V.S.A. § 5502

Because 12 V.S.A. § 5502 allows cost recovery only when the judgment obtained by the offeree is less favorable than the offer, the expected directional results are:

• Run A: Judgment ($45,000) is less favorable than the offer ($50,000) → cost recovery modeling should indicate “yes” (or equivalent)
• Run B: Judgment equals the offer → the “less favorable” threshold is not met → cost recovery should not trigger
• Run C: Judgment is more favorable than the offer → the “less favorable” threshold is not met → cost recovery should not trigger

If DocketMath behaves differently, re-check:

• whether inputs are interpreted as totals,
• whether values are being treated as net vs. gross,
• and whether Vermont (US-VT) is selected.

Related reading

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