Worked example: Damages Allocation in Pennsylvania

6 min read

Published April 15, 2026 • By DocketMath Team

Example inputs

Run this scenario in DocketMath using the Damages Allocation calculator.

Below is a worked example for allocating damages in Pennsylvania using DocketMath’s damages allocation calculator (jurisdiction-aware). This example focuses on time-based gating using Pennsylvania’s general statute of limitations (SOL), then shows how that gating can affect what portion of claimed damages remains potentially recoverable.

Scenario (fictional but realistic structure)

A plaintiff alleges:

  • A contract dispute with multiple payment dates across time.
  • Damages are made up of (1) liquidated amounts and (2) ongoing costs that accrue monthly.

Assume the claim is filed on:

  • Filing date: 2026-04-15

You have identified these “damages periods” and amounts:

Damages componentDescriptionAccrual window (start → end)Amount claimed
ALiquidated payments2024-03-01 → 2024-10-01$18,000
BMonthly costs2024-11-01 → 2025-09-01$27,000
CMonthly costs2025-10-01 → 2026-01-01$12,000

Pennsylvania SOL rule used in this example

DocketMath applies the general/default SOL period because no claim-type-specific sub-rule was found for this worked example.

So we compute the lookback date:

  • Lookback start = filing date minus 2 years
  • 2026-04-15 → 2024-04-15

Meaning for allocation in this example: any damages accruing before 2024-04-15 are outside the 2-year general window, while amounts accruing on or after 2024-04-15 fall within it.

Note: This worked example uses the general/default 2-year SOL in 42 Pa. Cons. Stat. § 5552. If a claim type has its own SOL, the allocation may change.

Inputs to enter in DocketMath (damages-allocation)

Use the calculator at: /tools/damages-allocation

Enter the following:

  • Jurisdiction: US-PA
  • General SOL length: 2 years
  • Filing date: 2026-04-15
  • Damages components: each component should include an accrual start and end date, plus the amount claimed

For DocketMath, you can model each component as accruing evenly across its window (a time-proration approach), then compute the portion that falls inside vs. outside the SOL lookback window.

Disclaimer: This is a modeling walkthrough, not legal advice. Actual accrual rules and dates can depend on the facts of when damages were incurred, how they were computed, and when they legally “accrued.”

Example run

Run the Damages Allocation calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Determine the SOL window

  • Filing date: 2026-04-15
  • SOL length (general/default): 2 years (42 Pa. Cons. Stat. § 5552)
  • Lookback start date: 2024-04-15

So the “potentially recoverable window” (for allocation purposes here) is:

  • 2024-04-15 → 2026-04-15

Step 2: Allocate each damages component

Component A: 2024-03-01 → 2024-10-01 ($18,000)

Split by the lookback start:

  • Portion before lookback start: 2024-03-01 → 2024-04-15
  • Portion inside window: 2024-04-15 → 2024-10-01

Assuming DocketMath’s time-based proration across the accrual window, we estimate the inside proportion:

  • Total duration (Mar 1 → Oct 1): ~214 days
  • Days inside window (Apr 15 → Oct 1): ~169 days
  • Inside proportion: 169 / 214 ≈ 0.790

Allocated:

  • Inside SOL: $18,000 × 0.790 ≈ $14,220
  • Outside SOL: $18,000 × (1 − 0.790) ≈ $3,780

Component B: 2024-11-01 → 2025-09-01 ($27,000)

This entire component accrues after 2024-04-15 and before filing.

  • Allocated inside SOL: $27,000
  • Allocated outside SOL: $0

Component C: 2025-10-01 → 2026-01-01 ($12,000)

Also entirely within the lookback window.

  • Allocated inside SOL: $12,000
  • Allocated outside SOL: $0

Step 3: Summarize totals

ComponentClaimedInside SOLOutside SOL
A$18,000$14,220$3,780
B$27,000$27,000$0
C$12,000$12,000$0
Total$57,000$53,220$3,780

Step 4: Understand what DocketMath is doing (mechanically)

In this worked example, DocketMath’s allocation is driven by:

  • The filing date (2026-04-15)
  • The general SOL (2 years) under 42 Pa. Cons. Stat. § 5552
  • The accrual windows for each damages component
  • A proration method (time proportion across each accrual window)

The output helps you convert “total claimed damages” into two buckets:

  • Inside SOL (within the general 2-year lookback)
  • Outside SOL (outside the lookback)

Warning: This date-based allocation is a modeling approach. Real-world accrual can depend on the specific facts and legal theory, which can shift effective accrual dates and therefore the allocation.

Sensitivity check

Change one input at a time and observe how allocation moves. These examples keep everything constant except the item under test.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

1) Filing date sensitivity (moves the 2-year lookback window)

Assume accrual windows stay the same, but the filing date changes.

Scenario: Filing date moved earlier by 30 days

  • New filing date: 2026-03-16
  • New lookback start: 2024-03-16

Component A (2024-03-01 → 2024-10-01) gains additional inside-window days.

Expected effect:

  • Outside SOL for A decreases
  • Inside SOL increases
  • Totals shift by roughly the change in A’s prorated inside portion

Intuition check:

  • Previously, the outside portion started at Mar 1 and ran until Apr 15.
  • Now it runs until about Mar 16—so fewer days are excluded.

Scenario: Filing date moved later by 30 days

  • New filing date: 2026-05-15
  • New lookback start: 2024-05-15

Component A loses inside-window days.

Expected effect:

  • Outside SOL for A increases
  • Inside SOL decreases

Practical takeaway:

  • If you can credibly support later accrual boundaries (or otherwise justify later-effective accrual), your “inside SOL” portion may grow. DocketMath helps you visualize that date math so you can document assumptions early.

2) Accrual window sensitivity (changes what falls inside the 2-year window)

Keep the filing date fixed at 2026-04-15, but vary the boundary between components.

Example: Suppose Component A’s accrual start is 2024-04-20 instead of 2024-03-01.

  • Then almost all of A falls inside the lookback start (2024-04-15).
  • Expected outcome:
    • Outside SOL could drop near zero
    • Inside SOL approaches the full $18,000

In contrast, if Component A’s accrual start is 2024-02-01:

  • More of A falls outside the lookback window.
  • Expected outcome:
    • Outside SOL increases
    • Inside SOL decreases

Checklist you can use when running DocketMath

Related reading