How to run Offer Of Judgment Analyzer in DocketMath for Connecticut

Step-by-step

Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.

Here’s a practical walkthrough for running the Offer Of Judgment Analyzer in DocketMath for Connecticut (US-CT), using jurisdiction-aware rules keyed to Conn. Gen. Stat. § 52-192a.

1) Open the analyzer and confirm jurisdiction

1. Open DocketMath’s Offer Of Judgment Analyzer: /tools/offer-of-judgment-analyzer
2. Confirm the jurisdiction is set to Connecticut (US-CT).
3. Take a moment to review the input fields before entering numbers—most avoidable mistakes come from date and amount mix-ups.

2) Enter the offer details the analyzer needs

Use the same offer settlement information you would document for a written offer of judgment in the case record.

Typical inputs (names may vary slightly in the UI):

• Offer amount: the settlement amount stated in the written offer
• Offer date: the date the offer was served/filed (choose the date that matches how your workflow records it)
• Case type (if prompted)
• Claim amount / judgment basis (if prompted): the amount the analyzer uses for comparison logic
• Offer side (if prompted): whether you made the offer (e.g., plaintiff/offering party) or the other side did (e.g., defendant/offering party)

As context for what the statute is talking about, Connecticut’s offer of judgment framework applies to an “offer of judgment”—i.e., a written offer to settle a claim made by one party to another party in a civil action. See Conn. Gen. Stat. § 52-192a (source):
https://www.cga.ct.gov/current/pub/chap_903.htm#sec_52-192a

3) Enter the outcome information used for comparison

The analyzer generally evaluates whether the eventual result is more or less favorable than the offer by comparing:

• the offer amount, and
• the final judgment (or a relevant award figure you enter)

Add these (as prompted):

• Judgment amount (or the relevant court-calculated figure)
• Any timing inputs the UI requests (for example, how long after the offer certain outcomes occurred)

If the tool asks for multiple monetary values (for example, principal vs. totals), enter the figures that correspond to what the analyzer expects for the judgment comparison. If you’re unsure, use the “total judgment” figure your judgment entry reports.

4) Confirm the Connecticut timing logic (default rule)

For Connecticut, the analyzer uses Conn. Gen. Stat. § 52-192a-based logic to model the consequences tied to offers of judgment in civil actions.

Important default reminder (no claim-type-specific sub-rule found):
In this brief, no claim-type-specific sub-rule was found, so the analyzer should rely on the general/default statutory period for computing the consequence window, rather than splitting into different timelines by claim category.

5) Run the calculation and review outputs

Click Calculate (or the analyzer’s equivalent button). Then review the outputs in this order:

1. Comparison result

   • Whether the final judgment (your entered judgment number) is more favorable than the offer according to the analyzer’s comparison rules.

2. Potential cost/fee impact estimates

   • The analyzer may report projected shifts or additional amounts tied to the statute-driven mechanism.

3. Step-by-step explanation panel (if available)

   • Many DocketMath workflows provide a breakdown of which inputs were used and how the thresholds were applied.

Because these models are only as accurate as the numbers you enter, double-check:

• whether your judgment amount is the same basis the tool expects (e.g., totals including interest vs. amounts excluding certain add-ons), and
• whether the offer amount matches the written offer amount (not an amended or later counteroffer figure).

6) Run sensitivity checks (change one variable at a time)

To see what drives the outcome, rerun scenarios with small, deliberate changes:

• Change offer amount first

  • e.g., try offer amount ± 10% or a fixed step like ± $5,000 (if you want a quick sense of sensitivity)
• Keep judgment amount constant for the first pass
• Then, if needed, adjust judgment amount slightly for a “near-threshold” view

If the analyzer UI supports timing modeling, you can also test earlier vs. later dates—but only if you’re intentionally modeling timing impacts, since changing dates can be harder to justify than changing amounts.

A helpful interpretation rule:

• If your analysis result “flips” when the judgment crosses a threshold, you’ll see that it’s the relative difference between offer and judgment doing the work.

Common pitfalls

These are the most common issues that cause wrong or misleading outputs when running offer-of-judgment calculations, especially when a tool relies on statute-linked logic like Conn. Gen. Stat. § 52-192a.

• Wrong judgment number

  • Example: entering a damages component when the analyzer expects the total judgment it uses for the comparison.

• **Inconsistent monetary basis (totals vs. components)

  • Some judgments are entered as totals that include interest or other add-ons; others are separated. Use the same basis your tool expects so the comparison is apples-to-apples.

• Incorrect “offer side”

  • If you accidentally select that the other side made the offer (when you made it), the interpretation can effectively reverse.

• Confusing offer date with filing date

  • Offer date can matter for timing logic. Use the date that matches how the offer was served/filed per your records and how the tool defines the “offer date.”

• Assuming claim-type-specific sub-rules

  • For this workflow, no claim-type-specific sub-rule was found, so the analyzer should use the general/default statutory period rather than creating claim-by-claim timelines.

• Only running one scenario

  • If you’re uncertain whether the court outcome will land above or below the offer threshold, run multiple scenarios (at least a couple of near-range alternatives) instead of relying on a single point estimate.

Try it

1. Go to /tools/offer-of-judgment-analyzer
2. Confirm the jurisdiction is **Connecticut (US-CT)
3. Enter:

   • Offer amount
   • Offer date
   • Judgment amount
4. Click Calculate
5. Do a quick scenario check:

   • Rerun with offer amount ± 10%
   • Keep judgment amount constant for the first comparison
6. Compare the results:

   • whether the analyzer changes from “not favorable” to “favorable” relative to your offer amount, and
   • how the estimated statutory consequences move as you cross that threshold.

This approach helps you identify which input—offer amount vs. judgment outcome—is most influential in the result.

Related reading

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