Slip and fall settlement guide for New Mexico

Direct answer

In New Mexico slip-and-fall settlements involving multiple defendants, you’ll typically allocate each defendant’s percentage share of fault so no one pays more than their share of the “total damages attributable to the negligence or fault” under N.M. Stat. Ann. § 41-3A-1(A) (New Mexico’s several-liability framework for covered causes of action).

DocketMath’s /tools/damages-allocation can help you model those allocation mechanics and keep settlement numbers consistent when there are multiple parties (for example, property owner/landlord, premises management, and a snow/ice or maintenance contractor). This can reduce the risk of structuring a settlement that later doesn’t track the governing allocation logic.

What you need to know

New Mexico recognizes a several liability concept through N.M. Stat. Ann. § 41-3A-1. In settlement terms, the practical consequence is:

• Each defendant’s payment is tied to their percentage of fault (i.e., their share of the “total damages attributable” to that defendant’s negligence or fault).

What “several liability” means for slip-and-fall settlement math

When you include allocation in a settlement discussion (especially with multiple defendants), you’re generally trying to align three moving parts:

1. Total damages (medical bills, future care, lost wages, non-economic damages, etc.)
2. Fault percentages among the parties
3. Settlement amounts that correspond to each defendant’s share

Default period used here (clarity on what this guide covers)

The jurisdiction notes provided don’t identify a claim-type-specific sub-rule. So, for this guide, treat the following as the general/default allocation period used for the allocation mechanics discussed:

• General/default period: Scott v. Rizzo, 96 N.M. 682 (1981); N.M. Stat. Ann. § 41-3A-1

Step-by-step

Use this workflow to run an allocation in DocketMath and pressure-test settlement ranges.

1) Identify who you’re allocating among

List each entity you believe could be at fault based on the case record and discovery. In slip-and-fall matters, this often includes:

• Property owner/landlord
• Premises management company
• Snow/ice removal contractor
• Cleaning or maintenance/vendor contractor
• Any other party implicated in pleadings or evidence

Then check whether you have more than one defendant. Allocation modeling is especially important in multi-defendant cases, but it can still help keep settlement positions internally consistent.

2) Estimate “total damages” first

Before allocation, you need a defensible damages estimate. In DocketMath, the /tools/damages-allocation approach is built around estimating:

• Economic damages (medical expenses, wage loss, etc.)
• Non-economic damages (pain and suffering, inconvenience)
• Future damages (if supported)

You don’t need perfection—you need internal consistency so the allocation shares are applied to the correct totals.

3) Assign fault percentages (and ensure they reconcile)

Next, develop a fault allocation based on the evidence available, such as:

• What each party knew or should have known about the hazard
• Inspection and maintenance practices
• Timing of notice, inspections, and repairs
• Control and responsibility (who had authority over the premises or the hazard area)
• Any comparative fault arguments that the posture of the case makes relevant

A key practical step: ensure your fault percentages add up correctly for the model you’re using (for many allocation frameworks, that means totaling 100% across the allocated defendants).

4) Enter inputs into DocketMath

Open /tools/damages-allocation and input:

• Your total damages estimate
• The fault percentages by defendant
• Any adjustments or scenario toggles the tool supports

If the tool flags inconsistencies (for example, percentages not reconciling), fix those inputs before relying on outputs.

5) Run multiple scenarios and compare

Negotiations evolve. To reflect that reality, run at least 2–3 scenarios, such as:

• Conservative / plaintiff-unfavorable fault map
• Middle / likely fault map
• Aggressive / defense-favorable fault map

Track how the following change across scenarios:

• Each defendant’s allocated share
• The resulting settlement range you can justify without creating allocation conflicts

Key statutes and citations

Several liability cap tied to fault: N.M. Stat. Ann. § 41-3A-1(A)

New Mexico’s several-liability rule provides, in relevant part, that for causes of action to which several liability applies:

• No defendant is liable for an amount in excess of the percentage of total damages attributable to that defendant’s negligence or fault.

In settlement terms, this is why you generally avoid a structure that effectively requires a defendant to pay more than their percentage share of fault-attributable damages.

Jurisdiction citation: Scott v. Rizzo, 96 N.M. 682 (1981)

Scott v. Rizzo is listed in the jurisdiction data as part of the allocation framework referenced alongside § 41-3A-1. For purposes of this guide’s modeling approach, treat Scott as supporting the allocation framework applied in New Mexico.

General/default period clarity (no claim-type-specific sub-rule found)

No claim-type-specific sub-rule was found in the provided jurisdiction notes. Therefore, this guide uses the general/default allocation period referenced above—Scott v. Rizzo and N.M. Stat. Ann. § 41-3A-1—for the allocation mechanics discussed.

Common pitfalls

• Aligning settlement dollars poorly with fault percentages

  • If the settlement implies a defendant pays more than what their percentage share suggests, you may need to renegotiate or restructure later.
• Using a “global” number without mapping to fault allocation

  • A single lump-sum figure can obscure whether each defendant’s practical exposure stays within the several-liability logic of § 41-3A-1(A).
• Fault percentages that don’t reconcile

  • Allocation math frequently fails basic checks (e.g., totals not matching the model’s required sum). Use DocketMath to validate inputs early.
• Confusing total damages with allocated shares

  • Keep your total damages estimate separate from your allocated payment amounts.
• Not rerunning scenarios after new facts

  • Discovery can shift the fault map (inspection logs, video, contract scope, notice timelines). If fault changes, re-run the numbers.

Run the numbers

Damages allocation input checklist (prepare before modeling)

• Total damages estimate (economic + non-economic + future damages, if any)
• Defendant list (all parties you plan to allocate)
• Fault percentages per defendant (and confirm the percentages reconcile for your model)
• Scenario set (at least 2–3: conservative / middle / aggressive)

Example (illustrative)

Assume you estimate $200,000 total damages and allocate fault between two defendants:

Under N.M. Stat. Ann. § 41-3A-1(A), the practical point is that settlement exposure should track the defendant’s percentage share of damages attributable to that defendant’s negligence or fault.

What changes when inputs change

When you adjust assumptions, these effects usually follow:

• Increasing a defendant’s fault percentage generally increases their allocated share.
• Updating the total damages generally scales allocated shares (if fault percentages stay constant).
• Adding another defendant often reduces each remaining defendant’s share, depending on how fault is redistributed.

Primary CTA

To model damages allocation quickly and compare scenarios, use: /tools/damages-allocation

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