Architect Exam Prep: The ARE Podcast cover art

Architect Exam Prep: The ARE Podcast

Architect Exam Prep: The ARE Podcast

By: David Doucette & Eric Corey Freed
Listen for free

About this listen

 Listen in as David and Eric talk about issues aimed at candidates preparing for the NCARB Architect Registration Exam (ARE) . We discuss topics related to helping you become a better test taker as well as become a more valuable employee.2012-2026 Art Economics Education Leadership Management & Leadership
Episodes
  • 091. ARE Technical: Top 5 Tips for Programming & Analysis (PA)

    091. ARE Technical: Top 5 Tips for Programming & Analysis (PA)
    Mar 20 2026

    David and Eric discuss five tips for passing the programming and analysis (PA) division of the Architect Registration Examination (ARE). They emphasize that PA is about evaluation, not design, and highlight the importance of using highlighting tools for long, wordy questions. They stress that programming focuses on constraints before opportunities, using codes and zoning as filters, and that economics matter at a high level. Programming is about relationships and feasibility, not just square footage. They also note that PA questions are longer, providing more clues for candidates to use.

    Listen to the Audio

    Show Notes

    A. Setup & Mindset Shift

    • Why PA feels so different from PCM / PJM / CE and PPD / PDD
    • PA = gray area, long wordy questions, more about judgment than memorization
    • Bonus: practice using the exam highlighter—critical for PA’s long questions

    B. What PA Is Really About

    • Programming phase = problem seeking, not problem solving
    • No design yet: you’re evaluating constraints, feasibility, and relationships
    • You’re analyzing inputs: site, climate, soils, codes, zoning, owner’s program

    C. Five Core Tips

    1. Stop Designing – Evaluate, Don’t Solve
      • You haven’t designed anything yet
      • Compare options, surface risks, and recommend feasibility
      • Bubble diagrams and big‑picture fit, not plans and details
    2. Start With Constraints Before Opportunities
      • Environment + context: sun, wind, soils, climate, topography, neighbors
      • Look for what cannot be done first, then what could be done
      • Treat this as due diligence at the very start of a project
    3. Codes & Zoning Are Filters, Not Afterthoughts
      • Use setbacks, easements, FAR, occupancy, construction type as early filters
      • Goal: define the buildable area / envelope and check viability
      • You’re not doing deep PPD/PDD code work—just feasibility‑level analysis
    4. Programming = Relationships More Than Square Footage
      • Quantitative: room sizes, totals
      • Qualitative: adjacencies, privacy, sound, light, experience
      • Residential example: public vs. private zones, don’t dump a powder room on the kitchen
      • Good programs describe how spaces relate and feel, not just how big they are
    5. Economics Matter, But Only at a High Level
      • Rough cost per SF or per unit to test viability, not detailed estimates
      • Don’t blindly pick the cheapest option; PA is not a bid
      • Think: “Is this project basically viable on this site with this program?”

    D. How PA Connects to PPD & PDD

    • PA, PPD, PDD as three views of the same project at different scales
    • Studying PPD can make a PA retake easier (you see the “other side” of programming)

    E. Big Takeaway

    • You pass PA by thinking like an architect at the very beginning of a project:
      curious, constraint‑driven, feasibility‑focused, and comfortable in the gray area.

    Please Subscribe

    Receive automatic updates when you subscribe below!

    Please rate us on iTunes!

    If you enjoyed the show, please rate it on iTunes and write a review. It would really help us spread the word about the ARE Podcast. Thanks!
    Show More Show Less
    20 mins
  • 090. ARE Mentor: The Identity Shift

    090. ARE Mentor: The Identity Shift
    Mar 16 2026
    This episode, “The Identity Shift,” is for ARE candidates who are close to finishing but feel stuck or suddenly full of doubt. David reframes that experience as a normal transition from student to licensed architect, where imposter syndrome, fear of passing, and completion anxiety are signals of change—not failure. Listen to the Audio Show Notes I. Why the Final Phase Feels Different Heaviness of the last exams Often PPD/PDD: more technical and denseEmotional weight added because the end is near Perception of “struggling” Thoughts like “I don’t know anything,” “I’m not ready,” “Why is this harder now?”Core idea: you’re not struggling, you’re transitioning II. Common Emotional Patterns & “Misreadings” Imposter Syndrome Fear of being “found out” or exposed“People think I know all the answers because I’m about to be licensed”Normal and common across professions Fear of Passing (not just fear of failing) Anxiety about: “What comes next if I actually achieve this?”Unfamiliar emotion for many candidates Completion Anxiety What happens after finishing a long-term goal?Self-doubt, fear, and discomfort misread as “red flags”Reframed as signals of change and signs of transition III. The Core Concept: The Identity Shift From learner to decision-maker You’ve been in a learning phase (“sponge mode”) for 1+ yearsTransition to phase where you must: Make judgment callsTake ownership of decisions Change in professional identity From “ARE candidate/student” to licensed architectExpectations from others increase (even if already making decisions at work)Your input begins to carry more weight and influence Loss of the “student” comfort zone Student role feels safe: “Pressure isn’t fully on me yet”After licensure: harder to hide behind “I’m just a student”Brain reacts with self‑protection: “I’m not ready, I don’t know enough” IV. How the Brain Protects the Old Identity Delaying tactics Postponing exams (“I’ll take it in summer/fall when I’m more ready”)Easing off studying due to fear and doubt Attachment of big life decisions to licensure “Once I get licensed, I’ll…” Leave my firm / change jobsMove to a new city (e.g., NYC, Seattle)Get married / have a baby As licensure gets close, all those attached decisions feel suddenly “due” V. Readiness and What the License Really Means The myth of feeling “ready” Nobody truly feels ready to protect health, safety, and welfareARE tests minimum competency, not total mastery License as confirmation, not creation, of capability You’re already: Solving problemsExercising judgmentContributing to real projects License makes the ownership of that judgment more visible License as a “license to learn” Parallel to getting a pilot’s licenseLearning doesn’t end at licensure; it actually begins a new phaseArchitecture as a path of lifelong learning and growing responsibility VI. Practical Recommendations Don’t change your overall approach Keep your existing study system and strategy Focus on execution and routine Study habitsPractice examsTime managementKeep it simple and consistent Suggested study cadence Study 6 days/week, with Friday offEven 20 minutes/day counts—maintain daily “touches” to keep momentum VII. Final Mindset and Encouragement Embrace the transition Acknowledge fear, imposter feelings, and anxiety as normalSee them as signs you’re close to the finish line Double down on commitment Resist self-sabotage: Imposter talkSelf-doubtPostponing exams without real cause The reward on the other side Strong sense of pride, self-satisfaction, and accomplishmentYou “walk a little taller” at work as a licensed architect Core reassurance If you’ve come this far, you’ve earned the right to call yourself a licensed architect— you just need to cross the finish line. Please Subscribe Receive automatic updates when you subscribe below! Please rate us on iTunes! If you enjoyed the show, please rate it on iTunes and write a review. It would really help us spread the word about the ARE Podcast. Thanks!
    Show More Show Less
    20 mins
  • 089. ARE Technical: Top 5 Tips for Construction & Evaluation (CE)

    089. ARE Technical: Top 5 Tips for Construction & Evaluation (CE)
    Mar 13 2026
    This episode of the ARE podcast gives five key tips for passing the ARE Construction & Evaluation (CE) exam. The focus is on thinking like an architect under the AIA contracts, emphasizing standard of care, observation vs. construction, administrative procedures, question-reading strategy, and performance-focused closeout/post-occupancy work. Throughout, they stress judgment, restraint, documentation, and staying within professional/contractual boundaries. Listen to the Audio Show Notes Main Tips (1–5) 1. Answer from the Architect’s Contractual Role (Standard of Care) Always answer exam questions from the standpoint of the architect’s contractual role, not your personal or local practice.Think in terms of standard of care: What would any reasonably prudent architect do in this situation, based on the information given? Deep or specialized experience can hurt you on the exam if you override the “standard” approach with niche real-world habits.CE is a national, standardized test, not region-specific.Focus on: Roles, responsibilities, and authority during construction.Who has/produces/reviews which documents.Who can stop the work, what “observe” means vs. “inspect,” etc. 2. Construction Observation (Architect as Observer, Not Builder) In CE/Contract Administration, the contractor’s job: Build in conformance with the contract documents.The architect’s job: Observe whether work conforms to the contract documents and report findings to the owner.Key boundaries: Do not dictate means and methods—that’s the contractor’s domain.Shop drawings: Produced by the contractor, not by the architect.Architect reviews them only for design/esthetic intent, not for how to build.They are not part of the contract documents. Nonconforming work: The owner has the right to accept nonconforming work (A201).Architect must inform the owner of implications so they can make an informed decision. Field reports and site visits: Document date, time, weather, observed conditions.Not a guarantee or full inspection of all work.Architect only visits as frequently as the contract requires, often at agreed milestones (e.g., foundation completion, framing completion). 3. Administrative Procedures (The “AIA Way”) CE is less about technical minutiae (e.g., OSB vs. plywood) and more about admin processes and AIA contracts.Critical procedures and documents: Submittals & shop drawingsRFIsApplications for paymentLien release formsChange Orders (COs)Construction Change Directives (CCDs)Project ManualSubstantial Completion & Project Closeout Core contracts: A201 – General Conditions (owner/architect/contractor relationships and responsibilities).B101 – Owner–Architect AgreementA101 – Owner–Contractor Agreement Why the architect reviews applications for payment: Owner is not expected to understand construction.Since architect observes the work, they can verify claims like “50% framing complete.”Also logical for architect to review lien waivers in relation to paid work. “There’s the right way, the wrong way, and the AIA way”: For the exam, the AIA way is what matters, and it usually aligns with industry practice.Deviating from it in practice can increase liability. 4. Reading Questions for Timing & Keywords (First / Best / Most Appropriate) Many wrong answers come from misreading or reacting too quickly, not from ignorance.Pay close attention to timing/context words: “First” thing you should do“Best” action“Most appropriate” response Always ask: What phase are we in? (Construction admin? Multi-phase project? Pre-bid?)What logically happens next in the process? Exam traps: Fake urgency: e.g., owner is on vacation and unreachable, contractor “needs” a decision. Your roles and responsibilities do not change. If the owner hasn’t appointed a representative, you wait. Multiple answers may be true statements, but: You must pick the one that actually addresses the question asked and fits the given context and timing. In their coaching sessions, candidates rarely reach consensus on answers at first, showing how easily people: Justify multiple answers as “true,” butMiss what the question really asked. 5. Post-Occupancy Evaluation & Closeout – Focus on Performance, Not Blame Post-Occupancy Evaluation (POE), substantial completion walk-throughs, punch lists, and final closeout are about performance: Does the building perform as intended?Are systems functioning properly?Are design goals (e.g., better test scores via daylight and ventilation) being met? It is not about blame or combative architect vs. contractor dynamics.POE is not part of the basic services in B101: Basic services end when the architect signs the final application and certificate for payment (changed from “60 days after substantial completion” in 2007). Contracts (B101 and A101) are the framework: They define what each party has promised to ...
    Show More Show Less
    30 mins
No reviews yet
In the spirit of reconciliation, Audible acknowledges the Traditional Custodians of country throughout Australia and their connections to land, sea and community. We pay our respect to their elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples today.