Worked example: Damages Allocation in Missouri

Example inputs

Run this scenario in DocketMath using the Damages Allocation calculator.

Below is a worked example of damages allocation in Missouri (US-MO) using DocketMath’s damages-allocation calculator (tool link: /tools/damages-allocation). This example focuses on how a calculator can allocate time-based components (e.g., recurring losses) and then align the included period to Missouri’s general statute of limitations rules.

Scenario (fictional, for demonstration)

A plaintiff claims damages for:

• Total compensatory damages incurred over a multi-year span
• A recurring category of damages that accrues each month
• A one-time category that accrues on a specific date

Assume:

• Incident date (start of loss): January 10, 2019
• Filing date: March 1, 2024
• Recurring damages: $2,000 per month
• One-time damages: $15,000 on June 20, 2022
• Total claimed compensatory damages input: $0 (we’ll compute allocation from components instead of relying on an all-in number)

Missouri timing rule used by this example (general/default)

Missouri’s statute of limitations timing basis used in this example is the general/default 5-year SOL period under:

• Mo. Rev. Stat. § 556.037 (general/default rule; 5 years)
  Source: https://law.justia.com/codes/missouri/title-xxxviii/chapter-556/section-556-037/

Important: No claim-type-specific sub-rule was found in the provided jurisdiction data. So this example clearly uses the general/default 5-year period and does not assume a shorter or alternate SOL applies.

DocketMath input fields (what you would enter)

Use DocketMath’s /tools/damages-allocation calculator with inputs like these (labels may vary slightly by UI):

• Jurisdiction: US-MO
• General SOL years: 5 (from Missouri general/default rule used here)
• Incident/loss start date: 2019-01-10
• Filing date: 2024-03-01
• Recurring damages monthly amount: $2,000
• Recurring accrual starts: 2019-01-10
• Recurring accrual ends: set to the calculator’s logic for the included SOL window (commonly “through the last included month”)
• One-time damages amount: $15,000
• One-time accrual date: 2022-06-20
• One-time damages accrual included only if within SOL window: Yes (default behavior in this example)

If the calculator includes settings such as “accrues on the first/last day of the month” or “include partial months,” choose the option that matches your data assumptions. For this example, assume monthly recurring damages are allocated by whole months whose accrual falls within the SOL lookback window.

Example run

Run the Damages Allocation calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Compute the SOL lookback window (5 years)

With a filing date of March 1, 2024, the 5-year lookback window (based on the general/default SOL period) is:

• SOL start (earliest included date): March 1, 2019
• SOL end (latest included date): March 1, 2024 (i.e., tied to the filing date boundary used by the calculator’s logic)

Because the incident date is January 10, 2019, the period from Jan 10, 2019 to Feb 28, 2019 is outside the included SOL window for this example.

Step 2: Allocate recurring monthly damages within the included window

• Monthly amount: $2,000
• First included month (for simplicity): March 2019
• Last included month: February 2024

Count of included months:

• March 2019 through February 2024 = 48 months

Recurring damages included in allocation:

• 48 months × $2,000 = $96,000

Recurring damages excluded (edge outside SOL):

• Two months (Jan–Feb 2019) × $2,000 = $4,000 excluded

Step 3: Allocate one-time damages if the accrual date is within the SOL window

• One-time accrual date: June 20, 2022
• This date is within March 1, 2019 → March 1, 2024, so it is included.

One-time damages included:

• $15,000

One-time damages excluded:

• $0

Step 4: Produce the damages allocation output

A typical allocation output from DocketMath for this setup would be summarized like:

So for this fictional example, the calculator’s allocated total is:

• Allocated total: $111,000
• Excluded amount (in this simplified recurring-only exclusion): $4,000

Step 5: Tie the output to Mo. Rev. Stat. § 556.037

The inclusion/exclusion in this example is driven by the general 5-year SOL period used here, tied to:

• Mo. Rev. Stat. § 556.037
  https://law.justia.com/codes/missouri/title-xxxviii/chapter-556/section-556-037/

Sensitivity check

A good damages allocation run should be stress-tested against assumptions that can move outcomes.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

1) Filing date shift (how timing changes included months)

Keep everything the same except adjust the filing date. Because the example uses a monthly recurring model, the number of included months can move by roughly a month around the edges.

In this example, that’s about $2,000 per month of recurring damages (the monthly amount).

2) Recurring damages accrual convention

If the calculator has a switch like “include partial month” vs “full-month only,” results can change around the SOL start boundary.

Key checklist (verify against your facts/data):

• Does recurring accrual start on the incident date or the first day of the month?
• Does the calculator include the filing month, or stop the month before?
• Is recurring measured as calendar months (as modeled here) or rolling periods?

3) One-time damages accrual date (binary inclusion)

One-time items are often “in or out”:

• If the one-time accrual date is inside the SOL window → included
• If it is outside → excluded

In this example, June 20, 2022 is inside the 5-year window, so it’s included. If instead the one-time accrual were:

• February 20, 2019 → likely excluded
• April 10, 2019 → likely included

4) General/default SOL rule confirmation

Because no claim-type-specific sub-rule was found in the provided jurisdiction data, the example assumes:

• Use Missouri general/default 5-year SOL
• If you later identify a claim-type-specific timing rule applies, rerun the calculator with the correct SOL period and adjust accrual logic as needed.

Gentle disclaimer: This is an educational, worked example using simplified fictional inputs. It’s not legal advice, and actual results can differ based on claim type, accrual facts, and how a court applies SOL rules.

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