CVEN9702 Chap.9 Project Control and Delay Entitlement
Project Control and Delay Entitlement
Delay analysis separates the duration of an event from its effect on project completion. The planner identifies the event, establishes the current programme and critical effect, tests mitigation, measures the change in practical completion and preserves contemporaneous records. The programme measures time consequence; the contract allocates responsibility, notice requirements, extensions and any cost entitlement.
What this chapter covers
- 01
Prove the delay event and its timing with records
- 02
Test the event against the contemporaneous critical path
- 03
Distinguish activity delay from project completion delay
- 04
Account for float, resource constraints and mitigation
- 05
Maintain an as-executed programme linked to factual records
- 06
Apply the governing clause before stating entitlement
Worked example · free
Measure an owner-controlled access delay
- +1Use access notices and site records to establish the event and exact four-day period.
- +1Use the programme current to the event to show that the affected activity was critical.
- +1Trace the delay through successors and measure the potential four-day completion effect.
- +1Record resequencing, alternative workface and recovery options considered as mitigation.
- +1Apply the contract clause and notice record separately to time and cost entitlement.
Key terms
- Delay event
- An occurrence that affects activity timing and may or may not change project completion.
- Critical delay
- A delay that affects controlling work and changes the expected project completion date.
- Extension of time
- A contract-based adjustment to the required completion date for a qualifying delay event.
- Mitigation
- Reasonable action taken to reduce the time or cost effect of a delay without assuming unlimited acceleration.
- As-executed programme
- A factual schedule showing actual sequence, delays, variations and agreed changes linked to project records.
Project Control and Delay Entitlement FAQ
Does every delayed activity delay the project?
No. An activity may use available float without changing completion. Test the event against the current feasible programme, including resource constraints, and trace its effect through successors before calling it a project delay.
Why are contemporaneous records important?
They establish what happened, when it happened, which work was affected and what mitigation was attempted. Site diaries, instructions, approvals, photographs and correspondence make an as-executed programme factual rather than a retrospective assertion.
Can the schedule decide cost entitlement?
The schedule measures time effect and supports causation analysis. The contract determines whether the event qualifies, what notices are required and whether time, cost or both are available. Keep those conclusions separate and clause-specific.
Why use the programme current before the event?
It records contemporaneous logic, float and forecast. Later reconstruction can assist, but it must be reconciled with actual sequence and disclosed rather than silently substituted.
Exam move
For every delay scenario, draw a five-part evidence chain: event, contemporaneous programme, critical effect, mitigation and contract clause. Practise with events that consume float, events that affect a critical path and events that appear non-critical until a shared resource is considered. State the difference between activity delay and completion delay explicitly.
Build a record list beside each answer, including instructions, access records, site diaries, progress photographs, approvals, correspondence and updated programmes. Then classify broad causation only as a starting point, not a final entitlement conclusion. Owner-caused, contractor-caused and neutral events can have different common outcomes, but the actual contract controls.
Finish with bounded wording that states what the schedule proves and what remains subject to notice and clause interpretation. This approach earns more confidence than either a categorical legal claim or a vague request for more information. Build an event chronology before altering the programme.
For each entry, capture the instruction or occurrence, notice date, affected area, available workfaces, actual response and supporting document. Select the programme update current immediately before the event and confirm that its logic reflects the feasible resource plan. Trace the event through affected successors to practical completion, testing available float, concurrent causes and later recovery.
Compare planned and as-executed sequence without inventing precision unsupported by records. Record mitigation options considered, their cost and the reason each was adopted or rejected; mitigation evidence is stronger than a generic statement that nothing else could be done. Keep the time analysis separate from contractual classification.
The schedule may demonstrate a measured critical effect, while the clause determines whether it is excusable, compensable, subject to notice or allocated to a party. Practise bounded conclusions for owner, contractor and neutral events, always naming the missing clause evidence. Reconcile site diaries, photographs, access logs, correspondence, approval registers and cost records to the same dates.
If sources conflict, disclose the conflict and explain which contemporaneous record is more reliable. End by stating the proven event period, net completion effect after mitigation, remaining uncertainty and exact contractual question. That structure avoids converting an activity disruption automatically into days of entitlement.
