Worked example: statute of limitations in Connecticut

5 min read

Published April 8, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Example inputs

Run this scenario in DocketMath using the Statute Of Limitations calculator.

Below is a worked example of how the DocketMath statute-of-limitations calculator can model the general statute of limitations (SOL) period in Connecticut.

Connecticut’s default/general SOL period for many civil claims is 3 years under Conn. Gen. Stat. § 52-577a. Per your jurisdiction data, no claim-type-specific sub-rule was found for this example—so we treat 3 years as the general default rather than attempting to select a specialized limitation period for a particular cause of action.

This is a practical illustration of date logic, not legal advice. Real cases may involve claim-specific statutes, accrual nuances, or tolling issues that are not modeled here.

Scenario (timeline-style)

Assume a plaintiff alleges a wrongful act that caused damages.

Event	Date	What it means for SOL modeling
Alleged injury / claim accrues	Jan 15, 2023	This is the “starting point” we feed into the calculator as the accrual date
Complaint filed (hypothetical)	Jan 20, 2026	This is the filing date we compare against the computed deadline
Outcome question	“Timely or late?”	Whether filing is on/before the computed SOL expiration

Inputs to the DocketMath statute-of-limitations calculator (modeled)

For this worked example, the core inputs are:

Tool: Use DocketMath at /tools/statute-of-limitations
Jurisdiction: Connecticut (US-CT)
General SOL period: 3 years
Accrual date (claim start): Jan 15, 2023
Filing date: Jan 20, 2026
Rule selection: General/default (Conn. Gen. Stat. § 52-577a; no special sub-rule applied in this example)

Note: This worked example intentionally uses the general 3-year period. Certain claim types may have different rules, including special SOL statutes or accrual doctrines. This example does not try to match a specialized cause of action.

You can think of the calculator as doing one main job for this simplified scenario: compute a deadline by adding the applicable SOL length to the accrual date, then compare the filing date to that deadline.

Example run

Run the Statute Of Limitations calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Apply the general SOL period

Under Conn. Gen. Stat. § 52-577a, the relevant baseline is:

3-year SOL period (general/default)

So the calculator effectively computes:

SOL expiration date = accrual date + 3 years

Step 2: Compute the expiration date

Accrual date: Jan 15, 2023
Add 3 years:
- Jan 15, 2026 = 3-year anniversary

That gives a baseline deadline of:

Baseline SOL expiration: Jan 15, 2026

Step 3: Compare filing date to the deadline

Filing date: Jan 20, 2026
Baseline deadline: Jan 15, 2026

Because Jan 20, 2026 is after Jan 15, 2026, the modeled result is:

Filing is late under the general/default 3-year rule

DocketMath output (conceptual)

When you run the calculator (via /tools/statute-of-limitations), you should expect an output structure conceptually like:

Computed SOL expiration date: Jan 15, 2026
Filing vs. expiration: Jan 20, 2026 is after the expiration
Modeled status: Time-barred under the default general period

As a sanity check, the next section shows how changing only one input at a time can flip the outcome.

Sensitivity check

SOL deadlines often hinge on details in the timeline—especially the accrual date and the filing date. The goal of this section is to show how small input shifts can change whether the filing is treated as “timely” or “late.”

A) Move the filing date earlier by 10 days

Keep accrual date fixed:

Accrual: Jan 15, 2023
SOL deadline (general): Jan 15, 2026
Filing becomes: Jan 10, 2026

Comparison:

Jan 10, 2026 is before Jan 15, 2026

Modeled result: Timely under the general/default period.

B) Move the accrual date later by 30 days

Assume accrual is discovered later than originally assumed.

New accrual date: Feb 14, 2023
SOL deadline: Feb 14, 2026
Filing date stays: Jan 20, 2026

Comparison:

Jan 20, 2026 is before Feb 14, 2026

Modeled result: Timely under the general/default period.

C) Same dates, but filing exactly on the deadline

Accrual: Jan 15, 2023
Deadline: Jan 15, 2026
Filing: Jan 15, 2026

Modeled result: On-time (because filing occurs on the computed expiration date).

Summary table (quick flips)

Accrual date	Filing date	Computed deadline (3 years)	Outcome under general/default
Jan 15, 2023	Jan 20, 2026	Jan 15, 2026	Late (time-barred)
Jan 15, 2023	Jan 10, 2026	Jan 15, 2026	Timely
Feb 14, 2023	Jan 20, 2026	Feb 14, 2026	Timely
Jan 15, 2023	Jan 15, 2026	Jan 15, 2026	Timely (on the deadline)

Pitfall: A change in the accrual date can shift a 3-year SOL deadline by a full month (or more). If your fact pattern involves delayed discovery, continuing harm, or tolling, the “accrual date” you enter into the calculator can affect the outcome even before any specialized statute or tolling issue is considered.

Checklist for running your own Connecticut SOL scenario

Use this short checklist before trusting the computed outcome:

If you want to explore alternative timelines, run multiple iterations in DocketMath and compare the computed expiration dates side-by-side.