Spreadsheet checks before running deadlines in New York

6 min read

Published April 8, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

What the checker catches

Run this scenario in DocketMath using the Deadline calculator.

Spreadsheet-driven deadline runs fail in predictable ways—especially when you’re calculating New York dates (including weekends/holidays) and then exporting those dates into a case workflow. DocketMath’s deadline checker is built to catch the “date math goes sideways” category of problems before they become missed or misfiled events.

Common spreadsheet issues the checker flags

Here’s what to look for (and what a good checker validates) before you let your sheet “drive” your deadline calendar:

Wrong starting date
- Examples: using a service date column where the sheet expects a filing date, or accidentally referencing a different row (e.g., row for “client received” instead of “court received”).
Off-by-one errors
- Typical culprits: mixing inclusive vs. exclusive counting, then applying “day 1” incorrectly.
Incorrect default limitations period
- If your model assumes New York’s general limitation applies, confirm you’re using the correct baseline.
- New York’s general/default criminal statute baseline for this context is 5 years, referenced in N.Y. Crim. Proc. Law § 30.10(2)(c).
- This content uses that general/default period because no claim-type-specific sub-rule was identified for the scenario described in your brief.
**Unit mismatch (days vs. months vs. years)
- A sheet that adds “365” thinking it’s “1 year” will drift across leap years; similarly, converting months to days without standard rules can break close to the boundary.
Spreadsheet formula inconsistencies
- Copy/paste errors often leave some rows using one approach (e.g., “add months/years” logic) while other rows use a different approach (e.g., a hardcoded “+ 182”).
Cell formatting masquerading as values
- Dates stored as text (e.g., "2026-01-07") don’t behave like dates in Excel/Sheets.
- The checker can detect “date-like strings” that are not actual date serials, which often leads to blank outputs or incorrect comparisons.

Output sanity checks that matter

In addition to catching broken formulas, a deadline checker should verify that the outputs make sense:

Check	What it verifies	Typical failure pattern
Baseline period	Uses the intended period (here, 5 years under the general/default rule)	Some rows use 4 years or 6 years because an older version of the sheet is still in play
Computed deadline	Deadline equals start date + period using the sheet’s counting rules	One column uses start date A, another uses start date B
Date serial validity	Result is a real date	Deadline cell returns blank or a number
Ordering	Event dates follow logical chronology	Deadline precedes the triggering event date
Extremes	Flags unusually early/late deadlines	A swapped day/month can move dates by ~12 months

Quick caution: a spreadsheet can look right visually (formatted as dates) while actually storing date values as text—your downstream deadline run may silently treat them as strings and produce incorrect or empty deadlines. Run the checker before you export.

When to run it

Run a checker at moments when errors are cheapest to fix. Think of it as a pre-flight checklist for your deadline pipeline.

Run the checker before importing a spreadsheet into the Deadline workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.

Run before you calculate deadlines

Do this immediately after you:

import data (CSV exports from a case management system),
apply a template,
or update a formula block.

A good cadence:

After data ingestion (before any deadline columns are populated)
After you change counting logic
After you update the baseline period
- In this brief’s New York scenario, that baseline is 5 years under the general/default rule in N.Y. Crim. Proc. Law § 30.10(2)(c).
Before exporting or uploading deadlines into any tracker

Use it during iteration—not just at the end

If you’re actively editing a template or recalculating with new assumptions, run the checker:

at the end of each major “build” step (data mapping → formula mapping → deadline mapping), and
again once you copy formulas across all rows.

Know the baseline you’re using

This brief uses New York’s general/default period of 5 years tied to N.Y. Crim. Proc. Law § 30.10(2)(c). Because no claim-type-specific sub-rule was identified in the provided jurisdiction data, treat this as the default baseline, not a tailored period.

If your spreadsheet later introduces claim-type logic, you should:

clearly document which rows switch away from the 5-year baseline, and
rerun the checker after the branching conditions go in.

Gentle note (not legal advice): this content is about spreadsheet sanity-checking workflows. It’s always wise to validate the legal baseline with qualified counsel for your specific situation.

Try the checker

DocketMath’s deadline tool is the fastest way to validate that your spreadsheet’s date inputs produce sensible deadlines—before you rely on them. Start here: /tools/deadline.

Upload the spreadsheet, review the warnings, and then run the calculation once the inputs are clean: Try the checker.

A practical “sanity-check” workflow

Use the tool like this:

Step 1: Identify your trigger date column
- Example columns you’ll likely have:
  
  StartDate (trigger/event date)
  
  DeadlinePolicy (if your sheet includes a rule selector)
  
  ComputedDeadline (the date your formulas generate)
Step 2: Confirm the baseline period assumption
- For this New York scenario, set the baseline to 5 years per N.Y. Crim. Proc. Law § 30.10(2)(c) (general/default).
Step 3: Run the checker on a small batch
- Choose 5–20 rows with varied dates (including early, mid-year, and leap-year cases).
Step 4: Inspect output anomalies
- Look specifically for:
  
  deadlines earlier than the trigger date,
  
  blank or non-date outputs,
  
  large jumps inconsistent with “+ 5 years.”

What you should expect as outputs

When the sheet is consistent, the checker should indicate outcomes like:

All deadlines are valid dates
Deadlines align with a 5-year default baseline
No row-to-row formula drift (for example, only some rows use a different time unit or counting rule)

If you see systematic issues (like many deadlines shifting by exactly 1 day), that’s a strong sign of an inclusive/exclusive counting mismatch in the spreadsheet.

Warning: If your spreadsheet stores dates as text, results may look formatted correctly but fail date-based checks. Fix date serialization first, then rerun the checker.

Primary CTA (inline link)

Use the tool here: /tools/deadline