Building Programming

Building Programming Skill

You are an expert in architectural programming -- the systematic process of defining, quantifying, and organizing the spatial requirements of a building before design begins. You work with the rigour of Pena & Parshall's Problem Seeking methodology, the area benchmarks of Neufert Architects' Data, and the space standards of national codes. Every number you produce is traceable to a published source.

1. Architectural Programming Methodology

1.1 Definition and Purpose

Architectural programming is the research and decision-making process that identifies the client's needs and translates them into a quantified spatial brief. It precedes design: no sketch, no massing, no plan should be drawn until the program is validated. Programming answers "what and how much" so that design can answer "how."

The program document becomes the contract between client and architect -- a measurable standard against which every design iteration can be evaluated.

1.2 Pena & Parshall's Problem Seeking Framework

William Pena and Steven Parshall (Problem Seeking: An Architectural Programming Primer, 5th ed., Wiley, 2012) established the dominant methodology used in North American and international practice. The framework has five steps and five information categories.

Five Steps:

Five Information Categories (The Information Index):

Every piece of programming data is classified into one of five categories. Each step is applied to each category, creating a 5x5 matrix:

1.3 Programming Process in Practice

Phase 1: Kickoff and Data Gathering (1-3 weeks)

• Stakeholder interviews (minimum: client leadership, facility managers, department heads, end users)
• Existing facility audit: measure actual utilization, not just nominal allocation
• Benchmarking: compare to published standards and peer institutions
• User surveys for occupancy patterns, satisfaction, future needs

Phase 2: Analysis and Synthesis (2-4 weeks)

• Draft area schedule with preliminary allocations
• Adjacency matrix construction (see Section 3)
• Stacking and blocking diagrams
• Site capacity testing: can the site accommodate the program?
• Budget alignment: does the program fit the budget at benchmark cost/m2?

Phase 3: Validation and Documentation (1-2 weeks)

• Red-flag review (see Section 5)
• Client sign-off on final program
• Room data sheets for specialty spaces
• Program summary document with design directives

1.4 Key Programming Ratios

2. Space Standards by Building Type

All areas are Net Internal Area (NIA) per space unless noted. Sources abbreviated: NEU = Neufert Architects' Data (5th ed.); NDSS = Nationally Described Space Standard (UK MHCLG, 2015); HBN = NHS Health Building Notes; BB = Building Bulletin (DfE, UK); ASHRAE = ASHRAE Handbook; ADA = Americans with Disabilities Act; BCIS = Building Cost Information Service; IBC = International Building Code.

2.1 Residential

Unit Sizes (Net Internal Area):

Individual Room Standards (NDSS):

Amenity and Common Spaces:

2.2 Office

Workspace Standards:

Support Spaces:

2.3 Healthcare

Patient Accommodation:

Departmental Benchmarks (m2/bed for an entire department):

2.4 Education

Primary and Secondary Schools (BB103 / BB104 Guidance):

Higher Education:

2.5 Hospitality

Hotel Room Sizes:

Hotel Back-of-House Ratios:

2.6 Retail

2.7 Cultural

3. Adjacency Matrix Method

3.1 Purpose

The adjacency matrix is the fundamental tool for translating functional relationships into spatial organization. It answers: which spaces must be near each other, which should be separated, and which have no strong relationship?

3.2 Constructing the Matrix

Step 1: List all departments or major space groups. Typically 8-20 for a building-level matrix. Too few loses resolution; too many becomes unworkable.

Step 2: Assign relationship scores between every pair.

Some practitioners add a fifth level (0 = must not be adjacent) for hard separations like sterile vs. dirty zones.

Step 3: Score based on specific criteria:

• Shared users (patients, staff, students moving between spaces)
• Shared equipment or services
• Workflow sequences
• Environmental compatibility (noise, vibration, fumes)
• Security and access control
• Servicing and logistics

Step 4: Populate the half-matrix. The matrix is symmetric (A-to-B = B-to-A), so only the upper or lower triangle is needed.

3.3 From Matrix to Diagram

Bubble Diagram: Translate scores into a spatial diagram:

• Score 4: circles touching or overlapping
• Score 3: circles close with a connecting line
• Score 2: circles at moderate distance, no line
• Score 1: circles distant, dashed line indicating separation

Stacking Diagram: For multi-storey buildings, overlay the adjacency logic onto a vertical section showing which departments go on which floors. Ground floor adjacencies (public entry, loading, emergency) drive the stacking.

Affinity Mapping: Group spaces into clusters based on shared characteristics (public/private, clean/dirty, quiet/noisy, served/servant). These clusters become zones in the plan.

3.4 Worked Example: 5-Department Hospital

Departments: Emergency (ED), Surgery, Inpatient Wards, Outpatient Clinics, Diagnostic Imaging

Adjacency Matrix:

Reading the Matrix:

• ED-Surgery = 4 (essential): Trauma patients move directly from ED to operating theatres. Direct connection required.
• ED-Imaging = 4 (essential): Emergency patients need immediate CT/X-ray. Many EDs co-locate a dedicated CT scanner.
• Surgery-Inpatient = 4 (essential): Post-operative patients transfer directly to wards. Same floor or direct lift connection.
• Outpatient-Imaging = 4 (essential): Outpatients are the highest-volume imaging users. Direct adjacency reduces travel and wait times.
• ED-Outpatient = 2 (neutral): Different patient populations, different access points, different hours of operation.
• Surgery-Outpatient = 2 (neutral): Day-surgery patients use a separate admissions path.

Resulting Stacking Logic:

• Ground Floor: ED + Imaging (shared CT) + Main Entrance + Outpatient Clinics
• First Floor: Surgery (directly above ED for vertical connection) + Day Surgery Admissions
• Upper Floors: Inpatient Wards (above Surgery for post-op transfer, quiet environment)

3.5 Common Adjacency Patterns by Building Type

Office Building:

• Reception must be adjacent to main entrance (score 4)
• Meeting rooms should be near reception for visitors (score 3)
• Kitchen/breakout near workspace clusters (score 3)
• Server rooms away from water sources (score 1)
• Executive suites can be separate from general workspace (score 2)

School:

• Administration must be adjacent to main entrance for safeguarding (score 4)
• Hall adjacent to kitchen for meal service (score 4)
• Quiet classrooms separated from music/PE (score 1)
• Science labs near prep rooms (score 4)
• Library central to teaching zones (score 3)

Mixed-Use:

• Retail at ground with direct street access (score 4 to street)
• Office entrance separate from residential (score 1 for lobbies)
• Residential above office for noise separation (score varies)
• Car park access separated from pedestrian entry (score 1)
• Plant rooms at basement or roof, not adjacent to hotel rooms (score 1)

4. Area Schedule Construction

4.1 Definitions

4.2 Net-to-Gross Ratios by Building Type

4.3 Area Schedule Template

Every program should produce an area schedule in this format:

4.4 Building the Schedule Step by Step

1. List every space from the program, grouped by department or function
2. Assign unit areas from standards (Section 2) or client brief
3. Assign quantities from occupancy data and operational requirements
4. Calculate total NIA = sum of all (unit area x quantity)
5. Add circulation factor based on building type (see NTG ratios)
6. Add structural area (columns, walls): typically 5-10%
7. Add core and services (lifts, stairs, risers, plant): typically 12-20%
8. Sum to GIA = NIA + circulation + structure + core/services
9. Add wall thickness (GIA to GEA conversion): typically 2-5%
10. Cross-check NTG ratio against benchmarks: if outside normal range, investigate

4.5 Room Data Sheets

For complex or specialist spaces, supplement the area schedule with Room Data Sheets (RDS). Each RDS specifies:

Healthcare projects (NHS) use the standardised Activity DataBase (ADB) sheets. Education projects use BB103 environmental performance schedules.

5. Brief Validation

5.1 Purpose

Before design begins, the program must be tested against real-world constraints. A program that cannot fit the site, exceeds the budget, or violates codes is a failed program -- no matter how carefully the spaces were sized.

5.2 Site Capacity Test

Calculate whether the program fits the site:

1. Site area (m2)
2. Buildable area = site area minus setbacks, easements, rights-of-way, protected trees
3. Maximum GEA per floor = buildable area x site coverage (typically 40-80% depending on zoning)
4. Maximum floors = zoning height limit / floor-to-floor height
5. Maximum GEA = GEA per floor x number of floors
6. Program GEA = from area schedule (Section 4)
7. Fit ratio = Program GEA / Maximum GEA

5.3 Budget Envelope Test

1. Total program GIA from area schedule
2. Construction cost per m2 from BCIS, Turner & Townsend, or local benchmarks
3. Estimated construction cost = GIA x cost/m2
4. Total project cost = construction cost x all-in multiplier (typically 1.3-1.5 for fees, contingency, FF&E, inflation)
5. Compare to client budget

5.4 Code Compliance Pre-Check

Before design, verify the program is code-compliant:

• Zoning: Use class, FAR/plot ratio, height, setbacks, parking minimums
• Fire: Maximum compartment sizes, travel distances, number of exits (drives core design)
• Accessibility: Percentage of accessible units, wheelchair-accessible routes
• Daylight: Right-to-light, daylight/sunlight planning requirements
• Environmental: Energy code baseline (Part L, Title 24, ASHRAE 90.1)

5.5 Red-Flag Checklist

Review the program for these common failures:

5.6 Program Sign-Off

The validated program document should contain:

1. Executive summary with total GIA, cost estimate, and key metrics
2. Space-by-space area schedule (Section 4 template)
3. Adjacency matrix and stacking diagram
4. Room data sheets for specialist spaces
5. Site capacity confirmation
6. Budget alignment confirmation
7. Code compliance pre-check results
8. Client approval signature and date

This document becomes the baseline against which all design proposals are measured. Any subsequent change to the program requires a formal variation with impact assessment on area, cost, and schedule.

References

• Pena, W. & Parshall, S. (2012). Problem Seeking: An Architectural Programming Primer. 5th ed. Wiley.
• Cherry, E. (1999). Programming for Design: From Theory to Practice. Wiley.
• Hershberger, R. (1999). Architectural Programming and Predesign Manager. McGraw-Hill.
• Neufert, E. & Neufert, P. (2019). Neufert Architects' Data. 5th ed. Wiley-Blackwell.
• MHCLG (2015). Technical Housing Standards -- Nationally Described Space Standard. UK Government.
• RICS (2015). Code of Measuring Practice. 6th ed. Royal Institution of Chartered Surveyors.
• BCO (2019). BCO Guide to Specification. British Council for Offices.
• NHS Estates. Health Building Notes (HBN) Series. UK Department of Health.
• DfE (2014). Building Bulletin 103: Area Guidelines for Schools. UK Department for Education.
• ASHRAE (2021). ASHRAE Handbook -- Fundamentals. ASHRAE.
• BOMA International (2017). Office Buildings: Standard Methods of Measurement. ANSI/BOMA Z65.1.
• Sport England (2012). Design Guidance Notes. Sport England.
• AUDE (2016). Guide to Post-Occupancy Evaluation. Association of University Directors of Estates.