Architectural programming: Before beginning a house design, the architect should know expected occupancy (how many people will live there) to size spaces, services, and egress appropriately. Evaluate whether the statement “An architect does not need to know how many people are going to live in a house before beginning the design” is correct.

Introduction / Context:
Early architectural programming identifies client needs, including the number of occupants. Occupancy affects bedroom count, bathroom count, kitchen size, storage, HVAC load, water demand, structural loading, egress, and accessibility. We evaluate the statement that an architect does not need this information upfront.

Given Data / Assumptions:

• Design phase: pre-schematic and schematic.
• Occupancy: number of residents and usage patterns.
• Codes: many requirements scale with occupancy.

Concept / Approach:
Without occupancy, requirements are undefined. Room sizes, count, and service capacities are derived from how many people will use the space. Early clarity prevents costly redesigns.

Step-by-Step Solution:
1) Gather client brief: household size and needs.2) Translate into space program and adjacency matrix.3) Size systems (HVAC, plumbing, electrical) accordingly.4) Iterate layout and confirm budget vs area.

Verification / Alternative check:
Standard architectural workflows begin with a program that explicitly lists occupants and room requirements.

Why Other Options Are Wrong:
“Correct”: Contradicts basic programming practice.“Only needed after permit”: Too late and inefficient.“Only needed for apartments, not houses”: Single-family design also scales with occupancy.

Common Pitfalls:
Starting design without a written program; ignoring future growth or guest accommodations.

Final Answer:
Incorrect