Cost of Delay Modeler Guide for Virginia

What this calculator does

Run this scenario in DocketMath using the Cost Of Delay calculator.

DocketMath’s Cost of Delay Modeler (Virginia) helps you translate schedule changes into dollars. You provide a few planning assumptions (e.g., your monthly cost of carrying people/equipment, expected revenue impact, and the length of delay), and the model produces an estimated total cost of delay and (optionally) a timing breakdown.

This is a planning and prioritization tool—not a litigation or damages calculation. You can use it to compare options like:

• Accelerate a project by 2 months vs. 6 months
• Accept a schedule slip if the cost impact is below a threshold
• Evaluate mitigation strategies (more staffing, changed sequencing, alternative suppliers)

When to use it

Use the Cost of Delay Modeler when you have credible timing assumptions and want to quantify the financial impact of schedule risk. In Virginia contexts (public procurement, contract performance, project planning), delays often show up as:

• Missed milestones (design complete, permit-ready, construction start)
• Extended lead times (materials, inspections, permitting)
• Regulatory or administrative friction that pushes start dates
• Downstream effects that reduce productivity or revenue realization

Best-fit use cases (check the ones that apply)

When to pause or refine inputs

Step-by-step example

Below is a practical example you can mirror in DocketMath. The numbers are illustrative; adjust them to your project.

Scenario: schedule slip delays project completion

You manage a construction-related project with a target completion date. A revised plan predicts completion will occur 3 months later than baseline.

Given assumptions (you estimate these):

• Baseline schedule length relevant to impact: 12 months
• Delay duration: 3 months
• Monthly cost of carrying the project (overhead, financing cost, staffing “standby,” equipment idling): $25,000/month
• Monthly value loss during delay (lost revenue opportunity or revenue realized later): $40,000/month
• Mitigation plan? No for this run
• Timing convention: costs and value loss accrue evenly each month

Step 1: Enter the baseline and delay horizon

In the calculator, set:

• Delay duration: 3 months
• Start of delay (optional depending on the model UI): set to the first month impacted

If the tool supports “baseline vs. new date,” pick the baseline completion date and revised completion date for the shift. If it’s duration-based, just enter 3.

Step 2: Enter the cost components

Add the monthly amounts for the categories you track:

• Carrying cost: $25,000
• Revenue/value impact: $40,000

Total monthly impact in this example:

• $25,000 + $40,000 = $65,000/month

Step 3: Choose the accrual method (if available)

If DocketMath offers options like linear accrual vs. weighted timing:

• Select linear/even accrual for a simple planning baseline.
• If your revenue loss accelerates near completion, consider a weighted profile later (see Tips for accuracy).

Step 4: Review outputs

With a 3-month delay and $65,000/month impact, the model estimates:

• Total cost of delay: $65,000 × 3 = $195,000

A timing breakdown (often shown as a month-by-month table or a chart) might look like:

Step 5: Run a mitigation comparison

Now test a second plan where you mitigate by adding resources to reduce delay from 3 months to 1.5 months (the mitigation cost itself may be entered as an additional one-time or ongoing amount, depending on what the calculator supports).

If the monthly impact remains $65,000:

• Total delay cost = $65,000 × 1.5 = $97,500

Then compare:

• Cost avoided: $195,000 - $97,500 = $97,500
• Net effect: subtract the mitigation expense (entered separately if supported)

Common scenarios

Delay costs don’t always look like a flat monthly number. Here are common patterns and how to reflect them in the model.

1) Flat monthly cost of delay

What it looks like:

• Overhead, standby labor, equipment idling
• Revenue impact that is proportional to time

Model approach:

• Use one monthly carrying cost and one monthly value loss.
• Apply linear accrual unless your revenue loss ramps.

2) Ramp-up value loss (front-loaded or back-loaded)

What it looks like:

• Early months have some cost, but revenue impact grows as milestones slip.
• Alternatively, early admin overhead spikes, then stabilizes.

Model approach:

• Use weighted timing if the UI provides it.
• If no weighted option exists, approximate by splitting the delay into segments (example: 1 month at 60% intensity, next month at 100%).

3) Step-change costs (discrete events)

What it looks like:

• One-time retesting fees
• Re-permitting costs
• Rerouting or rescheduling charges

Model approach:

• Enter one-time items as separate line items if supported.
• Otherwise, convert discrete costs into an equivalent monthly spread, but keep a note of what you did.

4) Offset effects (partial productivity restoration)

What it looks like:

• Even though completion is later, certain parts can start generating value earlier (partial occupancy; phased deliveries).

Model approach:

• If the calculator allows multiple phases, model value recovery earlier for partial milestones.
• If not, reduce the “monthly value loss” rate to reflect only the net unrecovered value.

5) Multiple delay intervals (pause → restart)

What it looks like:

• A long idle period, then resumed work at a different productivity level.
• Administrative delays that temporarily stop the work.

Model approach:

• Split delay into intervals with different carrying/value rates.
• If only one delay duration is allowed, run separate scenarios and compare ranges.

Tips for accuracy

To make DocketMath’s output more decision-grade, tighten your inputs and align them to how your organization actually incurs cost.

Use a consistent time unit and convention

Most cost-of-delay models become sensitive to month/day math. Pick one:

• Monthly accrual: convenient for leadership reporting
• Daily accrual: best when delays are measured in days and you need precision

If you’re entering dates, ensure the interval includes the months (or days) you truly consider impacted.

Separate “carrying cost” from “value impact”

Even when they feel similar, treat them differently:

• Carrying cost often tracks real expenditures (overhead, standby labor, equipment costs, financing).
• Value impact often tracks opportunity cost (revenue later, higher exposure to market risk, lost earning time).

This separation helps you run sensitivity tests:

• If carrying cost is fixed, value loss dominates.
• If both move together, delays hit double.

Do sensitivity runs instead of one “best guess”

Create at least 3 runs:

• Low: optimistic assumptions (e.g., delay cost rate is 80% of base)
• Base: your best estimate
• High: conservative assumptions (e.g., delay cost rate is 120% of base)

A simple sensitivity table can look like:

Capture mitigation costs explicitly

When you compare “delay without mitigation” vs. “with mitigation,” include mitigation cost in the second run:

• Additional crew hours / overtime
• Expediting fees
• Rental equipment to recover schedule
• Supplier surcharge for faster delivery

If the calculator supports it, put mitigation costs in the “mitigation” or “additional cost” field. If it doesn’t, run delay cost first, then subtract mitigation cost manually from the net comparison (and record the formula).

Keep assumptions traceable

As you iterate, maintain a short list of what changed between runs:

• Delay duration: 90 days → 45 days
• Carrying cost rate: $25k/mo → $28k/mo (new info on staffing)
• Value impact: $40k/mo → $35k/mo (phased revenue recovery)

This makes the model reproducible and easier to explain to internal

Sources and references

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

• Primary authority reference

Related reading

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