How to calculate pain and suffering damages in Mississippi

Direct answer

In Mississippi, pain and suffering damages in civil personal-injury cases are not calculated from a fixed statutory “rate” (for example, a specific dollar amount per day). Instead, pain and suffering is treated as a non-economic damages component that is assigned a dollar value by the factfinder and then adjusted through the case’s jurisdiction-aware allocation workflow.

For your DocketMath workflow, that means you should:

1. Model pain and suffering as part of non-economic damages (often alongside other non-economic items), and
2. Apply Mississippi’s contributory-negligence framework using Miss. Code Ann. § 11-7-15 during the damages allocation step.

Jurisdiction note: Mississippi’s supplied statute is a general/default negligence framework for the covered actions in the materials you provided. No claim-type-specific pain-and-suffering sub-rule was identified in the provided jurisdiction data, so the workflow below treats § 11-7-15 as the governing default negligence framework unless your record shows otherwise.

What you need to know

1) Mississippi doesn’t provide a pain-and-suffering schedule in the provided materials

Many jurisdictions publish calculation schedules or multipliers. In the materials you provided for Mississippi, § 11-7-15 is a negligence/contributory-negligence rule that addresses whether contributory negligence “shall not bar” recovery in covered actions—it does not provide a formula like “pain and suffering = $X/day.”

So in DocketMath, your pain-and-suffering “calculation” is best understood as:

• choosing a defensible valuation basis for non-economic harms (often grounded in duration, severity, and functional impact), and
• then allocating a recoverable amount under the applicable negligence framework.

2) Use DocketMath’s “damages allocation” workflow

The correct DocketMath tool name is damages-allocation. This tool is designed to handle damages inputs and then apply jurisdiction-aware allocation effects, rather than relying on a simplistic pain-and-suffering rate.

Primary CTA: /tools/damages-allocation

3) Your inputs will change the output

Pain and suffering is highly sensitive to how you translate the record into non-economic value. Changes in any of the following typically change the result:

• length of symptom period (weeks/months, or ongoing)
• whether treatment escalated (PT vs. surgery)
• functional limitations (sleep, mobility, work/ADLs)
• credibility and consistency of symptom testimony (as reflected in your inputs)

Step-by-step

Use this workflow in DocketMath → /tools/damages-allocation to estimate pain and suffering damages in Mississippi with negligence-aware allocation.

Step 1: Confirm you’re in a covered action type

Before entering numbers, align the case category your DocketMath model is simulating with the types of actions addressed in Miss. Code Ann. § 11-7-15:

• personal injury actions, and
• actions where such injuries result in death, and
• actions for injury to property.

Pain and suffering is typically relevant in the personal injury (and sometimes death-related) contexts—not in pure property-only models. If your model is property-only, keep pain-and-suffering out of scope.

Step 2: Separate economic vs. non-economic damages

Create or confirm two broad buckets in DocketMath:

• Economic damages (examples: medical bills, wage loss, out-of-pocket expenses)
• Non-economic damages, including pain and suffering

In your non-economic section, keep pain and suffering as its own line item if DocketMath supports it, so you don’t accidentally double-count with other non-economic entries.

Step 3: Enter pain-and-suffering facts as duration + severity drivers

Mississippi (in the materials provided) does not supply a statutory rate, so your model needs a consistent, record-based valuation basis. Capture these record drivers in your DocketMath inputs:

• symptom start date
• symptom end date (or “ongoing” with a reasonable estimated end window you input)
• treatment progression (PT, imaging, injections, surgery, ER visits)
• functional impact (sleep disruption, mobility limits, inability to work/perform activities)
• objective support where available (e.g., imaging findings or measurable functional restrictions)

These inputs don’t automatically “equal dollars” via a statute—but they drive the non-economic value you assign, which the allocation then uses.

Step 4: Apply Mississippi contributory-negligence effects under § 11-7-15

Next, ensure your negligence/contributory negligence settings match the statutory framework.

The provided statute text indicates contributory negligence “shall not bar” recovery in the covered actions (based on the excerpt you provided). That is why your DocketMath negligence logic should not treat contributory negligence as an automatic “zero recovery” switch.

In practical modeling terms:

• Don’t build a model that returns $0 whenever the plaintiff is at fault.
• Build an allocation model that reflects that the claim may still proceed and that negligence affects the allocation consistent with the statutory direction.

Gentle reminder: this is an allocation workflow explanation, not legal advice. Your case outcome depends on the full record and how the statute is applied in context.

Step 5: Allocate to the correct claimant(s) (if applicable)

If your model involves more than one injured party or claimant, map:

• pain and suffering to the correct claimant, and
• negligence inputs to the correct level in your case structure (claimant-specific vs. casewide), consistent with how you organize the record in DocketMath.

Step 6: Run scenarios to test sensitivity (recommended)

Because non-economic damages vary widely, run multiple scenarios in damages-allocation rather than one point estimate. A practical set:

• Scenario A (low): shorter duration, conservative treatment
• Scenario B (mid): moderate duration and mixed treatment
• Scenario C (high): longer duration, escalation to surgery/major treatment, substantial functional limits

Compare how the pain-and-suffering component and the final recoverable amount change across scenarios.

Key statutes and citations

• Miss. Code Ann. § 11-7-15
  Governs contributory negligence treatment in actions for personal injuries (including where such injuries have resulted in death) and actions for injury to property, using the concept that contributory negligence “shall not bar” recovery in the covered circumstances (based on the statute text provided).
  Source: https://law.justia.com/codes/mississippi/title-11/chapter-7/section-11-7-15/

• Default vs. claim-type-specific rule (per your materials)
  No claim-type-specific pain-and-suffering sub-rule was identified in the supplied jurisdiction data. Treat § 11-7-15 as the general/default negligence framework for this workflow unless your record indicates otherwise.

Common pitfalls

• Using a per-day pain-and-suffering rate If your spreadsheet or model assumes “$ per day” for pain and suffering, it may conflict with the reality that § 11-7-15 (as provided) is a negligence framework, not a pain-and-suffering schedule.

• Treating negligence as an automatic bar The supplied statutory direction indicates contributory negligence “shall not bar” the claim in covered actions. A DocketMath configuration that forces zero recovery for plaintiff fault would likely be inconsistent with the provided statute text.

• Double-counting non-economic items Keep pain and suffering in non-economic and avoid inadvertently counting the same impact twice (for example, once in pain and suffering and again in another non-economic category).

• Missing duration inputs Non-economic value is sensitive to duration. If you only input “severity” without start/end dates (or an ongoing window), outputs become harder to defend and often less accurate.

Run the numbers

To use DocketMath effectively, convert your record into the key damages-allocation math drivers. The exact fields depend on how /tools/damages-allocation is configured, but this checklist is a practical guide.

Input checklist (what to enter)

• Pain and suffering (non-economic) basis

  • symptom start date
  • symptom end date (or “ongoing” with an estimated end window you input)
  • treatment escalation (PT, imaging, injections, surgery)
  • functional impact (sleep, mobility, work/ADL restrictions)

• Economic damages total (for context and total allocation)

• Negligence/contributory negligence inputs

  • set them consistent with your record and the statutory framework under Miss. Code Ann. § 11-7-15

• Claimant mapping

  • confirm which injured party each damages component belongs to (if multiple claimants)

What to expect from the output

A typical damages-allocation run should produce results showing:

• a pain-and-suffering dollar figure (or a range, depending on how you model valuation inputs)
• an allocated/recoverable amount reflecting negligence handling under § 11-7-15
• scenario-to-scenario comparisons if you run multiple severity assumptions

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