Study RIBA Part 3 as a set of role-and-instrument decisions: for every scenario, first state which hat you wear, then state which document you are entitled to issue, and only then decide the action. Build this habit with a certificate chronology drill and two-role scenario annotations.
Which hat are you wearing? Separating designer, contract administrator and duty-holder duties
Scenarios place you in one role at a time. Before acting, name the role that authorises the action, because the same architect on one job may hold appointment-based, contract-based and statutory duties with different limits.
On a typical UK project, the architect may act as lead designer under the client appointment, as contract administrator under the building contract, and as a duty holder under construction safety legislation. These roles draw authority from different documents, owe duties to different parties, and impose different constraints. Treating them as one blended job description is the underlying confusion this exam is built to probe.
Turn every practice question into a role annotation exercise. Underline each action in the scenario and label it: designer duty, administrator duty, statutory duty or business duty. If you cannot label an action confidently, you have found a syllabus gap, not a wording problem. Repeat this on five scenarios and the role boundaries become visible patterns rather than memorised lists.
Practical completion versus making good defects: what each certificate actually triggers
Each contract certificate changes the legal position in a specific way: possession, retention, the defects period and insurance can all hinge on it. Learn every certificate as issuer, trigger, consequence and evidence, never as a name alone.
Scenario one: the contractor asks for the practical completion certificate while a list of snags remains outstanding, arguing the building is usable. A weak response is to certify informally and sort the list out later. A stronger response is to inspect, record the outstanding items in writing, judge whether they genuinely prevent the intended use of the building, and either certify with a clearly scheduled list of remaining work or defer certification with written reasons.
The reason the distinction matters is consequence: practical completion typically starts the defects period, releases part of the retention and transfers possession, while the making-good-of-defects certificate closes that period after rectification. A scenario answer that names the certificate but cannot state what changes when it is issued will read as guesswork. Build a one-line consequence note under every certificate name in your notes.
Building Regulations sign-off versus contractual completion: two approvals you must not merge
Statutory approval and contractual certification sit on separate tracks with different issuers. Building control confirms regulatory compliance; the contract administrator certifies completion under the contract. Neither substitutes for the other in a scenario answer.
Trace both tracks on one paper timeline. The statutory track runs from building control submission through plan checking and site inspection to the building control body's confirmation of compliance with the Building Regulations. The contractual track runs through the contract administrator's inspections, certificates and statements under the building contract. They interact in practice, but they answer different questions: is the building lawful, and has the contractor performed?
When a scenario shows a client pressing you to treat a building control sign-off as the end of the contractual process, your answer should separate the two and explain what remains open on each track, such as unrectified defects or outstanding contractual obligations. Practise writing three sentences per track rather than one merged paragraph; the separation itself demonstrates the understanding being assessed.
The Architects Code versus RIBA guidance: which standards bind you and when
The Architects Code, maintained by the Architects Registration Board, sets the standards tied to registration; RIBA membership materials provide separate guidance and support. Argue scenario answers from Code-level duties first, then layer guidance on top.
Registration with ARB is what permits use of the architect title in the UK, and the Code sets expectations of honesty, integrity, competence and professional conduct that apply to registered architects. RIBA offers its own membership framework, learning resources and practice support. These are related but distinct systems: a scenario about conduct obligations should be reasoned from the registration-level Code, not from membership materials, and vice versa for questions about professional community expectations.
Apply the layering with an example: a client instructs you to omit a fire-stopping detail to save cost. Your reasoning should move through statutory compliance, then Code-level duties such as honesty and not compromising standards you have certified or endorsed, then contractual and appointment consequences, and only then practical negotiation. Reading the Code actively, asking what each standard demands in a site situation, converts it from reference text into usable exam reasoning.
Matching procurement route to appointment and contract: a decision you must justify
Procurement choices reshape who holds design responsibility and who administers the contract. When a scenario changes the route mid-project, your job is to state what changes for your role, your appointment and your liabilities.
Scenario two: a client whose project you designed decides mid-stream to move to a design-and-build arrangement. A common misstep is to keep answering as though your contract administrator role simply continues. The better decision is to address the change directly: design responsibility may transfer to the contractor, your continuing role may shift, and your appointment and fee basis need review before you sign anything. State those consequences explicitly, in order, rather than describing the procurement route in general terms.
Contrast this with the traditional route, where design is completed largely before tendering and the contract administrator typically certifies on behalf of the employer under the contract. The comparison is the point: same architect, same building, different allocation of design risk, different documents and different limits on your authority. Practise explaining a route by what it does to roles, not by listing its stages.
| Role | Source of authority | Core function | Typical limit |
|---|---|---|---|
| Contract administrator | The building contract | Administers the contract between employer and contractor, including certificates | Acts under the contract's terms, not as the contractor's or employer's advocate |
| Employer's agent | The employer's appointment | Acts on the employer's behalf, commonly where the contractor holds design responsibility, and in that arrangement typically performs the certification functions the contract allocates to the employer's side | Its scope, including what it may certify, is defined by the employer's appointment and the contract provisions that engage it, so always check the source of authority before attributing duties |
| Principal designer duties | Construction safety legislation | Coordinates health and safety in the pre-construction phase with other duty holders | A distinct statutory role; holding it does not follow automatically from being the architect |
| Clerk of works | The employer's team | Day-to-day observation and reporting on site quality | Observes and reports; does not issue contract certificates |
The certificate chronology drill: one exercise that exposes your real gaps
Take one paper project from appointment to final account and list every certificate, notice and statutory approval with its issuer, trigger and consequence. Blank rows reveal exactly which concepts need study.
Run the drill in three passes. First, list the instruments in date order as they would arise on the project. Second, for each one write the issuer, what triggers it, and what changes legally or financially when it is issued. Third, mark which instruments belong to the statutory track rather than the contractual track. Passes two and three are where the learning happens; pass one alone just rehearses names.
Self-check rubric for the finished chart: every instrument has an issuer stated as a role, not a person's name; every consequence note names something that changes, such as possession, retention, defects liability or insurance; statutory and contractual instruments are visually separated; and you can explain any row aloud without notes. Treat a clean chart as a study milestone showing your map is complete, not as a prediction of any exam outcome.
- Row test: if you cannot state what changes on issue, the instrument is not yet learned.
- Role test: if two instruments share an issuer, check whether they belong to different tracks.
- Scenario test: give one sentence per row on what you would tell the client when it is issued.
A preparation sequence built on decisions, plus concrete readiness checks
Sequence your study by decisions rather than topics: framework week, instruments week, then alternating scenario and role-annotation weeks. Finish when you can explain any role boundary and certificate consequence without notes, under time pressure.
A realistic adaptable sequence: week one, read the Architects Code and map your own project's roles and duty-holder positions; week two, complete the certificate chronology drill from the previous section; weeks three and four, work past-style scenarios daily, annotating roles first and drafting the action second; week five, write full timed answers and compare them against the rubric. Shift the weighting toward whichever drill keeps exposing gaps rather than following the schedule rigidly.
Readiness checks before you sit: you can state, without notes, what changes when each major certificate is issued; you can separate the statutory and contractual tracks on a blank timeline in under five minutes; you can label the role behind any action in a fresh scenario; and you can distinguish Code-level duties from guidance in your own words. Administrative matters such as eligibility, dates and fees change, so confirm those directly with ARB via arb.org.uk and with RIBA via architecture.com rather than relying on any study material, including this one.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.