Slip and fall settlement guide for Pennsylvania

Direct answer

A Pennsylvania slip-and-fall settlement can often be modeled around 42 Pa.C.S. § 7102, because the statute addresses how contributory behavior (comparative fault concepts) and “receipts/other limitations” can affect ultimate payment shares when multiple parties or claims are involved. Using DocketMath, you can plug in your damages categories, set fault percentages, and apply the statute-aware logic for how those inputs change the allocation and net settlement value.

For the allocation math tool, use: /tools/damages-allocation.

What you need to know

Slip-and-fall settlement allocation in Pennsylvania commonly turns on two practical levers in your math workflow:

1. Fault allocation thresholds (comparative-fault style math)

   • In your DocketMath setup, use the verified comparative-fault configuration of 50% / 50% (a 50% breakpoint on each side in the comparative model).

2. Receipts / limitation concepts

   • If your settlement accounting includes “receipts” (or related limitation concepts), your DocketMath model needs to reflect the packet’s guidance that the limitation period is “see statute.”
   • In practice: you should enter receipt/limitation inputs in DocketMath consistent with how 42 Pa.C.S. § 7102 is being applied in your workflow.

To keep settlement numbers defensible, gather the inputs below in a consistent format before you run multiple DocketMath scenarios (for example, changing fault emphasis from plaintiff-heavy to premises-heavy).

Practical input checklist (for DocketMath)

• Liability parties you’re allocating between (commonly plaintiff vs. premises party; sometimes more depending on claim structure)
• Fault estimates for each party (as percentages that sum to the allocation total your model expects)
• Damages categories you’ll allocate (use the categories you actually plan to settle, such as economic vs. non-economic)
• Receipts/offset information relevant to “receipts” and limitation concepts in your accounting
• Any receipt limitation-period fields required by DocketMath—populate them from the 42 Pa.C.S. § 7102 text you are using, consistent with the “see statute” instruction in the verified facts packet

Step-by-step

Below is a Pennsylvania-ready settlement workflow you can run in DocketMath to allocate damages for a slip-and-fall matter.

Step 1: Build your damages stack (before allocation)

Start by compiling total damages by category so allocation is clean and totals reconcile.

• Create a Total Damages number for each category you plan to include.
• Keep a single master total you can reconcile against the final allocated totals.

Step 2: Define a scenario set (don’t commit to one number too early)

Set up multiple fault scenarios so you can see how sensitive the settlement value is to fault inputs.

Because the verified comparative-fault thresholds are 50% / 50%, include scenarios that test:

• A case where the plaintiff is at/below the breakpoint
• A case where the premises party is at/above the breakpoint
• A case where the fault split is closer to even to observe stability

Step 3: Enter fault allocations for each scenario

In DocketMath:

• Enter the fault percentages for each party for that scenario.
• Confirm your comparative-fault threshold configuration matches the verified setup (50% / 50%).

Step 4: Add statutory-structure inputs (receipts/limitations)

If your settlement has receipts/offset accounting, add those inputs in DocketMath using the statute-aware structure tied to 42 Pa.C.S. § 7102.

• The verified facts packet states the limitation period is “see statute.”
• That means any DocketMath field that requires a limitation period should be completed by referencing the statutory text you are relying on for your model (i.e., 42 Pa.C.S. § 7102 and the specific subsection structure you’re using).

Step 5: Allocate damages and record outputs

Run the allocation in DocketMath for each scenario and document:

• Allocated share by damages category
• Allocated totals by party
• Any effect of receipts/limitations on net settlement value

Step 6: Pick a negotiation posture based on the allocation spread

Compare scenario outputs:

• If the net result swings materially with small fault changes, you likely need stronger evidence on the fault drivers before tightening the demand/offer.
• If the net result stays relatively stable, you can negotiate more confidently around the central allocation estimate.

Key statutes and citations

This Pennsylvania settlement allocation guide is anchored to:

• 42 Pa.C.S. § 7102 (primary statute governing the allocation framework referenced for these settlement calculations)
• 42 Pa.C.S. § 7102(a)
• 42 Pa.C.S. § 7102(a.1)–(a.2)
• 42 Pa.C.S. § 7102(a.1)(1)
• 42 Pa.C.S. § 7102(a.1)(3)

Primary source URL (verified packet authority):

• https://www.palrb.us/pamphletlaws/20002019/2011/0/act/0017.pdf

Implementation warning: ensure the specific subsection structure you rely on in your workflow matches what DocketMath expects when you enter receipts/limitation inputs under 42 Pa.C.S. § 7102.

Common pitfalls

These are the issues that most often create settlement-allocation problems in DocketMath—not the underlying arithmetic.

1. Using one fault percentage and skipping scenarios

   • The verified comparative-fault threshold configuration is 50% / 50%—you should test how outcomes shift around that breakpoint.

2. Omitting receipts/offset inputs when the settlement accounting includes them

   • If you model net settlement value, DocketMath needs the receipts/limitations inputs aligned to 42 Pa.C.S. § 7102.

3. Not sourcing the “limitation period” correctly

   • The verified packet says the limitation period is “see statute.”
   • Avoid guessing—populate DocketMath from the statute text you are using in your analysis.

4. Forgetting joint/several model threshold configuration

   • The verified facts packet includes a 60% joint/several threshold parameter in the allocation model.
   • If your setup triggers a joint/several path, ensure your DocketMath configuration matches that threshold.

5. Category totals don’t reconcile

   • If your allocated category totals don’t tie back to your master damages total, negotiations become harder and outputs are less defensible.

Run the numbers

Use DocketMath to model a settlement range by running multiple allocation scenarios and tracking how outputs change.

Recommended scenario matrix (based on verified thresholds)

• Use the comparative-fault breakpoint testing implied by the verified 50% / 50% configuration.
• If your facts fit a joint/several-triggered modeling path, also validate the 60% joint/several configuration.

A simple structure for runs:

How to interpret outputs

After each DocketMath run, capture:

• Allocated damages totals by party
• Net settlement estimate after any receipts/limitations you modeled
• The delta vs. the prior scenario (how much net value moved)

Practical decision rule

• If small changes in fault inputs produce large net-value shifts, tighten your evidence on fault before locking in numbers.
• If outputs are stable across scenarios, you can negotiate nearer the center of your allocation range.

Related reading

• How to calculate Damages Allocation in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Damages Allocation in Philippines — Worked example with real statute citations
• Inputs you need for Damages Allocation in Philippines — Input checklist with sourcing guidance