Damages Allocation Guide for New Hampshire — Comparative Fault Rules

What this calculator does

Run this scenario in DocketMath using the Damages Allocation calculator.

DocketMath’s Damages Allocation calculator helps you model how a damages award may be reduced in New Hampshire when multiple people are at fault. It’s designed for the most common situation in civil cases: comparative fault—where the factfinder assigns percentages of fault to the parties, and the damages are then reduced accordingly.

In New Hampshire, the key rule is found in RSA 507:7-f (comparative negligence). Under that framework, the plaintiff’s recovery is reduced by their share of fault, rather than being barred entirely.

This guide also covers a second essential timing rule you’ll see when using the calculator outputs: New Hampshire’s general civil statute of limitations (SOL) period is 3 years, under RSA 508:4. That SOL is the baseline rule unless a different claim-specific SOL applies (no claim-type-specific sub-rule is provided here, so treat the 3-year period as the default baseline).

When to use it

Use this calculator when you need a structured way to think through fault allocation and damages reduction in New Hampshire. Typical use cases include:

• Estimating settlement ranges where fault allocation is disputed.
• Reconstructing scenarios for demand letters or mediation briefs (without final reliance on the tool’s output).
• Sanity-checking whether an attorney’s proposed fault split would mathematically produce the expected damages reduction.
• Comparing two competing fault theories, for example:

  • “The plaintiff was 20% at fault.”
  • “The plaintiff was 40% at fault.”

Timing reminder: SOL baseline

Before focusing on damages, confirm you’re working within the relevant filing window. For general civil actions, New Hampshire’s SOL is 3 years under RSA 508:4. If you’re preparing materials tied to a specific event date, this baseline can matter for triage and document collection planning.

Source for RSA 508:4 baseline: https://www.thelaw.com/law/new-hampshire-statute-of-limitations-civil-actions.391/?utm_source=openai

Step-by-step example

Below is a concrete walk-through showing how the calculator’s input choices change the result.

Scenario

Assume a car accident case in New Hampshire where:

• Total calculated damages for the plaintiff’s injuries: $50,000
• Factfinder apportions fault:

  • Plaintiff: 30%
  • Defendant: 70%

Step-by-step

1. Enter total claimed damages

   • Input: $50,000
2. Enter plaintiff’s fault percentage

   • Input: 30%
3. **Enter defendant’s fault percentage (optional, depending on calculator design)

   • Input: 70%
   • If the tool allows it, make sure the inputs sum to 100%. If the tool only needs plaintiff’s percentage, you can skip entering defendant’s.
4. Review the computed reduction

   • Comparative reduction model: the plaintiff recovery is reduced by plaintiff’s fault share.
   • Calculation: $50,000 × (1 − 0.30) = $35,000

Output you should expect

• Gross damages (before fault allocation): $50,000
• Plaintiff fault share: 30%
• Estimated recovery after reduction: $35,000

Quick sensitivity check

If you shift the plaintiff’s fault estimate:

• If plaintiff is 20% at fault → $50,000 × 0.80 = $40,000
• If plaintiff is 40% at fault → $50,000 × 0.60 = $30,000

That’s the practical value of comparative fault modeling: the damage number moves linearly with the assumed fault percentage.

Common scenarios

Comparative fault questions show up in many New Hampshire civil contexts. The exact legal labels vary by case type, but the damages reduction math you model with DocketMath often looks the same: reduce recovery by the plaintiff’s fault portion.

1) Multi-vehicle crashes (front-end vs. rear-end disputes)

Common input patterns:

• Plaintiff driver is alleged to be partially responsible (e.g., tailgating or failing to maintain proper lookout).
• Defendant driver is alleged to have contributed (e.g., sudden stop without sufficient notice).

Typical modeling:

• Plaintiff: 10–50%
• Defendant: remainder

How to use the tool:

• Use your best-supported fault percentage based on the record you have (reports, photos, timelines).
• Then run a second version with a higher and lower percentage to understand settlement leverage.

2) Pedestrian / cyclist scenarios

Fact patterns often involve:

• Roadway control and visibility
• Speed and braking distance
• Compliance with pedestrian crossing signals
• Whether the pedestrian/cyclist acted with reasonable care

Model approach:

• If the plaintiff is alleged to have ignored signals, assume higher plaintiff fault for the estimate.
• If the defendant’s failure to yield is clear, assume lower plaintiff fault.

3) Slip-and-fall / premises-related situations

In these cases, fault can be attributed to:

• The property owner/manager (maintenance, warning signage)
• The person injured (where they walked, whether they noticed hazards)

Use DocketMath to compare:

• “Plaintiff fault: 25%” vs “Plaintiff fault: 45%”
• Then compare the resulting net recovery numbers.

4) Shared causation in workplace injury disputes

Even when a defendant contests responsibility, fault allocation can still be a central battleground where negligence theories are competing.

Model approach:

• Assign fault based on the evidence you can point to (policies, training, warnings, compliance, timing of corrective actions).
• Use multiple runs to estimate the range of outcomes.

Tips for accuracy

A damages allocator is only as accurate as its assumptions. These practices help you reduce avoidable modeling mistakes.

Use consistent definitions for “damages”

Decide what your “total damages” number includes before entering it:

• Medical bills and future medicals?
• Wage loss?
• Non-economic damages (pain and suffering) if your model includes them?
• Interest or costs?

Then keep the inputs consistent across “what-if” scenarios.

Use fault percentages that reflect the evidence you actually have

If your evidence supports “plaintiff was 30% at fault,” don’t default to “plaintiff was 50%” just because it feels balanced.

To improve credibility in your own analysis:

• Tie fault assumptions to a specific disputed issue (e.g., failure to yield, lookout, speed).
• Maintain a short note on why you selected each percentage.

Keep totals aligned (100% sanity check)

If the calculator requires both parties’ percentages, ensure they add to 100%. If it only needs the plaintiff’s share, still ensure you’re not double-counting fault in your reasoning.

Consider SOL triage before investing time

Because the default civil SOL in New Hampshire is 3 years under RSA 508:4, track dates early. A common workflow:

• Identify the date of injury / accrual trigger used in your case theory.
• Confirm whether a different claim-specific SOL might apply (not covered here).
• Use the 3-year RSA 508:4 baseline for initial scheduling.

Source for the general SOL baseline: https://www.thelaw.com/law/new-hampshire-statute-of-limitations-civil-actions.391/?utm_source=openai

Track “range thinking,” not single-point certainty

Comparative fault often lands in a band. Instead of one number, run:

• Low estimate (lower plaintiff fault)
• Middle estimate
• High estimate (higher plaintiff fault)

Then compare which side has the larger swing in expected recovery.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules — Complete guide
• Damages Allocation Guide for Alaska — Comparative Fault Rules — Complete guide
• Damages Allocation Guide for American Samoa — Comparative Fault Rules — Complete guide