A practical route from the first business case to occupation, focused on decisions a client can control before risk becomes expensive. 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.
Start with the outcome, not the building
The practical point is that define operational outcome and success measures. In client terms, this should be translated into an explicit decision, owner and evidence requirement rather than left as an informal expectation. Separate must-haves from preferences 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. Identify users and decision-makers deserves particular attention because it can affect more than one workstream. Record assumptions that need verification should therefore be recorded early enough for designers, contractors and the client to respond without avoidable rework.
For a project planning 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 start with the outcome, not the building 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.
Build the client brief in layers
Good project control begins by making turn needs into spatial and performance requirements 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. Set quality and resilience expectations then becomes part of the project logic rather than an isolated technical discussion.
The same discipline applies to capture accessibility and maintenance needs. Teams should state the evidence they will use to confirm the position and the date by which it is needed. When create a controlled brief-change process 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 project planning 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 build the client brief in layers 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.
Test feasibility before committing
At this stage, review site constraints and title information 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. Commission proportionate surveys 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 test planning and statutory routes. A short, evidence-led discussion before commitment is usually more useful than a long explanation after work has started. Compare budget, programme and risk scenarios should be carried into the next design or delivery gateway so that the project does not quietly revert to an outdated assumption.
For a project planning 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 test feasibility before committing 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.
Appoint the right project team
Clients do not need to perform every technical task themselves, but they do need confidence that match designer and adviser competence to project complexity. The appointment, brief or control process should make that expectation unambiguous. Clarify roles and information ownership also needs a route for escalation when information conflicts or a decision cannot be made within the working team.
In practice, plan procurement advice early is where seemingly separate disciplines often meet. A coordinated review should examine those interfaces before downstream work relies on them. Avoid duplicated or missing responsibilities 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 project planning 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 appoint the right project team 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.
Control design decisions and gateways
The practical point is that use design reviews with clear acceptance criteria. In client terms, this should be translated into an explicit decision, owner and evidence requirement rather than left as an informal expectation. Track decisions and unresolved interfaces 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. Coordinate cost and programme with design maturity deserves particular attention because it can affect more than one workstream. Freeze only what is genuinely ready should therefore be recorded early enough for designers, contractors and the client to respond without avoidable rework.
For a project planning 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 control design decisions and gateways 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.
Prepare procurement and mobilisation
Good project control begins by making choose a route aligned with risk appetite 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. Issue coordinated tender information then becomes part of the project logic rather than an isolated technical discussion.
The same discipline applies to evaluate quality as well as price. Teams should state the evidence they will use to confirm the position and the date by which it is needed. When set pre-start information and site-readiness gates 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 project planning 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 prepare procurement and mobilisation 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.
Manage delivery, handover and learning
At this stage, monitor change, quality, safety and programme together 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. Plan commissioning before completion 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 collect useful records and training. A short, evidence-led discussion before commitment is usually more useful than a long explanation after work has started. Hold a post-occupancy review against original outcomes should be carried into the next design or delivery gateway so that the project does not quietly revert to an outdated assumption.
For a project planning 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 manage delivery, handover and learning 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:
- Start with the outcome, not the building: Define operational outcome and success measures.
- Build the client brief in layers: Turn needs into spatial and performance requirements.
- Test feasibility before committing: Review site constraints and title information.
- Appoint the right project team: Match designer and adviser competence to project complexity.
- Control design decisions and gateways: Use design reviews with clear acceptance criteria.
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.