Spreadsheet checks before running deadlines in New Hampshire

What the checker catches

Run this scenario in DocketMath using the Deadline calculator.

Spreadsheet errors can quietly sabotage deadline-driven workflows—especially when multiple dates, offsets, and copy/paste rules are involved. DocketMath’s deadline checker is designed to sanity-check the math before you operationalize a deadline in a New Hampshire workflow.

New Hampshire’s default civil statute of limitations is 3 years under RSA 508:4. There doesn’t appear to be a claim-type-specific sub-rule you must apply for this general checker discussion, so this checker workflow treats 3 years as the general/default baseline and focuses on whether your spreadsheet’s date logic matches that baseline. (This is general guidance and not legal advice—use it to validate your spreadsheet calculations, and confirm any legal specifics separately.)

Here are the most common issues the checker is built to catch:

• Wrong baseline duration

  • Example: your spreadsheet assumes 2 years or 4 years.
  • Output mismatch: the computed “end of limitations” date will drift by weeks or months depending on the start date.

• Date math done on text instead of real dates

  • Example: “1/2/2025” is stored as text rather than an actual date value.
  • Symptoms:

    • “+ 3 years” silently concatenates strings or throws errors.
    • “days until deadline” becomes blank, jumps unexpectedly, or flips negative.

• Off-by-one day logic

  • Example: treating an anniversary date as the day before or after the intended cutoff.
  • Symptoms:

    • The deadline lands one day early/late.
    • Columns that compute “remaining days” show odd transitions (e.g., the deadline appears passed but remaining days remain positive).

• **Misaligned start date fields (wrong column / wrong row)

  • Example: using “date received” rather than the “date of event,” or referencing the wrong row after copy/paste shifts.
  • Symptoms:

    • One case/person line is consistently off while others look plausible.
    • The error pattern tracks with where the source data came from, not with the date itself.

• Leap-year and month-end behavior

  • Example: start date is Feb 29, 2024.
  • Symptoms:

    • Adding “3 years” can yield Feb 28 or Mar 1 depending on the formula approach.
    • The checker helps you spot the anomaly so you can decide which convention your sheet uses and keep it consistent.

• Mixed locales / ambiguous date formats

  • Example: “03/04/2025” interpreted as March 4 vs April 3.
  • Symptoms:

    • Deadlines jump by ~30–31 days while still appearing “reasonable.”

To keep the checks concrete, DocketMath’s checker output should include:

• the computed limitations end date using the 3-year general/default period under RSA 508:4, and
• a cross-check that surfaces whether your computed end date aligns with the expected baseline for the start/event date you feed into the sheet.

When to run it

Run the checker at moments where your spreadsheet is most likely to change or where a deadline drives downstream actions.

Use this timing checklist:

• Before the first “deadline” column is trusted

  • When you add the column that calculates the “limitations end date” from a start/event date.

• After any formula edits

  • Even a “small fix” like changing DATE() inputs or switching YEAR()/EDATE() functions can alter month-end/leap-year outcomes.

• After bulk data imports or copy/paste

  • New rows, new cases, or pasted datasets often include dates stored as text or with different formatting.

• Whenever the date logic is reused across tabs

  • One tab’s working formula doesn’t guarantee another tab copied it correctly—cell references and named ranges can drift.

• On a schedule you can actually maintain

  • If you work deadlines weekly, run a quick checker sweep at the start of each week before decisions are made.

Suggested operational flow (fast and practical):

Try the checker

Here’s a worksheet-style way to validate your logic using DocketMath’s deadline tool—without changing your whole workflow.

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

1) Decide what your spreadsheet uses as the “start date”

Most deadline mistakes come from selecting the wrong column. For the purposes of the general baseline discussed here, your checker input should be the date you are using as the limitations start/event date in your sheet (even if your organization labels it differently, like “incident date” or “event date”).

Common columns to confirm:

• Event/incident date
• Filing date (usually not the start date for limitations math)
• Date received (often not the same as event)

2) Confirm the baseline rule your sheet encodes

DocketMath’s checker assumes the general/default 3-year period under RSA 508:4. Your spreadsheet should reflect that same baseline.

A quick comparison you can do in your sheet:

• Compute start date + 3 years using your current formula.
• Feed the same start date values into DocketMath’s checker.
• Compare the computed “end of limitations” dates.

If your sheet is using a different term (like adding 36 months vs adding 3 calendar years), results can differ around month-end/leap-year boundaries.

3) Use “known stress test” rows

Before running the full dataset, include at least:

• a mid-month start date (e.g., 2024-01-15)
• a month-end start date (e.g., 2024-01-31)
• a leap-year start date (e.g., 2024-02-29)
• a date near a year boundary (e.g., 2023-12-31)

Then validate:

• Does every row produce an end date consistent with 3-year logic?
• Do “days remaining” calculations (if you track them) decrease smoothly as expected?
• Are there any rows where the checker reports a mismatch or a date parsing issue?

4) Review outputs and decide what to fix in the spreadsheet

When the checker flags issues, you’ll typically adjust one of these:

• If dates are stored as text: convert to real date values and re-run.
• If your formula adds months instead of years: align your method to the convention you want.
• If one row is consistently off: check for the wrong start-date reference (cell shift, wrong column, or mixed units).
• If leap-year behavior looks inconsistent: standardize the convention in your sheet and keep it consistent across tabs.

Ready to apply this to your workflow? Start with DocketMath’s deadline tool: /tools/deadline

Related reading

• Browse the blog

Related reading

• Why deadlines results differ in Canada — Troubleshooting when results differ
• Worked example: deadlines in New York — Worked example with real statute citations
• Emergency deadline checklist for Canada — Emergency checklist and quick-reference inputs