How to run Settlement Allocator in DocketMath for Missouri

Step-by-step

Run this scenario in DocketMath using the Settlement Allocator calculator.

This practical walkthrough shows how to run Settlement Allocator in DocketMath for Missouri (US-MO), with an emphasis on jurisdiction-aware SOL (statute of limitations) inputs and how they can affect the allocator’s output.

Note: This is tool-use guidance, not legal advice about any specific claim.

1) Open the tool at the primary CTA

Start in DocketMath with this link:

• /tools/settlement-allocator

After the tool loads, you’ll typically see input fields for:

• jurisdiction selection (or a preselected jurisdiction)
• dates used for timing/SOL logic
• settlement and allocation-related fields (the exact labels can vary slightly by UI version)

2) Set jurisdiction to Missouri (US-MO)

Locate the jurisdiction selector and choose:

• Missouri — US-MO

Why it matters: DocketMath’s jurisdiction-aware rules depend on the correct state code to apply the right SOL baseline during the allocation workflow.

3) Enter the dates that drive the SOL baseline

To apply Missouri’s general SOL period, you’ll need the timing inputs the interface asks for—commonly something like:

• an event date (often “date of incident” / “alleged wrongful act date”)
• a filing date (often “date of filing” / “date of suit”)

Use dates that match your workflow and facts. At a minimum, keep these consistent:

• Event date: the date the alleged conduct occurred (or the closest fact-supported date you’re using)
• Filing date / date of suit: when the claim was brought (whichever date the tool label corresponds to)

If the UI requests additional timing fields, fill them according to your case worksheet and keep the timeline coherent (so you’re not accidentally entering a “demand date” where the tool expects a “filing date”).

4) Understand the Missouri SOL rule used by the tool

For Missouri, the calculator applies the general/default SOL period because no claim-type-specific sub-rule was identified for this setup.

Missouri general SOL period:

• 5 years under Mo. Rev. Stat. § 556.037

Source: https://law.justia.com/codes/missouri/title-xxxviii/chapter-556/section-556-037/

Key effect in practice (how output changes):

• If the event date → filing date timeline is within 5 years, the tool will treat the general SOL as satisfied for its timing logic.
• If it’s older than 5 years, the tool will treat the general SOL as potentially barred for its timing logic.

Important warning: the SOL impact is only as good as the dates you enter. Even a small date mismatch can change the result from “within SOL” to “outside SOL.”

5) Add settlement amount and allocation-related inputs

Next, move to the financial inputs. Settlement Allocator commonly needs some combination of:

• a total settlement amount
• allocation weights and/or category amounts
• sometimes damages components or other breakdown buckets, depending on the UI

Practical input tips:

• Use the format the UI expects (e.g., if a field clearly expects dollars, enter dollars as displayed—avoid ambiguity like “50” when it might mean $50,000).
• Avoid leaving required fields blank. If the tool flags a field as required, fill it with the best available value from your assumptions.
• Keep units consistent across all fields (don’t mix “thousands” and “full dollars” unless the tool explicitly indicates scaling).

6) Run the calculation

Once you’ve set:

• jurisdiction to Missouri — US-MO
• the relevant event and filing dates
• the settlement/allocation inputs

…click Calculate (or the equivalent button).

The tool should produce an output that reflects:

• the SOL baseline logic using 5 years (Mo. Rev. Stat. § 556.037, general/default)
• your settlement amount and allocation inputs

7) Review how outputs change when SOL flips

To understand how sensitive your results are to timing, do quick “what-if” checks.

Because the general SOL boundary is 5 years, you’re mainly watching for changes in:

• the tool’s SOL status indicator (e.g., “met” vs “not met,” or similar wording)
• any downstream allocation percentages/amounts that depend on that timing result

Controlled test approach:

• Keep the settlement amount and allocation inputs fixed.
• Change only the event date by a small amount (for example, ±30 days).
• Re-run the calculation and observe whether:

  • the SOL status changes, and/or
  • the allocation outputs change in response.

Near-threshold note (practical reality): If the timeline is close to the 5-year mark, output may shift due to the tool’s day-count conventions or rounding behavior. That’s expected for boundary cases.

8) Export or record results for your workflow

After running the calculation, record key outputs so you can explain and audit your assumptions later. Capture:

• the allocation results (amounts and/or percentages)
• the SOL-related status indicator the tool displays
• any relevant notes/messages in the output

If DocketMath provides an export option (PDF/CSV/screenshot), save it for your internal documentation.

9) Document the “general/default” assumption explicitly

Because this workflow uses the general/default SOL period (not a claim-type-specific rule), it helps to document that assumption in your worksheet.

For example, you can note:

• “Missouri general/default SOL baseline applied: 5 years under Mo. Rev. Stat. § 556.037 (general/default; no claim-type-specific sub-rule applied based on available rules).”

This makes it easier to keep results consistent across future runs and comparisons.

Common pitfalls

• Forgetting to set jurisdiction to US-MO

  • If another jurisdiction is selected, the tool may apply a different SOL baseline.
• Using the wrong “event date”

  • If the event date is accidentally later/earlier than the alleged conduct date, the SOL assessment can flip even if everything else is the same.
• Entering the filing date inconsistently

  • Some workflows use “demand date,” “petition date,” or “service date.” If the tool expects the filing date, use the filing date consistently.
• Assuming the tool applies a claim-type-specific SOL

  • For this Missouri setup, the tool uses the general/default SOL period:

    • 5 years under Mo. Rev. Stat. § 556.037
• Near-threshold date rounding

  • When you’re close to 5 years, small differences can matter. If your results change unexpectedly, verify both dates and consider rerunning with a slightly adjusted date to confirm sensitivity.
• Misreading output logic

  • Don’t focus only on the settlement allocation dollars. Check the SOL status indicator because that often drives the allocation changes.

Try it

1. Open /tools/settlement-allocator
2. Select Missouri — US-MO
3. Enter:

   • an event date
   • a filing date
   • the settlement amount and any allocation inputs the UI requires
4. Click Calculate
5. Review:

   • the SOL status based on 5 years (Mo. Rev. Stat. § 556.037)
   • the resulting allocation outputs

If you want to validate sensitivity:

• Keep settlement and allocation inputs fixed.
• Adjust only the event date by 10–30 days.
• Observe whether the SOL outcome stays stable or flips around the 5-year boundary.

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado