Key takeaways
- A complete request normally addresses the contractual event, notice and substantiation requirements, the relevant milestone, causation, mitigation, concurrency, and a schedule analysis appropriate to the timing and records.
- Verify the request against the contract, confirm the source schedule and calculation settings, test the event model and parallel paths, and document any concurrency or mitigation analysis.
What a request must actually show
A complete request normally addresses the contractual event, notice and substantiation requirements, the relevant milestone, causation, mitigation, concurrency, and a schedule analysis appropriate to the timing and records. The schedule should show how the event affects the controlling path under disclosed assumptions; the contract record should separately support the requested legal and commercial consequence.
How an owner evaluates one
Verify the request against the contract, confirm the source schedule and calculation settings, test the event model and parallel paths, and document any concurrency or mitigation analysis. Record time, compensation, responsibility, and approval as separate decisions unless the governing procedure directs otherwise.
Every request should be logged, every determination written, and every approved date change tied to a controlled schedule revision. Do not rely on an accepted update alone to communicate a contract modification when the agreement requires a separate authorized determination.
Sources and scope
Follow the reference trail.
This guide is original educational commentary. Kairos reference records identify the source organizations, editions and scope behind this guidance. The original publishers retain their publications and rights.
Delay and Disruption Protocol, second editionSociety of Construction Law · checked 2026-08-01UFGS 01 32 01.00 10: Project ScheduleWhole Building Design Guide / U.S. Department of Defense · checked 2026-08-01