How to calculate pre/post-offer damages split in Pennsylvania

Quick takeaways

• Pennsylvania’s pre/post-offer split for damages is driven by Pa. R.C.P. 238 (delay damages) and the offer-recovery framework in Pa. R.C.P. 238(b).
• In DocketMath (US-PA), you calculate delay damages before the offer and delay damages after the offer, then apply the offer-recovery threshold (125%) under Pa. R.C.P. 238(b) to adjust the post-offer component.
• For post-judgment interest, DocketMath’s US-PA defaults use a 6% per annum legal rate tied to 41 P.S. § 202.
• Jurisdiction-aware DocketMath settings for US-PA include:

  • delay_damages_rate = prime + 1%
  • delay_damages_threshold_offer_recovery_pct = 125
  • interest_rate_post_judgment = 6

Inputs you need

To calculate a pre/post-offer damages split in Pennsylvania (US-PA) with DocketMath, you’ll generally need the dates and amounts that define the delay-damages window and the offer-recovery comparison.

Use the calculator here: /tools/pre-post-offer-damages

Core timeline and amounts

• Offer date (this is the dividing line between the pre-offer and post-offer delay-damages portions)
• Delay-damages start date (the start point for the delay-damages period under Pa. R.C.P. 238)
• Delay-damages end date (the end point for that delay-damages period under the framework you’re using)
• Offer amount (the amount associated with the offer you are testing under Pa. R.C.P. 238(b))
• Comparison amount used by the tool (the judgment/figure the calculator uses for the offer-recovery comparison)

Interest / rates (DocketMath US-PA settings)

When you select Pennsylvania (US-PA), DocketMath uses these jurisdiction-aware defaults:

• Delay damages rate: prime + 1%
• Offer recovery threshold: 125%
• Post-judgment interest rate: 6 (per year basis used by the calculator)

DocketMath also flags certain limitation-period logic as statute-driven (e.g., “receipts limitation period: see statute”).

Output targets

After you enter your inputs, DocketMath will produce (conceptually):

• Pre-offer delay damages
• Post-offer delay damages (initial/unadjusted figure)
• Adjusted post-offer component after applying the 125% offer-recovery threshold logic
• Total delay damages (as reflected by the tool: pre + adjusted post, where applicable)
• Post-judgment interest computed using the US-PA 6% legal-rate setup

Quick accuracy checklist:

• You entered the offer date correctly (it’s the split boundary).
• You entered the comparison amount the calculator expects for the Pa. R.C.P. 238(b) comparison.
• Your delay-damages start/end dates match the time window you intend under Pa. R.C.P. 238.
• You selected US-PA so the prime + 1% and 125% defaults are applied.

How the calculation works

This section explains the mechanics DocketMath applies for US-PA when calculating a pre/post-offer damages split under Pa. R.C.P. 238 and the offer-recovery framework in Pa. R.C.P. 238(b).

1) Compute the delay-damages rate used for both segments

DocketMath’s US-PA setup uses:

• Delay damages rate = prime + 1%

Practical implication: if the underlying prime input changes in your workflow, your pre and post delay-damages numbers can shift even when your dates and amounts remain unchanged.

2) Split the delay-damages period at the offer date

DocketMath divides the delay-damages period into two segments:

• Pre-offer period: from the delay-damages start date up to the offer date
• Post-offer period: from the offer date to the delay-damages end date

At a high level, think of it as:

• Segment A produces Pre-offer delay damages
• Segment B produces Post-offer delay damages, which is then subject to the offer-recovery adjustment

3) Calculate delay damages separately for each segment

For each segment, DocketMath:

• uses the same delay-damages rate = prime + 1%
• applies the segment’s time length (based on your entered dates)
• uses the base/amount inputs you provide for the delay-damages computation

Conceptually, you can treat these intermediate outputs as:

• Pre-offer delay damages
• Unadjusted post-offer delay damages

4) Apply the Pa. R.C.P. 238(b) offer-recovery threshold (125%)

This is the “split refinement” in Pennsylvania.

DocketMath uses:

• delay_damages_threshold_offer_recovery_pct = 125

What the 125% threshold does (mechanically, not as legal advice):

• DocketMath compares the comparison amount you provided (for the calculator’s Pa. R.C.P. 238(b) framework) to the offer amount
• Then it determines how the post-offer delay damages should be reduced or recovered based on whether the comparison meets the 125% threshold

Validation tip (before you rely on results):

• Run the tool once with the dates and amounts you believe are correct.
• If the post-offer adjustment seems “too aggressive” or “not aggressive enough,” re-check:

  • offer date alignment (split boundary),
  • offer amount magnitude,
  • comparison amount magnitude (the figure used for the Pa. R.C.P. 238(b) comparison),
  • that you selected US-PA so the 125% parameter is active.

5) Add post-judgment interest using the 6% legal rate

DocketMath also calculates post-judgment interest in a way that is separate from the delay-damages split:

• The US-PA interest rate default is 6
• DocketMath ties this to 41 P.S. § 202 (legal rate of interest setup used by the tool)

Practical implication: even if the post-offer portion of delay damages gets adjusted under Pa. R.C.P. 238(b), post-judgment interest can still appear in the overall damages picture depending on your workflow inputs and how you’re presenting totals.

Common pitfalls

1. Off-by-one or wrong boundary on the offer date

• Because the offer date is the split point, entering it incorrectly can change the length of both segments and shift dollars in both pre and post.

1. Using the wrong amount for the offer-recovery comparison

• The 125% framework depends on a comparison between your offer amount and the comparison amount used by the tool.
• If you input a number that doesn’t match what your workflow intends, the post-offer adjustment may change materially.

1. Assuming a flat delay-damages rate

• DocketMath uses prime + 1% for the delay-damages computation (US-PA), not a single flat percentage that stays constant regardless of prime.

1. Treating post-judgment interest as the same thing as delay damages

• These are distinct computations in the tool:

  • delay damages follow the Pa. R.C.P. 238 mechanics and the Pa. R.C.P. 238(b) offer-recovery threshold for the split
  • post-judgment interest uses the US-PA 6% legal rate setup from 41 P.S. § 202

1. Skipping inputs where DocketMath flags “see statute” limitation logic

• If the tool expects a statute-driven limitation window (for example, tied to receipts logic under the broader Pa. R.C.P. 238 framework) and you don’t supply the relevant time details, you may not get the results you expect.

Sources and references

• Pa. R.C.P. 238 (delay damages framework)
  https://www.pacodeandbulletin.gov/Display/pacode?file=/secure/pacode/data/231/chapter200/s238.html
• Pa. R.C.P. 238(b) (offer-recovery threshold framework referenced by the US-PA calculator logic)
  https://www.pacodeandbulletin.gov/Display/pacode?file=/secure/pacode/data/231/chapter200/s238.html
• 41 P.S. § 202 (legal rate of interest setup used by DocketMath for post-judgment interest)
  https://www.legis.state.pa.us/cfdocs/legis/LI/consCheck.cfm?txtType=HTM&ttl=42&div=0&chpt=81

Next steps

1. Open /tools/pre-post-offer-damages.
2. Select Pennsylvania (US-PA) to ensure the jurisdiction-aware defaults apply (including prime + 1% and the 125% threshold).
3. Enter:

   • the delay-damages start date and end date for the period you’re modeling under Pa. R.C.P. 238
   • the offer date (the split boundary)
   • the offer amount
   • the comparison amount used by the tool for Pa. R.C.P. 238(b) threshold logic
4. Review outputs:

   • confirm **Pre-offer delay