Abstract background illustration for How Offer Of Judgment Analyzer rules vary in Connecticut

How Offer Of Judgment Analyzer rules vary in Connecticut

5 min read

Published June 4, 2026 • By DocketMath Team

Partially verified

older_than_packet

How Offer Of Judgment Analyzer rules vary in Connecticut

Connecticut’s offer-of-compromise framework is driven by a single statute—Conn. Gen. Stat. § 52-192a—and it includes a clear timing requirement tied to the trial date. DocketMath’s Offer Of Judgment Analyzer can help you model the potential financial impact of an offer, but the outputs only hold up if you apply Connecticut’s procedural prerequisites—especially the “not later than thirty days before trial” filing deadline.

Below is a jurisdiction-aware checklist of what varies in Connecticut (US-CT) and what to verify before relying on Analyzer results. This is not legal advice; use it as workflow guidance for case analysis and calculations.

Note: Connecticut’s statute does not appear to carve out a different deadline by claim type (no “contract vs. tort” timing exception was found). The Analyzer should use the general/default timing rule from Conn. Gen. Stat. § 52-192a.

What varies by jurisdiction

Offer-of-judgment mechanics typically vary across jurisdictions in three areas: (1) timing for serving/filing, (2) coverage scope (what types of cases are eligible), and (3) how the post-rejection consequences are triggered. In Connecticut, the most practically important variable for Analyzer calculations is the timing window.

1) Filing deadline relative to trial date (the timing gate)

Connecticut sets a hard cutoff for the plaintiff’s written offer:

  • Deadline:not later than thirty days before trial
  • Timing trigger: after commencement of a civil action
  • Offer form: a written “offer of compromise” directed to the defendant, signed by the plaintiff or the plaintiff’s attorney, and filed with the clerk

Statutory anchor: Conn. Gen. Stat. § 52-192a
Source: https://www.cga.ct.gov/current/pub/chap_903.htm#sec_52-192a

How this changes Analyzer outcomes:
DocketMath can compare offer economics to expected recovery, but if the offer falls outside the statutory timing window, the analysis may effectively be modeling an offer that is not procedurally usable. In other words: treat the “30 days before trial” calendar requirement as a gating item before you treat any output as meaningful.

2) Covered action types (coverage scope)

Connecticut’s statute describes the coverage in the opening clause:

  • Civil actions “based upon contractor
  • Civil actions “seeking the recovery of money damages

Statutory anchor: Conn. Gen. Stat. § 52-192a
Source: https://www.cga.ct.gov/current/pub/chap_903.htm#sec_52-192a

How this changes Analyzer outcomes:
If your matter does not fit within the statute’s coverage language, the Analyzer’s “offer of compromise” assumptions may not match the legal reality of your case. This can affect how confidently you should interpret any estimated financial impact.

3) Offer form and signatory (written + signed + filed)

Connecticut requires a written offer of compromise that is:

  • signed by the plaintiff or plaintiff’s attorney
  • directed to the defendant
  • filed with the clerk

Statutory anchor: Conn. Gen. Stat. § 52-192a
Source: https://www.cga.ct.gov/current/pub/chap_903.htm#sec_52-192a

How this changes Analyzer outcomes:
Even with the right “economic” offer amount, missing or incorrect form mechanics can undermine whether the statute is properly invoked. For Analyzer use, this means you should confirm the factual record supports eligibility before interpreting results.

What to verify

Before you use /tools/offer-of-judgment-analyzer for Connecticut, verify the following so the Analyzer is calculating against correct assumptions.

A. Confirm the “30 days before trial” deadline using the operative trial date

Check the dates that appear on the docket and any scheduling orders:

  • Offer filing date (the day the written offer was filed with the clerk)
  • Trial date (the scheduled trial date set by the court)
  • Compute: offer filing must be ≤ 30 days before trial

Connecticut rule to apply:
The offer must be filed “not later than thirty days before trial.”
Conn. Gen. Stat. § 52-192a
Source: https://www.cga.ct.gov/current/pub/chap_903.htm#sec_52-192a

Pitfall to avoid: If the trial date was changed by continuance or a scheduling amendment, use the operative trial date reflected in the most current order—not an earlier vacated date.

B. Verify the statute’s coverage language fits your case

Do a quick coverage sanity check:

  • ☐ The action is based upon contract, OR
  • ☐ The action seeks money damages

Connecticut anchor: “based upon contract or seeking the recovery of money damages.”
Conn. Gen. Stat. § 52-192a
Source: https://www.cga.ct.gov/current/pub/chap_903.htm#sec_52-192a

C. Confirm written offer mechanics (signature + filing)

Make sure the record supports:

  • ☐ The offer is written
  • ☐ It is signed by the plaintiff or the plaintiff’s attorney
  • ☐ It is filed with the clerk of the court

Statutory anchor: Conn. Gen. Stat. § 52-192a
Source: https://www.cga.ct.gov/current/pub/chap_903.htm#sec_52-192a

D. Enter complete inputs into DocketMath (so outcomes are interpretable)

In DocketMath’s Offer Of Judgment Analyzer (US-CT), use inputs that let the tool test timing and compare economics:

  • Offer amount (the compromised sum)
  • Offer date (to test the “30 days before trial” condition)
  • Trial date (operative docket trial date)
  • Expected/assessed recovery input (what benchmark you want the tool to compare against)
  • Costs/fees assumptions (if applicable in your Analyzer configuration)

To start, use: Offer Of Judgment Analyzer.

If you’re also organizing milestone dates, you may find it useful to cross-check timing in DocketMath with Case timeline before calculating “30 days before trial.”

Warning: Using the wrong trial date (e.g., an earlier date that was vacated) can flip the timing gate from “eligible” to “potentially noncompliant,” which will change how you should interpret the expected-value output.

Related reading

Sources and references