A term worth knowing
Schematic design
Schematic design is an early design phase in which the architect and consultants explore the basic organization and character of a project. Work commonly establishes site arrangement, building form, major spaces, circulation, preliminary systems concepts, and broad relationships among program requirements. The drawings and descriptions are developed enough to discuss the direction, but they are not usually complete instructions for construction or final pricing. The scope and deliverables of this phase should be defined in the design agreement and tailored to the project.
Context
Why it matters
Owners make foundational choices during schematic design that affect usability, area, systems, approvals, and later design effort. Reviewing the concept against the business and operational brief can reveal misalignment while options are still comparatively flexible.
Early estimates and schedules rely on assumptions because many details are unresolved. Owners should treat them as decision tools with stated qualifications, not as firm commitments, and keep track of which choices could change the project.
At the table
Questions for the owner
- 01Does the proposed concept meet the owner's functional brief, operating needs, and priorities? Ask users and relevant operators to review circulation, adjacencies, capacity, and access, then capture decisions and unresolved concerns in the project record.
- 02What assumptions support the current area, site layout, system approach, and cost or schedule discussion? Request a clear list of exclusions and unknowns so comparisons between design options remain meaningful.
- 03Which decisions must be made before design advances, and what information will the team provide to support each choice? Agree on review milestones, responsible decision-makers, and the process for recording changes to the approved direction.