Treat every Part 2 scenario as three questions in sequence: which role am I in, which rules bind that role, and what can this role actually do next? Answers that reason before identifying the role tend to cite the wrong instrument, conflate the Architects Code with commercial preference, and recommend actions the named role cannot take. Build the triage habit first, then attach subject knowledge to it.
Deciding which role the scenario gives you before reasoning about duties
Before reasoning about any answer, identify which role the scenario assigns you — registered architect, contract administrator, employer's representative, or employee — because your duties, liabilities and available next steps change with each.
The same facts trigger different obligations depending on the hat you wear. Under the ARB framework, the duties in the Architects Code attach to you personally as a registered architect, whatever your employment status. As contract administrator you additionally exercise functions defined in the building contract, which are owed to the administration of that contract rather than to either party. As an employee, your practice's internal procedures never absorb those personal professional duties. Answers that mix these registers typically cite the wrong instrument for the problem in front of them.
The method is a four-line triage written before any full drafting: (1) my role in this scenario; (2) the governing rules for that role; (3) my immediate duties; (4) sequenced next steps. Apply it to a case where you are an employee and a principal asks for something questionable — your employment position does not suspend your Code obligations. Practise checking that every recommendation you draft is something your named role can actually take; if it is not, the role or the recommendation needs revising.
Reconciling client instructions with the Architects Code when the two collide
When client instructions conflict with the Architects Code, the Code's standards on integrity, competence and the public interest take priority. Your task is to advise, document, and where necessary decline — not to negotiate the standard itself.
ARB's Architects Code: Standards of Conduct and Practice sets the expectations for professionalism, competence and conduct, and ARB publishes supporting guidance alongside the current (2025) version. ARB's complaint categories include unacceptable professional conduct (UPC) and serious professional incompetence (SPI), and the same set of facts can engage either lens. This is why an answer that stops at 'the client insisted' resolves nothing: the Code asks what you, the architect, did next, not what pressure you were under.
Train a repeatable reasoning pattern for collisions: advise the client in writing of the professional constraint, offer compliant alternatives that serve the client's underlying aim, record the exchange, and escalate within the practice if the pressure continues. Then separate two judgments explicitly in your answer — 'commercially undesirable for the client' and 'professionally impermissible for me'. The first can be negotiated; the second cannot. Scenarios reward answers that show both sentences rather than collapsing them into one vague refusal.
Choosing between procurement routes by tracking where design risk sits
Compare procurement routes along three threads: who carries design responsibility, how much control the client keeps over design, and where cost risk sits. The defensible route depends on the scenario client's stated priorities, not a universal ranking.
In a traditional route the design team retains design responsibility and the client keeps close control, with cost certainty improving once tendered. In design and build the contractor takes design responsibility, which shifts risk but reduces the client's direct line to the designers and changes your own role — on such projects the client's representative is often an employer's agent rather than a contract administrator. Use the RIBA Plan of Work, which RIBA publishes as a shared staging framework, to locate when each procurement decision has to land in a project timeline.
In an answer, name the route, name its consequence, and tie it to the client's stated priority; a route described purely by its advantages, unlinked to this client, is the recurring slip to avoid. Also hedge honestly: two-stage approaches rearrange risk compared with single-stage, so qualify claims about 'the' risk position. Reproduce the comparison below from memory in revision, then adapt it to each scenario's client.
| Route | Design responsibility | Client control of design | Cost risk position | Best suited when |
|---|---|---|---|---|
| Traditional | Design team retains it | High throughout | Client carries tender and construction risk; better certainty post-tender | Client values design control and can absorb early cost uncertainty |
| Design and build | Contractor takes it | Reduced after employer's requirements | Contractor carries more cost risk | Client prioritises single-point responsibility and certainty over direct design control |
| Management-based | Designer retains; contractor manages | High, with works packaged separately | Client carries cost risk; trade packages tendered sequentially | Client needs early starts or design to continue during construction |
Administering variations and certificates without abandoning impartiality
A variation answered by an informal 'carry on' undermines your contractual function. Issue a written instruction through the contract's own mechanism, assess its cost and time consequences, and certify only on the contractual basis.
Worked scenario: you are contract administrator under a traditional contract. At a site meeting you comment that a partition could move; the contractor starts the work; the client emails 'get on with it, we'll sort the money later'. The plausible mistake is nodding the variation through verbally and certifying a negotiated figure weeks later. That course leaves cost and time unrecorded, treats your impartial administrative function as the client's advocacy, and creates exactly the muddle that conduct complaints are made of.
The better decision: confirm in writing that no variation instruction should be treated as issued until the contractual procedure is followed, then issue a proper written instruction with its value and time consequences assessed, and keep a contemporaneous record. The reason it matters is internal consistency — the contract administrator role is defined by the contract, so an answer in which you act as the employer's agent while holding that role contradicts itself. Note that the exact procedure depends on the contract terms in play: cite the contract, and study the mechanism rather than memorising one contract's wording.
Keeping registration, PII, CPD and title use watertight in scenarios
Registration, insurance and title are checkable facts inside scenarios: confirm the person is on the Architects Register, that PII arrangements are current, that CPD obligations are recorded, and that the word 'architect' is used only where permitted.
ARB is the UK's regulator, and the Architects Register is the definitive record — if someone is not on it, they are not an architect. ARB regulates use of the title, pursues misuse, and publishes guidance including on using the word 'architect' within company names. Build a scenario habit: when a vignette mentions a 'consultant' or 'designer', ask whether that person or company can lawfully be described as an architect in that context, and flag it if not.
On the practice side, ARB publishes professional indemnity insurance guidance and renewal advice, and runs a CPD scheme in which activities are recorded. Treat PII in answers as more than a business detail — the adequacy and currency of cover shapes what advice you can properly give about practising and taking on risk. Read through the headings of ARB's guidance notes (for example on reportable incidents, criminal convictions, and resigning from the Register) so you can name the relevant document when a scenario touches it, rather than gesturing at 'the rules'.
Handling errors, competence limits and complaints under public-interest scrutiny
When an error or a competence limit surfaces, stop and assess rather than absorb the risk. Disclose honestly to those entitled to know, take steps proportionate to the implications, and never let client loyalty suppress the concern.
Worked scenario: reviewing a detail near handover, you realise an earlier drawing you issued does not achieve what the specification assumed; the contractor built to the drawing; the client wants it 'fixed quietly' under a variation. The plausible mistake is amending the record without telling anyone, treating the matter as purely commercial. The better decision is to assess the implications — building safety, compliance, cost — disclose promptly and factually to the client, propose remedial options, and document everything. It matters because honesty and openness are Code standards: concealment converts a technical error into a conduct question.
Ground your escalation knowledge in ARB's published complaints framework: how a complaint is made, how ARB screens and investigates new complaints, and how the Professional Conduct Committee decides cases. Understand UPC and SPI as two distinct lenses — conduct versus competence — that can apply to the same facts. A useful drill is to write one sentence per ethics scenario on what the public interest requires, kept deliberately separate from the client's interest. This guide teaches study approach; it is not legal advice for real projects.
A preparation sequence, scored drill and readiness checks you can adapt
Build preparation around applying documents to situations: weekly scenario drills against the Architects Code, a procurement comparison you can reproduce from memory, and a self-check rubric scoring role identification, rule citation, interest-separation and sequencing.
Exercise: once a week, take one syllabus topic, write the four-line triage, then draft a 300-word scenario answer. Score it against a rubric out of ten — role named (0–2); governing rule cited specifically, not just 'the Code' (0–2); client interest separated from public interest (0–2); next steps sequenced and lawful for the role (0–2); documentation noted (0–2). Expected observations: early drafts typically state conclusions without naming a role and cite the Code generically; by the third weekly cycle, drafts should quote the specific standard heading. Treat rubric scores as learning milestones for your drafts, not predictions of any exam outcome.
An adaptable sequence: weeks 1–2, the Architects Code plus ARB guidance-note headings; week 3, procurement routes and the contract administration drill from section four; week 4, practice management — registration, PII, CPD, title use; week 5, design, sustainability and building technology applied only through scenarios, not as abstract reading; week 6, mixed timed drills scored with the rubric. Readiness checks: you can reproduce the triage from memory; compare two procurement routes in five lines; state the UPC/SPI distinction unaided; and match a fact pattern to the right ARB guidance note. Administrative details such as dates, eligibility and fees live with the issuer — check ARB and RIBA directly for those.
- Triage reproducible from memory: role, governing rules, immediate duties, sequenced next steps.
- Procurement comparison reproducible in five lines, then adapted to the scenario client's priorities.
- UPC versus SPI stated in one sentence each, with an example fact that could engage both.
- One ARB guidance note correctly matched to a given fact pattern (incidents, title use, resignation).
- Three consecutive weekly drill drafts scoring at or near your rubric target.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.