How to calculate pain and suffering damages in Missouri

Direct answer

In Missouri, there isn’t a single fixed formula (for example, a set “per day” amount) for pain and suffering damages. Instead, the practical approach is to allocate non-economic damages based on the evidence—typically injury severity, duration, treatment, and functional impact—using DocketMath’s damages-allocation calculator.

For timing context, the jurisdiction data provided for this guide indicates the applicable time rule you’ll generally rely on here is the 5-year general default statute of limitations under Mo. Rev. Stat. § 556.037 (source: https://law.justia.com/codes/missouri/title-xxxviii/chapter-556/section-556-037/). The brief also notes no claim-type-specific sub-rule was found, so this 5-year general period is the default referenced in this content.

What you need to know

1) Pain and suffering is “non-economic,” not a line-item bill

Pain and suffering generally represents non-economic harm. That means you usually can’t justify it with receipts the way you can for medical bills or lost wages. Instead, you support it with testimony and records that show:

• Severity of injuries (what objective findings and observed limitations show)
• Duration (how long symptoms persisted)
• Treatment intensity/length (for example, therapy visits, follow-up care, procedures)
• Functional effects (sleep disruption, mobility limits, inability to perform daily activities or work tasks)
• Consistency over time (whether symptom descriptions and limitations remained consistent with records)

2) Separate economic vs. non-economic before you total anything

To keep your DocketMath run understandable and defensible, distinguish:

• Economic damages: things with clearer measurement (medical expenses, lost wages)
• Non-economic damages: things that require narrative support and evidence (pain and suffering, emotional distress, loss of enjoyment—depending on how you break it out)

3) Use Missouri’s provided default time rule—don’t mix it into the valuation

This guide provides a default time rule: 5 years under Mo. Rev. Stat. § 556.037. That statute is about when a claim must be filed, not how to compute the value of pain and suffering.

So:

• Use DocketMath to allocate damages (valuation workflow).
• Use Mo. Rev. Stat. § 556.037 to consider whether the claim is timely (timing workflow).

Because your brief says no claim-type-specific sub-rule was found, treat § 556.037’s 5-year period as the default for the jurisdiction context used here.

Step-by-step

You can use DocketMath’s damages-allocation tool to estimate and allocate pain-and-suffering damages in a structured way.

1) Open the allocation tool

• Start here: **damages-allocation

2) Define your “buckets” (categories)

Before entering numbers, decide how you want to structure outputs. A practical setup is:

• Medical expenses (economic)
• Lost wages (economic, if applicable)
• Pain and suffering (non-economic)
• (Optional) other non-economic items if your workflow separates them

The key is conceptual clarity: pain-and-suffering should be treated as non-economic, not duplicated inside economic categories.

3) Enter evidence-linked inputs for the pain-and-suffering allocation

Instead of trying to price pain using a made-up “rate,” use inputs that track your proof. Focus on:

• Severity tier (minor / moderate / severe, or whatever levels your worksheet supports)
• Symptom duration (how long the symptoms and limitations lasted)
• Treatment duration/intensity (rehab timeline, therapy frequency, follow-up care)
• Functional impairment window (when and how daily activities/work were affected)

4) Allocate across the timeline (not a single moment)

A common error is treating the harm as one instant. In the DocketMath allocation workflow, aim to reflect the timeline:

• Was the condition worse initially and then improved?
• Were symptoms persistent?
• Did limitations extend beyond treatment?

Your allocation should line up with what your record suggests (even if you have to estimate with notes).

5) Run multiple scenarios (conservative / baseline / high)

To see what actually drives the pain-and-suffering total, build at least 2–3 scenarios:

• Conservative: shorter duration and/or less persistent limitations
• Baseline: matches your best reading of records
• High: longer impairment window and/or higher severity tier support

6) Observe sensitivity—what changes the output most?

When you compare scenarios, look at the direction and magnitude of change. Pain-and-suffering totals often shift most with:

• Duration of impairment
• Severity tier
• Whether functional impact extends over time

Economic items may behave differently depending on what has documentation (for example, billed medical amounts).

7) Total damages and keep the breakdown usable

After running the scenarios, capture:

• Non-economic subtotal (pain and suffering)
• Economic subtotal
• Total damages (economic + non-economic)

Use the breakdown as a worksheet you can later explain or revise.

8) Document your assumptions (so your numbers aren’t “mystical”)

DocketMath outputs are only as credible as your inputs. Keep a short log:

• What record supports the severity tier?
• What record supports duration and functional impairment windows?
• What parts are estimates vs. directly supported facts?

Key statutes and citations

Missouri default statute of limitations (timing context): 5 years

How it affects your workflow (without changing the damages math)

A statute of limitations issue is about whether a claim can proceed, not how pain-and-suffering is valued. Still, timing can indirectly affect what evidence is available and how far back records and documentation go.

Because the brief’s jurisdiction data did not identify a claim-type-specific sub-rule, this guide uses § 556.037’s 5-year general period as the default rule.

Common pitfalls

• Using a “per-day” pain rate

  • Pain and suffering is not typically handled like a fixed Missouri schedule. DocketMath is better for evidence-linked allocation.

• Leaving out functional impact

  • Describing pain without tying it to limitations (sleep, mobility, daily tasks, work restrictions) makes the non-economic allocation harder to support.

• Double-counting the same harm

  • For example, treating a disruption as both part of a medical/treatment driver and also as pain-and-suffering, without separating categories. Keep buckets distinct.

• Running only one scenario

  • If you don’t test conservative vs. high assumptions, you won’t understand what drives the pain-and-suffering number.

• Confusing statute of limitations with damages valuation

  • Mo. Rev. Stat. § 556.037 controls timing, not the calculation method. Don’t assume it changes pain-and-suffering value.

• Ignoring the “default rule” instruction from the brief

  • Don’t assume a different period unless additional research identifies a claim-type-specific rule. Here, the brief says none was found, so use the 5-year default.

Run the numbers

Here’s a practical way to prepare your inputs for DocketMath damages-allocation when your goal is Missouri pain-and-suffering allocation.

1) Pick your scenario inputs (worksheet)

Before entering anything into damages-allocation, decide:

• Severity tier: minor / moderate / severe
• Symptom duration: weeks vs. months (or however you model it)
• Treatment timeline: approximate rehab/therapy duration and intensity
• Functional impairment period: when limits affected daily life or work
• Consistency notes: improvements or worsening that your records support
• Scenario plan: conservative / baseline / high

2) Run scenarios and compare outputs

After each run, compare:

• Pain & suffering subtotal (non-economic)
• Total damages (economic + non-economic)
• Delta between scenarios (how much changes when you alter duration/severity)

3) Reconcile outputs with the evidence timeline

If your “high” scenario assumes long-lasting limitations, but the medical record shows early resolution with minimal follow-up, reduce the high scenario or revise inputs so your assumptions match your proof timeline.

Reminder: The point of running DocketMath scenarios is to structure and test assumptions, not to “predict” a verdict with certainty.

Related reading

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