Tolling the statute of limitations in Massachusetts

Tolling the statute of limitations in Massachusetts

7 min read

Published May 24, 2025 • Updated April 23, 2026 • By DocketMath Team

Article claim inventory in progress

Trust release 4

This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.

Direct answer

In Massachusetts, the general/default statute of limitations is 6 years under Mass. Gen. Laws ch. 277, § 63. Using DocketMath (the statute-of-limitations calculator), you can estimate a “deadline” and then adjust for tolling—situations where the limitations clock is paused, delayed, or otherwise extended based on the facts you identify.

This post is about tolling and how it can make the effective filing deadline later than the basic 6-year rule. Important: The only jurisdiction data provided is the general 6-year period. This guide does not identify any claim-type-specific limitations period because none was supplied.

Note: This is general information and a practical estimation workflow—not legal advice.

What you need to know

Massachusetts uses statutes of limitations to set deadlines for filing legal actions. The baseline you start from (based on your provided jurisdiction data) is:

  • 6 yearsMass. Gen. Laws ch. 277, § 63

Tolling changes the effective timeline by affecting how long the “clock” runs. In practice, tolling analysis is usually fact-driven and depends on what legally qualifies as a clock-stopper (or clock-resetter) and the correct dates.

DocketMath inputs you’ll need (in plain terms)

To use DocketMath effectively, prepare:

  • Trigger date (the date your clock starts under the approach you’re modeling—often an accrual or equivalent starting point)
  • File-by date you want to test (or, alternatively, you use DocketMath to compute the latest timely date)
  • Tolling indicators with date ranges (start and end dates for the tolling you believe applies)

How tolling typically affects outcomes

Think in terms of “time added” or “time not running”:

ScenarioClock behaviorPractical effect on deadline
No tollingClock runs continuouslyDeadline ≈ trigger date + 6 years
Tolling pauses the clockClock stops during tollingDeadline extends beyond trigger date + 6 years
Tolling restarts/changes the start logicEffective start may changeDeadline can shift more than the tolling length

Because the output deadline depends on both (1) your chosen trigger date and (2) the tolling model and date ranges you enter, it’s smart to keep notes and document assumptions.

Warning: DocketMath can make your math structured and repeatable, but tolling eligibility and correct date ranges still depend on the underlying legal rules and facts. Treat the tool as a planning estimate, not proof of timeliness.

Step-by-step

Use this workflow to “toll” limitations deadlines in a Massachusetts context using DocketMath.

1) Start with the baseline (default/general) limitations period

With the jurisdiction data provided, your starting point is:

  • 6 yearsMass. Gen. Laws ch. 277, § 63

Because no claim-type-specific sub-rule was provided, treat 6 years as your default unless you have separate authority showing a different period applies.

2) Choose the correct trigger date for your modeled clock

Pick the date that starts the limitations clock under your facts. Common examples people model include:

  • a date of injury or harm
  • a date of breach (in contract-type contexts)
  • a date the claim accrued (often the default “start” concept)

Be consistent—if you change the trigger date, your calculated deadline changes too.

3) Decide whether you’re calculating a deadline or testing timeliness

Two common ways to use the calculator:

  • Deadline estimate: “What is the latest date I can file and still be timely?”
  • Timeliness test: “If I filed (or plan to file) on X date, is that within the tolled period?”

For most planning workflows, the deadline estimate is a good first pass.

4) Identify tolling events and convert them into date ranges

For each tolling theory you believe applies, create:

  • tolling event name
  • tolling start date
  • tolling end date
  • a brief note of why it applies (for your own review)

Then enter those tolling ranges into DocketMath so it can compute the adjusted timeline.

5) Run a baseline “no tolling” scenario first

Before modeling tolling, run the simple version:

  • Trigger date = your chosen start
  • Tolling = none

This baseline is your sanity check. It helps you confirm that DocketMath is behaving the way you expect with the 6-year rule from Mass. Gen. Laws ch. 277, § 63.

6) Re-run with tolling intervals added

Now add each tolling interval (start/end dates) and rerun the calculator.

Compare:

  • baseline deadline
  • tolled deadline

The delta (difference) will typically reflect the effect of the tolling interval(s) you entered, plus any interaction with how the calculator models time counting.

7) Record the assumptions behind the output

When you finalize your estimate, write down:

  • baseline deadline
  • tolled deadline
  • difference in days/months
  • the tolling ranges you entered

This makes it much easier to update the estimate if your facts (or your tolling theory) change.

Key statutes and citations

  • Mass. Gen. Laws ch. 277, § 636-year general statute of limitations (general/default period used as the starting point in this guide)

Because the provided jurisdiction data does not include a claim-type-specific sub-rule, this guide uses 6 years as the baseline and treats any movement from that baseline as coming from tolling inputs you model in DocketMath.

Common pitfalls

Watch for these common mistakes when tolling limitations deadlines with calculators:

  • Assuming “6 years from one date” always applies the same way. Even with a 6-year general period, the start date and tolling mechanics can change the effective deadline.
  • Using a claim-type-specific period without support. Your provided jurisdiction data supports the general/default 6-year rule only.
  • Entering tolling dates incorrectly (especially swapped dates). If the tolling end date is earlier than the start date, results can be meaningless.
  • Skipping the baseline run. Without a baseline (no tolling), you won’t know whether tolling inputs are having the expected effect.
  • Treating estimates as certain. Tolling validity depends on the facts and governing doctrine; the tool structures calculations but doesn’t decide legal applicability.

Pitfall to avoid: entering a vague “number of tolling days” instead of actual tolling date ranges. If you have dates, enter start/end ranges so the tool calculates the interval consistently.

A practical way to gauge risk is to run multiple passes:

  1. baseline (no tolling)
  2. tolling modeled with the most conservative/shortest interval you can justify
  3. tolling modeled with the longest interval you can justify

Seeing the range helps you understand sensitivity to your inputs.

Run the numbers

Use DocketMath’s statute-of-limitations calculator here: /tools/statute-of-limitations .

Below are example scenarios showing how outputs change when you add tolling intervals to a 6-year baseline from Mass. Gen. Laws ch. 277, § 63.

Example A: No tolling

  • Trigger date: Jan 1, 2020
  • Tolling: none
  • Baseline: 6 years (Mass. Gen. Laws ch. 277, § 63)

Estimated deadline (no tolling): Jan 1, 2026

Example B: Tolling pauses for 6 months

  • Trigger date: Jan 1, 2020
  • Tolling interval: Jul 1, 2022 → Dec 31, 2022 (6 months)
  • Baseline: 6 years

Estimated deadline (with 6-month pause): ~Jul 1, 2026 (the exact day depends on how the calculator counts partial periods)

Example C: Tolling pauses for 1 year

  • Trigger date: Jan 1, 2020
  • Tolling interval: Jan 1, 2023 → Dec 31, 2023 (1 year)
  • Baseline: 6 years

Estimated deadline (with 1-year pause): Jan 1, 2027

How to interpret DocketMath changes

When you adjust tolling inputs:

  • If the deadline moves later, that generally aligns with a “clock paused” model.
  • If the deadline changes only slightly, the tolling dates may be short, may overlap portions of the timeline already treated as non-running by the tool’s approach, or may be entered in a way that doesn’t fully capture the intended pause.

For review efficiency, capture:

  • baseline deadline
  • tolled deadline
  • the tolling date ranges entered

Related reading