OAA Admission Exam common mistakes
OAA Admission Exam · Understand the traps and how to avoid them.
Answering professional-conduct scenarios by instinct ('what a good architect would do') rather than by the specific obligation the regulator imposes, such as conflict-of-interest disclosure, the duty to report unlicensed practice, or the limits of an architect's authority to certify work.
Candidates rely on general workplace ethics and personal judgement, and never memorise the jurisdiction's licensing act, code of ethics, or the exact wording of duties like sealing drawings, supervision obligations, and continuing-education requirements.
What to do instead
Build a one-page map of the governing act and code of ethics: list each duty, who it is owed to (client, public, regulator), and the required action when breached. For every practice question, ask 'which specific clause is triggered?' before choosing an answer, and drill the distinctions between disclosure, avoidance, and consent.
Treating contract administration duties as interchangeable, for example confusing the architect's role in issuing a certificate for payment with certifying the contractor's compliance, or issuing a site instruction where a formal change order is required.
The roles of certifier, designer, and contract administrator overlap in practice, and candidates learn the workflow informally on projects without separating the legal consequences of each document.
What to do instead
Tabulate each instrument (site instruction, change order, certificate for payment, certificate of substantial performance, field review report) with its issuer, its evidentiary weight, and what it does and does not certify. Practise scenario questions by first naming the instrument the situation calls for, then the correct authority and timing.
Selecting a building assembly or system based on the most familiar product rather than on the governing performance requirement, such as choosing a wall assembly without checking its fire-resistance rating, or sizing a service without confirming the required load or redundancy.
Candidates default to assemblies they have seen on past projects and skip the step of deriving the requirement from occupancy, building height, and exposure before selecting the assembly.
What to do instead
Adopt a fixed sequence for every technology question: identify occupancy and building characteristics, derive the required rating or capacity, then evaluate the assembly against it. Memorise the standard fire-resistance and sound-transmission values for common assemblies and the conditions that void them (penetrations, unsealed joints, missing firestopping).
Ignoring building-science sequencing, for example placing a vapour retarder on the wrong side of the insulation, omitting continuity of the air barrier at junctions, or detailing a roof without addressing thermal bridging and drainage slope.
Candidates study components in isolation and never practise tracing control layers (water, air, vapour, thermal) continuously through wall, roof, and foundation junctions.
What to do instead
Redraw typical wall-roof-foundation junctions from memory and mark each control layer with its continuity path. For each detail question, check the four control layers in order and ask where each is interrupted. Learn the climate-based rule for vapour-retarder placement and the consequences of getting it wrong.
Applying the code requirement from the wrong occupancy or building classification, for example using the egress width, travel distance, or sprinkler trade-off for a group that does not match the scenario, or missing that a mixed-use building must be evaluated under separated or non-separated provisions.
Candidates memorise numbers without the classification framework, so they recall a value but not the conditions under which it applies.
What to do instead
Practise classifying scenarios first (occupancy group, construction type, height and area, sprinklered or not) before looking up any number. Create a decision tree that leads from classification to the applicable egress, fire-separation, and accessibility requirements, and test it against varied scenarios.
Answering accessibility questions from general intent ('make it accessible') instead of the specific dimensional or technical requirement, such as turning-space dimensions, grab-bar placement, ramp slope and landing requirements, or the exceptions for existing buildings.
Accessibility provisions are numerous and exception-heavy, and candidates skim them assuming intent-based answers will suffice.
What to do instead
Memorise the small set of high-frequency dimensions and clearances, and pair each with the element it governs. For each question, identify the element and the standard that governs it, then check whether an exception applies. Drill the differences between new construction, alterations, and upgraded existing buildings.
Misreading the contract's risk-allocation clauses, for example assuming the owner bears unforeseen site conditions, treating a design-build or stipulated-sum arrangement like a standard general contract, or missing the notice period that preserves a claim.
Candidates learn one contract form well and transfer its assumptions to other delivery methods and standard forms with different allocation of risk.
What to do instead
Compare the major delivery methods and standard contract families side by side on a fixed set of issues: design responsibility, site-condition risk, change pricing, notice periods, dispute resolution, and suspension and termination. For each scenario, identify the contract type first, then the clause that allocates the risk in question.
Confusing schedule and cost control techniques, such as treating a critical-path float as slack available to any party, using earned-value terms interchangeably, or approving a time extension without tracing the delay to the critical path.
Candidates memorise definitions without working through how float ownership, concurrent delay, and progress measurement interact in an actual claim.
What to do instead
Work short numerical exercises: compute total and free float, identify the critical path after a delay, and classify delays as excusable, compensable, or concurrent. Practise earned-value calculations and interpret each index rather than just recalling its formula.
Rushing the scenario stem: skimming a long fact pattern and selecting the first plausible option without noting the qualifier ('EXCEPT', 'best', 'first action') or the facts that rule out alternatives.
Under time pressure, candidates pattern-match on keywords and stop reading once an option looks familiar, which is exactly when distractors designed around common assumptions catch them.
What to do instead
Adopt a fixed reading protocol: paraphrase the question's actual ask, underline qualifiers, list the constraints given, then eliminate options that violate a stated fact. Practise with timed sets and review every error by writing why each rejected option was wrong, not just why the chosen one was right.
Managing time uniformly across the paper, spending equal effort on unfamiliar topics and on high-yield ones, and leaving multi-part scenario sets unfinished or guessed at the end.
Candidates do not know their own error profile, so they cannot triage, and they have not rehearsed pacing against the real section structure.
What to do instead
Take a diagnostic under timed conditions, rank domains by error rate, and allocate study time inversely to accuracy. In the exam, answer confident items first, flag and return to long scenarios, and never leave blanks. Rehearse full-length timed sections at least twice before the exam to lock in pacing.