Why Facade Design Reviews Keep Failing and What Design Leads Can Do About It

Common Design Review Failures

Facade design reviews fail for predictable reasons: inadequate stakeholder involvement, missing technical expertise, and documentation that cannot be reconstructed six months later. The consequences are familiar to anyone who has delivered an envelope package: redesign after procurement, clashes discovered at installation, and rework that was avoidable on paper. In the UK, the Building Safety Act has raised the stakes: on higher-risk buildings, the design must be substantially resolved and approved at Gateway 2 before construction begins. A weak review process is no longer just expensive; it can stop a project from starting.

The Five Critical Failure Points

1. Inadequate early involvement: facade contractors and specialist engineers are excluded from early design stages, so system constraints and buildability arrive after the design intent has hardened
2. Missing technical review: no structural, thermal or movement analysis during design development, leaving interfaces to be resolved at fabrication or on site
3. Poor documentation: incomplete specifications, missing details, and review comments scattered across email chains nobody can reassemble
4. No constructability review: details that cannot be fabricated, sequenced or installed as drawn
5. No performance validation: designs signed off without a route to test evidence, thermal modelling or a compliance check against the specification

Why Reviews Fail Even When the Process Looks Right

Most envelope packages have a review procedure on paper. The failure is rarely the checklist; it is the joins between the people and tools running it. Comments are issued from a document control system, answered by email, and closed in a spreadsheet, which creates three versions of the truth before anyone disagrees about anything. Interface reviews (facade to frame, facade to MEP penetrations, facade to roofing and waterproofing junctions) sit between parties, so they are nobody's job until they become everybody's problem. And the contractor design portion is a standing ambiguity: the design team believes the intent drawings are further engineered than they are, the specialist assumes performance requirements will be clarified, and the gap surfaces at fabrication, which is the most expensive moment to find it.

The deeper pattern is that review cycles track documents rather than decisions. A drawing revision gets closed out, but the decision that changed it (who made it, on what basis, with what consequences for adjacent details) is recorded nowhere. When the question resurfaces a year later, the review happens again.

What the Building Safety Act Changes

For higher-risk buildings (broadly, buildings at least 18 metres or seven storeys with two or more residential units) the Act's gateway regime changes both the timing and the evidential weight of design review. Gateway 2 requires Building Safety Regulator approval before construction starts, which means safety-critical facade design can no longer be "developed on site". Change control continues through construction: major changes need regulator agreement before the work proceeds, and notifiable changes must be recorded. The golden thread requires design information and the reasoning behind key decisions to be kept as accurate, digital, accessible, structured and transferable records. And the competence requirements apply to reviewers as much as designers: dutyholders must ensure that those carrying out and checking design work have the skills, knowledge, experience and behaviours to do it.

None of this is satisfied by a bigger folder structure. It is satisfied by review records that connect the comment, the decision, the revision and the person, and survive scrutiny.

Testing Evidence Belongs in the Review

Performance validation is a review activity, not paperwork after the fact. For systemised envelopes, CWCT test sequences (air permeability, water penetration, wind resistance, impact) have lead times that must be planned when details are approved, not when fabrication starts. Where the wall build-up relies on system fire performance, the test evidence must match what is actually being built, not merely resemble it. A review that signs off a detail with no identified route to test evidence is signing off a risk. Our CWCT testing evidence guide covers what that evidence needs to show and how to keep it connected to the as-built record.

Design Lead's Action Plan

Design leads can implement systematic improvements without inventing a new process:

• Establish early contractor involvement protocols, with named specialist input before each stage sign-off
• Mandate technical review checkpoints (structural, thermal, movement, fire) with the evidence for each recorded, not just the outcome
• Keep one register of comments and decisions; ban review-by-email for anything that changes a detail
• Require constructability analysis before approval, with fabricator and installer eyes on the details
• Validate performance against the specification, with test evidence identified and programmed at review stage
• Assign interface ownership by name for every facade junction: an interface without an owner is a defect waiting for a date

Keep the Decision Trail

Every item above produces records, and the records are where most review processes quietly fail. Comment trackers in Excel, approvals in email and photos in WhatsApp are where design review evidence goes to die: unanchored, unsigned and unfindable when a dispute or a regulator asks. The alternative is one living record, built as the work happens and anchored to the building, so the review history for any elevation, opening or detail is retrievable with its context intact. That is the approach BrieXO takes for envelope contractors: see BrieXO for facade contractors and our guide to Building Safety Act compliance software.