Statute of Limitations for Legal Malpractice in Minnesota

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

In Minnesota, legal malpractice claims are subject to a statute of limitations (SOL). The key takeaway for timelines: the default SOL for most legal malpractice lawsuits is 3 years, governed by Minnesota Statutes § 628.26.

Because missed deadlines can foreclose a case, the “when does the clock start?” question matters as much as the number of years. DocketMath’s statute-of-limitations calculator helps you model potential filing deadlines based on the facts you enter (especially the relevant date for “accrual” or “discovery,” depending on how the claim is framed).

Note: This page covers the general/default limitation period. A claim-type-specific sub-rule was not found for Minnesota legal malpractice here, so the 3-year period should be treated as the starting point for evaluation—not a guarantee for every scenario.

Limitation period

Default SOL: 3 years

Minnesota’s general limitation period for certain actions is 3 years. For legal malpractice in this guide, use 3 years as the default SOL period tied to Minn. Stat. § 628.26.

Practical “timeline” view

To make the SOL actionable, think in terms of three dates:

  1. Trigger date (start of the clock)
    This is usually when the claim accrues. In many civil contexts, accrual may be linked to when the injury occurs or when the client knew (or should have known) of the issue. Minnesota’s statute at § 628.26 provides the structure for measuring time, but the exact triggering fact pattern can still be case-specific.

  2. End date (filing deadline)
    Add 3 years to the trigger date (subject to any statutory exceptions discussed below).

  3. Filing/entry of court action
    Your case generally needs to be filed within the SOL window. (Court procedural rules and service issues can matter, but this page focuses on the statutory deadline framework.)

How inputs change the output in DocketMath

Using DocketMath’s statute-of-limitations tool, you’ll typically enter one or more of the following inputs:

  • Jurisdiction: Minnesota (US-MN)
  • Claim type / category: legal malpractice (using the general/default rule on this page)
  • Relevant date: the date you believe the SOL clock began
  • Method of counting: calendar-based approach (the tool will use statute-based calculation logic)

When you change the relevant date, the deadline shifts by the same time interval. For example:

  • If the relevant date is January 15, 2022, then the default 3-year deadline will land around January 15, 2025 (subject to how the tool handles exact-day counting).
  • If the relevant date is January 15, 2023, the deadline moves to about January 15, 2026.

Key exceptions

Even when the “default SOL = 3 years” is clear, exceptions and adjustments can change the outcome. In Minnesota, the main moving parts to watch for in the general SOL framework include:

1) Tolling (pausing the clock)

Certain circumstances can pause or delay the running of a limitations period. The presence of tolling generally depends on facts like the status of the parties and the nature of the legal relationship.

How this matters for your deadline:
If the clock is tolled for a period (for example, due to a statutory tolling event), your effective deadline may extend beyond the simple “relevant date + 3 years” calculation.

2) Discovery-related accrual concepts

Many legal malpractice timing disputes focus on when the client discovered—or reasonably should have discovered—the injury and its connection to the attorney’s conduct. Minnesota’s approach under § 628.26 frames the timing rules in a way that can implicate discovery concepts depending on the claim’s factual posture.

How this matters for your inputs:
In DocketMath, selecting the “relevant date” carefully is the biggest lever you control. If you set the relevant date earlier than the likely accrual date, the output deadline may be too tight; set it later, and it may be too generous.

3) Different statutory buckets could be argued—but this page uses the general/default rule

This guide states clearly what rule it’s using: the general/default 3-year period under Minn. Stat. § 628.26. A different limitations bucket sometimes applies in other contexts, and litigants may argue for alternative measurement. However, no claim-type-specific sub-rule was found here, so the calculation is based on the default period.

Warning: Don’t treat “3 years” as a universal guarantee. Two cases with the same type label (“legal malpractice”) can still differ dramatically on the trigger date, tolling, and accrual analysis. Your fact pattern drives the SOL calculation.

Statute citation

The general/default statute of limitations period referenced in this guide is:

  • Minnesota Statutes § 628.26 (general SOL period 3 years)

This page uses Minn. Stat. § 628.26 as the controlling citation for the default timeline framework for legal malpractice in Minnesota.

Use the calculator

Use DocketMath’s statute-of-limitations tool to translate the statutory rule into a deadline you can act on quickly: **/tools/statute-of-limitations

Steps

  1. Open: /tools/statute-of-limitations
  2. Choose:
    • Jurisdiction: Minnesota (US-MN)
    • Rule basis: default 3-year period under Minn. Stat. § 628.26
  3. Enter your relevant date (the date you believe triggers accrual/starting the clock).
  4. Review:
    • the computed deadline date
    • how changing the relevant date shifts the result

Inputs checklist (to improve accuracy)

How to interpret the output

  • The calculator’s deadline is only as good as the relevant date you enter.
  • If you believe tolling applies, rerun the calculator using an adjusted effective start date consistent with that tolling period (or at least test multiple plausible dates so you can see the range).

For Minnesota, the default assumption for this page is straightforward:

  • Default SOL: 3 years
  • Statute: Minn. Stat. § 628.26

Sources and references

Start with the primary authority for Minnesota and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

Related reading