Cost of Delay Modeler Guide for Pennsylvania

What this calculator does

Run this scenario in DocketMath using the Cost Of Delay calculator.

DocketMath’s Cost of Delay Modeler helps you estimate the economic impact of time in a Pennsylvania dispute by converting a schedule change into an estimated dollar cost of delay.

The core idea is straightforward:

• Time has value (or cost).
• You model how long things take (or how long they would take under another timeline).
• You attach an assumed cost rate per day (lost revenue, added expenses, financing costs, staffing overhead, etc.).
• The calculator produces a total cost difference attributable to the delay window.

This guide is written for Pennsylvania and uses the general/delivery default statute of limitations (SOL) period as the baseline:

• General SOL Period: 2 years
• General statute: 42 Pa. Cons. Stat. § 5552
• Source: https://www.legis.state.pa.us/WU01/LI/LI/US/PDF/2000/0/0136..PDF

Note (important): The Pennsylvania SOL referenced here is a general/default period. This guide does not identify any claim-type-specific sub-rule for shorter or longer limitations periods, so treat 2 years as the starting point for the model—not a substitute for claim-by-claim limitations analysis.

If you want to run the model, use: /tools/cost-of-delay.

When to use it

Use the Cost of Delay Modeler when your decision depends on time-to-resolution (or time-to-filing/decision-making). Common Pennsylvania contexts include:

• Settlement evaluation: Compare settlement today vs. settlement after additional procedural time.
• Case management planning: Test how accelerating key milestones changes total expected exposure.
• Demand strategy budgeting: Model different timelines for negotiation cycles and filing readiness.
• Operational cost tracking: Quantify whether additional weeks materially worsen cash flow or operating costs.

A practical rule: if moving from one timeline to another changes the number of days by 10, 30, 60, or more, the model is usually worth running.

Calculator inputs you’ll typically use:

• A delay window (e.g., 90 days of difference)
• A cost rate per day (e.g., $250/day)
• Optionally, multiple cost categories (and sum them)
• Optionally, you can also sanity-check SOL-related timeline implications using the general 2-year baseline under 42 Pa. Cons. Stat. § 5552 (not as legal advice)

Gentle disclaimer: This is a modeling tool to help you think in dollars-and-days. It is not legal advice, and it does not determine the correct limitations period for a specific cause of action.

Step-by-step example

Below is a concrete example you can mirror in DocketMath. This is a modeling walkthrough, not legal advice.

Scenario

You’re considering two approaches in a Pennsylvania matter:

• Approach A (faster): Resolve within the next 120 days
• Approach B (slower): Resolve within the next 210 days
• Net delay between approaches: 90 days

Assume your estimated cost of continuing the dispute is:

• $300 per day (mixed business costs: staffing, administration, opportunity cost)

Step 1: Set the delay window

• Approach A timeline: 120 days
• Approach B timeline: 210 days
• Delay window: 210 − 120 = 90 days

Step 2: Enter your daily cost rate

• Cost rate per day: $300/day

Step 3: Compute total cost of delay

In a simple “flat daily rate” model:

• Total cost of delay = delay window × daily rate
• = 90 days × $300/day
• = $27,000

Step 4: Translate into an action-oriented decision

Now you can compare:

• If a settlement offer costs less than ~$27,000 more than the faster alternative (in modeled time cost), the faster timeline may “pay for itself” on time-cost alone.
• If your settlement economics differ (e.g., different claim amounts, different risk posture), use the model to isolate time cost from price.

Optional: Bring the Pennsylvania SOL baseline into the timeline story (general default)

If your planning window connects to the ability to file within the limitations period, you can treat Pennsylvania’s general default SOL baseline as 2 years under 42 Pa. Cons. Stat. § 5552.

• General SOL Period: 2 years (baseline used for planning)
• For modeling convenience, that’s approximately 730 days (if using 365-day years)

So if a project plan assumes “we can still act” within that broader window, you can sanity-check that the modeled delay (e.g., 210 days) does not consume an outsized share of your timeline budget.

Common scenarios

The Cost of Delay Modeler becomes especially useful when you have recurring patterns of delay. Below are several scenarios and how you’d typically adjust inputs.

1) Negotiation drag (settlement talks)

Typical change: additional weeks of back-and-forth.
How inputs change:

• Increase delay window by the extra days
• Daily cost rate may include:

  • Legal/admin overhead while negotiating
  • Internal time cost
  • Any revenue or cash impact

Output behavior: cost grows linearly if the daily cost rate stays constant.

2) Procedural time (motion practice or discovery expansion)

Typical change: a discrete event adds delay (e.g., scheduling shifts, extensions).
How inputs change:

• Add event-specific delay blocks (e.g., +45 days)
• If costs change over time, use multiple blocks/categories

Output behavior: if you switch daily rates midstream, the result is the sum of each segment’s cost.

3) Filing timing uncertainty tied to the SOL baseline (general default)

Typical change: taking longer to prepare could affect whether actions remain timely.
How inputs change:

• Delay window between “ready-to-act” dates
• Daily costs for the dispute continuation
• SOL baseline: 2 years under 42 Pa. Cons. Stat. § 5552 as the general reference point only

Output behavior: the SOL baseline usually acts like a constraint check, not a daily cost itself. Your daily cost is whatever it costs you to keep the matter active.

4) Revenue interruption or customer churn risk

Typical change: each week of delay increases churn probability or reduces pipeline.
How inputs change:

• Flat daily rate: use an average $/day cost
• Segmented rate: increase $/day after a threshold (e.g., after 30 days)

Output behavior: segmented models can capture effects that accelerate with time.

5) Finance and funding costs

Typical change: delay increases borrowing needs, interest expense, or cash strain.
How inputs change:

• Daily interest/carrying-cost estimate
• Consider how your cost accrues (if you can’t model accrual exactly, use a reasonable best estimate)

Output behavior: interest-like costs can be close to linear for shorter windows, but segmentation may fit better if your financing structure changes.

Tips for accuracy

You’ll get better results by treating the calculator like a disciplined spreadsheet rather than a single “number guess.”

1) Convert every cost category into a daily number

If you have monthly costs, don’t force a guess—convert:

• Daily cost ≈ monthly cost ÷ 30 (or use your preferred day-count convention)

Examples to convert:

• Legal overhead (if it runs monthly)
• Staff time (if you know monthly or weekly spend)
• Carrying costs
• Revenue disruption (averaged over the likely delay period)

2) Model delays as blocks (when costs change)

If costs step up after milestones, split the delay:

• Block 1 (Days 1–30): $X/day
• Block 2 (Days 31–90): $Y/day

This often improves realism in disputes where staffing/effort changes over time.

3) Use “delay difference” when comparing options

If you compare schedules, model the incremental difference:

• Option 1: 120 days
• Option 2: 210 days
• Model 90 extra days rather than recalculating everything from day 0 each time.

This keeps the comparison consistent and easier to explain internally.

4) Treat the Pennsylvania SOL baseline as a planning constraint only

For this guide, the general/default limitations baseline is:

• 2 years under 42 Pa. Cons. Stat. § 5552

But claim-specific limitations can differ, and this guide does not provide claim-type-specific rules.

5) Document assumptions for auditability

When someone asks “How did you get $27,000?”, you’ll want a clean trail:

• Daily cost rate source (internal accounting/finance estimate)
• Delay window logic (what dates and what changed)
• Any segmentation triggers (e.g., “cost rate increases after discovery opens”)

A short assumptions list makes the output easier to defend.

6) Run sensitivity checks (at least 3)

Instead of one daily rate, bracket uncertainty:

• Low: $X/day
• Base: $Y/day
• High: $Z/day

Then observe whether the decision changes materially. If the range still supports your preferred path, the result is more robust.

Related reading

• Cost of Delay Modeler Guide for Alabama
• Cost of Delay Modeler Guide for Arizona
• Cost of Delay Modeler Guide for Colorado