Inputs you need for Damages Allocation in Pennsylvania
5 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Run this scenario in DocketMath using the Damages Allocation calculator.
Pennsylvania damages allocation often depends on what damages categories you’re allocating and when the claimed conduct occurred—not just the total claim amount. If you’re using DocketMath with the damages-allocation calculator (jurisdiction code US-PA), your results are only as reliable as the inputs you enter up front.
This checklist is built around Pennsylvania’s general/default statute of limitations of 2 years under 42 Pa. Cons. Stat. § 5552.
Note: The 2-year period referenced here is the general/default statute of limitations. No claim-type-specific sub-rule was found for this workflow, so the calculator is treated as applying the default period.
Input checklist (template: input-checklist)
Common approaches include percentages, separate sub-totals, or time-based allocation drivers.
Where to find each input
Here’s where you typically locate each input in your case file or drafting materials, plus what to look for so your entries are consistent.
Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.
1) Total damages amount
Where to find it
- Demand letter, complaint, settlement demand worksheet, or your damages spreadsheet.
- For medical/damage claims: medical billing summaries and economic damages summaries.
What to confirm
- Whether your “total damages” already includes attorney’s fees, interest, or costs. If it does, decide whether DocketMath should treat those as part of the main damages bucket (consistent with your model) or whether your workflow handles them separately.
2) Damages categories
Where to find it
- Complaint sections describing the damages sought (e.g., lost wages vs. property damage).
- Expert reports or internal damage model breakdowns.
What to confirm
- Your categories should match the breakdown you intend to allocate. If categories are inconsistent across documents, the allocation can appear “off,” even if the arithmetic is correct.
3) Allocation basis per category
Where to find it
- Your damages model (spreadsheet), expert schedule, or narrative that ties amounts to categories.
- If you allocate by time, use the same time windows stated in your damages analysis.
Common patterns
- Percent split across categories (e.g., 70% economic / 30% non-economic)
- Separate sub-totals per category that you then normalize or reconcile to your “total damages”
4) Dates for statute of limitations timing (default rule)
Where to find it
- The key facts timeline section of your complaint/demand packet.
- Any “accrual” explanation you included in filings.
Pennsylvania default period
- Pennsylvania’s general statute of limitations is 2 years under 42 Pa. Cons. Stat. § 5552.
Source: https://www.legis.state.pa.us/WU01/LI/LI/US/PDF/2000/0/0136..PDF
Important clarification
- Because no claim-type-specific sub-rule was found for this workflow, the system treats the applicable time limit as the general/default 2-year period.
Warning: The biggest input risk is choosing an accrual-trigger date that conflicts with your timeline theory. Even with perfect category data, a mismatched “start date” can change how much of the damages period the tool treats as time-limited.
Run it
After collecting the inputs, run DocketMath → damages-allocation and review whether both the math and timing outputs match your intent. Start here: /tools/damages-allocation
- Go to /tools/damages-allocation.
- Select jurisdiction US-PA so the calculator applies the 2-year general/default period (42 Pa. Cons. Stat. § 5552).
- Enter total damages.
- Define the damages categories you want allocated.
- For each category, enter either:
- a category sub-total, or
- allocation percentages, or
- the time-based driver values your model uses (if your workflow is structured that way)
- Enter timing dates:
- accrual/trigger date
- filing date (or the relevant date you want to test)
- Run the allocation and review the outputs.
What the output should tell you (and how it changes with inputs)
A damages allocation result typically reflects two layers:
| Output dimension | Depends on your inputs | What changes when inputs change |
|---|---|---|
| Allocation math | Category percentages/sub-totals | If category splits shift, category outputs shift proportionally |
| Timing-limited portion | Accrual date + filing date + US-PA default SOL | If the time window moves outside the 2-year period, the time-limited portion can change based on the tool’s timing allocation logic |
To validate your entries, sanity-check:
- Do category totals reconcile to the total damages you entered?
- Does the timing window match your timeline narrative?
- Are your categories defined at the same level of granularity as your damages spreadsheet or demand?
Pitfall: Categories that don’t sum to the “total damages” can produce outputs that are numerically tidy but factually confusing—especially when a timing adjustment is also applied.
Gentle disclaimer (workflow-level)
This walkthrough describes an allocation workflow and references a Pennsylvania default SOL period assumption. It’s not legal advice, and different claims may involve doctrines or specialized rules not covered by the “general/default 2-year” assumption used in this workflow.