Cost of Delay Modeler Guide for Missouri

What this calculator does

DocketMath’s Cost of Delay Modeler helps you estimate the economic impact of how long a legal matter takes to resolve in Missouri (US-MO). The model connects two things:

1. A timeline (how many years/months you expect the case to take)
2. A cost rate (what the delay costs per unit of time—lost profit, added carrying costs, interest on debt, staffing burn, etc.)

From those inputs, the calculator produces a total estimated cost of delay over the selected period.

How the calculator ties to Missouri timing rules (SOL)

When you’re assessing whether a claim might be timely, Missouri’s statute of limitations (SOL) period can serve as a key planning boundary. For many civil-related time-bar questions, Missouri uses:

• 5-year SOL period under Mo. Rev. Stat. § 556.037
• Source: https://law.justia.com/codes/missouri/title-xxxviii/chapter-556/section-556-037/

In other words, the model can be used to:

• Compare shorter vs. longer resolution timeframes within a planning horizon
• Stress-test business decisions against a 5-year default window

Built-in SOL timing boundary (for scenario framing)

This guide assumes Missouri’s 5-year SOL period:

• Mo. Rev. Stat. § 556.037 — 5 years (including an exception noted in the statute materials as exception O2)

Because SOL can be affected by specific facts (events, tolling doctrines, and exceptions), treat the 5-year figure as a modeling reference point, not a universal rule for every claim type.

When to use it

Use the DocketMath Cost of Delay Modeler when you need an actionable estimate of “what delay costs” and want to compare options numerically.

Common ways it’s helpful in Missouri case planning:

• Settlement timing comparisons

  • Example: Estimate cost if resolution happens in 12 months vs 30 months
• Business-case evaluation

  • Decide whether to allocate resources now or later based on the economic tradeoffs
• Budgeting and internal approvals

  • Create a quantified narrative for stakeholders: “Delaying by X months adds approximately $Y in costs”
• Scenario planning across a SOL horizon

  • Frame your planning around Missouri’s 5-year SOL period under Mo. Rev. Stat. § 556.037

If you’re using it for SOL-related framing, the calculator is best at showing:

• How quickly costs accumulate
• Whether a “delay” scenario is economically dominant
• How sensitive results are to your cost-per-time assumptions

Step-by-step example

Below is a practical, Missouri-focused walkthrough using the DocketMath tool.

Start by opening the calculator here: /tools/cost-of-delay.

Example scenario

Imagine you’re modeling the economic cost of delayed resolution for a claim you expect to take longer than expected. You decide to compare three resolution timelines.

Assume these inputs:

• Start date (for modeling): Today (we’ll model durations instead of exact dates)
• Time unit: Months (you can use years depending on your assumptions)
• Estimated cost rate: $2,000 per month

  • Think of this as carrying costs, legal overhead, contractor standby, or other delay-driven expenses
• Number of scenarios: 3 timelines

Scenario A: 12-month resolution

• Duration: 12 months
• Cost rate: $2,000/month
• Estimated cost: 12 × $2,000 = $24,000

Scenario B: 30-month resolution

• Duration: 30 months
• Cost rate: $2,000/month
• Estimated cost: 30 × $2,000 = $60,000

Scenario C: 60-month resolution (ties to Missouri SOL framing)

• Duration: 60 months (5 years)
• Cost rate: $2,000/month
• Estimated cost: 60 × $2,000 = $120,000

Results table

Add a “ramping cost” (when delay worsens)

Many real matters don’t cost linearly. If your costs accelerate after a certain point (example: you add new staffing or business operations stall), model two phases:

• Phase 1: First 12 months at $1,500/mo
• Phase 2: Months 13–36 at $2,500/mo

For a 36-month timeline:

• Phase 1 cost: 12 × $1,500 = $18,000
• Phase 2 cost: 24 × $2,500 = $60,000
• Total: $78,000

This is where the model becomes a planning tool rather than a simple multiplication exercise.

Common scenarios

Below are scenario patterns where cost-of-delay modeling is especially useful. Each one highlights what inputs you should consider and how the output changes.

1) Cash-flow strain from unpaid amounts

Typical inputs

• Monthly carrying cost rate (e.g., financing interest)
• Expected delay length

Output behavior

• Longer delays increase costs roughly proportionally—unless you model step-ups (e.g., interest changes after 6 months).

2) Operational disruption and staffing burn

Typical inputs

• Base legal/operations overhead per month
• Additional staffing cost after a threshold (e.g., after 9 months)

Output behavior

• Step models produce a noticeably higher estimate than linear models.

3) Revenue opportunity cost

Typical inputs

• Estimated margin per month you expect the dispute to affect
• Probability weighting (if your model supports it)

Output behavior

• If your “cost rate” is derived from margin, your results scale quickly—small changes in margin assumptions create large output differences over 36–60 months.

4) Planning around Missouri’s 5-year SOL horizon

When your analysis needs a “default” planning boundary, you can use the 5-year SOL period referenced in Mo. Rev. Stat. § 556.037 as a scenario endpoint.

• Default SOL period: 5 years
• Cite: Mo. Rev. Stat. § 556.037 (5-year SOL; exception referenced as O2 in statute materials)

Output behavior

• The 60-month scenario acts like a “cap” for comparison—so you can ask: “What happens economically if this runs its full 5-year planning horizon?”

Tips for accuracy

You’ll get the most reliable output from DocketMath when you treat inputs like underwriting assumptions: explicit, consistent, and scenario-specific.

1) Choose the right time unit (months vs. years)

• If your costs are tracked monthly (payroll, rent, contractors), use months.
• If your costs are naturally annual (certain overhead allocations), use years.

Consistency rule: Don’t mix units without converting—rounding can distort results over 48–60 months.

2) Model step-changes, not just averages

A strong accuracy improvement comes from separating:

• early stage costs (often lower)
• later stage costs (often higher)

Common step thresholds:

• 6 months
• 12 months
• 18–24 months

3) Validate the cost rate with a quick sanity check

Before relying on outputs, ask:

• Does $X/month reflect a real cost line item?
• Is the rate too low because you’re ignoring overhead?
• Are you double-counting the same cost in multiple categories?

A fast check:

• Multiply your monthly rate by 12 and see whether the annualized cost makes sense to your organization’s budget.

4) Use scenario ranges, not a single-point answer

Instead of one estimate, run at least three:

• Conservative (lower cost rate or shorter duration)
• Base case
• Stress case (higher rate or longer duration)

Example range approach:

• $1,500/mo vs. $2,000/mo vs. $2,800/mo
• 18 months vs. 30 months vs. 60 months

5) Tie outputs to the Missouri SOL reference carefully

If you include the SOL timeline boundary as a scenario endpoint:

• Use 60 months as the planning horizon reference tied to Mo. Rev. Stat. § 556.037
• Keep the result framed as economic planning, not a legal timeliness determination

For your citation log:

• Mo. Rev. Stat. § 556.037 — 5 years
• Reference materials indicate an exception (O2) in the statute description: https://law.justia.com/codes/missouri/title-xxxviii/chapter-556/section-556-037/

6) Document assumptions for stakeholders

When you export results (or capture them in a spreadsheet), keep a short assumptions list:

• Cost rate used: $____ per month
• Duration scenarios: ____ months / ____ months / ____ months
• Whether costs ramp after ____ months: yes/no
• Any exclusions: e.g., “no one-time litigation milestones included”

This makes the output defensible internally.

Related reading

• Cost of Delay Modeler Guide for Alabama
• Cost of Delay Modeler Guide for Arizona
• Cost of Delay Modeler Guide for California