How to run Settlement Allocator in DocketMath for Pennsylvania

Step-by-step

Run this scenario in DocketMath using the Settlement Allocator calculator.

This guide walks you through running Settlement Allocator in DocketMath for Pennsylvania (US-PA). It’s designed to help you understand the workflow and how the output changes when Pennsylvania’s jurisdiction-aware time rules are applied—without providing legal advice.

1) Open the calculator

Start at the primary call-to-action:

• /tools/settlement-allocator

If you’re navigating from elsewhere in DocketMath, you can also go to the platform’s tools area and select Settlement Allocator.

2) Select the jurisdiction: Pennsylvania (US-PA)

In the calculator settings, set:

• Jurisdiction: US-PA (Pennsylvania)

Why this matters: Pennsylvania’s general statute of limitations (SOL) period is used as the default “limiting” timeframe unless the tool is configured with a more specific rule. For this brief, no claim-type-specific sub-rule was found, so the tool uses the general/default period.

3) Enter the case timing inputs

Settlement Allocator generally depends on timing inputs—commonly:

• Incident date (or event date)
• Filing date (or demand/filing date used by your workflow)
• Optional: settlement date or other dates the tool asks for (if shown)

Enter dates in a consistent format (for example, 2024-06-15). Consistency helps ensure the elapsed-time calculations are correct.

What the tool is doing conceptually

• It measures the time between key dates you supply.
• It uses that elapsed time to determine whether claims may be treated as within the default SOL window.
• It allocates settlement components accordingly.

4) Confirm the SOL rule the calculator will use (Pennsylvania default)

For Pennsylvania, the jurisdiction data provided for this guide indicates:

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

Important clarification (per the brief):

• No claim-type-specific sub-rule was found.
• Therefore, the allocator should treat 42 Pa. Cons. Stat. § 5552 as the default/general period.

How this affects output: your result will reflect the 2-year default window rather than a narrower timeline tied to a specific claim category.

5) Add the settlement and allocation inputs

Next, enter the settlement-related numbers the tool requests. Typical inputs include:

• Total settlement amount
• Optional or additional allocation/bucket fields the tool supports (for example, splitting amounts among components, damage categories, or parties)

If DocketMath offers fields that map to allocation “buckets,” fill them with the amounts you want considered.

Practical tip

• If you only know the total settlement, enter that first.
• Then, if the tool prompts for bucket amounts, you can either:

  • leave optional breakdown fields blank (if allowed) so the allocator can propose a distribution, or
  • enter breakdown amounts if your workflow requires a specific allocation structure.

6) Run the allocator

After completing the required fields:

• click Calculate (or the equivalent action button)

The tool will generate output that typically includes:

• an allocation breakdown influenced by whether relevant periods fall within vs. outside the default SOL window, and
• one or more time-based adjustments describing how much settlement is treated as attributable to eligible vs. ineligible timeframes (wording can vary by interface).

7) Review output details and adjust inputs to see how results move

Before relying on the output, sanity-check it by adjusting one variable at a time.

Try these “what-if” recalculations:

• Change the incident date by 30–90 days and recalculate.
• Adjust the filing date and recalculate to see whether allocations shift when elapsed time approaches/passes the 2-year boundary.
• If the interface shows a within SOL vs. outside SOL indicator, treat that as a key interpretation signal while refining your inputs.

Common pitfalls

Below are common issues when using DocketMath Settlement Allocator for Pennsylvania.

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

1) Treating Pennsylvania as having one SOL for every claim type

For this workflow, the allocator relies on the general/default period:

• 2 years under 42 Pa. Cons. Stat. § 5552
• and no claim-type-specific sub-rule was found in the brief

If you later determine the matter involves a specialized or different timeline, the allocator’s default configuration may not match that scenario—so consider whether a different setup/rule selection is appropriate.

2) Mixing date formats or entering incomplete dates

Examples:

• 6/1/24 vs 2024-06-01
• missing day/month precision if the tool expects a full date

Consequence: the tool may reject the entry or interpret it in an unintended way, leading to incorrect elapsed-time calculations.

3) Using the wrong “start” date for elapsed time

Settlement Allocator’s logic depends on which date is treated as the beginning of the relevant time window (often the incident/event date).

Checklist:

• Does your incident date match the event date described in your records?
• Is your filing date the one the tool expects (not an unrelated notice date, unless the interface labels it that way)?

4) Entering inconsistent totals vs. allocation buckets

If you enter both:

• a total settlement amount, and
• per-bucket amounts,

then those values should align.

Quick consistency check:

• Do the bucket totals equal the total settlement you entered?
• If not, correct the inputs and rerun the calculation.

Try it

Use this quick “first run” to verify your setup in DocketMath:

1. Open /tools/settlement-allocator
2. Set Jurisdiction to US-PA
3. Enter:

   • Incident/event date
   • Filing date (or the tool’s required comparable date)
   • Total settlement amount
4. Click Calculate
5. Confirm the output reflects the Pennsylvania default/general SOL of 2 years based on 42 Pa. Cons. Stat. § 5552

Then run two controlled “what-if” scenarios:

• Scenario A: Move the filing date forward by ~90 days (keep incident date fixed).
• Scenario B: Move the incident date backward by ~90 days (keep filing date fixed).

If the elapsed time crosses a boundary near 2 years, you should see allocation outputs shift. If nothing changes, check that:

• the dates are actually different in the calculation inputs, and
• the tool is using the default general SOL (as provided by the brief), rather than waiting for a claim-type-specific configuration.

For convenience, you can revisit the tool via the tools area and again use /tools/settlement-allocator to iterate quickly.

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado