Statute of Limitations for Interference with Business Relations / Tortious Interference in Maryland

5 min read

Published March 22, 2026 • By DocketMath Team

Overview

In Maryland, claims for interference with business relations are typically brought under the broader umbrella of tortious interference. When you’re planning a case timeline, the most immediate question is usually: How long do I have to file in court after the interference?

Maryland uses a general statute of limitations framework for many tort claims. For tortious interference, the default limitations period is commonly treated as three years under Maryland’s general limitations statute for civil actions.

Note: This page focuses on the general/default limitations period for this category of claims. It does not identify every possible claim-type-specific carveout, because no such specific sub-rule was found in the governing materials provided—so you should treat the period below as the baseline.

Limitation period

Default limitations period: 3 years

Under Maryland’s general statute of limitations, the default time limit for the types of civil actions covered is 3 years.

  • Start point (typical approach): the clock generally runs from the date the claim accrues.
  • What “accrues” means in practice: the claim generally accrues when the plaintiff knew or should have known of the injury and that it was tied to the defendant’s conduct (details can be fact-specific).

DocketMath’s statute-of-limitations calculator (available at /tools/statute-of-limitations) helps you compute end dates based on a chosen accrual date. If you input a later accrual date, your deadline moves later; if your accrual date is earlier, the deadline moves earlier.

Practical filing deadline workflow

Use this sequence to avoid missing a deadline:

  1. Identify the alleged interference date(s)
    • If there are multiple acts, pick the date(s) that best fit when the injury became apparent.
  2. Determine the most defensible accrual date
    • For many tort scenarios, this is when the harm occurred and became reasonably discoverable.
  3. Add 3 years to get the default filing deadline
  4. Subtract a safety buffer (recommended)
    • Courts and clerks are unforgiving about late filings. Even if the statute says “through” a certain date, electronic filing cutoffs and processing delays can matter.

Inputs and how outputs change (DocketMath)

Open the calculator here: /tools/statute-of-limitations.

Typical calculator inputs include:

  • Accrual date (the date you believe the claim accrued)
  • Jurisdiction (set to Maryland)
  • General SOL selection (default/general)

Output you’ll get:

  • Recommended “last day to file” based on the 3-year general rule

How results shift:

  • Change the accrual date by one month → your computed deadline shifts by about one month.
  • Choose an incorrect accrual date (too early) → you risk generating a deadline that is already past.
  • Choose an accrual date that is too late → you may think you still have time when a court could view the claim as time-barred.

Key exceptions

Maryland law can change the outcome even when the general rule is 3 years. These are the common categories to check before treating the deadline as fixed:

  • Accrual timing disputes

    • Tortious interference cases often turn on when the plaintiff’s injury was discoverable and complete.
    • A “continuing harm” story does not automatically extend the limitations period—each jurisdiction analyzes the accrual facts carefully.
  • **Tolling (pause of the clock)

    • Tolling doctrines can suspend the limitations period in specific circumstances (for example, certain legal disabilities or other recognized bases).
    • If tolling applies, the filing deadline becomes later than the simple 3-year calculation.
  • Legal effectiveness of the claim

    • If a lawsuit is filed but dismissed and refiled, you may face procedural limitations that affect time calculations.
    • The statute of limitations analysis depends on whether the refiling is allowed and whether it relates back to the original filing.
  • Multi-defendant / multi-act scenarios

    • When interference allegations span multiple dates, courts may treat accrual differently for each alleged act.
    • Your chosen “trigger date” in DocketMath should align with the theory of when the actionable harm arose.

Warning: Do not rely solely on a single calendar computation if your case involves multiple interference events, delayed discovery issues, or any possible tolling. A court can apply a different accrual date than the one you assume.

Because your supplied briefing did not identify a claim-type-specific sub-rule for interference-with-business-relations/tortious interference, the baseline for this page remains the general/default 3-year period. You should still verify whether your fact pattern implicates tolling or a different accrual theory.

Statute citation

Maryland’s general limitations statute cited for this default period is:

  • Md. Code, Cts. & Jud. Proc. § 5-1063-year general statute of limitations for covered civil actions.

If you’re building a litigation calendar, § 5-106 is the key citation to start from for the default rule described in this page.

Use the calculator

To compute your deadline using DocketMath’s statute-of-limitations tool:

  1. Select **Maryland (US-MD)
  2. Enter your accrual date
  3. Use the general/default option (since no claim-type-specific sub-rule was identified here)
  4. Review the computed last day to file

Example (how changing inputs affects outputs)

  • If the accrual date is June 1, 2022, adding 3 years yields a default deadline around June 1, 2025 (with the calculator handling date specifics).
  • If you shift the accrual date to December 1, 2022, your deadline shifts by about 6 months accordingly.

Even small input changes can matter—especially in cases with multiple alleged interference acts.

Sources and references

Start with the primary authority for Maryland 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