Abstract background illustration for How to run statute of limitations in DocketMath for Vermont

How to run statute of limitations in DocketMath for Vermont

6 min read

Published June 4, 2026 • By DocketMath Team

Verified against 22 sources

This page has current canonical verification receipts.

Current verified answer

Vermont statute-of-limitations: period is 3; statute of limitations years is 3.

See your deadline

Authority and key facts

Citation: 12 V.S.A. § 511

View the primary source

Verified April 29, 2026

  • Period: 3
  • Statute Of Limitations Years: 3
  • Limitation Period: 6 years
  • Limitation Period: 3 years

Step-by-step

This guide walks you through running the statute of limitations in DocketMath for Vermont (US-VT) using the statute of limitations calculator.

In Vermont, this workflow centers on 12 V.S.A. § 511 for the tool’s general limitations period inputs (as reflected in the Verified Facts Packet). In DocketMath, the deadline you get depends mainly on three choices:

  1. Claim type (this drives the base limitation period the tool uses)
  2. Discovery option (when enabled, discovery can adjust timing)
  3. Any discovery “max-years-from-incident” limit (a ceiling on how far back discovery can push the start)

1) Open the correct tool

Start at DocketMath’s calculator:

If you’re coming from a general page or dashboard, go to the calculator directly—your result depends on the inputs you select.

2) Select Vermont (US-VT) jurisdiction

In the jurisdiction selector, choose:

  • US-VT — Vermont

DocketMath will then load Vermont-specific rule mappings, including the base time periods associated with the claim types available in the tool.

3) Choose the claim type that matches the alleged theory

In the calculator, set claim type to the closest match. The Vermont configuration reflected in the Verified Facts Packet maps these common buckets to fixed limitation periods:

Claim type (DocketMath category)Limitation period (Vermont config)
Breach of oral contract6 years
Breach of written contract6 years
Fraud / common-law fraud6 years
Legal malpractice (typical commercial/economic-loss setup)6 years
Personal injury3 years
Premises liability3 years
Medical malpractice3 years
Product liability3 years
Property damage3 years
Libel / slander3 years
Trespass3 years
UCC sale of goods4 years
Wrongful death2 years
Unjust enrichment / restitution6 years
Statute of limitations (general bucket in tool)3 years

Practical tip: If you’re unsure whether something fits a 3-year versus 6-year lane, treat claim-type selection as your first diagnostic step. The tool will produce materially different results based on that selection.

Warning: Using the wrong claim type is one of the fastest ways to get an incorrect deadline. For example, moving between a 3-year category (like personal injury) and a 6-year category (like breach of contract, fraud, or certain legal-malpractice mappings) can change the outcome significantly.

4) Enter the event date(s) DocketMath needs

Most statute-of-limitations calculators require at least the incident date (or an equivalent “start candidate” date tied to the underlying event).

If the tool requests it (or if discovery is enabled for your claim type), you may also provide a discovery-related date. When discovery rules apply, the tool uses them according to the Vermont configuration in the Verified Facts Packet.

5) Turn on discovery only when the tool’s setup indicates it’s applicable

For the Vermont configuration in this packet:

  • Discovery rule enabled: sub_rules.1.discovery_rule: true
  • Discovery max-years-from-incident: 7 years (discovery_rule.max_years_from_incident: 7)

That means DocketMath may adjust the timing using discovery, but it should not extend beyond the configured ceiling of 7 years from the incident.

6) Review the output: base limitation period vs. any discovery max

After DocketMath calculates, check that you understand what drives the final result. In particular, confirm:

  • The base limitation period used for your chosen claim type (e.g., 3, 4, 6, or 2 years, depending on the category)
  • Whether discovery changed the result
  • Whether a max-from-incident cap applied (the packet specifies a 7-year ceiling for discovery-based timing)

If the computed deadline seems “too short” or “too long,” don’t assume it’s broken—first verify your claim type selection and whether discovery timing is pushing against the 7-year max.

7) Use the tool’s internal confirmation signals (when shown)

The packet also includes configuration values that may appear in the tool UI (labels can vary):

  • statute_of_limitations_years: 3
  • statute_of_limitations.enumerated_tort_and_personal_injury: 3

If you see these displayed, they can help confirm the tool is using the expected Vermont mapping lane (especially if you selected a broad “statute of limitations” bucket rather than a specific tort/contract category).

8) Rerun with a close alternative to test category sensitivity

Category selection is often the biggest source of differences. A quick workflow that reduces surprises:

  1. Run once using your best claim type match.
  2. Run again using the next closest category that fits the facts (for example, comparing a tort-flavored bucket versus a contract/fraud-flavored bucket).
  3. Compare the outputs to see whether the difference comes from:
    • the base limitation period, or
    • discovery, or
    • the 7-year max-years-from-incident ceiling.

Common pitfalls

  • Choosing the wrong claim type bucket

    • Mixing up 3-year categories (e.g., personal injury/premises liability/medical malpractice) with 6-year categories (e.g., breach of oral/written contract, fraud, and certain economic-loss legal-malpractice mappings) can flip the deadline.
  • Assuming discovery always extends the deadline

    • In this Vermont configuration, discovery is limited by a 7-year max from the incident. If the discovery date is far out, the max may prevent further extension.
  • Assuming “legal malpractice” always means the same limitations period

    • The Verified Facts Packet’s Safe Facts indicate a Vermont mapping where economic-loss legal-malpractice is treated as 6 years in the tool’s configuration for the cited controlling-rule approach.
  • Using the “general” statute bucket when a specific category is a closer fit

    • DocketMath includes specialized mappings (including different “receipts”/category-style limitations). If the claim fits a specialized bucket (like UCC sale of goods: 4 years or wrongful death: 2 years), using a general bucket can yield the wrong result.

Try it

  • Open /tools/statute-of-limitations: /tools/statute-of-limitations
  • Set jurisdiction to US-VT (Vermont)
  • Pick the closest claim type
  • Enter the incident date (and discovery-related date if the tool requests it)
  • Leave discovery enabled if your claim type is one where discovery logic applies in the Vermont setup
  • Review:
    • the base limitation period for your chosen claim type
    • whether a discovery adjustment happened
    • whether the 7-year max-from-incident constrained the result
  • If the deadline seems surprising:
    • rerun with the next closest claim type category
    • compare whether the difference is coming from the base period or discovery timing

Related reading