Cost of Delay Modeler Guide for Louisiana

7 min read

Published March 22, 2026 • By DocketMath Team

What this calculator does

DocketMath’s Cost of Delay Modeler helps you estimate how a change in timeline can affect the total cost of waiting—by converting elapsed time into a structured “cost of delay” model.

In Louisiana, the calculator is especially useful for projects where timing interacts with applicable limitation periods—for example, when you’re comparing:

  • a claim that might be filed earlier vs. later, and
  • the cost impact of a delay measured against a statutory window.

This guide is not legal advice. Instead, it’s a practical walkthrough for using DocketMath to model delay costs based on Louisiana time limits you enter.

How Louisiana time limits show up in the model

The calculator can be configured using limitation period lengths tied to specific statutes or procedural rules. For this Louisiana guide, the following Limitation Period (SOL Period) values are represented:

Source / RulePeriodNotes / Exception label (as provided)
La. Rev. Stat. Ann. § 9:2800.91 yearexception O2
La. Code Crim. Proc. art. 5711 yearexception P2
La. Code Crim. Proc. arts. 571–5723 yearsexception O2
La. Code Crim. Proc. art. 5720.5 yearsexception V1
Articles 571 and 5721 yearexception P2
La. Rev. Stat. § 9:5605(E)1 yearexception M5
La. Civ. Code art. 3493.112 yearsexception M6

For day-to-day use, the most important concept is this: the longer the potentially applicable limitation window you enter, the more time the model may treat as “available,” which can reduce or increase the computed delay cost depending on how you define your delay and cost-rate assumptions.

Pitfall: A limitation period is not a guarantee that a filing is timely. Accrual rules, tolling, and other procedural facts can change when the clock starts and how it runs. DocketMath can model delay costs, but it can’t resolve those fact-dependent issues.

When to use it

Use DocketMath’s cost-of-delay modeler when you want to translate “we’re late” into an estimate you can compare across options—especially when Louisiana timing rules matter for planning.

Good use cases include:

  • Project planning: You’re scheduling internal tasks and want a numeric comparison of “accelerate by 60 days” vs. “proceed as planned.”
  • Decision support: You’re preparing documentation that requires a time-cost narrative (e.g., “If we wait until month X, the cost increases by $Y”).
  • Strategy comparisons: You’re comparing two potential timelines against a statutory window (e.g., a 1-year vs. 2-year period).
  • Budgeting: You want to quantify cost pressure from extended investigation or preparation time.

Where the calculator fits with Louisiana statutes

You can model delay against a limitation period length associated with a particular claim type or procedural posture. Common Louisiana anchors to consider when configuring the model include:

  • La. Rev. Stat. Ann. § 9:2800.9 (1 year)
  • La. Code Crim. Proc. arts. 571–572 (3 years), and the subcomponents
    • art. 571 (1 year)
    • art. 572 (0.5 years)
  • La. Rev. Stat. § 9:5605(E) (1 year)
  • **La. Civ. Code art. 3493.11 (2 years)

The calculator is most effective when you treat it as a scenario tool: enter assumptions, compare results, then refine inputs.

Warning: Do not treat statute periods as interchangeable. The cited time frames above correspond to different Louisiana provisions and can apply in different circumstances. Your inputs should match the claim type and procedural posture you’re modeling.

Step-by-step example

Below is a concrete walkthrough using DocketMath to compare two filing timelines in Louisiana. This example focuses on a 1-year limitation period entry aligned with La. Rev. Stat. Ann. § 9:2800.9 (exception O2).

We’ll model the cost of delay as a cost accruing per unit time, then calculate the total cost difference between:

  • Scenario A: file at the 9-month mark
  • Scenario B: file at the 12-month mark (a 3-month delay)

Step 1: Start the tool

Open the modeler here: **/tools/cost-of-delay

Step 2: Choose the limitation period input

In the configuration area, set:

  • Jurisdiction: Louisiana (US-LA)
  • Statute / Rule: La. Rev. Stat. Ann. § 9:2800.9
  • Limitation period (SOL Period): 1 year
  • Exception label: O2 (as shown in the guide data set)

Step 3: Enter your timeline assumptions

Now set timing facts for each scenario:

  • Scenario A planned filing date relative to start: 9 months
  • Scenario B planned filing date relative to start: 12 months
  • Delay difference: 3 months

Even if your dates are calendar dates in practice, DocketMath can work from a “months from start” representation as long as you keep the unit consistent.

Step 4: Enter a cost rate (the “cost of waiting”)

To model delay costs, you need a time-cost rate. For illustration:

  • Cost rate: $1,000 per month of delay
  • (You can think of this as a blended estimate: staffing, opportunity cost, prevention/mitigation expenses, or other quantified costs.)

Step 5: Run the comparison

Compute:

  • Scenario A delay: 9 months × $1,000 = $9,000
  • Scenario B delay: 12 months × $1,000 = $12,000
  • Cost difference: $12,000 − $9,000 = $3,000

Step 6: Interpret the output

The model output should communicate at least two layers:

  1. Total modeled cost per scenario
  2. Incremental cost of the added delay (Scenario B minus Scenario A)

That incremental value—$3,000 here—is what makes the model decision-useful. If you can reduce delay by 3 months, the model suggests you may reduce modeled cost by roughly $3,000 under your assumptions.

Note: If you change only the limitation period input from 1 year to 2 years (e.g., La. Civ. Code art. 3493.11), the scenario’s “within-window” framing changes. In many workflows, this affects whether the delay is treated as urgent (near expiration) or manageable (well within the window). DocketMath’s usefulness increases when your cost rate and “delay start” are clearly defined.

Common scenarios

Louisiana limitation periods show up in practice in a few repeating “planning patterns.” These are not legal conclusions—think of them as ways to structure your modeling inputs.

1) Near-expiration planning (1-year window)

If you are modeling a situation tied to La. Rev. Stat. Ann. § 9:2800.9 (1 year) (exception O2), your scenario comparisons often focus on:

  • “Filed at 11 months” vs. “Filed at 13 months”
  • a cost rate that increases as the deadline approaches (optional: you can approximate a step-up cost rate in your own assumptions)

Checklist for this scenario

2) Multiple sub-rules inside a procedural set (Criminal procedure timing)

Louisiana’s procedural rules can include multiple time frames. For example, the dataset includes:

  • La. Code Crim. Proc. arts. 571–572 (3 years) (exception O2)
  • La. Code Crim. Proc. art. 571 (1 year) (exception P2)
  • La. Code Crim. Proc. art. 572 (0.5 years) (exception V1)
  • Articles 571 and 572 (1 year) (exception P2)

When modeling this type of situation, a practical workflow is to run separate model runs for each relevant period rather than trying to compress everything into one number.

Common modeling approach

3) Different limitation periods across claim types (1-year vs. 2-year)

If your matter could involve different kinds of claims or procedural theories, you may compare:

  • 1-year: La. Rev. Stat. § 9:5605(E) (exception M5)
  • 2-year: La. Civ. Code art. 3493.11 (exception M6)

This scenario is great for decision-makers because it quantifies tradeoffs in scheduling. If one path has a 2-year model window and another has a 1-year window, your modeled cost impact may look very different—even with the same delay.

Tips for accuracy

To get outputs you can actually use, tighten the inputs. DocketMath’s value increases when your modeled assumptions are internally consistent.

Use consistent time units

Pick one unit (days, months, or years) and stick to it across:

  • limitation period
  • delay

Sources and references

Start with the primary authority for Louisiana and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

Related reading