Inputs you will need

To calculate litigation deadlines in Connecticut with DocketMath’s deadline calculator for US-CT, you’ll need a small but precise set of inputs. Think of this as your “pre-flight checklist” before you click Run.

Use this as a quick reference while you’re in DocketMath:

Below is how each one affects your Connecticut deadline calculations.

Jurisdiction

• What you select: United States – Connecticut (US-CT)
• Why it matters:
  Connecticut has its own:

  • Practice Book rules (civil, criminal, family, appellate)
  • Court-specific standing orders
  • State holidays

DocketMath uses the jurisdiction to pull the correct rule set and holiday calendar.

Trigger event type

• Examples:

  • Service of complaint
  • Entry of judgment
  • Filing of motion
  • Notice of decision or order
  • Service of discovery requests
• Why it matters:
  Different rules attach to different events. For example:

  • Time to respond to a complaint may be different from time to respond to a motion.
  • Post-judgment deadlines may have their own clocks.

DocketMath uses the trigger type to select the right rule(s) from the Connecticut Practice Book or applicable procedural rules.

Trigger event date

• What you enter: The calendar date the event legally occurred:

  • Date of service
  • Date of entry on the docket
  • Date of filing
  • Date of notice
• Why it matters:
  This is the “Day 0” for the calculation. Connecticut rules often:

  • Exclude the day of the event from counting
  • Start counting on the next day

A one-day error here shifts every dependent deadline.

Trigger event time (when relevant)

• When it comes up:

  • Events close to midnight or end of business
  • Same-day filing cutoffs (e.g., before/after 5:00 p.m. or e-filing cutoff)
• Why it matters:
  Some rules:

  • Treat filings after a certain time as filed the next court day
  • Tie rights to whether an event happened “on” a given day at all

If DocketMath asks for time, it’s because the rule can change depending on whether the event is counted as that day or the next.

Service method

• Common options:

  • In-person / hand delivery
  • Mail
  • E-filing / electronic service
  • Overnight delivery / commercial carrier
• Why it matters:
  In some contexts, Connecticut rules:

  • Add extra days when service is by mail or certain other methods
  • Treat e-service differently from traditional service

Changing service method can:

• Extend or shorten the deadline
• Change whether weekends/holidays adjustments apply at the end of the period

Court type and level

• Examples:

  • Connecticut Superior Court (civil / criminal / family)
  • Connecticut Appellate Court
  • Connecticut Supreme Court
  • Probate or specialized proceedings (where supported)
• Why it matters:
  Different courts apply:

  • Different rule books (Practice Book sections vs. appellate rules)
  • Different holiday calendars or local practices
  • Different timing for appeals, motions, and post-judgment filings

Selecting the wrong court type can silently pull the wrong rule set.

Case type / proceeding type

• Examples:

  • General civil
  • Family
  • Criminal
  • Housing
  • Administrative appeal
• Why it matters:
  Within Connecticut:

  • Civil, criminal, and family often have different response times
  • Some proceedings (e.g., administrative appeals) have statutory deadlines

DocketMath uses case type to narrow down which Connecticut rules apply to your specific matter.

Document type or action

• Examples:

  • Answer or responsive pleading
  • Motion to strike / motion to dismiss
  • Opposition / objection to motion
  • Reply brief
  • Notice of appeal
  • Discovery responses (interrogatories, requests for production, etc.)
• Why it matters:
  Even within the same case type:

  • An answer might be due on one schedule
  • An objection to a motion might be due under another
  • A notice of appeal may have its own strict clock

DocketMath maps document/action types to the specific Connecticut Practice Book sections or statutes that control timing.

Calendar options (weekends and holidays)

• Typical options:

  • Count all days, but move the due date if it lands on a weekend/holiday
  • Count only court days (for some time periods)
• Why it matters:
  Connecticut rules can:

  • Count in calendar days (including weekends)
  • Or in business/court days for certain tasks

DocketMath uses your calendar options plus the Connecticut holiday calendar to:

• Skip state holidays when required
• Push deadlines that land on a weekend or holiday to the next court day, when the rule says so

Time zone

• What you select: Usually Eastern Time for Connecticut courts.
• Why it matters:
  For e-filing and time-sensitive cutoffs:

  • A filing made at 11:45 p.m. Eastern vs. 12:05 a.m. Eastern can change the filing date
  • Remote practitioners in other time zones must still hit Connecticut-based cutoffs

DocketMath uses the time zone to interpret the trigger time and end-of-day rules correctly.

Local rule set / standing orders (when available)

• Examples:

  • Judicial district–specific standing orders
  • Scheduling orders in a particular case
  • Special rules for complex litigation or specific dockets

• Why it matters:
  Even if the statewide Connecticut rules say one thing, a:

  • Case management order or
  • Scheduling order

  can override default timing.

You may need to:

• Select a local rule profile, or
• Manually adjust if your judge’s order sets different dates

Extensions, stipulations, or modified deadlines

• What to consider:

  • Court-ordered extensions
  • Written stipulations between parties that the court has adopted
  • Tolling orders or stays
• Why it matters:
  If the court has already changed a deadline:

  • The rule-based date becomes a reference point, not the actual due date
  • You may need to add or subtract days from DocketMath’s calculation to reflect the order

DocketMath is most accurate when:

• You enter the original trigger and
• Then factor in any extensions the court has granted.

Where to find each input

Use this section as a sourcing guide for each field you’ll need to fill in DocketMath’s Connecticut deadline calculator.

Some practical habits:

• Check the docket entry, not just your PDF.
  The “Date of entry” on the Connecticut docket can differ from the date on the face of the order.

• Read the certificate of service.
  That’s usually where you’ll see:

  • Mail vs. e-service
  • Service date
  • Sometimes even the exact time for electronic service

• Confirm case type from the initiating document.
  A matter that feels “civil” may actually be:

  • An administrative appeal
  • A special statutory proceeding
    with different timing rules.

Run it

Once you’ve gathered your inputs:

1. Open the Connecticut deadline calculator
   Go to the DocketMath Deadline tool:
   👉 /tools/deadline

2. Select the jurisdiction

   • Choose United States – Connecticut (US-CT)
   • Confirm the court level (e.g., Superior Court, Appellate, Supreme)

Inputs you will need

Use this checklist to gather the core inputs before you run the Deadline tool.

• trigger event date
• rule set (civil/criminal or local rule)
• court level or venue
• service method
• holiday/weekend calendar
• time zone and filing cutoffs

Capture the source for each input so another team member can verify the same result quickly.

Where to find each input

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

Run it

Enter the inputs in DocketMath and run the Deadline calculation to generate a clean breakdown: Run the calculator.

Capture the source for each input so another team member can verify the same result quickly.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Related reading

• Why deadlines results differ in Canada

• Worked example: deadlines in New York

• Deadlines reference snapshot for New Hampshire

• Why we started the DocketMath blog