ExAC Podcast | Examitect

Read the site from the ground up. We survey the physical factors that influence a project, including soil, groundwater, slope, drainage, climate, vegetation, sunlight, and wind. We also look at existing buildings and buried services, showing why the same checklist produces very different answers on rural and urban sites and why reliable source documents matter.

A program describes what the project needs; site analysis tests whether the land can support it. We introduce physical, cultural, and regulatory factors and explain why their boundaries often overlap. From rural landscapes to dense urban sites, learn how the architect brings specialist information together, weighs constraints, and turns a collection of facts into a useful judgment.

Turn a list of needs into a program the client can review. We follow the process from bubble diagrams and space tables to room requirements, adjacencies, and a complete program document. Using everyday examples, we show how testing relationships and gathering input early helps uncover missing information before the project moves into design.

How does a green building earn its certification? We introduce the LEED framework presented in the episode, including its credit categories, points, and certification levels. We also consider the limits of a scorecard, the uneven value of individual credits, and the existence of other rating systems, helping you focus your study on the overall structure and key concepts.

Sustainability asks how a building affects the environment; resilience asks how it will respond when the environment puts it under pressure. We explore that distinction through early project decisions and the example of changing stormwater expectations. Learn why both ideas belong in programming and how client priorities, regulations, and long-term risks shape the brief.

A useful program starts with careful listening and a solid understanding of the building type. We explore how client goals, daily operations, major occupancies, and relationships between spaces become design requirements. Learn why research, delivery methods, and site conditions belong in the conversation early, especially when the project type is unfamiliar.

Before a building takes shape, its purpose and requirements need to be clear. We introduce programming as the process of defining a building's functions, spaces, and needs before design begins. Along the way, we clarify related terms such as brownfields, life cycle, and renewable energy, building the vocabulary needed for the rest of Section 1.

A promising idea still needs to pass a feasibility test. We examine how site conditions, zoning, building code requirements, budget, and specialist studies help determine whether a project can move forward. From market research to the final report, we trace how the findings come together and why client review and sign-off are essential before design begins.

Architects are responsible for meeting a professional standard of care, and that starts with understanding the limits of the job. We explore reasonable professional performance, the risks of working beyond your expertise, and the responsibility attached to signing and sealing documents. We also return to RAIC Document 9 to consider the care required when retaining consultants.

A quick percentage can help frame a fee, but a detailed work plan tells a different story. We compare top-down pricing with bottom-up estimates built from the hours a project requires. We also discuss how fees distribute across project phases, why some services are difficult to predict, and the professional rules surrounding work offered without a fee.