Module 7: Architectural Programming and Preliminary Design

Module 7: Architectural Programming and Preliminary Design

$Learning Objectives$

Translate an approved client brief into traceable functional requirements, user groups, occupancy assumptions, measurable spaces, capacities, and area criteria.
Organize spaces through adjacency, public/private/service zoning, circulation, accessibility, wet-area, storage, utility, equipment, and site relationships.
Recognize how preliminary architectural decisions create structural, civil/site, fire/life-safety, and building-services implications.
Read and coordinate preliminary plans, sections, elevations, levels, and design assumptions without representing a CE learner as independently authorized to practice architecture.
Assemble a controlled preliminary-design issue package that gives consultants enough information to review interfaces and return coordinated constraints.

$Architectural programming$

Architectural programming is the structured process of identifying and organizing a project's users, activities, spaces, capacities, relationships, performance needs, constraints, and other requirements so that an architectural design can be developed from an explicit and traceable basis.

$Professional-Scope Boundary for CE Learners$

R.A. 9266 places building programming, space planning, architectural design, and architectural documents within regulated architectural practice. The Supreme Court's March 15, 2023 decision in G.R. Nos. 200015 and 205846 further held that R.A. 9266 limits Civil Engineers from preparing, signing, and sealing architectural documents. This lesson therefore teaches multidisciplinary understanding, engineering-interface awareness, and coordination from an architect-controlled design basis. A CE learner may assist with coordination and lawful engineering/documentation tasks, but this lesson does not authorize independent architectural authorship, preparation for signature/seal, or practice outside the lawful CE scope.

$From Client Language to Design Information$

Clients often begin with statements such as “we need a small clinic,” “the office should be flexible,” “we expect 200 users,” or “we may add another floor later.” These statements are not yet a coordinated design basis. They must be translated by the responsible design team into measurable requirements: users, activities, occupancy assumptions, capacities, space types, equipment, privacy, circulation, accessibility, environmental conditions, servicing, structural implications, and future-change criteria.

Client Requirement to Multidisciplinary Design Basis

Translate client language into measurable and traceable functional information before it becomes a preliminary layout.

Project Brief, Users, and Functional Requirements

$Project brief$

A project brief is the controlled statement of the owner's approved objectives, intended use, user needs, scope, performance expectations, constraints, budget/schedule context, and other information that defines what the project is expected to achieve.

$Information to Clarify Before Space Planning$

Project purpose: the service, business, institutional, residential, industrial, or other function the building must support.
User groups: occupants, visitors, staff, maintenance personnel, service/delivery personnel, persons with disabilities, emergency responders, and other relevant users.
Operating pattern: hours, peak periods, shift changes, queuing, controlled access, delivery windows, cleaning/maintenance cycles, and special events.
Occupancy assumptions: intended uses and occupant populations requiring confirmation against the governing code and responsible architect's design basis.
Capacity: people, workstations, seats, beds, vehicles, storage units, equipment, inventory, or other measurable demand.
Performance needs: privacy, acoustics, daylight/view preferences, ventilation/conditioning needs, security, cleanliness, vibration sensitivity, loading, durability, or specialist requirements.
Growth and change: future expansion, convertible rooms, additional equipment, possible vertical/horizontal extension, and phasing.
Owner constraints: budget, schedule, procurement, branding, operational continuity, and acceptable trade-offs.

$Do Not Confuse Operational Headcount with Code Occupancy$

In programming, “occupancy” can be used informally for the number and pattern of people using a space, while building and fire regulations also use formal use/occupancy classifications and occupant-load concepts. A client's expected headcount is therefore not, by itself, the code occupancy classification or the final occupant-load basis. Keep these inputs separate and have the responsible professionals verify the applicable code classifications and calculations.

$Do Not Convert an Unverified Client Number Directly into a Drawing$

A stated headcount, room count, or preferred area may be an aspiration rather than an approved design input. Record its source and status. Capacity and area decisions may also be affected by occupancy, accessibility, egress, equipment, circulation, sanitation, structure, servicing, and other requirements that require professional and regulatory review.

Building the Space Program

$Space program$

A space program is a structured schedule of required spaces and their relevant planning criteria, such as function, users, capacity, target or minimum area basis, equipment, environmental needs, adjacency, access, privacy, services, and special constraints.

$Useful Space-Program Fields$

Space/room name and unique identifier
Function and principal activities
User group and expected capacity
Area criterion and source/status
Major furniture and equipment
Required clearances or operational working zones
Accessibility considerations
Public, private, secure, sterile/clean, service, or other access character
Preferred/required adjacency and separation
Wet-area or drainage needs
Power, ICT, ventilation, mechanical, plumbing, fire-protection, or specialist-service needs
Floor-loading, vibration, span, height, or other structural interface
Storage and maintenance access
External/site relationship
Future-expansion or adaptability requirement
Assumption, decision owner, and verification status

$Area Program — Reconcile Targets as the Scheme Develops$

Area programming needs a controlled quantity basis, not just a room list.

Area layer	Programming meaning
Room/space target area	Target or minimum area assigned to an individual programmed space, with the criterion/source and status recorded
Net/usable program area	Sum of the spaces treated as usable/programmed area under the project's stated definition
Circulation/support/service area	Corridors, lobbies, stairs/lifts, toilets, storage, shafts, plant/service rooms, walls/structure, or other support areas that may sit outside the project's net/usable definition
Gross/project floor area	Building- or project-level floor-area measure used for design, cost, regulatory, or owner reporting under a clearly stated definition

Do not apply a universal net-to-gross percentage. Ratios vary with building type, design stage, code/standard definitions, structural and service systems, circulation strategy, and project criteria. A ratio may be used as an early planning assumption only when its source and status are explicit, and it must be replaced or reconciled against the developing scheme.

$Area Reconciliation and Change Control$

STEP-BY-STEP

Record each room/space target area and the criterion or owner decision that produced it.
Sum the current net/usable program using one documented project definition; do not mix area definitions in the same total.
Add or separately track circulation, vertical circulation, toilets, storage, service/utility rooms, shafts, walls/structure, and other non-room/support areas needed by the scheme.
Compare the developing gross/project floor area with the client brief, site/designable-envelope limits, budget/cost basis, and applicable regulatory area definitions.
Reconcile the schedule after every material layout revision instead of leaving the original program total unchanged.
When client capacity, room count, function, equipment, or operating assumptions change, record the change, identify the affected spaces and support areas, update the program totals, and reissue the current design basis.
Keep target area, current planned area, variance, status, and decision owner visible for material spaces so unexplained area drift can be resolved deliberately.

$Developing a Traceable Space Program$

STEP-BY-STEP

Start from the approved project brief and list every user group and major activity.
Convert activities into required functions and identify the spaces needed to support them.
Assign capacities, area criteria, equipment, access conditions, and performance requirements using verified project inputs and the responsible professionals' criteria.
Record relationships among spaces: must-adjoin, should-be-near, may-be-separated, and must-be-separated.
Add circulation, toilets/wet areas, storage, utility/service rooms, vertical circulation, and operational support spaces rather than treating them as leftover area.
Add site-facing requirements such as main entry, service entry, loading, parking interface, outdoor space, fire/emergency access, and utility connections.
Flag structural and building-services implications that need consultant input before the layout is fixed.
Keep unknown or conditional values explicitly marked rather than inventing precision.

Programming Relationship Matrix

Classify spatial relationships before drawing a plan. These relationship classes are project-specific instructions, not universal room adjacencies.

Use the matrix to state why two functions should connect, remain near, or be separated. Public, controlled/private, and service relationships should be explicit so later layouts can be tested against the approved program.

MUST ADJOIN — direct connection is functionally required; record the reason and the two spaces/functions involved

SHOULD BE NEAR — convenient short movement is preferred but direct connection is not mandatory

SHOULD BE SEPARATED — privacy, security, hygiene, noise, safety, or operational conflict requires deliberate separation

ZONE RELATIONSHIP — PUBLIC ↔ CONTROLLED/PRIVATE ↔ SERVICE interfaces are identified, including where transitions or crossings require control

Adjacency, Functional Zoning, and Circulation

$Adjacency$

Adjacency describes the required or preferred spatial relationship between two functions, ranging from direct connection to deliberate separation, based on movement, operations, privacy, safety, service, or user experience.

$Public, Private, and Service Relationships$

Functional zoning is a planning aid, not a universal three-color formula. A project may distinguish public/reception areas, controlled staff areas, secure/private rooms, service/back-of-house zones, wet or utility areas, high-noise zones, clean/dirty flows, or other operational categories. The responsible architect determines the architectural organization; engineering coordination checks whether the proposed organization can be supported by structure, site works, fire/life safety, accessibility, and building services.

$Horizontal Circulation Questions$

Where do occupants enter, queue, transition, and leave?
Which movement paths must be obvious to first-time users?
Which service, waste, delivery, or maintenance routes should avoid public flows?
Which spaces need direct connection rather than corridor access?
Where could door swings, columns, equipment, stairs, ramps, or shafts obstruct movement?
Which routes form part of the accessible path or egress system and therefore require code-specific review?

$Vertical Circulation Questions$

What user and service flows move between floors?
Where are stairs, ramps, lifts/elevators, service lifts, or other vertical systems required by the approved design basis?
How do stair/lift cores affect structural grids, floor openings, lateral systems, and foundation loads?
What headroom, landing, pit, overhead, shaft, machine/equipment, fire-separation, or accessibility interfaces require specialist confirmation?
Can vertical circulation remain coherent if future expansion occurs?

Functional Zoning and Circulation Relationship Map

A programming relationship map—not a universal floor plan—showing the spatial systems that must be reconciled before preliminary layout is accepted.

Read each card as a required relationship to test in the architect-controlled scheme. Color is not used as the sole carrier of meaning; every zone and path is named explicitly.

PUBLIC ZONE ↔ PRINCIPAL PUBLIC / ACCESSIBLE PATH — entry-facing and visitor functions connect through legible circulation

CONTROLLED / PRIVATE ZONE ↔ CONTROLLED TRANSITION — restricted functions avoid uncontrolled public through-traffic

SERVICE ZONE ↔ SERVICE PATH — delivery, maintenance, waste, and back-of-house movement are coordinated and public-path crossings are reviewed

VERTICAL CIRCULATION ↕ SERVED ZONES — stairs, ramps, lifts/elevators, and service vertical movement connect levels and affect structure, egress, and accessibility

WET / SERVICE CORE ↔ WET + UTILITY FUNCTIONS — toilets, shafts, service rooms, drainage, and vertical service routes are coordinated rather than scattered accidentally

INTERFACE CHECK — review PUBLIC↔PRIVATE, PUBLIC↔SERVICE, SERVICE↔CORE, accessible routes, and path crossings; revise relationships before treating any arrangement as fixed

Accessibility, Toilets, Wet Areas, Storage, and Service Rooms

$Accessibility Begins in Programming$

Accessibility should affect the space program, entrance sequence, route continuity, vertical circulation strategy, toilets, counters/work surfaces where applicable, parking/site access, and other user interfaces from the beginning. Verify the current B.P. 344 implementing rules and project-specific requirements; do not attempt to retrofit an “accessible path” after rooms, stairs, structural grids, and levels have already been frozen.

$Wet and Service Spaces Are Coordination Anchors$

Toilets, janitor rooms, pantries, kitchens, laboratories, treatment rooms, and other wet areas create drainage, water-supply, waterproofing, ventilation, floor-level, and structural-opening interfaces.
Electrical, mechanical, plumbing, fire-protection, electronics/ICT, generator, pump, tank, transformer, refuse, maintenance, and other service spaces require access, clearances, ventilation, loads, drainage, acoustics, and sometimes fire separation.
Stacking compatible wet/service zones can simplify routing, but it must not be treated as an absolute rule when function, access, structure, safety, or maintenance requires another solution.
Equipment rooms should be sized from verified equipment and maintenance envelopes, not from an arbitrary leftover rectangle.

Site Relationships, Orientation, and Expansion

$The Building Program Extends Beyond the Building Footprint$

Preliminary planning should coordinate the building with arrival and drop-off, pedestrian access, accessible route, parking and loading, fire/emergency access, service yards, utilities, drainage, grading, existing trees/features, neighboring properties, views, noise sources, prevailing environmental conditions, and future site development. Site orientation can affect solar exposure, wind, daylight opportunity, façade design, drainage, and mechanical loads, but these relationships require project-specific climate/site evidence rather than generic orientation slogans.

$Future Expansion Must Become a Design Input$

If expansion is part of the brief, define what kind: added rooms, horizontal wing, vertical floors, larger equipment, increased occupancy, or phased fit-out. The responsible structural-engineering professional/team needs the approved expansion assumption early because columns, foundations, lateral systems, roof framing, joints, load allowances, and construction sequencing can be affected. “Future expansion” without a defined scenario is not a usable structural design input.

Preliminary Plans, Sections, and Elevations as Coordination Information

$What Preliminary Drawings Need to Communicate$

At coordination stage, preliminary architectural information should clearly communicate the approved concept sufficiently for other disciplines to review interfaces. Depending on project stage this may include floor plans, key dimensions, grid proposals, levels, sections, elevations, roof form, stairs/cores, wall zones, major openings/voids, ceiling or headroom-sensitive areas, façade constraints, equipment zones, service areas, external works relationships, and future-expansion assumptions.

$Why Sections Matter Early$

A floor plan may appear workable while vertical relationships fail. Preliminary sections expose floor-to-floor heights, beam/ceiling zones, stairs, ramps, roof geometry, shafts, tall equipment, façade transitions, drainage slopes, retaining conditions, and site level changes. Sections therefore belong in early multidisciplinary exchange rather than being postponed until the plan is considered “finished.”

Design Assumptions and Consultant Issue Package

$Design assumption$

A design assumption is a stated provisional input adopted so work can progress before complete information is available. It must identify its basis, owner, consequence, and verification/expiry condition so it cannot silently become permanent fact.

$Minimum Preliminary Design Basis for Consultant Review$

Controlled drawing issue and revision/date
Project brief and approved scope summary
Space program and major capacities
Occupancy/use assumptions requiring consultant awareness
Floor plans, levels, sections, elevations, roof geometry, and site relationships appropriate to the stage
Grid proposals and known structural constraints
Stair, lift/core, shaft, opening, façade, equipment, and service zones
Accessibility and fire/life-safety assumptions that affect layout
Future-expansion scenario
Known utilities/site constraints
Assumption and decision register
Specific questions requiring structural, civil/site, MEPF/electronics, fire, specialist, or authority response

Preliminary Design Information Package

Assemble the information consultants need to understand the proposed building and the questions requiring their response.

$Issuing the Preliminary Design Basis to Consultants$

STEP-BY-STEP

Freeze a clearly identified coordination issue; do not circulate multiple unlabeled “latest” plans.
Include the drawings, schedules, assumptions, and specific questions needed for the requested consultant review.
Identify decisions that are fixed by the client/architect, decisions still open, and constraints already verified by authorities or site evidence.
Request responses in a controlled form: markup, sketch, calculation/design note, issue log, or coordination meeting record.
Incorporate accepted responses into the next coordinated issue under the responsible professional's control.
Keep rejected, deferred, and unresolved items visible with decision owner and required date/evidence.
Do not promote a preliminary layout to detailed documentation until material multidisciplinary interfaces are sufficiently resolved for that stage.

Consultant Issue and Response Sequence

Control preliminary design exchange so accepted consultant responses become part of the next coordinated design basis.

$A Beautiful Preliminary Plan Is Not Yet a Coordinated Design$

A layout can satisfy the room list and still fail because of structure, egress, accessibility, shafts, plant space, drainage, site grading, utilities, façade support, or maintenance access. Preliminary design becomes a multidisciplinary design basis only after the relevant disciplines have reviewed the interfaces and their accepted responses have been incorporated.

$Programming Review Case: A Room Target Changes$

The client enlarges the multipurpose room while keeping the total project area target unchanged. Record the revised functional requirement and ask the responsible Architect to reconcile the space programme.

Check the consequences for circulation, support/service space, accessibility, occupancy assumptions, site placement, and consultant inputs. Do not silently reduce another room or assume that its original area was optional. The revised programme should show which targets changed, who accepted the trade-offs, and which preliminary drawings were reissued. Completion means the programme and the controlled preliminary design communicate the same decision, with unresolved implications still visible.

Key Takeaways

Translate client statements into traceable functions, capacities, target areas, spaces, relationships, assumptions, and performance criteria before relying on a layout.
Reconcile room/space targets, net/usable area, circulation/support/service area, and gross/project floor area as the scheme develops; never assume one universal net-to-gross percentage.
Treat circulation, accessibility, toilets/wet areas, storage, utilities, equipment, and service rooms as programmed requirements rather than leftover spaces.
Use plans together with sections, elevations, levels, roof geometry, and site relationships so vertical and multidisciplinary conflicts appear early.
Preserve the legal distinction between architectural practice and CE coordination/drafting responsibilities.
Issue one controlled preliminary-design basis to consultants, record their responses, and iterate before detailed discipline design is fixed.

$References$

Republic Act No. 9266, Architecture Act of 2004 — statutory source defining architectural practice, architectural programming, space planning, design, and professional responsibilities.
Supreme Court, G.R. Nos. 200015 and 205846, March 15, 2023 — decision relevant to architectural documents and the professional-scope interface under R.A. 9266 and the National Building Code framework.
PRC: Civil Engineering — Professional Regulation Commission resource for R.A. 544, as amended, and Civil Engineering regulation.
National Council on Disability Affairs: 2024 Revised IRR of B.P. 344 — current official accessibility-rule resource for programming and preliminary-design interfaces.
Republic Act No. 9514, Revised Fire Code of the Philippines of 2008 — statutory fire-safety basis relevant to occupancy, egress, access, and fire-protection coordination.
BFP: Revised IRR of R.A. 9514 (2019) — official base RIRR for fire-safety planning and plan evaluation; verify later BFP/DILG amendments and supplemental issuances.
DHSUD/HLURB CLUP Guidebook, Volume 1 — official planning guidance relevant to site context, land-use regulation, and zoning coordination.

Previous TopicModule 6: Building Permit Processing

Next TopicModule 8: Architectural–Structural Design Exchange

Prev Next