ARE 5.0 common mistakes
ARE 5.0 · Understand the traps and how to avoid them.
Answering contract-administration items from the way their last office actually ran the job - assuming the architect can order the contractor to stop work, that the architect owns the construction schedule, or that submittal review is a dimensional/quantity check - instead of from the AIA A101/B101/A201 allocation of duties.
Most candidates learn contract administration by osmosis in a firm that has informal workarounds, so the office norm feels like the correct answer even when it contradicts the contract documents the exam is written against.
What to do instead
Build a three-column matrix (Owner / Architect / Contractor) for the 12 most-tested issues: means and methods, site safety, construction schedule, cost of the work, submittals and shop drawings, payment certification, substantial completion, rejection of nonconforming work, stop-work authority, warranty, changed conditions, and termination. For each row write the contract article reference and one sentence in your own words.
Studying almost exclusively from memorized fact lists and flashcard decks, then discovering on exam day that items are scenario- and document-based questions drawn from the NCARB exam guidelines and the published reference list.
Fact drilling gives fast, visible progress and a comforting sense of coverage; reading a code chapter or a contract document gives slower, less measurable progress, so it gets deferred until it never happens.
What to do instead
Anchor the study plan to the division's official exam objectives and its published reference list. For each objective, do at least one pass through a primary source (the code chapter, the contract document section, the reference text) and write a one-page summary in your own words before touching practice items on that topic.
Reading a case-study scenario and immediately selecting the option that reflects the generally correct professional practice, without first testing the options against the specific constraints stated in that scenario (a stated budget cap, an existing structural grid, a client's ranked priorities, a fixed milestone date).
Long scenarios create time pressure and cognitive load, so the brain pattern-matches to the last familiar concept instead of holding the stated constraints in working memory.
What to do instead
Before looking at the options, write one line: 'The binding constraint is ____.' Then eliminate any option that violates a hard constraint or a stated fact, even if it is otherwise good practice. Only compare the survivors on quality. Practice this on every case-study item until it is automatic.
Sinking five or more minutes into a single calculation or case-study item, then rushing the final third of the division with unreviewed flagged items and unanswered questions.
Candidates treat every item as equally weighted and are reluctant to abandon work already invested, so one hard item consumes the budget for four easy ones.
What to do instead
Set a per-item ceiling (roughly two minutes on average for a multiple-choice division) and a hard rule: if you have not reached an answer after one full attempt plus one re-read, flag it and move on. Do at least two full-length timed practice runs where you practice the abandon-and-return loop, and complete the official tutorial/demo to rehearse the item interfaces (hotspot, drag-and-place, case-study navigation) so interface learning does not eat exam time.
Treating Programming & Analysis items as design-preference questions - picking the scheme or option the candidate personally likes rather than the one supported by the collected data, the validated needs statement, or the site and code constraints that programming analysis is supposed to surface.
Architects are trained to jump to synthesis; analysis and information-gathering feel like the slow part before the 'real' work, so candidates under-practice it and default to design intuition.
What to do instead
For every P&A item, ask first: 'What information must be gathered, measured, or verified before a decision can be made, and who owns that information?' Write a short programming brief from a real or invented project - goals, facts, needs, constraints - and practice deriving area tabulations and adjacency requirements from it rather than from a preferred parti.
Quoting code and accessibility numbers from memory without the condition or unit basis attached - reciting a turning-space dimension without the approach direction, using an occupant-load factor with the wrong gross-versus-net basis, or quoting an egress-width-per-occupant figure without distinguishing stairways from other components and sprinklered from nonsprinklered conditions.
Studying produces numbers stripped of their context, and the exam items are written precisely to test whether you know which condition the number belongs to.
What to do instead
Build a one-page number sheet with three fields per row: the number, the exact condition it applies to (including gross vs. net, sprinklered vs. not, and approach direction), and the source citation. Rebuild the sheet from the code itself each time you review, and refuse to add a number you cannot state the condition for.
Handling site-planning and massing items by eye - sketching a footprint or height without actually computing the buildable envelope from floor area ratio, lot area, setbacks, height limit, lot coverage, and parking or open-space requirements, and without checking which of those controls is the binding one.
Zoning math is taught as a list of definitions rather than as a sequence of checks, so candidates approximate the arithmetic under time pressure and pick a plausible-looking answer.
What to do instead
Drill a fixed five-step sequence on every site item: (1) compute maximum gross floor area from FAR times lot area; (2) apply setbacks to get the buildable footprint; (3) apply the height limit and count floors; (4) check lot coverage and open space; (5) identify which constraint governs and state it in one sentence. Run the sequence on at least ten different lot geometries until the arithmetic is fast.
Answering building-envelope and assembly items by choosing familiar materials or details rather than tracing each control layer - water, air, vapor, thermal - and its continuity from foundation through wall to roof, including penetrations, transitions, and the location of the dew point relative to the insulation.
Candidates recognize assembly names and assume recognition equals understanding, so they never practice asking 'where does this layer stop, and what happens at the junction?'
What to do instead
Take four common wall types and draw the four control layers as continuous colored lines over a section from footing to parapet. Mark every discontinuity and write the flashing, sealant, or transition detail that resolves it. Then answer detail items by checking each control layer against your diagram, and explicitly reject options that create a thermal bridge or leave a layer unsealed at a transition.
Not knowing what is expected at each phase of documentation - confusing schematic design, design development, and construction documents in terms of level of detail, drawing types, specification development, coordination with consultants, and what the architect is obligated to deliver at each stage.
In practice, phase boundaries blur and candidates work inside a single phase for years, so they never build an explicit phase-by-deliverable map and treat the phases as labels rather than as defined scopes.
What to do instead
Create a phase-by-deliverable grid: phase across the top, deliverable categories (drawings, outline versus final specifications, cost estimate type, consultant coordination, owner approvals, code review, permit submission) down the side. Fill it from the owner-architect agreement's description of basic services, then test yourself by sorting a shuffled list of drawing and document types into the correct phase without looking.
Conflating construction-phase roles and authorities - treating the architect's submittal review as a guarantee that the contractor's quantities and dimensions are correct, treating the architect as able to direct the contractor's means, methods, or safety program, or confusing the architect's authority to reject nonconforming work with authority to order the work stopped or to refuse to certify payment.
These are the items where the intuitive 'the architect is in charge of quality' instinct directly contradicts the contract's allocation of risk, and candidates answer from instinct rather than from the documents.
What to do instead
Write out, with citations, the four distinct CA actions and who holds each: rejection and correction of nonconforming work, stop-work order, submittal review scope and its stated limits, and certification of amounts due based on the architect's observations. For each, write one sentence beginning 'The architect does not...' Then answer CA items by naming which of the four actions the question is actually about before evaluating options.