Tolling the statute of limitations in Pennsylvania

Tolling the statute of limitations in Pennsylvania

7 min read

Published April 15, 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

Run this scenario in DocketMath using the Statute Of Limitations calculator.

In Pennsylvania, the general statute of limitations is 2 years under 42 Pa. Cons. Stat. § 5552. “Tolling” generally means events that pause or delay the operation of that 2-year clock, so the filing deadline may move later depending on the specific facts.

This is a timeline-and-facts exercise. DocketMath’s jurisdiction-aware statute-of-limitations calculator can help you model how different tolling inputs change an end date. But the calculator can’t decide whether tolling is legally available for your situation—you must verify the underlying dates and tolling circumstances based on the facts (and, where appropriate, with qualified legal guidance).

Important baseline for this guide: you noted no claim-type-specific sub-rule was found, so this post uses § 5552 as the default SOL period for the computations.

Note: DocketMath can model how potential tolling inputs change the end date of an SOL window, but it can’t determine tolling eligibility by itself—your dates and the underlying event details are what drive the outcome.

What you need to know

Tolling is a timeline concept. In plain terms, it affects the SOL deadline by pausing the clock (or sometimes by using a different trigger date), depending on the facts and the tolling doctrine(s) that may apply.

For Pennsylvania, the baseline rule used in this guide is:

How tolling impacts the “end date”

When tolling applies, it typically changes one (or both) of these:

  • Accrual date (when the clock starts), or
  • Running time (the length of time the clock is allowed to run before the deadline).

What DocketMath does (practically)

DocketMath helps you compute an adjusted SOL deadline by letting you enter key dates—such as an accrual/trigger date and tolling start/stop dates—and then calculating the resulting end date using US-PA rules and the default 2-year SOL period (unless you configure an alternate rule).

Because this guide uses the general/default rule, you can treat § 5552 as the anchor for the SOL length, then apply tolling inputs as your scenario changes.

Key timeline inputs you’ll want ready

Before you calculate anything, gather:

  • The date the underlying event occurred (incident date, depending on the facts)
  • The date your claim accrued (if you know the accrual trigger; if not, use the closest applicable trigger date you can support with the record)
  • Any tolling-related dates, such as:
    • a tolling start date
    • a tolling end date (or a date the pause ends)
    • any intervening period you want to model as “paused” time

Step-by-step

Use DocketMath to model Pennsylvania’s default SOL and test tolling scenarios. Here’s a practical workflow:

  1. Confirm the jurisdiction

    • Select US-PA (Pennsylvania) in the statute-of-limitations calculator.
  2. Use the default SOL baseline

    • Set the SOL period to 2 years.
    • This guide’s default is 42 Pa. Cons. Stat. § 5552.
    • Reminder: since no claim-type-specific sub-rule was found for this brief, we do not switch to a different SOL length here.
  3. Enter your core dates

    • Enter the date that corresponds to your accrual trigger (or the closest supported date).
    • Accurately identifying accrual is often more important than the event date itself.
  4. **Add tolling inputs (if you have them)

    • Enter a tolling start date.
    • Enter a tolling end date (or duration), if the pause is finite.
    • If your situation is “pause until X,” you’ll need the date when the pause ends so the tool can compute the adjusted deadline.
  5. Run multiple scenarios

    • Scenario A (baseline): no tolling inputs → baseline 2-year end date
    • Scenario B: tolling begins on the earliest plausible date
    • Scenario C: tolling begins on a later date (and/or ends later), to see how sensitive the deadline is to your assumptions
  6. Read the output as a deadline under your model assumptions

    • The tool should show an adjusted SOL end date based on the inputs.
    • Treat it as a “latest filing” target for the scenario you modeled, not as a definitive legal conclusion.
  7. Check your assumptions and rerun

    • If your modeled tolling window doesn’t match the facts, update the dates and rerun.
    • Pay special attention if tolling dates overlap your accrual/start date—overlaps can significantly change the adjusted end date.

If you want to start right away, use the primary CTA:

  • /tools/statute-of-limitations

(And if you’re organizing inputs before calculating, you may find other date tools helpful as you prepare your timeline: /tools/.)

Key statutes and citations

This guide uses Pennsylvania’s general/default civil SOL rule as the anchor:

Claim-type-specific exceptions

Per your note, no claim-type-specific sub-rule was found for this brief. Therefore:

  • This post does not apply shortened or lengthened claim-type SOL periods.
  • All calculations in this guide assume the 2-year period under § 5552 as the governing default.

Common pitfalls

Tolling is where timeline mistakes most often happen. Avoid these:

  • Using the incident date instead of the accrual/trigger date

    • SOL analysis usually turns on when the claim accrued, not only when the event happened.
  • Failing to specify a tolling start and stop

    • A pause typically needs a defined window to compute a meaningful adjusted deadline.
  • Assuming all “tolling” works the same way

    • Some doctrines affect accrual, others operate like a pause, and eligibility can depend on detailed conditions.
  • Mixing jurisdictions or rules

    • This guide and the tool usage described here are for US-PA with § 5552 as the default.
  • Using § 5552 even when the claim may not be governed by the default

    • If your claim is likely outside the default SOL length, tolling may still matter, but the baseline clock length would change—and the tool inputs should reflect the correct SOL period.

Warning: Overlapping date ranges and missing “pause end” dates can create an artificially late (or early) deadline in your model. If tolling dates are uncertain, run multiple scenarios and compare the resulting end dates.

Run the numbers

Below is a simple illustration of how the modeling works using the US-PA default 2-year SOL under 42 Pa. Cons. Stat. § 5552.

Baseline (no tolling)

Assume the accrual/trigger date is:

  • Day 0: March 1, 2023
  • 2-year baseline end date: March 1, 2025

With no tolling inputs, the adjusted deadline remains the baseline.

Example tolling adjustment (pause during a window)

Now assume you enter a tolling pause window:

  • Tolling starts: August 1, 2023
  • Tolling ends: October 1, 2023

Conceptually, the adjusted deadline logic is:

  • Baseline end date
  • + time attributable to the paused period
  • → resulting adjusted end date (later than the baseline)

So if the paused time is modeled as 61 days (calendar-day count in the tool’s approach), the adjusted end date would move later by about 61 days—around May 1, 2025 in this simplified example.

How output changes with your inputs

When you change your tolling inputs, the adjusted end date generally shifts:

  • Later tolling start date

    • Usually means less time paused → smaller extension → earlier adjusted deadline than a scenario with an earlier tolling start.
  • Later tolling end date

    • Usually means more time paused → larger extension → later adjusted deadline.
  • No tolling inputs

    • Returns the baseline deadline under the 2-year default.

To run your specific timeline, go to:

  • /tools/statute-of-limitations

Related reading