Spreadsheet checks before running statute of limitations in Delaware

Sanity-checking your spreadsheet before you run a statute-of-limitations calculation in Delaware is less about “perfect formatting” and more about “can I trust every date and label here?” DocketMath’s spreadsheet checker is designed to stress-test that trust before you click “calculate.”

Below is a practical walkthrough of what the checker looks for, when to run it, and how to interpret what it tells you—using Delaware statute-of-limitations work as the running example.

What the checker catches

The checker is designed around a few simple ideas:

1. Every key date must be unambiguous.
2. Every row should know what “kind” of date it is (accrual, tolling, filing, etc.).
3. The jurisdiction and claim type must be explicit, not implied.

Here’s how that plays out in a Delaware statute-of-limitations spreadsheet.

1. Date-format and parsing issues

The checker looks for dates that are:

• Text instead of dates (e.g., "3/5/22?", "spring 2022")
• Ambiguous formats (e.g., 03/04/22 without a locale setting)
• Missing year pieces (e.g., 3/5 with the year in a separate column)
• Mixed date systems (Excel serial dates in some rows, ISO dates in others)

Typical flags you’ll see:

• “Unparseable date in row 14: ‘3/5/22?’”
• “Inconsistent date format between rows 10 and 35.”

Why it matters in Delaware:
Delaware’s limitation periods are often short (e.g., 2–3 years for many civil claims), so a one-day error can be outcome‑determinative. If the checker can’t confidently parse a date, it warns you before DocketMath’s statute-of-limitations calculator attempts any Delaware-specific logic.

2. Missing or inconsistent “event type” labels

Most statute-of-limitations spreadsheets have a column like:

• Event type
• Category
• Timeline label

The checker looks for a consistent set of labels, for example:

• Accrual
• Injury discovered
• Breach
• Tolling start
• Tolling end
• Filing
• Demand letter (if relevant to your workflow)

It will flag:

• Rows with dates but no event type
• Event types it doesn’t recognize or that conflict with your own mapping
• Multiple rows all labeled as the “main” accrual event

This matters because DocketMath’s Delaware statute-of-limitations logic needs to know:

• Which date(s) could start the clock (accrual or discovery)
• Which ranges might pause it (tolling periods)
• Which date might stop it (filing)

3. Jurisdiction and claim-type mismatches

For Delaware work, you’ll usually want a dedicated column for:

• Jurisdiction (e.g., Delaware, DE, or US-DE)
• Claim type (e.g., contract, personal injury, fraud, etc.)

The checker looks for:

• Missing jurisdiction on rows that look like claim records
• Mixed jurisdictions in the same spreadsheet (e.g., DE and PA)
• Claim types that don’t match your configured list or your DocketMath template

How this affects outputs:

• If all rows are Delaware, the calculator can safely apply Delaware periods.
• If some rows are not Delaware, you’ll be prompted to either:

  • filter to Delaware-only rows, or
  • map each jurisdiction to its own calculation run.

4. Incomplete tolling ranges

Tolling is often the trickiest part of a limitations spreadsheet. The checker looks for:

• A Tolling start with no matching Tolling end
• Overlapping tolling intervals on the same claim
• Tolling ranges that end before they start (a common data-entry error)

For each affected row or claim ID, it will highlight:

• “Tolling start without tolling end”
• “Overlapping tolling intervals for Claim ID 102”

Why this matters in Delaware:

• Delaware courts can treat certain periods (e.g., minority, some fraud/discovery scenarios) as delaying or pausing the clock.
• DocketMath needs clean start/end pairs to show you the clock math clearly.

5. Claim-level consistency checks

If you use a Claim ID column, the checker will also:

• Group events by Claim ID
• Confirm each claim has:

  • At least one candidate accrual/discovery date
  • At most one primary filing date (or clearly labeled multiple filings)
  • A consistent jurisdiction and claim type

If any claim is missing a critical piece, you’ll see something like:

• “Claim ID 204: no accrual or discovery event detected.”
• “Claim ID 310: Delaware jurisdiction, but no claim type set.”

When to run it

In practice, you don’t want the checker to be a once-per-case ritual. It works best if you treat it as a quick test you run at predictable points in your workflow.

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

1. Right after importing or consolidating data

Run the checker immediately after you:

• Import from a case-management system
• Copy/paste from a legacy spreadsheet
• Merge multiple attorneys’ or paralegals’ timelines

This catches:

• Hidden text-formatted dates
• Columns that shifted during copy/paste
• Claim IDs or jurisdictions that didn’t carry over

Checklist:

2. Before each major Delaware limitations analysis

Any time you’re about to use DocketMath’s Delaware statute-of-limitations calculator for a case or matter:

1. Filter your spreadsheet to the relevant Claim IDs.
2. Run the checker on that filtered range.
3. Fix or annotate any warnings that look material.
4. Then send the cleaned range to the calculator.

This helps ensure:

• The calculator’s output lines up with your intended dates.
• Any “edge” issues (e.g., competing accrual theories) are clearly labeled.

3. After manual edits to key dates

Any time someone:

• Changes an accrual date
• Adds or removes a tolling period
• Updates the filing date

…run the checker again on that claim’s rows. Even a single typo (e.g., 2034 instead of 2024) can dramatically change the calculator’s projected deadline.

Try the checker

You can use DocketMath’s spreadsheet checker as a front door to the Delaware statute-of-limitations workflow:

1. Prepare your spreadsheet

   At minimum, include:

   • Claim ID (optional but recommended)
   • Event date (or multiple date columns)
   • Event type (accrual, discovery, tolling start/end, filing, etc.)
   • Jurisdiction (e.g., US-DE)
   • Claim type (e.g., contract, personal injury, fraud)

   A simple structure might look like:

   Claim ID	Event date	Event type	Jurisdiction	Claim type	Notes
   101	2021-03-15	Accrual	US-DE	Contract	Alleged breach
   101	2022-01-10	Tolling start	US-DE	Contract	Negotiation standstill
   101	2022-03-01	Tolling end	US-DE	Contract	Talks ended
   101	2023-02-28	Filing	US-DE	Contract	Complaint filed in DE court

2. Upload or connect your sheet

   • Import from Excel or CSV, or
   • Connect your cloud spreadsheet (if supported in your workspace).

3. Run the checker

   • Select the relevant sheet and range.
   • Confirm which column corresponds to:

     • Dates
     • Event types
     • Jurisdiction
     • Claim type
     • Claim ID (if any)

4. Review the report

   The checker will return:

   • A summary (e.g., “5 warnings, 2 informational notes”)
   • A per-row breakdown of:

     • Parsing issues
     • Missing or conflicting event types
     • Suspicious tolling ranges
     • Jurisdiction/claim-type gaps

5. Clean and re-run

   • Fix obvious data-entry errors.
   • Add clarifying notes where the data reflects a legal judgment call.
   • Re-run until the warnings are either resolved or explicitly acknowledged.

6. Send to the calculator

   Once the checker output looks reasonable, you can pass the same range directly into DocketMath’s statute-of-limitations tool for Delaware and get a step-by-step breakdown of:

   • Candidate start dates
   • Tolling adjustments
   • Projected deadline(s) under your inputs

You can start that process here:
Run a statute-of-limitations calculation in Delaware

Related reading

• Spreadsheet checks before running deadlines in California

• How to calculate deadlines in Delaware

• Choosing the right statute of limitations tool for Vermont

• Why we started the DocketMath blog