Architectural Guide Notes

Architectural Guidance defined what the design must satisfy; the Guide Notes package it for the reality of procurement and delivery — the document set an appointed design team is briefed with, prices against, and is reviewed against through every design stage. This is where strategy meets the machinery of RIBA stages, tender packages and value-engineering rounds. Guide Notes that arrive as strategy prose get translated by the delivery process into its own defaults; Guide Notes structured as briefing instruments keep the evidence in command through the two years in which most workplace strategies are quietly unmade.

• In Deliver, as the final consolidation before design team briefing or procurement
• At design-stage gates, as the review standard
• Updated through Living Workplace Outputs when model changes revise requirements mid-delivery

• Strategist consolidating with the project manager
• Architect and interior architect as receiving parties
• Cost consultant, so the brief and the budget meet before tender rather than at it
• IT, FM, accessibility and sustainability leads validating their briefs
• Change lead attaching the behaviour-and-change brief

• Architectural Guidance with its performance criteria and verification methods
• Kit of Parts with quantities and requirement profiles
• Stacking and blocking model and zone plan
• Programme of requirements in its accepted form
• Budget envelope and procurement strategy
• Project timeline and phasing from the implementation roadmap

1. Assemble the functional brief: what the workplace must do, population by population, drawn from the demand evidence — the 'why' the design team needs to design with rather than merely comply with.
2. Assemble the spatial brief: the programme of requirements, kit quantities, stack and zoning, adjacency and separation requirements — the quantified 'what'.
3. Attach the design intent per zone and setting family from Architectural Guidance, calibrated to invite design quality within evidence boundaries.
4. Package the specialist briefs: technology brief (room systems, booking, measurement infrastructure), environmental quality brief (the acoustic, lighting, thermal, air-quality criteria with verification methods), accessibility brief (base conditions, not annex), and the change and behaviour brief (the design features behavioural assumptions depend on).
5. Integrate the project-management implications: phasing, decant logic, dependencies between change milestones and construction milestones, and the decision points where governance re-enters.
6. Map every requirement to its design-stage verification: which criteria are reviewed at concept design, which at technical design, which at handover commissioning — so the review programme is built into the brief.
7. Reconcile with the cost plan before issue: a brief the budget cannot carry is a value-engineering schedule in waiting; better to make the trade-offs in governance now than in a contractor's spreadsheet later.
8. Issue as the contractual briefing basis and induct the design team against it — a walkthrough of the evidence chains, not a document transmittal.

• Brief–budget divergence discovered at tender, handing the trade-off decisions to the cheapest interpretation
• Specialist briefs (accessibility, environmental, change) issued as appendices and treated accordingly
• Requirements without stage-mapped verification, which surface as handover disputes
• The design team inducted by transmittal, absorbing the documents without the reasoning
• Mid-delivery model changes (a revised ratio, a reorganisation) never propagating into brief revisions

• Complete Guide Notes package: functional brief, spatial brief, design intent, kit, zoning, specialist briefs, project implications
• Stage-mapped verification programme
• Cost-reconciled brief with recorded trade-offs
• Design team induction record

The Guide Notes are the design team's contractual brief and every design review's standard. The verification programme structures stage gates through delivery. The change and behaviour brief synchronises the change programme with construction. Post-handover, the commissioning verifications become the first evidence Recalibrate's Post-Occupancy Evaluation builds on — the delivered workplace measured against what it was briefed to be.

Briefing is calibration: too prescriptive and the design team delivers compliance without quality; too open and the evidence dissolves into interpretation. Judging where each requirement sits on that spectrum — and which budget trade-offs to decide in governance before tender — is delivery experience the documents encode but cannot exercise.

• Issuing the strategy document as the brief and expecting the design team to extract requirements
• Skipping cost reconciliation, then losing the environmental layer to value engineering line by line
• Verification methods defined but never mapped to design stages
• Treating design team induction as optional
• Freezing the Guide Notes at issue while the living models move on without them

A financial services firm issued Guide Notes with every environmental criterion stage-mapped: acoustic performance reviewed at technical design against calculations, then at handover against commissioning measurements. When handover testing found three meeting-room classes missing their speech-privacy criterion, the verification record made it a contractual remediation, not a negotiation. The FM director's observation: previous projects had discovered the same failure eleven months in, through complaints — this one discovered it before occupation, through the brief.