8.1 Delay Classification, Criticality, and Contract Questions

8.1 Delay Classification, Criticality, and Contract Questions

Delay analysis has two connected but distinct layers. The technical layer asks what happened to the schedule: when the event occurred, which activities it affected, whether it reached a controlling path, and how much milestone movement resulted. The contract layer asks who accepted the risk, what notice and proof are required, and what remedy is available.

AACE RP 29R-03 focuses on technical forensic schedule analysis. It expressly says the selected method and implementation depend on the contract, facts, applicable law, and quality of contemporaneous documentation. It is not a legal rulebook and is not intended to establish a mandatory standard of practice.

Classification framework

The word potentially matters. An unknown subsurface condition may qualify under a differing-site-condition clause, but only after checking the clause’s type, the information represented in the contract, actual conditions, reliance, notice, and causal impact. The event name alone does not create an automatic entitlement.

Event-to-impact workflow

1. Define the event. Use dates and records rather than labels such as “owner delay.”
2. Validate status. Confirm the data date, actual starts and finishes, remaining durations, calendars, and logic in the contemporaneous schedule.
3. Identify affected activities. Tie the event to real work through records, not assumption.
4. Test criticality. Determine whether the event delayed the controlling path, a contractual interim milestone, or only consumed float.
5. Measure impact. Apply a method suited to the timing and available records.
6. Check concurrency and mitigation. Identify independent delays and reasonable response actions.
7. Apply the contract. Review risk allocation, notice, substantiation, change, and remedy clauses.
8. Separate cost proof. A time impact does not by itself prove the amount or recoverability of cost.

Float consumption

Suppose an approval activity has 22 days of total float and an event delays it 12 days, with no separate protected milestone and no change to the controlling path. The straightforward schedule result is ten days of float remaining and no project-completion movement from that event at that update. That finding generally does not support twelve days of project time extension.

It also does not prove that every possible cost claim is zero. A party might allege disruption, resequencing, or direct cost under a separate contract provision. Those allegations require their own causation and damage proof. Keep the schedule conclusion narrower than the legal conclusion.

Cost formulas versus entitlement

The Eichleay formula is associated with federal-contract claims for unabsorbed home-office overhead. Arithmetic can compute a formula amount from supplied figures, but entitlement depends on legal prerequisites and the governing forum. A PSP study problem may ask for the arithmetic; a professional report should label the result as a calculated amount before contractual and legal eligibility is determined.

For billings of 9 million on the affected contract, 45 million total firm billings, 3 million home-office overhead, 600 performance days, and 30 assumed compensable days:

• allocable overhead = 9/45 × 3 million = 600,000;
• daily rate = 600,000 / 600 = 1,000; and
• formula amount = 1,000 × 30 = 30,000.

The calculation is correct; calling 30,000 an automatic entitlement is not.

Professional reporting

Use language such as “the modeled event moved the forecast milestone by 12 days” and “potential entitlement is subject to Clause X, notice compliance, cost substantiation, and counsel’s review.” Avoid “the contractor is legally entitled” unless the decision-maker with authority has actually resolved those questions.

That discipline is not evasive. It preserves the boundary between a scheduler’s technical opinion and a legal or contractual determination.

Applied review: keep technical classification separate from entitlement

A schedule analyst may classify an event by timing, affected work, apparent responsibility, and whether it influenced a controlling path. Entitlement is a broader conclusion that depends on contract language, notice, causation, mitigation, applicable law, and the complete factual record. Therefore a technically excusable event is not automatically compensable, and observed critical delay is not by itself a legal award.

Build an event chronology from contemporaneous records, establish the accepted schedule and update history, test the relevant paths, and state limitations. Consider whether other events affected the same period and whether reasonable mitigation was available. Use neutral language such as “the analysis indicates” rather than claiming that a software result proves liability.

AACE RP 29R-03 explicitly presents forensic schedule analysis as non-prescriptive guidance whose application depends on the facts, contract, law, and records. On the exam, favor answers that preserve that boundary, disclose assumptions, and route entitlement determinations to the authorized contractual or legal process.