How to run deadlines in DocketMath for Connecticut

Connecticut’s procedural rules are full of “count X days from Y event” instructions—and a few traps about weekends, legal holidays, and whether a period is shorter than 7 days. DocketMath’s deadline calculator is built to handle these mechanics for you, as long as you give it the right inputs.

This guide walks through how to run Connecticut deadlines in DocketMath, what each input means, and how to avoid the most common mistakes.

Step-by-step

The examples below assume you’re using the DocketMath deadline calculator and that you’ve selected Connecticut (US-CT) as your jurisdiction.

• Select Connecticut in the Deadline tool.
• Enter the trigger dates and any caps or rates.
• Run the calculation and save the output.

1. Start with the triggering event

Every deadline in DocketMath starts with a triggering event. In Connecticut practice, that might be:

• Service of process
• Filing of a motion
• Entry of an order or judgment
• Mailing of a notice
• A scheduled hearing date

On the calculator:

1. Open DocketMath → Deadline calculator.
2. Select Jurisdiction: Connecticut (US-CT).
3. In the “Triggering event” or “Start date” field, enter the calendar date of the event.

DocketMath will use this date as “Day 0” unless the specific rule says otherwise. It then applies Connecticut’s counting rules to figure out the due date.

Example inputs

• Triggering event: “Order granting motion to strike”
• Date of event: 2026-03-01
• Time of event (if required): 4:30 PM (or your best approximation)

DocketMath will then count forward (or backward, if applicable) based on the rule you select.

2. Choose the correct rule or deadline pattern

The calculator needs to know which Connecticut rule pattern to apply. DocketMath usually gives you:

• A search box to find a rule by name or number
• A list of patterns, such as:

  • “X days after service”
  • “X days before hearing”
  • “X days after judgment”
  • “N days to respond to interrogatories”

For Connecticut, look for patterns tied to:

• Connecticut Practice Book rules
• Statutory deadlines (e.g., certain appeals)
• Court-specific patterns (if available)

When you select a pattern, DocketMath will often show you additional fields, such as:

• Number of days (if the rule is configurable)
• Direction (after/before the triggering event)
• Method of service (if service adds extra days)

3. Enter the number of days and direction

Many Connecticut deadlines are expressed as “within X days after” or “at least X days before” a given event.

In DocketMath, you’ll typically see fields like:

• Length of period: enter the number of days (e.g., 20)
• Count direction:

  • “After event” → forward from the triggering date
  • “Before event” → backward from the triggering date

How that changes the output

• If you select “20 days after service”:

  • DocketMath will start counting the day after service as Day 1 (unless the rule says otherwise).
  • It will apply Connecticut’s rules about weekends and holidays.
• If you select “20 days before hearing”:

  • DocketMath will count backward from the hearing date.
  • The hearing date itself is usually Day 0.

You’ll see the raw counted date and the adjusted due date (after applying weekend/holiday rules) in the results.

4. Specify the method of service (if applicable)

Connecticut rules often modify deadlines depending on how service was made. For example, certain deadlines may be extended when service is made by mail or electronic means.

If the DocketMath pattern includes a “Method of service” or “Additional time for service” field, you’ll see options like:

• Personal service
• Mail
• Electronic service
• Sheriff or marshal service (for some contexts)

When you choose a method, DocketMath:

• Applies any extra days the rule provides for that service method
• Re-runs the counting with the new total period

Example

• Base deadline: 20 days after service
• Extra time for mail service: +3 days
• Total period: 23 days

DocketMath will show you both:

• The base period due date (20 days)
• The final due date after adding the extra days and adjusting for weekends/holidays

5. Let DocketMath handle weekends and Connecticut legal holidays

Connecticut has specific rules on what happens when a deadline falls on:

• A Saturday or Sunday
• A legal holiday recognized by Connecticut courts

In many Connecticut contexts:

• If the period is 7 days or more, intermediate weekends and holidays are counted, but if the last day is a weekend or holiday, the deadline typically rolls to the next business day.
• If the period is less than 7 days, weekends and holidays may be excluded from the count.

DocketMath’s Connecticut logic is built to:

• Identify Connecticut court holidays
• Apply the correct rule depending on the length of the period
• Automatically move the due date when required

You’ll usually see:

• A “Counted date” (the raw X-day calculation)
• A “Final due date” (after weekend/holiday adjustment)

6. Adjust for time-of-day or “end of day” rules

Some Connecticut deadlines are tied to:

• Close of business
• Midnight
• Filing system cutoffs (e.g., e-filing by 11:59 PM)

Where applicable, DocketMath will:

• Assume a default end-of-day cutoff for filings
• Show the due date rather than a specific time (unless a time is required for the pattern)

If you need a specific time:

• Enter it in the time field (if available) or
• Note it in your internal workflow, even if the calculator only shows a date

7. Review the Explain++ breakdown

For Connecticut, the safest workflow is to audit the calculation, not just rely on the final date. DocketMath’s Explain++ feature (where available for the pattern) gives you a step-by-step breakdown of:

• How the days were counted
• Which weekends/holidays were skipped or adjusted
• How extra time for service was added
• How the final date was reached

Look for an “Explain++” or “Show breakdown” button in the result panel.

When you click it, you’ll typically see:

1. Start date and whether it was counted as Day 0 or Day 1
2. Day-by-day progression or summarized steps
3. Holiday/weekend adjustments with explanations
4. Final due date and any assumptions used

This makes it easier to:

• Compare the calculation to the Connecticut rules you’re reading
• Catch any mismatch between the rule you intended and the pattern you selected
• Document your reasoning for internal QA

You can read more about Explain++ here: Introducing Explain++: step-by-step calculation breakdowns.

8. Save, export, or re-run with variations

Once you’re satisfied with the Connecticut deadline:

• Save the calculation in your workspace (if your account supports it).
• Export to your case management system or calendar.
• Re-run the same rule with:

  • A different triggering date
  • A different service method
  • A different number of days (if the rule is configurable)

This is especially useful when you need to:

• Compare “what if we serve today vs. tomorrow?”
• Check how a holiday week affects the due date
• Run the same pattern for multiple parties or related filings

Common pitfalls

Connecticut’s rules are detail-heavy. Here are mistakes DocketMath can help you catch—or that you still need to watch for.

• counting from the wrong triggering event
• ignoring court-closed days or holiday rules
• mixing calendar days with court days
• missing time-of-day cutoffs for filing

1. Using the wrong triggering event

Misidentifying the start date can throw off the entire schedule. Examples:

• Counting from the filing date when the rule says “after service”
• Using the hearing date when the rule says “after notice of hearing”
• Using the date of an oral ruling instead of the written order entry date

To avoid this:

• Read the exact rule text: “after service,” “after entry,” “before hearing,” etc.
• Confirm whether the event is filing, service, or entry.
• Match that to the triggering event in DocketMath.

2. Forgetting extra time for mail or electronic service

Connecticut rules may grant extra days when service is made by certain methods. If you:

• Select “personal service” when it was actually mail, or
• Ignore the “add days for service” option,

you’ll get a due date that’s too early.

Use this workflow:

1. Identify the actual service method.
2. Select the matching method in DocketMath.
3. Confirm that the total period (base + extra days) matches your reading of the rule.

3. Miscounting short deadlines (less than 7 days)

Short Connecticut deadlines can treat weekends and holidays differently from longer ones. Two common errors:

Try it

Open the Deadline calculator and follow the steps above: Run the calculator.

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

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

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