Common statute of limitations mistakes in Connecticut

The top mistakes

Running statute of limitations (SOL) calculations in Connecticut can go wrong in predictable ways—especially if you rely on generic “3-year” assumptions without checking the triggering facts and the relevant accrual rules. Using DocketMath to calculate deadlines can help, but the accuracy of any SOL result depends on the inputs you feed it and the legal facts behind those dates.

Below are the most common mistakes we see when people calculate Connecticut SOL timelines.

1) Treating “3 years” as the whole answer—without confirming the claim type

Connecticut’s general/default SOL is 3 years under Conn. Gen. Stat. § 52-577a. However, that statute is a baseline rule, not a guarantee that every lawsuit is governed by the same limitations period.

• What the statute says (general rule): Conn. Gen. Stat. § 52-577a provides a 3-year limitations period as the default/general SOL.
• How this affects your calculation: If your situation is actually governed by a different SOL rule (or a special accrual trigger), using the default 3-year period can produce a deadline that’s off by months—or more.

2) Using the wrong “start date” (triggering event vs. filing date vs. injury date)

Most SOL errors come from a date mix-up. Common wrong inputs include:

• Injury/incident date instead of when the cause of action accrued
• Settlement/notice date instead of when the claim became actionable
• Service/communication date instead of the event that starts the limitations clock

With DocketMath, the deadline is only as good as the start date you input. If the “start date” is wrong, the computed deadline will be wrong—even if the SOL period is correct.

3) Confusing “commencement” with the “mailing” date

A classic timeline slip is assuming that mailing or emailing a complaint is what matters. In many practice settings, SOL analysis depends on when the action is commenced under Connecticut procedure—not when you drafted or mailed paperwork.

If you enter the “mail date” as your filing/commencement date, you may accidentally believe you’re within the window when the operative commencement date is later.

4) Confusing notice dates with accrual dates

People often reach for “when the other side was notified” as a substitute for accrual. In many SOL analyses, notice may provide context, but the legal question is typically tied to accrual—when the claim became actionable.

If you input:

• “Date you discovered harm” as the start date when accrual was actually earlier (or later), your calculated SOL cutoff can shift substantially.

5) Ignoring calendar mechanics (weekends/holidays and exact day counting)

Deadline math is unforgiving. Off-by-one errors can happen when:

• day counting is inconsistent with the tool’s method
• users assume “same day last year” logic without checking how the tool counts
• the deadline falls on a weekend/holiday and filing timing rules apply

Even with the correct start date and period, a calendar error can turn a “timely” deadline into a “late” one.

6) Picking one “reasonable” date and forgetting to test alternatives

Some fact patterns produce multiple plausible dates—incident date, discovery date, communications date—and then the user selects whichever yields the later deadline.

Instead of running only a “best case” scenario, it’s often safer to run separate DocketMath scenarios using different start-date theories that match the accrual facts you believe control, then compare the results.

How to avoid them

A better workflow is simple and repeatable: lock down the governing SOL rule, standardize inputs (especially the start date), and sanity-check the output against the case timeline.

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

1) Confirm the governing SOL rule: use § 52-577a for the general/default 3-year period

Connecticut’s general/default SOL is 3 years under Conn. Gen. Stat. § 52-577a. Treat that as your baseline unless you have documentation indicating another rule applies.

Practical checklist:

• Identify whether your matter fits the general/default category for § 52-577a
• If not, do not rely on the default 3-year period
• If yes, proceed with the 3-year calculation

2) Define the “start date” to match accrual (and keep it consistent)

Before you calculate, write down—in plain language—what event starts the limitations clock. Then use that exact date in DocketMath.

Start-date checklist:

If your facts support more than one plausible accrual date, run multiple scenarios rather than guessing which date is “probably” right.

3) Use DocketMath to compute the deadline concept you actually need

In a typical workflow, DocketMath computes a deadline by combining:

• the 3-year SOL period (for § 52-577a in this general/default setting)
• the start date you input

Your job is to confirm that the “deadline” the tool calculates matches what you’re trying to determine in your process (for example, the time by which the action must be commenced).

For direct access, calculate using:

• DocketMath Statute of Limitations Calculator

4) Sanity-check the computed deadline against your timeline

After you generate a cutoff date, compare it to key record dates:

• filing/commencement-related dates in your workflow
• communications and internal notices
• discovery/knowledge milestones (only if relevant to your accrual theory)
• any events that might affect commencement timing

If the computed deadline is dramatically earlier than your expectations, re-check the start date definition and the facts that support accrual.

5) Reduce calendar mistakes with consistent date handling

To minimize errors:

• use the exact dates pulled from documents
• keep formatting consistent (don’t mix date styles)
• avoid informal “deadline adjustments” unless you are applying a known, documented filing-timing rule

6) Document your SOL assumptions so you can re-run them later

SOL issues are often revisited. Add a short assumptions note, such as:

• statute used: Conn. Gen. Stat. § 52-577a
• period used: 3 years (general/default)
• start date definition: what “accrual” date you used
• commencement-related date concept: how you intend the deadline to be applied in your workflow

This helps prevent “input drift” the next time someone reviews the timeline.

Related reading

• Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
• Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Statute of limitations in United States (Federal): how to estimate the deadline — Full how-to guide with jurisdiction-specific rules