5.1 Programming: Validating the Project Program

Why Validate the Program

The project program is the foundational document of every interior design project. It is not a design — it is a written statement of the problem the design must solve: what activities will occur, who will use the space, how much area each function needs, and what relationships between functions are required. Programming is the research and analysis phase that produces this document, and validating the program means testing it against the realities of the building shell, code requirements, and the client's budget before design begins. A program that has not been validated is just a wish list.

Net vs. Gross Area

Two area metrics drive every feasibility decision:

• Net Assignable Area (NAA): the sum of all usable spaces the occupant can actually occupy — offices, workstations, conference rooms, restrooms, and corridors inside the tenant suite. It excludes building structure, shafts, and mechanical/electrical rooms serving the whole building.
• Gross Building Area (or gross interior area): everything inside the exterior walls, including structure, vertical circulation cores, and building services.

The relationship between them is the efficiency ratio (also called the space efficiency ratio or net-to-gross ratio):

Efficiency Ratio = Net Assignable Area ÷ Gross Area

A low ratio means more of the rentable area is consumed by circulation and service, leaving less for productive use.

Worked Example

A tenant leases 20,000 gross sq ft. The client's program lists 14,000 sf of net assignable space. The efficiency ratio is 14,000 ÷ 20,000 = 0.70, well within the conventional-office range. If the design must later add a 200 sf server room and an 80 sf accessible restroom, net assignable climbs to 14,280 sf and the ratio to 0.714 — still feasible. But if the program then adds a 2,000 sf staff lounge, net assignable becomes 16,280 sf / 20,000 = 0.814, an aggressive ratio for partitioned space that signals the program no longer fits the shell.

Adjacencies and Circulation

The program must specify adjacencies — which spaces must be near, desirable to be near, neutral, or undesirable to be near each other. Common examples:

• Required: reception adjacent to waiting; copy/print adjacent to open office; restroom adjacent to break room.
• Undesirable: a noisy break room next to a quiet focus library; a loading dock next to executive suites; restrooms directly visible from the lobby.

Circulation is the system of paths that connect adjacencies. Three tiers:

1. Primary circulation — main corridors and lobby routes serving the whole floor; minimum 44 in. clear per IBC Section 1018.2 for egress, with concourse widths of 6–8 ft common.
2. Secondary circulation — aisles between workstations, typically 36–48 in.
3. Service circulation — back-of-house routes for mail, trash, and catering, often 36 in. minimum.

Required clearances turn adjacency requirements into hard constraints: a 36 in. doorway, a 60 in. wheelchair turning space (ADA), and a 44 in. egress corridor all consume net area.

Occupancy Load and Occupancy Types

The program must validate that the projected occupant load fits the building's egress and plumbing capacity. The occupant load is calculated per IBC Table 1004.5 (2021 IBC) by dividing the floor area of a space by the load factor assigned to its occupancy classification.

Factors labeled gross are calculated on the gross area of the space; factors labeled net are calculated on the net area. The resulting occupant load drives:

• Egress width — 0.3 in. per occupant for stairways and 0.2 in. per occupant for doors/level corridors in sprinklered buildings (IBC Section 1005.3).
• Plumbing fixture count — per IPC Table 403.1, separated by sex when the occupant load exceeds 15.
• Number of exits and travel distance limits.

If the program calls for a 60-person training room and the floor's exit stairs are already sized for 200 occupants, the program is feasible. If the program then adds a 250-person town hall to the same floor, egress capacity fails and the program must be revised — before design begins.

Typical Square Footage Allocations

Programming references typical sf allocations to sanity-check client requests. These are typical ranges drawn from professional practice and standards (BOMA, IFMA, ASID); they are not code minimums.

Treat these as typical ranges — the actual allocation depends on the client's work pattern, furniture system, and brand standard. A tech company may target 40 sf per workstation; a law firm may demand 120 sf per private office.

Exam Scenario

A 30,000 sf floor is being leased for a 200-person call center. Validate: occupant load = 30,000 ÷ 150 (Group B) = 200 occupants. Egress width needed = 200 × 0.2 = 40 in. of door width. The program lists 200 workstations at 50 sf each = 10,000 sf, plus support spaces (break, training, restrooms, circulation). A call center typically runs a 0.65–0.70 efficiency ratio, so gross need ≈ 14,000 ÷ 0.70 = 20,000 sf. The 30,000 sf floor has capacity to spare; the program is feasible.