Architect Exam Prep: The ARE Podcast Podcast Por David Doucette & Eric Corey Freed arte de portada

Architect Exam Prep: The ARE Podcast

Architect Exam Prep: The ARE Podcast

De: David Doucette & Eric Corey Freed
Escúchala gratis

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 Arte Economía Educación Gestión y Liderazgo Liderazgo
Episodios
  • 092. ARE Technical: Top 5 Tips for Project Planning & Design

    092. ARE Technical: Top 5 Tips for Project Planning & Design
    Mar 27 2026
    David and Eric discuss how PPD fits into the ARE sequence, how it differs from other divisions (especially PDD), and five key mindset/strategy tips for candidates. The main emphasis: PPD is about integration and judgment, not memorizing formulas or hyper‑detailed systems data. Listen to the Audio Show Notes Candidates often see PPD as “the big one” and psych themselves out.Compared to exams like PcM, PjM, CE, PA, PPD and PDD: Are longer and more technically demanding.Test how “architect‑like” a candidate thinks. Other divisions feel more siloed (e.g., contracts, firm types, corporate structures).PPD throws in multiple dimensions at once: cost, aesthetics, structure, codes, ADA, systems, site, climate, etc. → The challenge is the breadth and integration, not obscure content. Tip 1 – PPD is an Integration Exam, Not a Systems Exam PPD’s biggest module is Project Integration, and that’s where many struggle.The architect is the “conductor”: Coordinates structural, mechanical, electrical, code, and owner requirements.No one else on the team is integrating all of this. On questions: Don’t fixate on missing info (“that depends…”).Focus on the one or two key clues NCARB gives you.You’re not picking the perfect answer, you’re picking the best answer among several “good” ones.This requires adopting a realistic architect mindset (compromise, “good enough,” best fit). Tip 2 – Let Site and Climate Drive Design Decisions PPD is basically the schematic design phase: Programming is done; spaces and relationships are known.Now you must actually place and shape the building on its site. Candidates often underuse: Sun path, wind, micro vs. macro climate, orientation. Example: If the question says “Phoenix, Arizona,” that’s a huge clue: hot, dry climate → certain orientations and shading strategies are clearly better. Many candidates: Treat climate as secondary.Have never used a sun chart or don’t know they vary by latitude. Key message: If your design ignores the site and climate, it’s likely wrong – and NCARB is explicitly testing that. Tip 3 – Codes Shape Design; They Don’t Kill It Code thinking evolves across phases: Programming/PA: basic occupancy type, rough allowable height/area (e.g., table 503).PPD / schematic design: feasibility and layout: Allowable building height & area.Occupancy separations.Egress requirements and egress strategy. Codes aren’t “copy‑paste” details: Architects interpret the code and its intent.Egress, ADA, etc., are designed experiences, not just diagrams. Relationship to PDD: In PPD you decide: building type, heights, separations, general strategy.In PDD you detail and carry out those decisions. Bonus point: When codes conflict, it’s not either/or: You must comply with both; practically, you follow the more restrictive so both are satisfied. Tip 4 – Systems Questions Are Conceptual, Not Calculational PPD = still schematic design → things are fluid, nothing is sized to the last CFM.You might see very light “back‑of‑the‑envelope” math, but: Focus is on choosing appropriate systems conceptually, not crunching numbers. Example: Church used mainly on Sundays → large volume, infrequent use → CAV system makes sense.Music studio with small rooms: CAV could be noisy and inappropriate.Hydronic or quieter solutions may be more suitable. You use: Use type, occupancy pattern, acoustics, flexibility, climate as clues. Again: there is no “perfect” system, only the most appropriate given the clues.Don’t silo PPD vs. PDD: PPD‑style conceptual questions can show up on PDD, and vice versa.NCARB expects flexible knowledge application. Tip 5 – Budget Is a Design Constraint, Not a Math Problem In schematic design you do not: Produce detailed cost estimates or exact per‑unit pricing. You do: Understand relative costs: Brick vs. CMU: similar order of magnitude but different roles.Core‑ten vs. ACM panel vs. stucco.Marble countertop vs. plastic laminate. Recognize major cost drivers: Deep underground parking.High water tables and hydrostatic pressure.High‑performance envelopes for hurricane/tornado zones. As per B101 (Bonus Tip): Architect provides an estimate of the Cost of the Work at each phase (SD, DD, CD).Detailed cost estimates are typically done by a third‑party cost estimator or contractor, or as an additional service. Exam wise: If the owner wants a detailed cost estimate at SD, that’s unrealistic.PPD focuses on: “Given this budget constraint, which design move is more appropriate?” Closing Points from the Episode PPD vs. PDD distinction: PPD: concept, integration, “we’ll figure that out later.”PDD: “there is no later” – now you must detail and make it buildable. Candidates must: Stop chasing perfect answers and precision they don’t have at schematic phase.Work with clues, appropriateness, standard of care, and ...
    Más Menos
    34 m
  • 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!
    Más Menos
    42 m
  • 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!
    Más Menos
    20 m
Todas las estrellas
Más relevante
Fun to listen to, easy to follow. Has a good balance of ARE study tips and insides

Fuzzy topics

Se ha producido un error. Vuelve a intentarlo dentro de unos minutos.