Spreadsheet checks before running deadlines in United States (Federal)

What the checker catches

Run this scenario in DocketMath using the Deadline calculator.

Before you run federal deadlines off a spreadsheet, you want to catch “silent failures”—cases where the sheet produces a date that looks plausible, but the underlying date logic is wrong. DocketMath’s spreadsheet-checker (the template is “spreadsheet-checker”) is built for this sanity-check step: it reviews the inputs and the deadline computation rules you’ve set up and flags common issues that can lead to missed or miscomputed deadlines.

In a US-FED deadline workflow, the checker most often catches problems like these:

• Wrong starting point

  • Example: your logic expects a service date, but the sheet uses a filed date (or vice versa).
  • Spreadsheet symptoms: everything appears consistent internally, but every deadline shifts by a constant offset.

• **Misapplied “days” rules (calendar vs business)

  • Example: treating “X calendar days” like “X business days,” or the reverse.
  • Spreadsheet symptoms: dates drift forward/back in a way that seems reasonable, but the errors become clearer around weekends and federal holidays.

• Incorrect business-day counting convention

  • Example: counting the start day when your rule counts from the next day, or vice versa.
  • Spreadsheet symptoms: classic off-by-one behavior—often repeatable across every computed deadline.

• Federal holiday handling gaps

  • Example: the sheet’s “business day” calendar is missing a recognized federal holiday (or doesn’t follow your intended holiday list).
  • Spreadsheet symptoms: the spreadsheet agrees with itself, but differs from tools/systems that correctly recognize official observances.

• Timezone / timestamp truncation

  • Example: stripping times in a way that causes a “late day” event to spill into the next calendar date.
  • Spreadsheet symptoms: only certain rows are wrong—often those near midnight—or patterns emerge after copy/import steps.

• Spreadsheet formula breakage

  • Example: copy/paste causing references to point to the wrong column, or an absolute/relative reference mismatch.
  • Spreadsheet symptoms: some deadlines are correct, others are subtly wrong—with no clear explanation based on the underlying date values.

• Ambiguous or inconsistent date formats

  • Example: using a mix of formats like “04/05/2026,” where interpretation can vary by locale or import behavior.
  • Spreadsheet symptoms: only a subset of rows yields extreme shifts (e.g., months/days swapped).

• Blank cells and partial rows

  • Example: one upstream field is missing (like the event date), but the sheet falls back to a default and still outputs a deadline.
  • Spreadsheet symptoms: output cells are “filled in” everywhere, but those rows should have been invalid or flagged due to missing inputs.

Gentle note: this is about data integrity, not legal strategy. A clean spreadsheet helps ensure your calculations are trustworthy, but it’s not a substitute for legal review when stakes are high.

When to run it

Run the checker at two points: before you trust the sheet, and before you commit the results.

A practical cadence for federal deadline spreadsheets:

1. After you finish building or updating the columns, before you duplicate the sheet

   • Validate that:

     • date inputs are consistently formatted
     • the “event date → deadline date” transformation behaves stably
     • your weekend/holiday logic matches the counting rule you intended
   • Also check that you didn’t accidentally hard-code any assumptions into just one column or one branch of an IF statement.

2. Right before you publish, share, or submit calendars

   • This second run catches:

     • manual edits during review
     • new rows that introduce blanks or unexpected formats
     • formula reference drift caused by last-minute copy/paste

A quick spot-check checklist you can use (even before running the tool):

• a weekday event
• a Friday event
• a Saturday/Sunday event
• a row near a federal holiday
• the earliest/latest dates in the sheet

If your sheet supports multiple deadline types, also ensure each type maps to the correct “days” mode (business-day counting vs calendar-day counting). One incorrect mapping can contaminate downstream results across many rows.

Try the checker

Use DocketMath to sanity-check your inputs and date logic before you run deadline calculations.

1. Start from the deadline workflow

   • Open the DocketMath deadline tool here: /tools/deadline
2. Select your spreadsheet input

   • Provide the date columns and the calculation parameters/rules that your sheet is intended to follow.
3. Run the spreadsheet-checker

   • The checker analyzes the sheet’s structure, date parsing, and the logic used for deadline generation.
4. Review the flagged items

   • Prioritize:

     • row-level discrepancies (often blanks, parsing issues, or inconsistent date formats)
     • systemic offsets (often calendar-vs-business-day confusion, or start-day conventions)
     • formula reference anomalies (often copy/paste problems or absolute/relative reference mistakes)

How inputs should change outputs (so you can tell when something is “off”):

• Shift an event date by 1 day

  • Under a correct sheet, deadlines should move in a predictable way according to your counting convention.
  • If deadlines barely move (or jump unexpectedly), the sheet may be anchoring to the wrong input field.
• Use two rows that differ only by date format

  • If one row is “MM/DD/YYYY” and another uses a different format, the checker should reveal parsing inconsistencies—especially if locale/import behavior differs.
• Compare a case near a weekend or federal holiday

  • Business-day and calendar-day rules should produce distinguishable outcomes near non-business days.
  • If results look identical across those scenarios, the sheet may be ignoring a business-day setting.

Once the checker passes, treat that as confirmation to proceed—but keep the habit: re-check after any edits. Spreadsheets are mutable by design, and small changes can ripple into many deadline outputs.

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