Key takeaways
- Schematic design compares; design development commits. Confusing the two produces false confidence.
- Cost certainty is gained in design development, not from a schematic render.
- Material decisions belong in design development because they carry structural and fire consequences.
- Coordination between architecture, structure and services is what design development is actually for.
Continue exploring all architectural design process guides.
Different jobs, not different levels of detail
The usual framing is that design development is “schematic design with more detail.” That is misleading, because the two stages are doing different kinds of work.
Schematic design compares. It generates arrangements and tests them against the brief, the site and the budget. Its output is deliberately provisional because most of it will be discarded — that is the point.
Design development commits. It takes the chosen arrangement and resolves it into something that can be costed and built, coordinating architecture with structure and services along the way.
What is open and what closes
| Schematic design | Design development | |
|---|---|---|
| Arrangement | Being tested, multiple options | Fixed |
| Dimensions | Approximate | Resolved and coordinated |
| Structure | Strategy only | Sized, positioned, coordinated |
| Envelope | Concept | Build-up specified, junctions understood |
| Services | Zones and strategy | Routed, with space allocated |
| Materials | Palette, intent | Specified, with consequences understood |
| Cost | Order of magnitude | Substantial certainty |
| Approval | Pre-application discussion | Submission-ready in most cases |
Why cost certainty lives here
A schematic design tells a cost consultant the size, the rough form and the intent. That supports an estimate with a wide band around it.
Design development tells them the structural approach, the envelope build-up, the services distribution and the principal materials. Those are the items that actually drive cost, which is why the estimate tightens dramatically at this stage rather than at the previous one.
If someone offers a firm price against schematic information, the price is carrying risk that has to land somewhere — usually as variations later.
The handover is where projects go wrong
Three recurring failures:
Treating a schematic render as a specification. Renders are produced before materials are fixed and details are indicative. If something in one matters to you, get it confirmed on a drawing or in the specification — see floor plan vs elevation vs section.
Deferring materials. Material choice has structural, fire and detailing consequences. Deferring it past design development means reopening coordinated work. The selection process belongs at this stage.
Skipping coordination to save time. Uncoordinated information is one of the most reliable sources of cost on site. Design development is where the clashes are meant to be found, on paper, where they cost hours instead of weeks.
What to ask at each transition
Leaving schematic design:
- Which arrangement are we proceeding with, and what were the alternatives we rejected?
- What is the cost estimate, and how wide is the band around it?
- What is still genuinely open?
Leaving design development:
- Is the structural design coordinated with the architecture?
- Are the principal materials specified, and do they satisfy fire and structural requirements?
- What would change now cost, in fee and in programme?
For where these two sit in the full sequence, see the five stages of architectural design, and the architectural design process guide for the reasoning behind the sequence. Before appointing anyone, work through the questions to ask.
Frequently asked questions
Can I get a fixed price after schematic design?
You can get an order-of-magnitude estimate, but not a reliable fixed price. Too much is still undefined — structure, envelope build-up, services routes. A price quoted against schematic information usually moves once those are resolved.
How much detail should schematic drawings have?
Enough to compare options and test the brief, and no more. Over-resolving a schematic wastes effort on arrangements that will be discarded, and creates pressure to keep an option because time was spent on it.
What if the client changes their mind during design development?
Changes are still workable but no longer free, because coordinated decisions have to be revisited. The further into design development, the more consultants are affected. This is the point where change control should start being explicit.
Do all projects have both stages?
The names vary and small projects may compress them, but the two activities always happen. Skipping the comparison work means committing to the first arrangement; skipping the resolution work means discovering the problems on site.
Sources
- RIBA Plan of Work — Royal Institute of British Architects (RIBA) Accessed August 27, 2026.