5.2 Programming, Schematic Design Development & Stakeholder Engagement

Programming, Schematic Design Development & Stakeholder Engagement

Two CSE tasks live here: develop schematic designs based on program requirements and local, state, and federal regulatory jurisdictions, and prepare and present schematic design documents to stakeholders such as community groups for feedback. The exam treats these as professional-practice questions rather than design questions. It asks who supplies the program, what the architect owes when the program and the budget do not reconcile, how consultants and users are brought into the design decision, and what legal weight community input actually carries.

Program Development and Validation

The owner is contractually responsible for the program. Under AIA B101-2017 Section 3.2, the architect reviews the program and other information furnished by the owner, prepares a preliminary evaluation of the program, schedule, budget for the cost of the work, project site, and the proposed procurement or delivery method, and reports to the owner. The architect is entitled to rely on the accuracy of owner-furnished information — but the duty to evaluate it and report discrepancies is the architect's, and that duty is exactly what the exam probes.

Programming converts stated needs into measured area:

1. Functional program — activities, users, occupancy counts, hours of use, adjacency and separation requirements, equipment, and growth assumptions.
2. Net assignable area — the usable area of each programmed space.
3. Gross area — net area multiplied by an efficiency factor that accounts for circulation, structure, shafts, restrooms, and mechanical rooms. Efficiency varies sharply by building type; a laboratory or hospital carries far more non-assignable area than an open-plan office.
4. Code testing — occupant load and exit capacity, accessible clearances and maneuvering space, plumbing fixture counts, and Title 24 envelope and lighting assumptions applied to the programmed area before massing is set.
5. Site testing — the program is placed in the buildable envelope established during feasibility. When it does not fit, the honest options are reducing program, increasing height or footprint through a discretionary approval, changing construction type, or changing the site.

Program validation is the working session in which the owner, user groups, and consultants confirm or revise the program before design proceeds. It is cheap; discovering the same disagreement during design development is not.

Developing the Design Solution with Clients, Users, and Consultants

Schematic design under B101-2017 Section 3.2 produces documents that illustrate the scale and relationship of project components, typically a site plan, floor plans, sections, elevations, and a preliminary description of building systems. The exam's emphasis is on process:

• Alternative approaches. The architect discusses alternative approaches to design and construction with the owner. Presenting a single scheme with no alternatives is a weak answer on the exam and a weak practice.
• Consultant integration. Structural, mechanical, electrical, plumbing, civil, landscape, and specialty consultants are engaged early enough to influence the scheme rather than to document it. In California, the seismic system, the Title 24 Part 6 compliance path, and accessible circulation are all scheme-level decisions.
• User groups. For institutional clients, user groups (departments, faculty, clinical staff) provide functional detail but do not control budget or scope. The architect routes their requests through the owner's designated representative so that the single-point-of-contact structure in the agreement is preserved.
• Decision logs. Every meeting produces a written record of what was decided, who decided it, and what remains open. This is the practical answer to the exam's recurring "how should the architect respond" question.
• Mock-ups and simulations. Physical mock-ups, virtual walkthroughs, and full-size layout tape-outs resolve user disagreement about clearances and finishes before they become construction changes.

Presenting to Stakeholders and Community Groups

California projects are frequently reviewed in public. The architect must understand what these forums are and what they are not.

The Brown Act (Government Code Section 54950 et seq.) governs meetings of local legislative bodies, including school district and special district boards. Regular-meeting agendas must be posted at least 72 hours in advance, action generally cannot be taken on items not on the agenda, and a majority of the body may not use serial private communications — including an architect relaying positions from one member to another — to develop a collective concurrence outside a public meeting. An architect who carries messages between board members can cause the client to violate the Act.

Housing projects are subject to compressed engagement. Under Government Code Section 65905.5, a local agency may hold no more than five hearings on a housing development project that complies with applicable objective standards, and the Housing Accountability Act constrains the agency's ability to deny or reduce the density of a compliant project. Practically, this means the design team has fewer opportunities to iterate in public and must front-load outreach.

Managing Feedback Without Losing the Project

• Separate comment from condition. Community comments are input. Only a condition adopted by the decision body is binding. Never tell a client that a neighborhood group "approved" anything.
• Track and respond. Maintain a comment-and-response matrix. At the hearing, the ability to show that each substantive comment was considered is worth more than the redesign itself.
• Control scope creep. Repeated redesign driven by community input is an additional-services event under B101 Section 4. Identify the trigger in writing when it happens, not at the end of the phase.
• Protect the CEQA and appeal record. Statements made in community meetings can appear in litigation. Describe the project accurately and consistently across every forum.

CSE Exam Traps & Practical Takeaways

• Trap 1: Treating community consensus as approval. The correct exam answer routes final authority to the decision body identified in the ordinance.
• Trap 2: Accepting the program without evaluation. B101 requires a preliminary evaluation of the program, schedule, and budget. Silently designing an unbuildable or unaffordable program is a standard-of-care failure.
• Trap 3: Taking user-group direction as a scope change. User requests that change scope must be routed to the owner's representative and confirmed in writing before they enter the drawings.
• Trap 4: Becoming the conduit for a Brown Act violation. Do not carry substantive positions between members of a public board outside a noticed meeting.
• Trap 5: Presenting only one scheme. The exam rewards the architect who presents alternatives with their cost, schedule, and approval consequences, and lets the owner choose.