Abstract background illustration for: Spreadsheet checks before running statute of limitations in Vermont

Spreadsheet checks before running statute of limitations in Vermont

7 min read

Published January 26, 2026 • Updated February 2, 2026 • By DocketMath Team

Spreadsheet checks before running statute of limitations in Vermont

Running statute-of-limitations calculations from a spreadsheet can be fast—and risky—especially when you’re dealing with Vermont’s mix of general and subject‑specific limitation periods.

This guide walks through how to sanity‑check your spreadsheet before you push those dates into a statute‑of‑limitations calculator like DocketMath for Vermont (US‑VT).

The goal: catch obvious data and logic problems early, so the calculator is validating good inputs—not rescuing bad ones.

What the checker catches

Think of your “checker” as a small, repeatable set of spreadsheet tests you run on every Vermont limitations sheet.

Here are the main categories to cover and how to implement them.

1. Missing or malformed date inputs

Your first pass is just: “Are these even real dates?”

Checklist

  • All required date fields are populated
  • Date columns are actually stored as dates (not text)
  • No dates outside a reasonable range (e.g., 1980–2050)
  • No obvious “template leftovers” like 1/1/1900 or 00/00/0000

Practical formulas

Assume:

  • A:A = Claim identifier
  • B:B = Accrual date (injury, breach, etc.)
  • C:C = Tolling start
  • D:D = Tolling end

Use helper columns:

=IF(AND(ISNUMBER(B2), B2>=DATE(1980,1,1), B2<=DATE(2050,12,31)), "", "CHECK: accrual date")
=IF(OR(ISBLANK(B2), NOT(ISNUMBER(B2))), "MISSING/INVALID", "")
=IF(AND(NOT(ISBLANK(C2)), NOT(ISBLANK(D2)), D2<C2), "CHECK: tolling end < start", "")

Note: DocketMath will validate and interpret dates, but it can’t tell if 1/1/2030 is a typo for 1/1/2020. The spreadsheet checker is where you catch those “looks valid, but isn’t” issues.

2. Vermont‑specific limitation period selection

Vermont uses different limitation periods depending on the claim type (e.g., contract, personal injury, property, etc.), plus special rules for some categories.

Your checker should confirm that:

  • Each row has a claim type or limitations category selected
  • That category maps to a Vermont‑specific limitations period in a reference table
  • No row silently defaults to a generic period

Suggested structure

Create a reference table on a separate sheet, e.g.:

CodeVermont claim categoryLimitations period (years)Notes (non‑authoritative)
K1Written contract612 V.S.A. § 511 (general)
PIPersonal injury / negligence312 V.S.A. § 512(4)
PROPInjury to property312 V.S.A. § 512(5)
MEDMedical malpractice3Special accrual & repose
FRAFraud / misrepresentation6Check accrual/tolling rules
OTHOther civil (catch‑all)6General civil limitations

Table is illustrative only—confirm the mapping against your own research or firm standards.

Then in your main sheet:

  • E:E = Claim type code (e.g., PI, K1, MED)
  • F:F = Vermont limitations period (years) via lookup
=IFERROR(
  VLOOKUP(E2, ClaimTypes!$A$2:$C$20, 3, FALSE),
  "CHECK: unmapped VT category"
)

What this catches

  • Blank claim types
  • Claim types that don’t exist in your Vermont mapping
  • Rows that would otherwise default to a generic “6 years” without Vermont context

3. Accrual logic vs. filing date

Once you have:

  • Accrual date (B2)
  • Limitations period in years (F2)
  • Any tolling periods (C2:D2, etc.)

You can build a sanity‑check deadline and compare it to the filing date.

Assume:

  • G:G = Filing date

Basic (non‑tolling) check

=IF(
  AND(ISNUMBER(B2), ISNUMBER(F2), ISNUMBER(G2)),
  IF(G2 > EDATE(B2, 12*F2), "LATE? check VT rules", ""),
  "CHECK: missing date/period"
)

This doesn’t try to be a full Vermont computation. It simply flags filings that land after a naive “accrual + period” calculation, so you know where to apply more detailed Vermont rules (e.g., discovery, repose, disability, etc.) or run a full calculator pass.

With a simple tolling block

If you track one tolling interval:

=IF(
  OR(ISBLANK(C2), ISBLANK(D2)),
  0,
  D2 - C2
)

Call that H2 = Number of tolled days.

Then:

=IF(
  AND(ISNUMBER(B2), ISNUMBER(F2), ISNUMBER(G2)),
  IF(G2 > EDATE(B2, 12*F2) + H2, "LATE? check VT rules", ""),
  "CHECK: missing date/period"
)

This gives you a triage view:

  • Blank = likely within time, under the simple model
  • "LATE? check VT rules" = needs closer Vermont‑specific review

4. Internal consistency checks

Add a compact set of “red flag” columns that must be blank before you trust the sheet.

Common ones for Vermont limitations work:

  • Negative durations

    =IF(G2<B2, "CHECK: filing before accrual", "")
    
  • Overlapping tolling periods (if you track more than one)

    =IF(
      AND(NOT(ISBLANK(C2)), NOT(ISBLANK(D2)), NOT(ISBLANK(I2)), NOT(ISBLANK(J2))),
      IF(MAX(C2,I2) <= MIN(D2,J2), "CHECK: overlapping tolling", ""),
      ""
    )
    
  • Unusual Vermont categories (e.g., where special statutes might apply—consumer, UCC, construction, etc.)

    =IF(
      AND(E2="OTH", G2>EDATE(B2,72)),  /* 6 years */
      "CHECK: VT special-category candidate",
      ""
    )
    

Warning: These checks are only sanity filters. They do not replace Vermont‑specific legal analysis or a full statute‑of‑limitations calculation. Any row with a warning should be treated as “needs legal review,” not “definitely time‑barred.”

When to run it

Build the checker into your workflow so it’s automatic, not optional.

Before importing into DocketMath

Run the spreadsheet checks:

  • After data entry (paralegal/assistant input)
  • After data migration (from a case management system or legacy spreadsheet)
  • Whenever you add a new Vermont claim category or change your mapping table

Only send rows to the DocketMath statute-of-limitations calculator when:

  • All “CHECK:” columns are blank, and
  • You’ve spot‑checked a few rows manually

Before relying on a Vermont limitations report

Even after you’ve run the calculator:

  • Use the checker to re‑scan the underlying spreadsheet if:
    • You revise accrual theories
    • You add or remove tolling periods
    • New Vermont caselaw or statutes change how you categorize claims

A simple practice:

  • Lock the version of the spreadsheet used for each major Vermont SOL review
  • Re‑run the checker on any new version
  • Record the date/time the checker was last run in a header cell

This creates a lightweight audit trail without extra software.

Try the checker

You can turn the ideas above into a reusable Vermont‑specific template in a few steps:

  1. Create a “VT_SOL_Checks” sheet

    • Columns for Claim ID, Accrual date, Claim type, Filing date, Tolling start/end, and your “CHECK:” columns.
    • Freeze the header row and color any “CHECK:” outputs in red.
  2. Add a Vermont claim‑type mapping tab

    • Maintain a curated table of your firm’s Vermont claim categories and corresponding limitations periods.
    • Include a “Last reviewed” note and who approved it.
  3. Wire up the formulas

    • Implement the date validity, lookup, and “LATE? check VT rules” formulas.

    • Add a final column, e.g. Overall status, that aggregates issues:

      =IF(
        OR(
          ISNUMBER(SEARCH("CHECK:", X2)),
          ISNUMBER(SEARCH("LATE?", Y2))
        ),
        "REVIEW",
        "OK"
      )
      
  4. Filter before export

    • Filter Overall status = "OK" for rows you’re comfortable sending to DocketMath.
    • Filter Overall status = "REVIEW" to create a worklist for attorney review.
  5. Run in parallel with DocketMath

    • For a sample of Vermont matters, compare:
      • Spreadsheet “naive” deadlines
      • DocketMath’s computed Vermont limitations dates
    • Where they differ, document why (e.g., discovery rule, statutory repose, disability, cross‑border issues).

Pitfall: Treating the spreadsheet deadline as authoritative instead of as a screening tool. Always treat the checker output

What the checker catches

  • Date ordering problems (end date before start date).
  • Rates entered as whole numbers instead of percentages.
  • Missing caps or discounts in the spreadsheet.
  • Inconsistent rounding or day-count conventions.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

When to run it

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.

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

Try the checker

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.

Related reading