The Client-Side Design Review Before Construction Starts

Treat the review as an authorization decision, not a presentation

The last design review before construction often arrives as a polished meeting: updated drawings, a model walkthrough, a cost headline, and a list of items said to be nearly closed. That format can conceal the decision the client is actually making. Starting procurement, signing a building contract, releasing a package, or allowing work on site converts design assumptions into commercial, programme, safety, and operational consequences. The review should therefore produce an explicit authorization, not general reassurance.

RIBA's Plan of Work describes Stage 4 as technical design and sets an end-stage outcome of completing the design information required to manufacture and construct the project [1]. Its detailed overview also warns that Stage 4 and Stage 5 commonly overlap, with specialist subcontractor design continuing according to the procurement route [2]. Those are important qualifications. 'Ready' does not always mean every detail is finished; it means the information is mature enough for the specific commitment being made and every material remainder has a defined owner, dependency, and closure point.

A project is ready to proceed when the next commitment is supported by evidence and the remaining uncertainty is bounded, owned, and timed.

Define exactly what is being released

Begin by naming the decision boundary. Is the client authorizing tender, contractor appointment, early works, a long-lead package, full construction, or work only in a defined zone? Each decision needs a different level of resolution. A foundation package may proceed while later interior details remain open, but the loads, grids, penetrations, surveys, approvals, and change consequences that govern that foundation cannot remain vague. A conditional release is legitimate only when its boundary is precise.

The client should ask the lead designer and project manager for a release statement: package, purpose, current information issue, included scope, excluded scope, unresolved items, dependent decisions, and the authority accepting residual risk. This is E2W professional interpretation, not a universal contractual form. It prevents a broad phrase such as 'design signed off' from being mistaken for approval of information the client has not seen, specialist design not yet appointed, or statutory matters that another authority must determine.

Gate 1: trace the design back to the approved brief

Construction readiness begins with purpose. Compare the current design with the approved brief, user needs, capacity, adjacencies, quality aspirations, performance outcomes, accessibility requirements, sustainability targets, operating model, and agreed derogations. Do not ask only whether the drawings changed. Ask whether the project still delivers the outcome for which the client is about to spend money, and whether every deliberate compromise is recorded with its consequence.

Commissioning guidance describes the Owner's Project Requirements as the owner's statement of goals, performance criteria, cost considerations, success criteria, training, documentation, and operating expectations; it is intended to be maintained across project phases [3]. The source is commissioning-focused, so it does not replace a full architectural brief. Its broader lesson is useful: design acceptance needs a stable, current baseline. If the client cannot trace a critical requirement into the present design or an approved change, the team is reviewing appearance and completeness without reviewing fitness for purpose.

Gate 2: separate design confidence from statutory authority

List every consent, condition, submission, certificate, survey, third-party agreement, and specialist review that affects the proposed start. Record its status, responsible party, required evidence, due date, and the work it constrains. Planning permission does not itself prove technical compliance; a submitted application is not an approval; and an approval may carry conditions that must be discharged before a particular activity begins. The applicable route varies by jurisdiction, building type, scope, and procurement strategy, so qualified local advice is essential.

Current guidance for building work in England requires clients and designers to allocate sufficient time and resources, share building information, plan and monitor design work, and take reasonable steps toward compliance with relevant building regulations [4]. Higher-risk building procedures add specific controls: agreed documents, assessed changes, change logs, and approval before work proceeds on a major change [5]. These duties are jurisdiction-specific. The client-side principle is wider: the review must distinguish verified approval, pending authority, design-team opinion, and client acceptance rather than compressing all four into a green status.

Gate 3: review closed interfaces, not isolated disciplines

Ask each discipline to show the consequential interfaces it has checked: structure with openings and loads; services with ceiling zones, access, and plant replacement; envelope with drainage, movement, fire, and thermal continuity; interiors with accessibility, acoustics, equipment, and maintenance; landscape and civil work with thresholds, utilities, and levels. A federated model or clash report is evidence of a process, not proof that the design is coordinated. Sequence, tolerance, support, commissioning, and safe access can fail without a geometric clash.

Under Great Britain's CDM framework, designers must eliminate, reduce, or control foreseeable risks, provide relevant design information, and communicate, cooperate, and coordinate with other designers and contractors [6]. Applicability must be determined for the actual project. For the review, request a short interface register showing the issue, affected parties, current evidence, decision owner, and disposition. This keeps the meeting focused on the spaces between professional scopes, where many costly assumptions survive.

Gate 4: reconcile design, cost, programme, and procurement

A design can be technically coherent but commercially unready. Confirm that the cost plan and programme refer to the same information issue being reviewed. Test major quantities, provisional sums, allowances, exclusions, long-lead items, escalation assumptions, temporary works interfaces, surveys, specialist packages, and client-supplied items. If bids rely on different assumptions, a low price may represent a narrower scope rather than better value. If the programme assumes approvals or information earlier than the design schedule can provide them, the apparent start date simply moves risk downstream.

RIBA describes its Plan of Work as procurement-neutral and explains that the boundary between design-team and specialist-subcontractor information is a core project decision [2]. The review should therefore include a current responsibility matrix and design programme, not assume that one procurement label answers who designs what and when. For every incomplete package, identify who carries design responsibility, who coordinates it, what the contractor has priced, what the client has retained, and which upstream geometry or performance criteria may no longer change.

Gate 5: test the information as a controlled construction system

Review the drawing register, specifications, schedules, models, reports, issue status, revision history, and superseded-information controls together. Sample several critical elements and trace each from requirement to location, performance, interface, approval, installation, inspection, and change. This is different from repeating a full construction-documentation risk review or checking whether an individual drawing is practically buildable. At this gate, the client is asking whether the controlled information set is reliable enough for the release decision.

ISO 19650-2 specifies an information-management process for the delivery phase and the exchange of built-asset information, applicable across asset types, organization sizes, and procurement strategies [7]. Using a common data environment or BIM platform does not by itself establish conformity. The practical test is whether recipients can identify origin, status, suitability, revision, authorization, and intended use; whether comments have recorded dispositions; and whether a change reaches every affected record before conflicting information is used.

Gate 6: bring operations, maintenance, and commissioning into the room

Invite the people who will operate, maintain, clean, secure, furnish, commission, and eventually adapt the building. Ask them to review access, isolation, replacement routes, controls, metering, cleaning, consumables, storage, training, seasonal operation, spare parts, and the evidence they will receive at handover. A system that fits the drawing but cannot be tested, maintained, or understood is not ready in the way the owner needs it to be.

ASHRAE Guideline 0 describes commissioning as a process for verifying that a facility and its systems meet the Owner's Project Requirements, with acceptance and documentation activities extending from predesign through occupancy and operation [8]. Commissioning scope varies, and the guideline is not a substitute for project-specific technical standards. It supports an essential client question before construction: have testing, access, controls, documentation, training, and acceptance been designed into the work, or left as promises to solve at handover?

Gate 7: convert every residual risk into a managed condition

Collect the unresolved decisions, approvals, coordination items, surveys, specialist designs, procurement assumptions, value-engineering proposals, and operational concerns into one residual-risk register. For each item, state its consequence, affected work, decision owner, evidence needed, latest safe decision date, interim constraint, and escalation path. Avoid percentages such as 'ninety-five percent complete' unless they are tied to defined deliverables; one unresolved fire, structure, waterproofing, access, or long-lead decision can matter more than hundreds of finished details.

The HSE's CDM guidance states that clients influence procurement, appointments, time, money, and resources, and require suitable arrangements for managing project health, safety, and welfare [9]. That legal context is specific, but the governance lesson is direct: the client controls conditions that shape readiness. A project should not proceed because the team feels late. It should proceed because known high-consequence risks are closed or consciously bounded, competent people are appointed, and the remaining work has enough time, information, and authority to be completed responsibly.

Use the E2W seven-gate readiness record

Score each gate—brief, authority, coordination, cost and programme, construction information, operations, and residual risk—as go, conditional go, or hold. A go rating includes the evidence reviewed and the role authorizing release. A conditional go defines the exact package boundary, condition, owner, due date, verification route, and consequence if the condition is not met. A hold identifies what cannot responsibly proceed and the evidence required to return for decision. Mixed results should produce a bounded release, not an averaged score.

End with a signed or otherwise controlled decision record: meeting date, information issue, participants and roles, decision, conditions, accepted residual risks, actions, distribution, and next review. This record does not transfer professional duties, approve statutory matters, amend contracts by implication, or guarantee a defect-free build. It makes the client's decision legible. E2W uses this kind of stage-aware review to connect design intent with project governance, delivery, and operational reality.