How to run Damages Allocation in DocketMath for Pennsylvania
6 min read
Published April 15, 2026 • By DocketMath Team
Step-by-step
Run this scenario in DocketMath using the Damages Allocation calculator.
This guide walks you through running Damages Allocation in DocketMath for Pennsylvania (US-PA). You’ll set jurisdiction-aware assumptions, choose the correct inputs, and interpret the allocation output. No claim-type-specific SOL sub-rule was found for this particular damages allocation workflow, so DocketMath uses the general/default limitations period for Pennsylvania.
Before you start, make sure you have the following basics ready:
- Jurisdiction: Pennsylvania (US-PA)
- Damages categories you want allocated (for example: compensatory vs. other damages types your case uses)
- Total damages amount (and any partial totals per category, if you track them)
- Allocation method inputs your case supports (e.g., shares/ratios or category amounts)
1) Open the calculator and select Pennsylvania
- Go to the primary calculator page: /tools/damages-allocation
- Ensure the jurisdiction is set to Pennsylvania (US-PA).
- Confirm the SOL basis displayed by the tool matches Pennsylvania’s general default.
Pennsylvania’s general statute of limitations for most actions is 2 years, codified at:
- 42 Pa. Cons. Stat. § 5552
Note: DocketMath’s Damages Allocation for Pennsylvania is running off the general/default 2-year limitations period because no claim-type-specific sub-rule was identified for this particular damages allocation workflow.
2) Enter your damages inputs
DocketMath’s Damages Allocation generally works best when you provide clean numeric inputs. Typical inputs include:
- Total damages (a single number), or
- Breakdown amounts by category (if your case tracks components)
Use numbers in consistent units (usually dollars). If your case uses periods (for example, different time ranges), add those as separate categories only if the tool supports category-level time distinctions.
Quick input checklist
3) Choose the allocation inputs that match your case logic
Depending on the Damages Allocation calculator configuration, you may be asked for one of the following patterns:
- Category amounts → you enter what portion each damages bucket represents
- Allocation weights/percentages → you enter shares that sum to 100%
- Recoverable vs. non-recoverable splits → you enter which portions the allocation should treat differently
If the interface offers both amounts and weights, pick the approach that reflects your source documents:
- Use amounts if your damages spreadsheet already gives line-item totals.
- Use weights if your case has already normalized figures (e.g., “30% for Category A”).
- Use splits if you have an explicit recoverability boundary and DocketMath is designed to treat those differently.
4) Run the allocation
Click the Calculate/Run action in DocketMath.
Watch for these output areas (names can vary, but the structure usually follows this pattern):
- Allocated totals by category
- Derived totals (sanity-check totals)
- Remaining/unallocated amounts (if your inputs don’t fully account for the total)
- Any SOL-related computed flags/fields the calculator uses as part of the workflow
5) Interpret what changes when SOL is applied
Because Pennsylvania’s general default SOL is 2 years under 42 Pa. Cons. Stat. § 5552, DocketMath may do one or both of the following in the Damages Allocation flow:
- Apply a time window (if you entered dates or periods)
- Distinguish in-scope vs. out-of-scope damages components when the tool is date-aware
If you provided any date ranges (or time-segmented damages categories), changing those dates can shift:
- how much of each category is considered “within the limitations window,” and
- the final allocated totals accordingly.
If you did not provide dates/periods, you’ll likely see allocation changes only from the damages-category inputs—not from the SOL component.
Warning: If you entered damages by period (e.g., “Jan–Mar” and “Apr–Jun”) without matching how the tool interprets the boundaries, the SOL window may cause unexpected reallocation. Re-check the time ranges you selected before relying on the output.
6) Validate the results with a quick consistency check
Before you export or copy results into your workflow, do a 30-second check:
For a fast sanity check, compare:
| Check | What to look for | What it suggests |
|---|---|---|
| Category sum | Categories ≈ total | Your inputs likely balance correctly |
| SOL effect | Some components reduced/excluded | Dates/period inputs likely drove the result |
| Missing remainder | Tool shows unallocated amount | Your inputs may not cover the full total |
7) Export or document the output
Use the calculator’s provided export/copy options (if available). When you save your work, also keep a note of:
- the jurisdiction setting (US-PA),
- that the calculator used Pennsylvania’s general/default 2-year SOL under 42 Pa. Cons. Stat. § 5552, and
- the input method (amounts vs. weights vs. splits).
This makes later review easier, especially when you iterate on inputs.
Gentle reminder: this walkthrough is about using DocketMath and interpreting calculator outputs—not about providing legal advice. If you’re unsure how limitations apply to your specific claim, consider consulting a qualified attorney.
Common pitfalls
These are the most frequent issues users run into when running Damages Allocation for Pennsylvania in DocketMath:
Relying on the wrong SOL rule for a specific claim type
The workflow here uses the general/default limitations period because no claim-type-specific sub-rule was identified for this calculator setup. Pennsylvania’s general period is 2 years under 42 Pa. Cons. Stat. § 5552.Entering category amounts that don’t reconcile with the total
If your category line items don’t sum to the total, the tool may show:- a remainder/unallocated amount, or
- scaled results (depending on the tool’s logic).
Mixing dollars and thousands
Example: entering “50” when your spreadsheet uses “50,000.” The output will be off by a factor of 1,000 even if the math is internally correct.Date boundary confusion
If the tool is SOL-date-aware, small date shifts can change which components land inside the limitations window.Overlapping time periods
If two categories cover the same days and the tool treats them as separate components, the allocation can effectively double-count time slices (unless it has overlap protections).
Pitfall: If your case timeline includes multiple events (e.g., separate accrual points) but you input only one broad date range, the tool may apply the SOL window uniformly—potentially producing misleading “in-window/out-of-window” splits.
Try it
Ready to run your Pennsylvania Damages Allocation in DocketMath?
- Open the calculator here: /tools/damages-allocation
- Set Pennsylvania (US-PA).
- Enter your damages inputs:
- either total damages or a category breakdown
- If prompted for dates/periods, enter the time ranges you want evaluated within Pennsylvania’s general 2-year SOL under 42 Pa. Cons. Stat. § 5552.
- Click Calculate and review:
- allocated totals by category,
- any SOL-based in-window/out-of-window effects,
- and category sum consistency.
If you want the quickest path to accurate results, use this checklist while you input:
