Abstract background illustration for How to run Settlement Allocator in DocketMath for Pennsylvania

How to run Settlement Allocator in DocketMath for Pennsylvania

6 min read

Published June 4, 2026 • By DocketMath Team

Partially verified

older_than_packet

Step-by-step

This guide walks you through running Settlement Allocator in DocketMath for Pennsylvania (US-PA) using jurisdiction-aware rules tied to Pa. R. Civ. P. 1701–1716. It’s written to help you get correct results from the tool, not to provide legal advice.

1) Open the correct calculator

  1. Go to /tools/settlement-allocator.
  2. Confirm the jurisdiction selector is set to Pennsylvania (US-PA).

2) Gather the settlement inputs the calculator needs

Settlement Allocator typically requires enough information to compute the allocation period and then distribute settlement amounts across relevant components. Before you start clicking:

  • Identify the settlement total you want to allocate.
  • Collect the relevant date(s) used to define the allocation period (for example, start and end dates used for the timeline).
  • Confirm whether the case involves multiple claim categories/components that your inputs will split and allocate separately (even if you don’t have claim-type-specific instructions, you still need the tool’s component inputs to match what you want to allocate).

Pennsylvania rule note (important): This Pennsylvania implementation uses the general/default period under Pa. R. Civ. P. 1701–1716. No claim-type-specific sub-rule was found, so you should not expect special “period rules” based on claim labels inside this guide.

3) Enter Pennsylvania-relevant dates and amounts

In DocketMath:

  • Enter the settlement total.
  • Enter the allocation timeline inputs (such as “from” and “to” dates or other period-defining fields, depending on the calculator’s UI).
  • If the tool asks for component breakdowns (for example, principal vs. other components), enter those figures as separate inputs so the calculator can allocate within the structure you provided.

Quick self-check before you submit:

  • Verify your date order (start date should come before end date).
  • Use the same date basis you intend to support in your case notes (for example, the date the settlement is effective vs. the date it is signed—whichever your workflow requires).

4) Run the allocation

  1. Click Calculate (or the equivalent action in the DocketMath interface).
  2. Review:
    • The computed period (or any derived timeline field).
    • The allocation outputs for each component the tool supports.

5) Interpret outputs and verify sensitivity

After calculation, treat the results like a model output you can audit:

  • If you change the end date by 30 days, does the output shift in the expected direction?
  • If you increase the settlement amount, do allocations scale proportionally (or do only certain components move)?

These directional checks help you catch input mismatches (like swapped dates or entering net vs. gross settlement numbers).

6) Use the jurisdiction rule set explicitly in your workflow notes

For Pennsylvania, the timeline logic you’re relying on should trace back to:

  • Pa. R. Civ. P. 1701–1716 (Chapter 17 — Actions at law; Pretrial practice and depositions of witnesses, including rules that relate to procedural timelines/periods)

When documenting your run:

  • Record the exact inputs you entered (especially dates).
  • Note that the tool uses the general/default period in Pa. R. Civ. P. 1701–1716 and not a claim-type-specific sub-rule (since none was identified for this Pennsylvania setup).

7) Export or save results for your file

If DocketMath offers export, save:

  • The allocation table/results view.
  • Any displayed assumptions or derived timeline values shown by the calculator.

If your workflow includes versioning, save your output under a label like:

  • “US-PA allocator run – v1 (2026-06-04)”

This makes it easier to compare later runs when dates or component amounts change.

Common pitfalls

These are the mistakes that most often lead to incorrect or confusing Settlement Allocator outputs in Pennsylvania.

  • Using claim-type-specific periods despite the setup using the general/default period

    • For this Pennsylvania configuration, no claim-type-specific sub-rule was found. The tool uses the general/default period under Pa. R. Civ. P. 1701–1716.
  • Swapping start and end dates

    • Even if the tool accepts your entries without error, swapped dates can create a shorter/incorrect effective period depending on validation logic.
  • Entering net settlement instead of total settlement

    • If your settlement amount is net of deductions, the allocator may produce allocations that don’t match the totals you’re trying to represent.
  • Mixing date types (effective date vs. filing date) without consistency

    • Pick the date basis you intend to model and keep it consistent across runs (especially if you will compare outputs later).
  • Not performing a directional sanity check

    • You should expect time-based allocations to move when you move the end date forward or backward.
  • Failing to capture derived period values

    • Derived values (like the computed period length) are often what you’ll want later to explain how the tool arrived at the numbers.

Warning: Don’t assume that because two calculators exist (or because another jurisdiction uses claim-type splits) that Pennsylvania will mirror that behavior. In this Pennsylvania setup, the identified logic relies on the general/default period in Pa. R. Civ. P. 1701–1716.

Try it

Ready to run a Pennsylvania allocation in DocketMath? Use this quick “make it real” checklist.

Quick run checklist (3 minutes)

  • Set jurisdiction to Pennsylvania (US-PA)
  • Enter settlement amount
  • Enter the start date and end date that define the allocation period
  • Confirm component inputs (if shown) match the breakdown you want to allocate
  • Click Calculate
  • Review the derived period value and allocation table
  • Change the end date by ±30 days and confirm outputs move logically

What to look for in the results

On the output screen, verify you can identify:

  • The allocation period (or equivalent derived timeline value)
  • The allocation breakdown by the components the calculator supports
  • Any displayed note that Pennsylvania logic was applied (aligned to Pa. R. Civ. P. 1701–1716)

If you later want to compare results across systems, compare the behavior of jurisdictions where claim-type-specific rules are known to exist. (For Pennsylvania, remember this setup relies on the general/default period rather than a claim-type-specific sub-rule.)

Related reading