Curious about what schematic design is trying to achieve? Read on to understand how it shapes the project before DD begins.
Opening Thoughts
Schematic Design can feel unpredictable at times, especially when the early steps are not well defined. SD is most effective when it builds on clear direction from PreDesign, not when the team is still sorting out basic questions. When PD leaves gaps, those issues often reappear during SD as decisions that can no longer wait. This article looks at how SD clarifies what the project is aiming to build, turning early studies into a more defined design direction with a clearer sense of scope, cost, and expectations
PD has evolved into a much more substantive phase over the last decade or so. On large healthcare and civic projects, it is no longer just a round of early sketches or simple site evaluations. PD is where the project’s purpose is defined, where the program is validated, and where the first outlines of the building begin to emerge. The team works through site constraints, service access, environmental reviews, early massing, preliminary structural and MEP assumptions, and the location and quantity of elevators. City agencies and community boards frequently enter the conversation at this stage, shaping entrances, public access, height, bulk, and how the building meets the street. All of this belongs in PD because it sets the stage for meaningful design.
Budget formation also begins in PD through cost modeling and benchmarking that establish the project’s initial financial range. These early numbers do not need precision, but they must be realistic enough to frame expectations and give the client a sense of projected square‑foot costs, which is often the first indication of whether the project is trending within their target range. Risk awareness develops here as well. Potential site issues, infrastructure conflicts, utility constraints, or regulatory hurdles often surface long before SD starts. Even if they cannot be resolved immediately, they should be understood and documented so the team enters SD with a clear list of open items.
By the time the project reaches SD, the team should already understand the site, the program, the structural direction, the envelope expectations, and any operational priorities. This includes a clear grasp of programming needs with an outlook toward future expansion, early master planning studies, site planning and zoning analysis, access and circulation strategies, stormwater direction, parking assumptions, and the status of site utilities and supporting infrastructure. At minimum, there should be a written Basis of Design summarizing what the team is carrying. The BOD is not a final document, but it is a reliable reference that keeps SD grounded in the work already done. When PD and the BOD are handled well, SD becomes the moment when ideas gain form. When PD is thin, SD becomes an exercise in backtracking.
SD needs solid footing because it is no longer a loose, conceptual phase. Modern delivery pushes SD toward early technical alignment. Structural grids need to be resolved. Floor-to-floor heights must be confirmed. Core locations cannot be placeholders. Envelope concepts, mechanical room sizes, and service routes require enough definition for consultants to work without guessing. These are not DD-level details, but they demand consistent logic that supports technical development. SD is where the project shifts from what might work to what can be built.
As SD progresses, the consultant team expands in both breadth and influence. Many disciplines are already engaged during PD, including the associate architect, MEP, structural, civil, landscape, restoration, theater, medical planning, vertical transportation, sustainability, and emissions consultants. Their early work shapes programming, site planning, operational assumptions, and regulatory direction.
In SD, this group typically continues while additional specialists become more active, such as vibration and acoustics consultants, envelope and curtain wall experts, wind analysts, and soils and geotechnical teams. Their input begins to influence geometry and performance more directly. Topics such as entrainment, intake and exhaust placement, mechanical noise, stack effects, envelope behavior, wind conditions, and soil capacities all begin shaping architectural and structural decisions. The questions become more technical, and coordination becomes more frequent.
The meeting load increases as well. Consultant coordination sessions, client reviews, steering committees, and user group sessions all become more common. These interactions add complexity, but they also bring clarity when managed properly. They help refine priorities, confirm assumptions, and keep the project aligned with operational expectations. This rise in activity is why SD often feels like the transition between concept and technical design.
With these forces shaping the phase, SD becomes the practical bridge between PD and DD. It has one foot in each world. It still needs the openness that allows design exploration, but the coordination that occurs in SD should remain flexible enough to avoid locking in components prematurely. The aim is to align systems, massing, and layout at a schematic level so cost modeling, consultant input, and client feedback are based on information that is coordinated without being over‑fixed. This balance allows the design to progress while still giving the CM and the architect what they need to provide meaningful estimates and confirm the project’s direction. When SD works well, DD becomes a natural progression. When SD is rushed or unclear, DD becomes a phase spent revisiting decisions that should already be settled.
The strongest SD phases are always built on strong PD. The massing is studied. The entrances, loading, and material flow make sense. The program is tested, efficiencies understood, and grossing factors confirmed so the project is sized correctly. The approvals path is outlined. The structural and MEP strategies have direction, even if not fully defined. Everyone understands the major goals and constraints. This clarity allows SD to focus on refining the architecture, aligning the systems, and preparing the project for the technical depth of DD. When PD provides that grounding, SD becomes a confident bridge instead of a stressful one.
What Schematic Design Should Accomplish
Schematic Design sits between the exploratory work of PD and the technical demands of DD. It must take early studies, constraints, and program goals and turn them into a coordinated direction the entire team can build on. SD is where the building’s logic becomes real and where decisions gain structure. To work well, the phase must accomplish several essential tasks.
1. Architectural Clarity
SD establishes the architectural framework. Plans should reflect accurate program areas, functional adjacencies, and circulation patterns, with structure and services aligned to support operations. Sections and elevations must reinforce massing, floor-to-floor logic, and the early envelope approach. Representative spaces need enough definition to communicate scale, daylight, and material direction. The architectural language does not need to be fully resolved, but it should be coherent and consistent.
Key supporting elements include:
- coherent massing that responds to site and program
- scaled drawings that confirm functional and structural logic
- an early understanding of envelope proportions, system direction, and sustainability considerations
- visuals or diagrams that communicate design intent
2. Technical Direction
SD confirms the major systems that will guide DD. The structural grid, spans, and lateral strategy should be established so engineering can advance without revisiting fundamental moves. Mechanical and electrical direction must be defined at a level that supports coordination, equipment sizing, and early pricing. Core locations, risers, and main equipment rooms need clear spatial alignment.
Key considerations include:
- a structural approach that supports the architectural layout
- preliminary MEP/FP concepts with clear distribution paths
- envelope performance expectations that influence wall depth and glazing
- input from specialty consultants such as acoustics, vibration, wind, and vertical transportation
3. Regulatory and Code Alignment
The project’s regulatory basis must be visible in SD. Occupancy classifications, egress approaches, stair sizing, travel distances, and accessibility should be addressed at a schematic level. Fire and life safety concepts, such as separations and shaft strategies, need early definition so they do not disrupt the design later.
SD should also reflect zoning constraints, environmental review conditions, and agency or community feedback gathered during PD. These factors influence massing, access, and configuration, and must appear in the documents.
4. Cost, Risk, and Coordination
A schematic estimate depends on documents that describe scope clearly while stopping short of DD‑level detail. The challenge in SD is producing enough content to support a reliable estimate without over‑drawing or over‑specifying the work. Drawings, narratives, and material intent should align so pricing reflects the actual design direction, and supplemental narratives can reinforce the documentation so the team does not drift into expectations more appropriate for DD. Alternates should be identified, assumptions recorded, and scope defined so cost feedback can shape DD effectively.
Risks identified in PD become clearer in SD. Site constraints, utilities, structural complexity, envelope performance expectations, long-lead systems, or regulatory issues should be documented and carried forward. Coordination also intensifies. Multiple disciplines advance their work simultaneously, and the project engages steering groups, user groups, and client committees. SD must provide a stable platform for these interactions.
The Schematic Design Report
The Schematic Design Report is the written record of the project at the close of SD. It explains the design intent, documents the assumptions that shaped the work, and provides the owner and project team with a reliable basis for DD. Drawings show the building. The SD Report explains it. Many teams organize it using a Uniformat structure so that narratives and estimates speak the same language.
A. Project Intent and Foundations
This opening section restates the project’s objectives and the direction established in PD. It summarizes program goals, site influences, operational needs, and the priorities that informed early decisions. Its purpose is to show how the work completed in PD translates into the SD design direction.
B. Description of the Recommended Design
This portion describes how the building works. It outlines the plan organization, massing, circulation, site approach, and the early character of the exterior. It explains how the design responds to program needs and how the architecture supports the project’s purpose. It also summarizes the developing approach to the envelope, interiors, and major spatial ideas. The goal is clarity, not repetition of the drawings.
C. Engineering and Specialty Input
Short engineering narratives outline the structural, mechanical, electrical, and fire protection strategies taking shape. They describe system direction, performance expectations, and the reasoning behind these choices. Specialty consultants, such as acoustics, envelope, vertical transportation, or environmental reviewers, contribute brief summaries when their work influences DD. These inputs help identify early risks and maintain consistency across disciplines.
D. Regulatory and Code Overview
This section documents the regulatory conditions shaping the design. It typically includes zoning context, site requirements, occupancy classifications, egress assumptions, fire separation strategy, and accessibility considerations. It does not finalize compliance but ensures the project is progressing with a clear understanding of governing requirements.
E. Cost and Schedule Summary
A schematic‑level estimate accompanies the report and is supported by the drawings and narratives. This portion explains major cost drivers, identifies alternates, and outlines key assumptions. An updated schedule shows how the SD package aligns with procurement milestones, long‑lead items, and construction phasing.
Why the SD Report Matters
A clear SD Report becomes the baseline for DD. It documents the decisions made, the assumptions that carry forward, and the issues requiring continued study. It keeps the project aligned as technical detail increases and helps prevent the team from revisiting decisions that should remain stable.
Closing Thoughts
Schematic Design works best when its foundations are solid. PD establishes the strategic direction, and the SD Report records the assumptions that guide the work ahead. Drawings complete the picture. They are essential, because they translate intent, systems, and constraints into coordinated geometry the entire team can build on.
SD is the point where ideas become organized decisions. The architecture gains structure, the systems gain shape, and the regulatory and cost frameworks gain clarity. Each drawing, narrative, and diagram contributes to a shared understanding of how the project works and why it is moving in a certain direction.
When SD is grounded in clear goals and supported by disciplined documentation, DD becomes a phase of refinement rather than correction. The project enters technical development with alignment instead of uncertainty. Momentum replaces friction.
This is why a practical SD checklist matters. It strengthens the clarity SD depends on and gives project teams a common reference for what must be established before detailed coordination begins. A strong SD phase sets up a strong DD phase. The checklist simply makes that goal easier to reach.
A Typical SD Drawing Package
While the depth of drawings in SD varies by project, most schematic packages follow a predictable structure. The goal is to communicate scope, intent, and system direction without drifting into DD‑level detailing.
1. Title Sheet & Drawing Lists
[ ] Project Image, Project Title, Drawing List, Issuance name and date
2. Symbols & Abbreviations Sheet
[ ] All drawing symbols and abbreviations that can found throughout the drawing set
3. Zoning Analysis
[ ] Zoning map along with a spreadsheet documenting permitted use groups, floor are ratio, lot coverage, max. building height, parking requirements, loading berths, etc… plans and sections are included to provide overalls and show deductions.
4. Site Survey
[ ] Shows property lines, easements, access, building footprint, grading, site utilities, paving, plantings, and key site furnishings, scaled to the needs of the project. (Provided by Client)
5. Code Summary
[ ] A preliminary code review that confirms occupancy, use group, egress strategy, stair sizing, travel distances, fire resistance ratings, and plumbing counts.
6. Life Safety Sheets
[ ] Floor Plans for ever floor with below grade spaces and roofs. Plans generally show, hourly rating & smoke partitions, travel distances, exit signage, occupant load calculations for egress stairs and doors and floor occupancy.
7. Materials Indexes – Interior & Exterior
[ ] Materials Indexes provide a summary of the proposed finishes & materials to support early SD pricing.
8. Demolition Drawings (if required)
[ ] Identify the demolition scope to indicate selective or complete removals. Coordinate with the other consultants – MEP & Structural
9. Site Plan (architectural)
[ ] With input from Civil and Landscape, plan typical shows: property line, Building footprint, dimensions, elevations, easements, utilities, entries, driveways, sidewalks, landscape, bike racks and more.
10. Floor Plans
[ ] Plans for all levels indicating program spaces, square footages, circulation, exits, toilet rooms, and accessibility compliance. Interior partition types are often keyed to a simplified Partition Types sheet.
11. Roof Plans
[ ] Indicates drainage, roof slopes, roof system type, pavers, dunnage, and major roof‑mounted equipment.
12. Building Elevations
[ ] Column grids and elevations, overall facade and storefront elevations noting materials, floor to floor dimensions, system types. Bulkheads drawn similarly. Grade lines, curbs, ramps. Lot line buildings are typically dashed in for reference.
13. Building Sections
[ ] Column grids and elevations, cross and longitudinal sections should show spatial and floor‑to‑floor relationships.
14. Exterior Wall Systems Sheets
[ ] Typical façade systems at an enlarged scale provide greater definition and may include interfaces that better inform early pricing.
15. Partition Types Sheet
[ ] If keyed on floor plans, a simplified partition types sheet is included to clarify the anticipated interior construction.
16. Interior Elevations and Details
[ ] Provided for major spaces where the plans don’t capture the extent of materials and where more detail is needed for pricing.
17. Stair Plans & Sections
[ ] Typically included but with very limited information at the SD phase.
18. Elevator Stop Diagram & Plans
[ ] Provides overall hoistway height and overrun. Door heights and floor to floor dimensions provided.
19. Reflected Ceiling Plans
[ ] Complicated ceiling designs and ceiling systems are generally shown with limited detail and material tagging for pricing.
20. Consultant Drawings (See Consultant Checklist in past articles)
[ ] Structural plans define the proposed foundation and superstructure with preliminary framing layouts. MEP/FP drawings show system direction, major equipment, design criteria, and early distribution paths. Vertical Transportation and Facade Maintenance drawings are also included.
A Typical SD Report Format
While every project tailors its SD Report to its needs, many follow a structure similar to the outline below. It provides a clear framework without dictating style or formatting.
A. Introduction – [ ] Project overview – describe the project location, site, size, program, process, and any other particulars such as sustainability goals, the design vision, or future growth and expansion considerations.
B. Cost Estimate Overview
C. Alternates
D. Schematic Design Reports & Narratives – Include reports from all the contributing consultants, such as:
- Geotechnical Engineering
- Civil Engineering
- Structural
- M.E.P & FP
- Food Service
- Code Analysis
- Materials Handling
- Parking Consultant
- Acoustics
- Lighting
- Audio Visual
- Theater Design
E. Outline Specifications – Uniformat
- Intro – Project Requirements
- Element A – Substructure
- Element B – Shell
- Element C – Interiors
- Element D – Services
- Element E – Equipment & Furnishings
- Element F – Special Construction & Demolition
- Element G – Sitework
References:
Be the ONE
