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 integrated thinking.
- You closed by recapping the five tips and heading to your Monday Round Table call for Platinum coaching members.

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!

Tip 1 – PPD is an Integration Exam, Not a Systems Exam

Tip 2 – Let Site and Climate Drive Design Decisions

Tip 3 – Codes Shape Design; They Don’t Kill It

Tip 4 – Systems Questions Are Conceptual, Not Calculational

Tip 5 – Budget Is a Design Constraint, Not a Math Problem

Closing Points from the Episode

Please Subscribe

Please rate us on iTunes!