What architectural programming is, and what it produces
Architectural programming is the pre-design process of defining what a building must do before anyone designs it. You work with the client, end users, and consultants to capture goals, facts, concepts, needs, and constraints, then organize them into a written program document the client signs off on. That document drives schematic design, design development, and construction documents.
A finished program is not a design. It does not commit to a massing, a plan diagram, materials, or elevations. It commits to what the building has to do: who uses it, what they do in it, how much space each activity needs, how those activities relate, what the budget and schedule allow, and what sustainability or performance targets must be met. Treat programming questions on the ExAC as process and documentation questions, not design questions.
Key distinction
Brief, program, and functional program overlap but are used differently. The brief is the client's initial statement of intent (often a few pages). The architectural program is the detailed document the architect develops from the brief. The functional program defines the character, services, scope, functions, and space requirements in enough detail for design or approvals; the Functional Programming guide notes the term is also used for design briefs, facilities programs, and space programs.
1.1 Understand the process involved in developing an architectural program
What sub-category 1.1 tests. Sub-category 1.1 of Examitect's ExAC study plan, taken from the official ExAC exam objectives, is "Understand the process involved in developing an architectural program." The primary reference is CHOP Chapter 6.1. The supplementary references are the Functional Programming guide and Mastering the Business of Architecture (2004), Volume 2, Section 2.
Sub-category 1.1 questions check whether you know how to run the programming process: who you talk to, what you collect, in what order, what you produce, and how you hand the result off to schematic design. Expect process questions, ordering questions ("place these steps in the correct sequence"), and "what does the architect do next?" scenarios.
The Problem Seeking method: five steps
The Problem Seeking method was developed by William Pena and Steven Parshall and published in Problem Seeking: An Architectural Programming Primer. CHOP Chapter 6.1 (Predesign) lists it among its programming references, and it remains the academic backbone of architectural programming in North America. Its vocabulary is a useful frame for the process questions the ExAC asks. The method organizes the architect's work into five steps.
- Establish goals. Sit down with the client and user groups to define what success looks like. Goals are qualitative and aspirational: "create a welcoming front door for the school", "support flexible learning groups of 6 to 30", "achieve Net Zero carbon by 2030". Goals frame every later decision.
- Collect and analyze facts. Gather measurable inputs: site dimensions, zoning rules, code limits, climate data, user head counts, equipment lists, existing-building surveys, market data. Facts are objective.
- Uncover and test concepts. Concepts are alternative ways the program could work: open plan versus cellular, single building versus campus, ground-up versus renovation. Test concepts against goals and facts before committing.
- Determine needs. Translate goals, facts, and concepts into a space list with quantities (net areas), qualities (acoustic, lighting, security), and relationships (adjacencies). This is the bulk of the program document.
- State the problem. Distill the program into a one-page problem statement that hands off to schematic design. It names the unique conditions, the major design directions, and the constraints the design team must respect.
The four considerations: Form, Function, Economy, Time
Problem Seeking organizes every programming decision into one of four columns. The five steps and four considerations form a 5 by 4 matrix that frames the architect's work. ExAC examiners often test whether you can place a given programming input into the correct cell of that matrix.
| Consideration |
What it covers |
Programming inputs |
| Form |
Site, context, environment, image, architectural expression. |
Site survey, neighbourhood context, zoning, views, climate, soils, heritage. |
| Function |
People, activities, and relationships. |
User counts, organizational structure, adjacencies, workflows, hours of use. |
| Economy |
Initial cost, life-cycle cost, operating cost. |
Construction budget, soft costs, contingency, FF&E, energy targets, maintenance. |
| Time |
Past, present, future. Historical context, current need, future change. |
Heritage constraints, current operations, growth forecasts, phasing. |
Stakeholder engagement and information gathering
A program is only as reliable as the people you talked to. CHOP Chapter 6.1 calls out three groups the architect must engage during programming.
- The client (or project sponsor). The party who signs the contract and pays the bills. The client owns the budget, the schedule, and the final sign-off on the program.
- The user groups. The people who will occupy and operate the building. They know the activities, the workflows, and the day-to-day frustrations of the current space.
- Subject-matter experts and consultants. Cost consultants, code consultants, mechanical and electrical engineers, accessibility consultants, sustainability consultants. They confirm what is technically and financially possible.
Typical techniques: kick-off workshops, structured user interviews, questionnaires, observation of the existing facility, precedent tours, and a series of workshop-and-review cycles to converge on the final program. Document every interview. The notes become the audit trail when a future decision is challenged.
Programming deliverables: what an architect actually produces
The output of programming is a written program document the client reviews and signs off on. CHOP Chapter 6.1 lists the contents.
| Deliverable | What it contains |
|---|
| Project goals and success criteria | Qualitative aspirations the design must satisfy. Used at every later milestone to test design choices. |
|---|
| Stakeholder and user-group register | Who was consulted, when, and what they contributed. Names, roles, dates. |
|---|
| Space list (functional and space requirements) | Every space the building must contain, with net area in square metres, occupant count, equipment, finishes, and special requirements. |
|---|
| Adjacency diagram or matrix | How spaces relate. Bubble diagram or a tabular matrix showing required, preferred, and prohibited adjacencies. |
|---|
| Site and contextual constraints | Buildable envelope, zoning setbacks, height limits, easements, heritage, neighbour issues. |
|---|
| Budget and cost benchmarks | Construction cost target, cost per square metre, soft-cost allowance, contingency, FF&E, escalation. |
|---|
| Schedule and phasing | Milestone dates, occupancy date, decanting plan if applicable. |
|---|
| Sustainability and performance targets | LEED, Zero Carbon, WELL, energy use intensity, embodied-carbon ceiling. |
|---|
| Risk and assumptions log | What was assumed, what is unknown, what could change. |
|---|
| Problem statement | One-page summary that hands the program off to schematic design. |
|---|
How to spot a 1.1 question
The question describes a phase before drawings exist, names a stakeholder or user-group activity, asks about order or process, or asks "what does the architect do next?" Those are 1.1 territory. The right answer almost always involves consulting a stakeholder, documenting an input, or producing a piece of the program document.
1.2 Analyze an architectural program
What sub-category 1.2 tests. Sub-category 1.2 of Examitect's ExAC study plan, taken from the official ExAC exam objectives, is "Analyze an architectural program." The primary references are CHOP Chapter 2.2 (The Client), Chapter 5.2 (Stakeholder Management), and Chapter 6.1 (Predesign). The supplementary references match 1.1.
Sub-category 1.2 questions check whether you can take a draft program and stress-test it. Expect calculation questions (net to gross, cost per area), scenario questions ("the program totals 3,200 sq m net, the budget allows 4,500 sq m gross, what do you do?"), and multi-select questions about which constraints to flag.
The five constraint tests
When the program lands on your desk, work through five constraint tests in this order. CHOP Chapter 6.1 outlines the logic; Chapter 2.2 grounds it in the client's needs and expectations; Chapter 5.2 ties it to stakeholder management.
1. Budget
Multiply the gross floor area by the regional cost per square metre for that building type, add soft costs, contingency, FF&E, and escalation, and compare to the client's construction budget. RSMeans and Yardsticks for Costing give the cost-per-area benchmarks Examitect's ExAC study plan cites for Section 1, Cost management. If the program does not fit the budget, the architect documents the gap in writing and presents the client with options: cut scope, raise the budget, phase the project, or reduce specification level.
2. Site capacity
Test whether the program fits the buildable envelope after zoning setbacks, height limits, parking ratios, and amenity-space requirements. If the program is 5,000 sq m gross and the buildable envelope only supports 4,200 sq m, the architect flags it. Site analysis (Section 1, Site and Environmental Analysis) is the partner topic.
3. Code
Check occupant load, exit width, barrier-free path, fire separations, and major-occupancy classification against the National Building Code (NBC) 2020. A program that calls for 600 occupants on the third floor of a Group A Division 2 building is testable against NBC 3.4.3 (width of means of egress) before any plan is drawn.
4. Schedule
Test whether the design and construction sequence can hit the client's milestones. Long-lead items, permit cycles, and phasing constraints get checked here. CHOP Chapter 5.2 covers the stakeholder management behind the schedule conversations that happen at program sign-off.
5. Sustainability and performance targets
Confirm that the brief's targets (Net Zero carbon, LEED Gold, WELL, Toronto Green Standard, BC Energy Step Code tier) are achievable with the program as written. A program with a tight construction budget and a deep-glazed perimeter envelope may not reach the energy target without rebalancing.
Net area, gross area, and the efficiency ratio
Programming math on the ExAC almost always involves net area, gross area, and the ratio between them. Memorize the definitions and the benchmarks.
Net assignable area (NSA) = sum of usable program spaces
Gross floor area (GFA) = total enclosed area, walls to walls
Efficiency ratio = NSA / GFA
Gross-up factor = 1 / Efficiency ratio (used to size GFA from a net program)
| Building type | Typical net-to-gross efficiency | Gross-up factor | Notes |
|---|
| Office | 65 to 75% | 1.33 to 1.54 | Open plan trends higher, cellular and high-security lower. |
|---|
| Educational (K to 12, post-secondary) | 60 to 70% | 1.43 to 1.67 | Heavy circulation and shared amenity drive efficiency down. |
|---|
| Healthcare (hospitals, clinics) | 55 to 65% | 1.54 to 1.82 | Mechanical, support, and code-driven corridor widths dominate. |
|---|
| Laboratory (research, teaching) | 50 to 60% | 1.67 to 2.00 | Shafts, headhouses, and equipment-driven services lower efficiency. |
|---|
| Residential (apartment) | 75 to 85% | 1.18 to 1.33 | Stacked units with common corridors are highly efficient. |
|---|
| Retail (big box) | 85 to 95% | 1.05 to 1.18 | Open sales floor with minimal back-of-house pushes efficiency near 1.0. |
|---|
| Museums and galleries | 55 to 65% | 1.54 to 1.82 | Storage, conservation, and circulation are large non-program loads. |
|---|
Worked example: sizing a building from a net program
A client gives you a net program of 2,400 sq m for a community recreation centre with gymnasium, pool, change rooms, fitness studio, and meeting rooms. Recreation buildings sit at roughly 60 percent efficiency because of pool decks, plant rooms, and double-height volumes. Gross floor area = 2,400 / 0.60 = 4,000 sq m. At a regional construction cost of 5,000 dollars per sq m (from Yardsticks for Costing), construction cost = 4,000 x 5,000 = 20 million dollars. Add 25 percent for soft costs, FF&E, and contingency: total project budget = 25 million dollars. If the client's budget is 18 million, the program is over by 7 million. The architect documents the gap and presents options to the client in writing.
Cost-per-area sanity checks
Examitect's ExAC study plan pairs Programming with Cost management (Section 1, sub-categories 4.1 to 4.4). On Programming questions, you may be asked to apply a cost-per-area benchmark to a program area without doing a full estimate. Memorize the order of magnitude: simple warehouses around 2,000 dollars per sq m, offices around 4,000 to 5,000, schools around 4,500 to 5,500, hospitals around 7,000 to 10,000, and labs around 7,000 to 9,000 (2025 Canadian dollars, varies by region). Yardsticks for Costing is the source the study plan cites.
How to spot a 1.2 question
The question gives you a program total, a budget, a site area, a building type, an occupancy, or a sustainability target, and asks whether they fit together. Expect calculations, "which of the following constraints is binding?" multi-selects, and "what does the architect document next?" scenarios.
The Functional Programming guide (supplementary reference)
Functional Programming is a short practice primer prepared by Justin Saly, MRAIC, and edited by the Alberta Association of Architects (2010), written to supplement the programming material in the Canadian Handbook of Practice. It does not replace architectural programming; it summarizes it. The guide defines functional programming as the decision-making process that clearly defines the problem and scope of work for design, then walks through how a program is prepared, how net and gross areas work, and how to evaluate a program before design starts.
| What the program describes | What it captures | Example |
|---|
| Philosophy, vision, and goals | Why the facility exists and what the client wants it to achieve. | "Provide accessible recreation for the residents of the regional municipality." |
|---|
| Services and delivery | The services the new facility provides and how they will be delivered or operated. | "Aquatics programs run seven days a week alongside drop-in fitness." |
|---|
| Activities, workload, and people | Activity volumes, throughput, staffing, and the major equipment that drive space needs. | "Peak load of 250 visitors with 12 staff on shift." |
|---|
| Space relationships and requirements | Relationships between spaces or groups of spaces, then detailed space requirements. | "25-metre, 6-lane pool with barrier-free change rooms directly adjacent." |
|---|
The guide adds that a functional program may also determine the overall implementation schedule, preliminary budgets, the project delivery method, and site evaluation. On the ExAC, remember what a functional program must do: define the character, services, scope, functions, and space requirements in sufficient detail for subsequent design or approvals.