Cost of Delay Modeler Guide for Utah

What this calculator does

DocketMath’s Cost of Delay Modeler for Utah (US-UT) helps you estimate the economic impact of time passing in a case—using a structured “cost of delay” approach you can plug into the Cost of Delay tool calculator.

At a high level, the model lets you connect three things:

• When key events happen (or don’t happen)
• How long the delay lasts
• What the delay costs (lost value, carrying costs, additional expenses, or other financial impacts you assign)

A central Utah-specific reference point you can use in the model is the statute of limitations period for certain criminal matters, which is 4 years under Utah Code § 76-1-302, including the “exception P4” structure reflected in Utah’s legal help guidance. See Utah courts’ summary: Utah Code § 76-1-302 (4 years; exception P4).
Source: https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html

The Utah timeline reference you can parameterize

If you’re modeling timing pressures against a 4-year SOL period for matters covered by Utah Code § 76-1-302, you can set your “latest relevant date” assumptions accordingly. The statute-length reference is:

Use this period as an input for scenario comparisons, not as a guarantee that any particular claim is barred.

When to use it

Use DocketMath’s Cost of Delay Modeler when you need a repeatable way to quantify what “time” means financially. This is especially useful in Utah if you’re working with a multi-year timeline where the 4-year SOL period in Utah Code § 76-1-302 (per exception P4) is part of your planning assumptions.

Common use cases include:

• Scheduling decisions: Comparing the cost of moving an event earlier versus later.
• Negotiation leverage (financial framing): Building an economic narrative around urgency, even when legal standards are separate.
• Case management: Understanding how expenses and opportunity costs scale over time.
• Budgeting for time-based spend: Estimating carrying costs, staffing costs, or recurring expenditures that increase as delay grows.

Practical timing prompts

Ask yourself:

• Do I have a start date (e.g., an event or baseline) and a target date?
• If the case process moves from month 12 to month 24, what changes financially?
• Does Utah’s 4-year SOL window shape the “outer boundary” of my scenarios? If so, you can parameterize it using Utah Code § 76-1-302 (4 years; exception P4 as referenced in Utah courts guidance).

Step-by-step example

Below is a worked example using DocketMath’s Cost of Delay Modeler for Utah. Since your financial assumptions drive the output, we’ll focus on showing how each input changes the result.

Before you start, open the calculator: /tools/cost-of-delay .

Example goal

You want to compare two timelines for the same matter:

1. Scenario A (faster): Key activity happens in 18 months
2. Scenario B (slower): Key activity happens in 30 months

You’ll model the cost of that added 12 months.

Step 1: Define your “delay window”

Choose:

• Start date: the baseline from which you measure delay

  • Example: 2026-01-01
• End date: when the delay impact stops (or the next milestone occurs)

  • Scenario A end date: 18 months later → 2027-07-01
  • Scenario B end date: 30 months later → 2028-07-01

Step 2: Choose a cost structure for time

A cost of delay model usually needs a cost rate. Common approaches include:

• Monthly carrying cost (e.g., $X/month for financing, storage, staffing)
• One-time costs triggered at the milestone
• Opportunity cost expressed as a monthly value

For the example, assume:

• Carrying/administrative cost: $2,000 per month
• Milestone cost difference: none (we’re isolating time cost)

Step 3: Use Utah’s 4-year SOL as an outer scenario check (optional)

If your planning is bounded by the 4-year SOL period referenced for Utah Code § 76-1-302, you can verify that both scenarios fall within that outer time horizon.

• 4 years = 48 months
• Scenario B end = 30 months → within 48 months

This doesn’t prove anything legally; it helps you keep modeling assumptions aligned with a known Utah timeframe reference:

• Utah Code § 76-1-302 (4 years; exception P4)

Utah courts’ guidance page provides this SOL-length summary: https://www.utcourts.gov/en/legal-help/legal-help/procedures/statute-limitation.html

Step 4: Compute modeled costs for each scenario

Because the example uses a linear monthly rate ($2,000/month), the model behaves predictably:

Step 5: Calculate the “cost of delay”

The difference is what you can use to quantify impact:

• Cost of delay = $60,000 − $36,000 = $24,000

Step 6: Stress test the assumptions

Try changing inputs to see how the model responds.

Checkpoints:

• If your monthly cost is $3,000/month instead of $2,000:

  • Scenario A: 18 × 3,000 = $54,000
  • Scenario B: 30 × 3,000 = $90,000
  • Difference = $36,000
• If the delay cost is not linear (e.g., steeper after month 24), set a tiered rate if the calculator supports it. If it doesn’t, you can approximate by running separate scenarios for “low-rate” and “high-rate” periods.

Common scenarios

Below are scenario patterns people use DocketMath’s Cost of Delay Modeler for Utah, organized by the kind of “time cost” being modeled.

1) Staged milestones with recurring costs

What you model: recurring expenses until the next milestone.

• Input pattern:

  • Start date → recurring monthly cost
  • End date → stop recurrence
• Output use:

  • Compare “milestone earlier” vs “milestone later”

2) Two-track planning tied to the 4-year SOL reference

What you model: urgency bounded by an outer timeline reference.

You can parameterize scenarios like:

• Scenario A: ends at 24 months
• Scenario B: ends at 42 months

Both are within 48 months (4 years), aligning with Utah Code § 76-1-302’s 4-year SOL period summary (exception P4 noted in Utah courts guidance).

Again, keep this as planning alignment, not legal certainty.

3) Opportunity cost of delayed resolution

What you model: the economic value of “earlier is better.”

• Example inputs:

  • Monthly opportunity cost: $1,500/month
  • Delay difference: 10 months
• Output:

  • $15,000 modeled opportunity loss

4) One-time costs triggered after delay

What you model: delay causes a one-time event cost.

• Example:

  • Additional review or compliance cost: $8,000 triggered when milestone occurs
• Comparison:

  • If Scenario B triggers that cost, Scenario A doesn’t, the “cost of delay” is partly the incremental one-time charge

5) Tiered delay effects

Some costs accelerate after certain time thresholds.

Common modeling choices:

• Flat cost for months 0–12
• Higher cost for months 13–24
• Even higher cost after month 24

If the calculator supports multiple rates, you can mirror these tiers. If not, run separate calculations for each tier and add them.

Tips for accuracy

These are accuracy improvements that typically matter more than people expect—especially when your output becomes part of a decision memo, negotiation position, or internal planning discussion.

Confirm date logic first

Before numbers, validate:

• Your start date is the correct baseline for the cost driver.
• Your end date reflects when the cost stops.
• Your scenarios differ only in delay length—not in cost assumptions (unless you’re intentionally comparing different strategies).

Use consistent units

DocketMath’s calculator works best when:

• Monthly costs are truly monthly
• Annual costs are converted to monthly if you’re entering them as such
• “Delay length” is measured in the same time basis you used for rates

Calibrate costs with at least one real reference

If you can, anchor your monthly rate to:

• Actual invoices
• Recurring internal expenses
• A documented estimate you can defend internally

Even a

Related reading

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