Cost of Delay Modeler Guide for Indiana

What this calculator does

DocketMath’s Cost of Delay Modeler helps you estimate the economic impact of time in an Indiana criminal case by modeling a “cost of delay” using a fixed, statute-based baseline for the relevant speedy-trial period.

For Indiana, this model is built around the 5-year statutory period in:

• Indiana Code § 35-41-4-2 — 5 years (with exception V3)

Source: https://law.justia.com/codes/indiana/2022/title-35/article-41/chapter-4/section-35-41-4-2/

How the modeler thinks about delay (high-level)

Most people use a cost-of-delay estimate to quantify questions like:

• “If the case runs 18 months longer than expected, what does that imply financially?”
• “How sensitive is the result to the assumed monthly cost of carrying the case?”

In DocketMath, you can treat the statute-based period as a reference window, then apply your inputs to calculate an estimated cost for the portion of time you mark as “delay” beyond that reference.

Inputs you control

You’ll typically specify (or select) items such as:

• Monthly cost of delay (or another time-based unit)
• Time measure for the period you want to model (e.g., months)
• Optional multipliers/adjustments (depending on how you configure your scenario)

Output you get

The tool produces an estimated cost number based on your assumptions—useful for comparing scenarios side-by-side, not for predicting outcomes.

When to use it

Use DocketMath’s Cost of Delay Modeler for Indiana when your workflow requires turning “time” into an actionable number—especially for decision-making, documentation, or internal planning.

Ideal use cases

• Scenario comparison

  • Example: Compare cost if the case ends in 48 months vs. 62 months.
• Settlement or negotiation posture

  • Quantify the “wear-and-tear” over time for parties who care about costs.
• Business-impact framing

  • Translate timeline risk into an estimated dollar amount (lost opportunity, staffing, compliance burden, etc.).
• Case management budgeting

  • Model how long continued uncertainty could strain resources.

Indiana-specific trigger: 5-year statutory period reference

Because the modeler’s baseline incorporates Indiana Code § 35-41-4-2 (5 years, exception V3), it’s especially helpful if you’re aligning your timeline analysis to that statutory framework.

You’ll want to be consistent about how you define:

• the period you consider as “delay,” and
• where your “clock start/end” aligns to your internal timeline (since the tool cannot verify every docket event).

Step-by-step example

Below is a practical, Indiana-focused walkthrough using the modeler to convert months of delay into dollars. Adjust the numbers to match your assumptions.

Statutory anchor (Indiana)

• Indiana Code § 35-41-4-2: 5 years
  That’s 60 months as the reference length used in many time-based models.

Example scenario

Assume you want to model the economic impact of a case taking longer than the 5-year reference window.

Checkboxes help you keep track of what you decided:

• Jurisdiction reference period = 5 years / 60 months (IC § 35-41-4-2)
• You consider “delay” = the months beyond the 60-month reference
• Assumed monthly cost of delay = $2,500
• Case resolution occurs at 67 months total elapsed time

Step 1: Calculate “months of delay”

1. Reference window: 60 months
2. Modeled elapsed time: 67 months
3. Delay beyond reference: 67 − 60 = 7 months

Step 2: Apply your cost rate

• Monthly cost of delay: $2,500
• Modeled delay: 7 months
• Estimated cost: $2,500 × 7 = $17,500

Step 3: Run a “sensitivity check”

You can make the analysis more robust by testing a few plausible monthly costs:

This helps you answer: “Is the outcome driven by a few dollars per month—or by the length of delay itself?”

Step 4: Document assumptions for repeatability

In your notes (or case file), capture:

• the jurisdiction and statutory reference used (IC § 35-41-4-2 — 5 years, plus awareness of exception V3)
• your definition of elapsed time (what dates you used)
• your monthly cost assumption
• whether you included any adjustments/multipliers

Where the tool comes in

To model this quickly, you can go to:

• Primary CTA: /tools/cost-of-delay

Common scenarios

DocketMath is most useful when you apply it to repeatable patterns. Here are common Indiana scenarios you can model without reinventing your approach each time.

1) The case resolves slightly after the 5-year window

• Example: 63 months elapsed
• Delay beyond 60 months: 3 months
• Estimated cost = 3 × monthly cost

Use this when you need a “small delay” estimate for internal review or messaging.

2) The case extends materially beyond the reference period

• Example: 78 months elapsed
• Delay: 18 months
• Estimated cost = 18 × monthly cost

This scenario is where cost-of-delay figures tend to become compelling for comparisons.

3) You’re comparing two outcomes

Run the model twice using the same monthly cost assumption:

• Scenario A ends at 64 months
• Scenario B ends at 70 months

The difference is:

• A delay: 4 months
• B delay: 10 months
• Delta months: 6 months
• Delta cost = 6 × monthly cost

This helps avoid “apples-to-oranges” comparisons.

4) You want to reflect uncertainty about timing

Instead of one number, you can model a range:

• Low case: 66 months
• Mid case: 72 months
• High case: 80 months

Then estimate costs at each point to see where your planning threshold lies.

5) Exception awareness: exception V3

Indiana’s statutory framework includes a 5-year period with exception V3 referenced for this section (Indiana Code § 35-41-4-2).

Because “exception” handling can affect what you treat as relevant periods, a best practice is to:

• decide whether your model treats the entire elapsed time as “delay,” or
• adjust your delay calculation to the time you are specifically modeling.

Tips for accuracy

Small consistency choices dramatically improve how meaningful a cost-of-delay output becomes. Focus on these items before saving or sharing results.

1) Keep your time definition consistent

When you calculate months elapsed, pick one approach and stick to it:

• from a clearly chosen start date to a clearly chosen end date
• converted consistently into months

Even a one-month shift can matter once you multiply by monthly cost.

2) Use a realistic monthly cost

Your cost-of-delay number should represent an aggregated monthly burden, such as:

• employment disruption costs
• ongoing legal/compliance process costs
• opportunity cost (if you track it)
• administrative burden (if you estimate it)

If you don’t know what to use, consider a worksheet approach:

• total estimated monthly burden from multiple categories
• then sum into one monthly figure

3) Test at least 3 cost rates

For credibility, run a low / expected / high assumption set:

• Low: $1,500/month
• Expected: $2,500/month
• High: $4,000/month

If your conclusion changes drastically between low and expected, your analysis is dominated by assumption risk rather than timeline.

4) Separate “elapsed time” from “modeled delay”

In your notes (and when entering data), distinguish:

• Total elapsed months (e.g., 67 months)
• Modeled delay months (e.g., 7 months beyond 60-month reference)

This prevents confusion later when someone reviews the numbers.

5) Capture the statute anchor you used

Your model should explicitly reflect:

• Indiana Code § 35-41-4-2
• 5-year reference period
• awareness of exception V3 (without assuming the tool resolves it for you)

Including this detail in your saved output notes makes the model defensible in internal documentation.

6) Keep a change log

When updating, record:

• what changed (end date? monthly cost? delay definition?)
• when changed
• why changed

That turns a one-off estimate into a repeatable analytical routine.

Related reading

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