SLIA Part III common mistakes
SLIA Part III · Understand the traps and how to avoid them.
When a scenario asks who is liable, the candidate answers by naming the party who physically caused the defect (e.g., the contractor) instead of first establishing the contractual relationship and the architect's duty of care to the client.
Candidates carry over a construction-site mental model where fault follows the physical act. Part III tests professional conduct, where liability flows from the appointment, the scope of services, and the standard of reasonable skill and care, not from who was on site.
What to do instead
Before answering any liability scenario, write down three things: who holds the appointment, what the scope of services actually says, and whether the architect had a duty to warn or to certify. Then assign liability against that chain. Practise with short scenarios where the physical causer and the contractually liable party are deliberately different people.
The candidate treats 'the architect should inform the client' as a complete answer to an ethical conflict, without identifying the specific conflict-of-interest rule, the need for written disclosure, or the option to decline the instruction.
Professional conduct questions reward naming the governing principle and the procedural step. Candidates give a plausible-sounding but incomplete answer because they reason from general good manners rather than from the code of conduct and its disclosure requirements.
What to do instead
Build a one-page conduct checklist: conflict of interest, confidentiality, competence limits, advertising and publicity, signing and certifying, and gifts or inducements. For each, memorise the required action and whether it must be in writing. Answer in the form 'identify the rule, state the disclosure, state the consequence of refusal'.
In statutory approval scenarios the candidate answers with the general building-regulation principle but misses the specific procedural step, such as which submission stage triggers which approval, who is the authority having jurisdiction, or what happens when work proceeds without approval.
Candidates learn the substantive technical requirements well but skim the administrative sequence of submissions, approvals, inspections, and occupation certification. The exam tests sequence and authority as much as substance.
What to do instead
Draw the full approval timeline from site investigation to occupation, and label at each node: applicant, authority, document submitted, statutory time limit, and consequence of non-compliance. Rehearse by taking a real project and mapping every approval it would need.
The candidate confuses the roles of the building authority, the planning authority, and the professional institute, attributing enforcement or disciplinary powers to the wrong body.
These bodies interact on the same project, so their functions blur under exam pressure. Candidates also assume the institute can compel design changes or that the building authority can discipline an architect.
What to do instead
Make a three-column table: body, legal basis, powers, and appeal route. Test yourself by writing, for each of ten hypothetical breaches, which body acts and what sanction it can impose. Keep the table to one page and revise it before the exam.
When asked about contract administration duties, the candidate lists generic activities (site visits, minutes, valuations) but cannot state the timing, the issuing instrument, or the consequence of failing to act within the stated period.
Candidates memorise the list of services from a fee scale or appointment document without studying the contract conditions that set periods for instructions, certificates, and notices. The exam asks about timing and instruments precisely because disputes turn on them.
What to do instead
For each standard form you are examined on, extract every clause that contains a number of days. Build a timeline of certificates and notices with the trigger event, the period, and the remedy for late action. Then answer practice questions by citing the clause type and the period.
The candidate answers a variation or payment dispute by describing what is fair, rather than by applying the valuation rules and the certification mechanism in the contract.
Fairness reasoning feels safe and is easy to write, but the examiner is testing whether the candidate can follow the contractual machinery. Candidates who have not internalised the valuation rules default to equitable language.
What to do instead
Learn the valuation hierarchy in the relevant form: rates in the contract, then analogous rates, then a fair valuation, and the notice requirements that make a variation valid. Practise writing short model answers that cite the mechanism, then the outcome, in that order.
On design and technology questions the candidate gives a performance outcome ('it will be waterproof', 'it will meet fire resistance') without naming the assembly, the test standard, or the failure mode being controlled.
Candidates revise from summary notes that describe intent rather than construction. They can state what a detail must achieve but not how the layers, joints, and fixings achieve it, which is what the question asks.
What to do instead
For each common assembly (roof, facade, wet area, fire compartment, thermal bridge), draw the section from memory and annotate: vapour control, insulation, drainage path, fire stop, fixing, and movement joint. Then state the standard or test that verifies it. Redraw until the annotations come without notes.
The candidate answers accessibility or fire-safety questions from memory of a similar project rather than from the current code edition, and does not flag where the code has changed.
Many candidates practise on older project experience or outdated study material, and the exam is set against the current edition. The error is invisible to the candidate because the answer feels familiar.
What to do instead
Work only from the current edition of the code and its amendments. Keep a change log of provisions that were recently revised, and for each one write the old rule, the new rule, and a one-line example. Date-stamp your notes so you know which edition you are citing.
In project management scenarios the candidate recommends a tool (a programme, a risk register, a meeting) without diagnosing the actual failure, such as unclear scope, late information, or an unapproved change.
Candidates reach for familiar project-control artefacts because they are easy to name. The scenario usually describes a governance or information-flow problem that a new document will not fix.
What to do instead
Use a fixed diagnostic order: scope and brief, information release, decision authority, change control, then monitoring. State the diagnosis in one sentence before recommending action, and make the recommendation address that diagnosis. Practise by writing the diagnosis alone, without the remedy, for ten scenarios.
The candidate runs out of time because they write long narrative answers to short-mark questions and then have no time for the scenario-based questions carrying most of the marks.
Narrative writing is the habit formed in design education, and candidates do not rehearse under time pressure. They also start with the questions they find easiest rather than the ones worth most.
What to do instead
Before the exam, calculate minutes per mark from the paper structure and write it on your rough sheet. In practice, allocate marks to bullet points, one bullet per mark, and stop when the bullets match the marks. Do two full timed papers and review where time was lost.