What the ARE 5.0 asks you to do
The Architect Registration Examination (ARE 5.0) is a computer-based exam taken in separate divisions. It uses selected-response items and case studies with exhibits such as drawings, specifications, contracts and code excerpts. In a case study, the task is to navigate the information provided and apply it to a realistic situation—not simply recall a fact from memory.
Across divisions, you need to connect technical knowledge, codes and standards, and professional practice decisions. Those decisions may involve competing constraints: scope, time, cost and risk. A sound preparation method therefore trains two things together: knowing the underlying concepts and using evidence to make a defensible decision.
The exact division names, current exam policies and official content descriptions can change. Check the official NCARB website for the current ARE 5.0 information rather than relying on an old study schedule or a third-party summary.
Set up your material before you study
Start with the official content outline for the division you are preparing for. Use it to define the boundaries of your study, then assemble the material you will actually revise: your notes, course slides, practice problems, code references and professional-practice resources. Keep a record of the source and version of code or contract material; a remembered rule without its jurisdiction or document context can lead you astray.
Organise your revision by decisions you may need to make, not just by the names of books. For example, a building-code topic might connect occupancy and construction type to separations, egress and accessibility. A contract topic might connect the parties’ roles to submittal review, change documentation and risk. The point is to practise moving from a fact to a decision and then to the next action.
In MySummaries, the ARE examiner strip foregrounds the habits to practise across those topics:
Build a board around decisions
For each topic, make a compact revision board from your own source material. A useful section should help you answer a question: What facts matter? Which document supplies them? What rule or role applies? What should happen next? Keep key thresholds and definitions tied to their source and applicable context. If a rule depends on jurisdiction, occupancy, contract language or project conditions, record that dependency instead of turning it into an unconditional flashcard.
A board on a rooftop-equipment case ends up looking like this:
- Issued drawing schedule: rooftop unit is 600 lb
- Submittal: proposed unit is 850 lb
- Provided structural exhibit gives no joist capacity for the proposed load
- Compare the submittal with the issued equipment schedule
- Record the discrepancy and the information needed to evaluate it
- Follow the provided contract's process for a proposed scope or cost change
- Document the review and route the decision to the parties authorised by the contract
In this practice packet, the contractor is responsible for construction means and methods. The architect reviews the submittal for conformance with the contract documents; the excerpt does not authorise the architect to approve a change in scope or price.
Prioritise life safety and structural adequacy. State what is known, what remains unverified, who must provide the missing information, and what decision is on hold.
- A 250 lb difference is not evidence that the roof framing can support the proposed unit
- Request structural review using the proposed unit's weight, support points and equipment data
- Do not represent an unverified capacity as acceptable
Use the same structure for other areas: a drawing coordination issue, a code analysis, a specification question or a professional-practice decision. Keep the distinction between a project fact and an assumption visible. In case studies, that distinction prevents you from importing a detail that the exhibits do not give you.
Practise selected-response items as decisions
For selected-response practice, do more than memorise the right option. After answering, explain why it is best and why the strongest distractor fails. Is the distractor based on a wrong role, an unsupported assumption, a life-safety risk, or a step taken out of sequence? That explanation becomes the useful part of the question.
When you miss an item, record the concept and the reasoning error separately. “I forgot the rule” needs a different review from “I used a correct rule without checking the provided project facts.” Revisit the source material for the first. For the second, practise extracting and citing relevant exhibit information before choosing an action.
Work case studies in a repeatable sequence
Case studies reward controlled document use. Practise a short routine:
- Read the task first. Identify exactly what the question asks you to decide, calculate, identify or recommend.
- Find the relevant exhibit. Use the document list and headings to locate the drawing, specification, contract excerpt or code material that bears on the task.
- Extract the facts. Note the information that affects the answer. Separate stated facts from assumptions and missing data.
- Apply the rule or role. Use the applicable technical concept, code excerpt or contract language in the supplied material. Check the conditions and scope of the rule.
- Choose and support the action. Give the decision, point to its evidence, and identify the next step or required documentation where relevant.
A practice case should include deliberate distractors: a proposed change that differs from the drawings, an incomplete technical submittal, or a request that exceeds a party’s authority under the supplied contract excerpt. Do not treat every discrepancy as a request to redesign the project. First establish what the exhibits say and what process applies.
Here is a marked example from a practice case. The score and feedback below are MySummaries’ practice assessment, not an ARE score or official marking scheme.
The equipment schedule shows a 600 lb rooftop unit. The contractor submits an 850 lb unit and asks the architect to approve it. The structural exhibit provides no capacity for the proposed unit. Based on the supplied contract excerpt, identify the immediate response and the information or workflow needed before the change can proceed.
7/9I would not approve the unit as submitted. The proposed equipment is 250 lb heavier than the scheduled unit and the structural exhibit does not establish capacity. I would request structural review and the equipment data. The architect should review the submittal for conformance, while the contractor remains responsible for means and methods. A change in scope or price must follow the contract process.
The answer uses the relevant schedule and structural exhibit, identifies the unverified load and distinguishes the architect’s review from the contractor’s responsibility. It also recognises that a scope or price change needs the contract process.
Missed
−State that the discrepancy and pending information should be documented and routed to the parties authorised by this project’s contract before treating the change as accepted.
Model answerDo not approve the proposed unit as submitted: the schedule identifies a 600 lb unit, while the submittal is 850 lb, and the structural exhibit gives no capacity for that proposed load. Request the equipment data and structural review needed to assess the loading and support conditions. Under the supplied excerpt, the architect reviews for conformance with the contract documents; the contractor retains responsibility for means and methods. Record the discrepancy and the information requested. If the proposal changes scope or price, use the contract’s stated change process and route the decision to the authorised parties.
That is a MySummaries paper, filled with ARE material. Yours is written from your own notes. Start free
Review the missed point while the case is still fresh. Write a concise correction in your own words, then return to the source document and confirm that it supports the correction. Avoid memorising the model answer as a universal rule: the specific contract excerpt and project facts govern this example.
Review core knowledge without flattening context
A short “must not miss” checklist is useful when it preserves the conditions attached to an answer. It should remind you how to reason, not imply that every project follows the same contract or code provisions.
A core checklist for this case might be:
For code-related revision, use a similar checklist but attach each requirement to its context. Record the occupancy or use, construction type and relevant separations or egress facts when those are provided. Then check the applicable code excerpt and document how it supports the conclusion. If the case does not supply an essential fact, identify the gap rather than quietly assuming an answer.
Make each study session produce something
A productive session has a clear output. For example, spend one session building a board from a topic, another answering a small set of practice questions, and another working through exhibits under a time limit you set for practice. After each session, update your error log and decide what to revisit. The practice limit is your own training tool, not a statement about the official exam’s timing.
A useful rhythm is to alternate knowledge review with application. First retrieve a concept from memory; next apply it to a short scenario; then check the source and correct your reasoning. At the end of the week, revisit the errors that recur. If you repeatedly miss roles and workflow, do not spend the next session rereading a technical chapter that you already understand.
Audio can help you revisit a board while away from your desk, but treat it as another explanation of your notes, not a substitute for reading drawings, specifications or code excerpts. A lecture on the rooftop-equipment board could walk through the decision sequence aloud:
Transcript · tap any word to jump there
Start with the task: the contractor has asked for approval of a proposed rooftop unit. Before deciding, compare the submitted equipment with the issued schedule. The schedule says 600 pounds; the submittal says 850. That difference is a project fact, not proof that the structure can or cannot support the proposed unit.
Now check the structural exhibit. It gives no capacity for this proposed loading. Do not fill that gap with an assumption. Identify the equipment information and structural review needed to evaluate the proposal, and make clear that the current documents do not establish that the change is acceptable.
Finally, use the contract excerpt rather than relying on a general idea of what an architect can approve. Here, the architect reviews the submittal for conformance, while the contractor is responsible for means and methods. Document the discrepancy and follow the stated process for any change in scope or price, routing it to the parties authorised by this project’s contract.
Check progress by the errors you can now correct
Do not judge readiness only by how many pages you have read. Track whether you can find the right exhibit, explain why an option is wrong, distinguish facts from assumptions and identify the next action in sequence. When an answer is incomplete, label the cause: knowledge gap, missed exhibit, misread role, weak prioritisation or incomplete documentation. Each label points to a different repair.
When reviewing current exam requirements or a code question whose jurisdictional context is unclear, use the official source rather than guessing. Your practice should build a reliable method for applying the information in front of you—not confidence in a rule detached from its conditions.
How MySummaries helps
MySummaries lets you build a revision board from your own PDFs, slides and photographed notes, then generate flashcards, written practice and audio from that material. For ARE preparation, use a board to keep exhibit facts, technical checks and contract workflow together; use written practice to rehearse a supported decision and review what you missed. Start at portal.mysummaries.app.