Spreadsheet checks before running deadlines in Connecticut

What the checker catches

Before you run any Connecticut deadline logic from a spreadsheet, DocketMath’s deadline checker can help you catch “silent failures” that otherwise show up as wrong dates, off-by-one errors, or missing assumptions.

This is especially useful because Connecticut’s general/default limitations period is typically 3 years under Conn. Gen. Stat. § 52-577a. Important: the checker is not trying to guess a specific claim-type deadline from your sheet. Instead, it helps you validate that your spreadsheet’s date math matches the default 3-year framework you’re using—so you can trust the computed deadlines you’re about to operationalize.

Common issues the checker can catch in a deadline spreadsheet:

• Date parsing errors

  • Example: a cell formatted as text ("2026-01-05") won’t behave like a real date, causing downstream calculations to return nonsense or blanks.
• Start-date mistakes

  • Many deadline formulas depend on the trigger date (the “event date” you’re using). If the trigger date is entered off by a day, your deadline will shift too.
• Off-by-one day logic

  • Spreadsheet teams often disagree on whether to count the trigger day as day 0 or day 1. A one-day discrepancy can cascade into “missed deadline” outcomes.
• Incorrect “add years” method

  • Using =DATE(YEAR(start)+3,...) can break on leap years or month-end dates (e.g., Feb 29). A robust approach should match how you intend to compute “3 years from the trigger date.”
• Mixing date systems

  • Some files use Excel’s serial date system while others store ISO strings. The checker can help you verify that the inputs you think are dates are actually consistent.
• Hidden time components

  • If your spreadsheet stores timestamps, a midnight vs. midday difference can affect ordering or rounding if your formula includes time-aware steps.
• Missing override flags

  • If your sheet has special-case columns like is_tolling_applied or is_extension_expected, your formula might ignore them unless you explicitly check those flags.

Note (disclaimer): This page focuses on spreadsheet validation, not legal advice. Also, Conn. Gen. Stat. § 52-577a is the general/default period. If a specific matter is governed by a different, claim-type-specific rule, the spreadsheet’s “default 3-year” assumption may not match the governing law.

Quick sanity-check table (what changes when inputs change)

When to run it

Run the checker at two points: (1) before you bulk-run deadlines and (2) after any structural change to the sheet.

A practical workflow that reduces risk:

1. After you set up the inputs

   • Confirm the column that represents your trigger date (the “start date” for computing the limitations deadline).
2. Before you apply formulas to every row

   • Test the logic on 3–5 rows with known dates, including:

     • A normal date (e.g., 2025-06-15)
     • A month-end date (e.g., 2024-01-31)
     • A leap-year date (e.g., 2024-02-29)
3. Whenever you edit formulas

   • If you change DATE(...), EDATE(...), or conditional branching, re-run the checker. Spreadsheet refactors commonly introduce subtle differences.
4. Before exporting or using results

   • If your workflow produces an attachment, docket entry, or task list, validate the final output dates.

Go/no-go checklist:

Also, because Connecticut’s general/default limitations period is 3 years under Conn. Gen. Stat. § 52-577a, your sheet’s core calculation should reflect that default assumption. If your sheet includes logic to decide when the default applies versus when another rule might apply, make sure that branching is explicit and testable.

Try the checker

Use DocketMath to validate the deadline calculation your spreadsheet is about to produce. Since your sheet likely uses the trigger date as the key input, you can align your spreadsheet logic with the tool output before you run the full table.

A minimal, spreadsheet-first approach:

1. In your spreadsheet, identify:

   • TriggerDate (the date you’re treating as the limitations start)
   • DeadlineCalculated (your computed result)
2. Pick 3 test rows and record:

   • TriggerDate values
   • The computed DeadlineCalculated values
3. Run those same trigger dates through DocketMath’s deadline calculator at least once before bulk export.

Primary CTA: DocketMath Deadline Tool

To validate properly, compare what you get from your spreadsheet against what the tool returns. Adjust your spreadsheet only where there’s a mismatch—most often due to:

• date parsing (text vs. date),
• leap-year handling,
• or the “add years” function choice.

If you want to improve your spreadsheet formulas before checking them, start by auditing the date-handling portion:

• Convert trigger dates to consistent date types.
• Ensure leap-day cases are treated consistently with your chosen “3 years from trigger” rule.
• Avoid formulas that silently coerce text to dates incorrectly.

Finally, document the default assumption in your sheet so reviewers can quickly understand what the number represents. For the general rule, the key citation driving the default is:

• Conn. Gen. Stat. § 52-577a — general/default limitations period of 3 years

Related reading

• Why deadlines results differ in Canada — Troubleshooting when results differ
• Worked example: deadlines in New York — Worked example with real statute citations
• Deadlines reference snapshot for New Hampshire — Rule summary with authoritative citations