Statute of Limitations for Murder / First-Degree Murder in Vermont

5 min read

Published March 22, 2026 • By DocketMath Team

Overview

In Vermont, most serious homicide prosecutions are governed by a statute-of-limitations rule that—depending on the charged degree and the specific facts—may provide very little time to file or may effectively allow prosecution at any time.

For murder (including first-degree murder charges), Vermont’s limitations framework is tracked in DocketMath’s statute-of-limitations calculator for US-VT. In this guide, you’ll see what the calculator is configured to use for the limitation period and how the “exception V3” condition changes the outcome.

Note: This page explains the limitations framework at a high level and how to use DocketMath’s calculator. It’s not legal advice and doesn’t replace review of the full statute text and any case-specific procedural issues.

Limitation period

What DocketMath is configured to calculate (Vermont)

DocketMath’s statute-of-limitations calculator for Vermont is configured with the following inputs from the jurisdiction data you provided:

  • SOL period (base): 1 years
  • Sub-rules:
    • exception V3 → null — 1 years — exception V3

Because the jurisdiction data you supplied does not show a longer “no limitations” period for homicide, DocketMath will calculate a 1-year limitations window by default for the applicable homicide limitation configuration.

How to interpret the 1-year output

When you run the calculator, you’ll typically see output that reflects:

  • A start date (commonly tied to the relevant triggering event—often the date of the offense or other specified accrual concepts in the governing provision)
  • A deadline date = start date + 1 year
  • Potential adjustments if an exception applies (here, “exception V3”)

If exception V3 is not applicable to the scenario you’re evaluating, you should expect the calculator to keep the default 1-year timeline.

Key exceptions

Exception V3 (configured in the calculator dataset)

Your Vermont jurisdiction data includes a sub-rule labeled “exception V3”. Practically, this means DocketMath treats at least one set of circumstances as capable of changing how the limitation period is applied.

Because the dataset you provided shows:

  • null — 1 years — exception V3

…DocketMath will still reflect a 1-year limitations period under the exception. However, the exception likely affects whether the 1-year rule applies in the first place, or which triggering event/classification is used in the calculation.

Check the calculator’s scenario/inputs carefully:

  • If you select inputs that correspond to exception V3, DocketMath will switch to the exception logic path.
  • If you do not select those inputs (or if the fact pattern does not meet the exception’s condition), DocketMath will remain on the base SOL period logic.

Quick checklist for exception applicability

Use this checklist when running the calculator:

Warning: Exceptions are where limitations calculations most often diverge. Even small fact changes (or differences in how a charge is labeled) can alter whether an exception applies.

Statute citation

The jurisdiction data you provided references a Vermont legislative document:

However, your provided “Statute citation” field is null, and the dataset does not include the specific Vermont statute number and subsection text.

To keep DocketMath’s workflow accurate, the calculator result shown for Vermont will be driven by the jurisdiction data configuration you provided (base 1 years, with exception V3 routing). If you need an exact citation for filing or litigation purposes, you’ll want to map the calculator’s “jurisdiction configuration” back to the specific Vermont code section and subsection from the source document (or updated codification).

Use the calculator

Ready to compute the limitations deadline using DocketMath?

  1. Go to the DocketMath calculator: **/tools/statute-of-limitations
  2. Select jurisdiction: US-VT
  3. Enter the relevant triggering date (the date the limitations clock begins under the applicable rule used by the calculator)
  4. Review whether the scenario maps to exception V3:
    • If the calculator offers an option/toggle for the exception logic, turn it on only when the fact pattern fits that condition.
  5. Run the calculation to generate:
    • the computed deadline date
    • the duration basis (configured as 1 year for Vermont in this dataset)
    • any exception-based adjustments reflected by the calculator logic

How outputs change as inputs change

Think of the calculator’s behavior like this:

  • If you keep everything the same, but move the start/triggering date:
    • the deadline date shifts by the same time change (because the SOL period is fixed at 1 year in the Vermont dataset).
  • If you change whether “exception V3” is selected:
    • DocketMath may use a different logic path for applying the limitation rule.
    • even if the displayed SOL period remains 1 year, the exception can still affect how the calculation is justified or which timeline basis is used.

Example of interpreting a result (conceptual)

If DocketMath outputs a deadline that is exactly 365 days (or the equivalent in date arithmetic) after your triggering date, that matches the configured 1-year rule. If the exception path produces a different deadline, treat that difference as evidence that the exception changed the operative assumptions in the calculation.

Related reading