Spreadsheet checks before running deadlines in Vermont

What the checker catches

Running deadlines off a spreadsheet is where small math errors turn into big timing problems. DocketMath’s spreadsheet checker is designed to catch the “silent failures” that happen before you even compute a due date—especially errors that look plausible at a glance but are wrong when you stress-test the logic.

Here are the most common spreadsheet issues it can help you sanity-check when you’re working with Vermont deadlines:

• Off-by-one day logic

  • Mistakes like adding “+1 business day” or “+0 calendar days” inconsistently across rows.
  • Example: you compute a deadline with date + 14 in one tab, then compute another deadline with date + 13 in a second tab.

• Business-day vs calendar-day mismatches

  • Some workflows correctly use business days (excluding weekends/holidays), while others accidentally use calendar days.
  • The checker flags patterns where your formulas imply one system but your output looks like another.

• Date parsing errors

  • Excel/Google Sheets often interpret dates as text (e.g., 01/02/2025) or as locale-specific formats.
  • A spreadsheet that “looks right” can still be calculating from a text value rather than a true date serial.

• Inconsistent “start date” fields

  • Deadlines depend on a chosen trigger date (e.g., filing date, service date, receipt date).
  • A frequent spreadsheet bug is mixing triggers—some rows start from “Filed” while others start from “Received,” without a consistent rule.

• Wrong default limitations period assumption

  • Vermont has a general/default statute of limitations period of 1 year. Claim-type-specific sub-rules were not identified here, so the general/default 1-year period is the baseline referenced in this guide.
  • If your sheet assumes a different period—or leaves the period blank and default-fills something else—deadlines will shift materially.
  • Your checker can confirm that the period you’re applying is indeed 1 year for the default workflow you’re running.

• Unit conversion and rounding issues

  • Formulas like =A2 + (365/12) or using day counts derived from months can drift across leap years.
  • The checker helps catch suspicious transformations—especially when outputs change drastically across a 1–2 row sample.

When to run it

A spreadsheet is safest when you validate it before you generate final deadlines and then re-check after you make changes. In practice, run DocketMath’s spreadsheet checker at these points:

1. After you set up the model

   • Right after formulas, columns, and date logic are created.
   • Especially after you add:

     • a trigger date column,
     • a “days/months/years” conversion column,
     • a business-day adjustment column.

2. Every time you change a formula

   • If you touch any date-addition logic, weekend handling, or parsing code.
   • Spreadsheet errors tend to propagate—one changed formula can shift every downstream deadline.

3. Before exporting or sharing deadlines

   • The final step before you:

     • produce a PDF,
     • send a task list to a team,
     • or paste dates into a case management system.

4. On a small “test subset” first

   • Pick 3–5 rows that span different calendar conditions:

     • one where the trigger date is a weekend,
     • one near month-end,
     • one spanning a leap day (e.g., Feb 29),
     • one where holidays might matter if your sheet uses business days.

Recommended test checklist (quick)

Try the checker

Use DocketMath like a calculation stress test: verify inputs first, then confirm the output pattern makes sense.

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

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

Inputs to review in your spreadsheet

Even without changing your data, you can check whether your sheet is set up to compute deadlines correctly. In your spreadsheet, identify:

• **Trigger date (the “start”)

  • The column representing the event that kicks off the period.

• Default limitations period

  • For the Vermont general/default baseline used here: 1 year.
  • If your spreadsheet has a “years” field, confirm it’s set to 1 for the default workflow.

• Date-add method

  • If you’re adding years directly (e.g., =DATE(YEAR(start)+1,...)), confirm it handles Feb 29 correctly.
  • If you’re converting years to days (e.g., 365), confirm leap years are addressed.

• Business-day rules

  • If your deadline system excludes weekends (and possibly holidays), ensure the adjustment happens exactly once.

What outputs should look like (for the 1-year default baseline)

For a default workflow applying 1 year, the checker should help you confirm these output behaviors:

• Deadlines should typically be consistent in spacing (no random 364/366 jumps unless leap-year logic is intentionally modeled).
• Deadlines derived from the same trigger date should not diverge across rows with identical inputs.
• If you toggle from calendar-day to business-day computation in your sheet (even temporarily), deadlines should shift in predictable ways—never in a way that suggests mixed unit logic.

A practical “sanity run” sequence

1. Run the checker on the full sheet after setup, but validate with a test subset first.
2. Fix any flagged issues, then rerun the checker.
3. Confirm that the default period used aligns with Vermont’s general/default 1-year baseline referenced in the jurisdiction data (with no claim-type-specific sub-rules identified here).

• Vermont general/default limitations period: 1 year
• Claim-type-specific sub-rules: not identified in the provided jurisdiction data (so this guide treats 1 year as the baseline default)

If your spreadsheet applies a non-1-year period anywhere (including a hidden default), your deadlines will be off even when formulas look “close.” Catch this early by checking the “years” or “days” parameter used in every path of the formula.

Launch DocketMath deadline tools

Start here if you want to compute/validate deadlines using DocketMath: **Open the deadline tool

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