Programming, Planning, and Analysis
Programming
Programming establishes the problem before any solution is drawn: goals, functional needs, space requirements, adjacency desires, budget, schedule, and constraints. Methods include client interviews, questionnaires, observation, user surveys, document review, and benchmarking against comparable projects. Deliverables are typically a program statement, an area tabulation, and a written functional and organizational analysis.
Numbers: net, gross, and efficiency
Net assignable area is usable space within a room; gross area includes circulation, walls, mechanical, and structure. Efficiency ratio equals net divided by gross, commonly 60–75% for offices and lower for dense or highly serviced facilities. Programmed net area divided by the target efficiency yields the gross building area - a calculation candidates are frequently asked to perform.
Planning tools
Adjacency matrices rank relationships by importance and frequency. Bubble diagrams express proximity without geometry; blocking and stacking plans add relative size and floor-to-floor organization, often used in multi-story buildings to place heavy or public functions low. Zoning and site analysis, code analysis, and budget checks run in parallel with this work.
From program to design
Schematic design tests alternatives against the program, then design development fixes dimensions, materials, and systems. Post-occupancy evaluation closes the loop with measured performance and user feedback.
Traps
Questions blur programming with schematic design, or misapply efficiency - remember efficiency is net ÷ gross, so gross is always larger. Do not treat an adjacency matrix as a layout; it conveys priority, not geometry. Watch for requests for “usable” versus “gross” area when budgeting.
Rule of thumb
If the program requires 8,000 net sf and the target efficiency is 75%, plan for 8,000 ÷ 0.75 ≈ 10,670 gross sf.