HKIA/ARB PA Paper 2 common mistakes
HKIA/ARB PA Paper 2 · Understand the traps and how to avoid them.
In the Case Study, you read the scenario once and immediately start writing the answer, without first listing the constraints (site area, plot ratio, permitted use, client budget, statutory submissions) that the question actually tests.
Time pressure makes candidates treat the case as a comprehension exercise rather than a design-and-compliance problem; the scenario is long and it feels productive to start writing prose early.
What to do instead
Spend the first 5–8 minutes building a one-page constraint table from the scenario (numbers, regulations named, client priorities, red flags), then answer only against that table and check each paragraph maps to at least one constraint. Practise on past-style cases under timed conditions.
You answer the Case Study in general professional terms ('consider the OZP', 'consult the client') without citing the specific statutory instruments, submission stages, or authorities the scenario implies.
Candidates memorise broad process language and default to it when unsure of the precise ordinance or authority; the marking rewards specificity that generic phrasing cannot supply.
What to do instead
Build a one-page reference of the core Hong Kong statutory and administrative framework (Buildings Ordinance and regulations, town planning process, Lands Department lease control, Buildings Department submission and consent stages, OP/ occupation permit sequence) and rehearse naming the correct instrument and authority for each issue type.
You ignore the commercial and programme dimension of the Case Study - fee, cash flow, procurement route, consultant appointments, programme risk - and write a purely technical or design answer.
Architectural training and exam revision focus on design and compliance; candidates underestimate how much the case tests professional practice and business judgement.
What to do instead
For every case, force a short section on procurement and appointment strategy, fee basis, programme milestones, and risk allocation. Use a template: client brief → procurement → appointments → statutory programme → fee and cash flow → risks and mitigations.
In the Professional Interview, you give textbook definitions instead of narrating your own project experience with your specific role, decisions, and outcomes.
Candidates fear revealing gaps in experience or being challenged on details, so they retreat to general theory; interviewers probe for authentic, first-hand judgement.
What to do instead
Prepare 6–8 structured project stories (situation, your role, the professional issue, your decision, the outcome, what you would do differently), each 2–3 minutes, covering design coordination, statutory approval, contract administration, and a conflict or ethical dilemma.
When asked about a regulation or procedure you are unsure of, you invent a plausible-sounding answer rather than stating what you know and how you would verify it.
Interview nerves and the belief that admitting uncertainty fails the candidate; in practice, fabricated detail is far more damaging than a bounded, professional answer.
What to do instead
Rehearse a 'bounded answer' formula: state the principle you are confident about, name the source you would check (ordinance, practice note, PNAP, contract clause, senior colleague), and describe the verification step. Never invent section numbers or figures.
You cannot discuss the ethical and professional-conduct dimensions of a scenario - conflict of interest, pressure to certify or sign off prematurely, fee-cutting, gifts, or client instructions that conflict with statutory duties.
Candidates prepare technical and design content but treat ethics as abstract; they freeze when asked what they would actually do under pressure.
What to do instead
Prepare a decision framework (identify the duty owed, to whom, the relevant code or ordinance, the risk to safety and the public, the escalation route) and rehearse 3–4 realistic dilemmas, including one involving a contractor and one involving a client's commercial pressure.
You treat the two parts as separate exams and do not connect them - the Case Study answer never draws on practice experience, and the Interview never demonstrates the analytical structure used in the case.
Revision is siloed by paper; candidates do not realise the same professional judgement is being assessed in different formats.
What to do instead
Use the same analytical template (brief, constraints, statutory route, procurement, risk, ethics) in both. When practising the case, speak the answer aloud as if in interview; when preparing interview stories, write the constraint-and-decision structure used in the case.
You misallocate time: over-writing the first Case Study question until it is exhaustive, then leaving later questions with skeletal answers or none at all.
The first question feels safest and candidates chase completeness on it; without a timed rehearsal they have no calibrated sense of pace.
What to do instead
Before the exam, set a per-question minute budget from the marks available and practise to it at least twice. In the exam, write the budget on the answer sheet, move on when the time expires, and return only if time remains.
You answer the question that was asked in a different form - for example, producing a design narrative when the question asks you to advise the client on options, or listing regulations when asked to evaluate a proposal.
Under pressure, candidates latch onto familiar content and the verb in the question ('advise', 'evaluate', 'justify', 'compare') is skimmed rather than parsed.
What to do instead
Underline the command word and the object of every question before writing, and open each answer with a one-sentence statement of what you are doing (e.g. 'I will compare two procurement routes against the client's programme and cost constraints'). Re-read the question after drafting to confirm the answer matches the verb.
In the Professional Interview, you cannot explain the contractual and administrative mechanics of a project you claim experience on - payment terms, variation and extension-of-time procedures, certification duties, or the architect's role under the contract.
Candidates often have design-heavy experience and limited exposure to contract administration, and they assume general involvement is enough; interviewers test depth by drilling into process.
What to do instead
For each project story, prepare the contractual layer: which form of contract, the architect's duties and authority, how instructions and variations were handled, how progress and final accounts were certified, and one dispute or risk you managed. Read the relevant contract conditions and your own project records before the interview.