A prevention-focused look at common delay mechanisms that clients can influence through briefing, surveys, decisions, procurement and disciplined change control. This guide is written for clients and non-specialist decision-makers who need a clear framework for asking better questions, commissioning the right evidence and understanding where specialist input is essential.
Late or unstable scope
The practical point is that freeze strategic requirements before detailed design. In client terms, this should be translated into an explicit decision, owner and evidence requirement rather than left as an informal expectation. Record priorities should be tested against the brief and the constraints already known. If the project team cannot explain the assumption in plain language, the assumption is not yet controlled.
A useful review asks three things: what is known, what is still uncertain, and what decision becomes harder if the uncertainty remains. Separate true new need from clarification deserves particular attention because it can affect more than one workstream. Assess programme impact before approving change should therefore be recorded early enough for designers, contractors and the client to respond without avoidable rework.
For a programme decision, the useful question is not simply whether this topic has been discussed, but whether the discussion changed the project information. The project record should show the chosen position, any alternatives rejected, the assumptions that remain open and the trigger for revisiting them. That makes late or unstable scope a working control rather than a retrospective narrative. It also gives future team members enough context to understand why a decision was made instead of repeating the same investigation.
Insufficient surveys
Good project control begins by making investigate ground existing structures and services proportionately visible. That does not mean producing more paperwork; it means ensuring the relevant people can see the requirement, understand its consequence and act at the right time. Share limitations then becomes part of the project logic rather than an isolated technical discussion.
The same discipline applies to target uncertainty before pricing. Teams should state the evidence they will use to confirm the position and the date by which it is needed. When avoid using contingency as a substitute for information is also considered, the client can compare options on a consistent basis and avoid decisions that appear cheaper or faster only because important consequences were omitted.
For a programme decision, the useful question is not simply whether this topic has been discussed, but whether the discussion changed the project information. The project record should show the chosen position, any alternatives rejected, the assumptions that remain open and the trigger for revisiting them. That makes insufficient surveys a working control rather than a retrospective narrative. It also gives future team members enough context to understand why a decision was made instead of repeating the same investigation.
Slow approvals and client decisions
At this stage, maintain a decision schedule is best treated as a managed choice rather than a background detail. The team should establish the baseline, identify interfaces and document who has authority to approve a change. Give decision-makers complete options can then be reviewed in the same decision framework, with cost, time, safety, quality and operational consequences shown together.
This approach is especially valuable where allow governance time. A short, evidence-led discussion before commitment is usually more useful than a long explanation after work has started. Escalate missing inputs before they reach the critical path should be carried into the next design or delivery gateway so that the project does not quietly revert to an outdated assumption.
For a programme decision, the useful question is not simply whether this topic has been discussed, but whether the discussion changed the project information. The project record should show the chosen position, any alternatives rejected, the assumptions that remain open and the trigger for revisiting them. That makes slow approvals and client decisions a working control rather than a retrospective narrative. It also gives future team members enough context to understand why a decision was made instead of repeating the same investigation.
Uncoordinated design
Clients do not need to perform every technical task themselves, but they do need confidence that resolve spatial and technical interfaces. The appointment, brief or control process should make that expectation unambiguous. Track information release also needs a route for escalation when information conflicts or a decision cannot be made within the working team.
In practice, review buildability is where seemingly separate disciplines often meet. A coordinated review should examine those interfaces before downstream work relies on them. Avoid tendering incomplete packages without a deliberate strategy completes the control loop: define what acceptable looks like, obtain the relevant evidence and retain the record in a form that will still make sense at handover.
For a programme decision, the useful question is not simply whether this topic has been discussed, but whether the discussion changed the project information. The project record should show the chosen position, any alternatives rejected, the assumptions that remain open and the trigger for revisiting them. That makes uncoordinated design a working control rather than a retrospective narrative. It also gives future team members enough context to understand why a decision was made instead of repeating the same investigation.
Long-lead procurement discovered too late
The practical point is that identify critical products during design. In client terms, this should be translated into an explicit decision, owner and evidence requirement rather than left as an informal expectation. Approve technical requirements in time should be tested against the brief and the constraints already known. If the project team cannot explain the assumption in plain language, the assumption is not yet controlled.
A useful review asks three things: what is known, what is still uncertain, and what decision becomes harder if the uncertainty remains. Track manufacture and logistics deserves particular attention because it can affect more than one workstream. Maintain alternatives only where they remain compliant should therefore be recorded early enough for designers, contractors and the client to respond without avoidable rework.
For a programme decision, the useful question is not simply whether this topic has been discussed, but whether the discussion changed the project information. The project record should show the chosen position, any alternatives rejected, the assumptions that remain open and the trigger for revisiting them. That makes long-lead procurement discovered too late a working control rather than a retrospective narrative. It also gives future team members enough context to understand why a decision was made instead of repeating the same investigation.
Site access and logistics constraints
Good project control begins by making plan delivery routes permits neighbours and working windows visible. That does not mean producing more paperwork; it means ensuring the relevant people can see the requirement, understand its consequence and act at the right time. Secure temporary rights where necessary then becomes part of the project logic rather than an isolated technical discussion.
The same discipline applies to coordinate cranes and storage. Teams should state the evidence they will use to confirm the position and the date by which it is needed. When reflect real constraints in productivity assumptions is also considered, the client can compare options on a consistent basis and avoid decisions that appear cheaper or faster only because important consequences were omitted.
For a programme decision, the useful question is not simply whether this topic has been discussed, but whether the discussion changed the project information. The project record should show the chosen position, any alternatives rejected, the assumptions that remain open and the trigger for revisiting them. That makes site access and logistics constraints a working control rather than a retrospective narrative. It also gives future team members enough context to understand why a decision was made instead of repeating the same investigation.
Commissioning and handover squeezed at the end
At this stage, schedule tests and training explicitly is best treated as a managed choice rather than a background detail. The team should establish the baseline, identify interfaces and document who has authority to approve a change. Complete systems in commissioning sequence can then be reviewed in the same decision framework, with cost, time, safety, quality and operational consequences shown together.
This approach is especially valuable where protect time for failures and retesting. A short, evidence-led discussion before commitment is usually more useful than a long explanation after work has started. Tie progress reporting to readiness not superficial percentage complete should be carried into the next design or delivery gateway so that the project does not quietly revert to an outdated assumption.
For a programme decision, the useful question is not simply whether this topic has been discussed, but whether the discussion changed the project information. The project record should show the chosen position, any alternatives rejected, the assumptions that remain open and the trigger for revisiting them. That makes commissioning and handover squeezed at the end a working control rather than a retrospective narrative. It also gives future team members enough context to understand why a decision was made instead of repeating the same investigation.
Client review checklist
Before moving to the next project stage, use this short review to test whether the core decisions are actually controlled:
- Late or unstable scope: Freeze strategic requirements before detailed design.
- Insufficient surveys: Investigate ground existing structures and services proportionately.
- Slow approvals and client decisions: Maintain a decision schedule.
- Uncoordinated design: Resolve spatial and technical interfaces.
- Long-lead procurement discovered too late: Identify critical products during design.
Not every item will apply with the same weight to every project. The value of the checklist is to expose assumptions early, allocate them to a competent person and make the consequences visible before commitment.