Common deadlines mistakes in New York

Running deadlines in New York looks simple—until it isn’t. A missed day here, a misread rule there, and suddenly a motion is late or a notice is defective. This post walks through common traps in New York deadline calculations and how to structure your workflow so they’re less likely to happen.

Throughout, assume we’re talking about civil litigation deadlines in New York state courts unless otherwise noted.

The top mistakes

• 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

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

1. Forgetting to add mailing days (CPLR 2103)

One of the biggest recurring issues is misapplying the extra days for service by certain methods.

Typical problems:

• Treating every deadline as “X days from service” without asking how service was made.
• Adding the wrong number of days for mailing or overnight delivery.
• Forgetting that some service methods (e.g., personal delivery) do not get any extra days.

Key New York quirks:

• Service by mail usually adds 5 days.
• Service by overnight delivery usually adds 1 business day.
• Service by electronic means (e.g., NYSCEF) generally does not add mailing days unless a rule or stipulation says otherwise.
• Service by personal delivery: no extra days.

When you plug a date into a tool like DocketMath’s deadline calculator, choosing the wrong service method input will shift the computed due date by days.

2. Miscounting “days” vs “business days”

New York rules often say “days,” but not all days are created equal.

Common mistakes:

• Treating a “10 day” period as “10 business days” when the rule means calendar days.
• Forgetting that when the period is less than 7 days, you often exclude weekends and certain holidays.
• Assuming your local practice (e.g., federal court) about business days applies in state court.

This shows up a lot with:

• Short motion schedules
• Orders to show cause
• Time to serve after filing

If you don’t check whether the rule says “days” or “business days,” your deadline can slide by two or three days without you noticing.

3. Ignoring New York court holidays and “snow days”

New York has:

• Statewide legal holidays
• Occasional emergency closures (storms, blackouts, public health emergencies)
• Local variations in court operations

Two frequent problems:

1. Calculating a deadline that falls on a Saturday, Sunday, or legal holiday and not rolling it to the next business day when the rule requires it.
2. Forgetting about emergency orders that toll or extend deadlines (for example, during major storms or the COVID-19 tolling orders).

If your workflow doesn’t explicitly account for holidays and closures, your “perfect” math can still yield a wrong date.

4. Confusing state and federal rules in New York

Practitioners who bounce between:

• New York Supreme/County/City courts, and
• S.D.N.Y./E.D.N.Y. (or other federal courts)

often mix up:

• The counting method (FRCP vs CPLR)
• Mailing rules
• Local rule extensions
• Electronic filing rules

Example: Federal Rule 6(d) vs CPLR 2103’s mailing extensions. They’re similar but not identical—and they don’t apply interchangeably.

If you use the wrong rule set as your mental template, your deadline can be off by a day or more.

5. Not pinning down the true “triggering event”

Your calculation is only as good as your start date. Common “trigger” mix-ups:

• Using the date on the document instead of the date of service.
• Using the date of e-filing instead of the date the system records as service via NYSCEF.
• Using the date you received a letter rather than the date it was mailed (when the rule keys off mailing).
• Using the date the order was signed instead of the date it was entered or served with notice of entry, depending on the rule.

If you misidentify the trigger, every subsequent deadline built on that date is wrong—even if your counting method is flawless.

6. Overlooking local rules, part rules, and orders

New York practice is famously “local.” Beyond the CPLR and statewide rules, you may have:

• County-specific rules
• IAS judge part rules
• Case-specific orders (e.g., scheduling orders, stipulations “so ordered”)

Mistakes that flow from this:

• Relying only on CPLR time periods when a case management order has shorter (or longer) deadlines.
• Missing a judge’s part rule that modifies briefing schedules or reply time.
• Assuming a stipulation “subject to court approval” is effective before it is actually so ordered.

If your calculation ignores these overlays, your deadline can be technically late even if it complies with the default CPLR period.

7. Failing to track multiple dependent deadlines

New York litigation often chains deadlines:

• Opposition due X days after service of motion.
• Reply due Y days after service of opposition.
• Sur-reply or supplemental submissions by court order.

Typical issues:

• Updating the motion return date but forgetting to recompute opposition and reply dates.
• Adjusting for one party’s service method but not the other’s (e.g., movant served by NYSCEF, opponent serves opposition by mail).

Without a clear dependency map, one change in the chain silently corrupts all the later dates.

8. Not documenting assumptions in your calculations

Even when you get the math right, future-you (or a colleague) may not remember:

• Which service method you assumed
• Which holiday calendar you used
• Whether you treated a date as “date of entry” or “date of service with notice of entry”
• Whether you assumed CPLR default rules or a specific scheduling order

When the other side disputes timeliness or the court questions a date, you’re stuck reconstructing your logic from scratch.

How to avoid them

Below are practical ways to structure your inputs and review your outputs so the odds of error drop.

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. Treat “service method” as a mandatory input

Before you calculate anything, lock in:

• How was the document served?

  • Personal
  • Mail
  • Overnight delivery
  • NYSCEF / electronic
  • Other method authorized by court or agreement
• When was it served (not just when you saw it)?

In DocketMath’s deadline tool:

• Select the exact service method instead of defaulting to “mail” or “electronic.”
• Watch how the due date changes as you switch between “mail” and “personal” to see the impact of mailing days.

If you’re unsure of the service method, mark the calculation as tentative and verify with the proof of service or NYSCEF record.

2. Always confirm whether the rule uses calendar days or business days

When you read a rule or order:

• Note whether “days” means:

  • Calendar days (weekends count, but the last day may roll if it falls on a weekend/holiday), or
  • Business days (weekends/holidays don’t count).
• For short periods (under 7 days), confirm whether weekends/holidays are excluded from the count.

In your workflow:

• Add a brief label next to every deadline in your case chart:

  • “C” for calendar days
  • “B” for business days
• Use the same notation in DocketMath’s notes field or your case management system so the assumption is visible.

3. Use a New York-specific holiday and closure calendar

To reduce “surprise” non-business days:

• Maintain or subscribe to:

  • A New York state court holiday calendar
  • Alerts for emergency orders (e.g., OCA announcements)
• When counting:

  • Confirm whether the last day falls on a weekend or legal holiday.
  • If so, verify whether the rule rolls it forward.

With DocketMath:

• Compare the tool’s result to your manual count for at least one sample deadline in a case, especially around late December/early January and long weekends.
• If there’s a discrepancy, double-check whether a New York-specific holiday or emergency order is in play.

4. Explicitly choose the rule set: CPLR vs FRCP

When you start a new matter:

• Label each case as:

  • “NY state (CPLR)”
  • “Federal (FRCP + local rules)”
• For hybrid situations (e.g., removed cases), document the transition point: which deadlines are governed by which system.

In DocketMath:

• Use jurisdiction filters (e.g., US-NY) to ensure the rules engine is using New York state rules when you run a calculation.
• Avoid reusing a calculation template built for federal court in a New York state case without revisiting every assumption.

5. Nail down the triggering event before you count

Before you enter a date:

• Identify whether the rule is keyed to:

  • Date of service
  • Date of entry of an order
  • Date of service with notice of entry
  • Date of mailing
• Pull supporting evidence:

  • NYSCEF notification
  • Stamped order
  • Proof of service
  • Envelope postmark (if relevant)

Then:

• Enter that specific trigger in the calculator.
• Add a note like: “Trigger = service with notice of entry via NYSCEF on 3/14/26 (per NYSCEF email).”

If later someone claims the notice was served on a different date or by a different method, you can quickly rerun the calculation with updated inputs.

6. Overlay local rules and orders on top of CPLR

Develop a two-step rule check:

1. Baseline: Determine the default CPLR or statewide rule deadline.
2. Overlay: Check for:

   • County rules
   • Part rules
   • Case-specific orders or stipulations

If any of those conflict with the default period, the more specific authority (e.g., a so-

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