If you look back to the recommended AIA building project structure, you’ll notice that concept design and schematic design are listed together. However, when the client and architect are a good match and communicate effectively, schematic design can be an invigorating creative adventure! What is the difference between concept design and schematic design? This has the potential to be fraught, for example if a client seems to change their mind about their priorities, or if an architect does not respond well to the rejection of their ideas. In short, the schematic design process is a back-and-forth featuring a lot of negotiation. Even when client and architect have settled on a basic design, it will likely go through several iterations as ideas are refined.
The client evaluates these, either selecting one design to take forward or requesting further options to better meet their needs. Initially, the architect draws out a number of possible options for the building, based on input from the programming strategy stage. Schematic design is a collaborative process in which the client is heavily involved. The overarching goal of schematic design is for the client to have in their hands a design they are happy with, but this is not a simple march from A to B. While most of the drawings made during the schematic design phase are likely to be plans, these should be accompanied by elevations and sketches of suggested details. Schematic designs should include information about building systems (structural, mechanical, electrical, plumbing, HVAC) and potential finishes, both exterior and interior.
When making these sketches, architects take into account the area and arrangement of the rooms on site, as well as local zoning rules and any other physical specifications that were made during the programming strategy phase. Note the plural sketches – the goal is not for the architect to propose one finished and polished idea, but to offer a range of possible options that meet the client’s requirements. The purpose of schematic design is to produce sketches based on the initial discussions between architect and client. However, in most cases the two stages are seen as separate. This allows them to respond immediately and visually to a client’s description of what they want. So, simply put, the schematic design phase is when architects first get their ideas down on paper.ĭepending on their working style, some architects might choose to combine the programming strategy and schematic design stages of a project. What naturally follows from this is a phase of initial sketching by the architect. The first phase, programming strategy, is when architects and clients meet to discuss the requirements of the building.
The AIA recommends that building projects are structured as follows:Ġ5 Tender bid, negotiation and appointmentĪs you can see, schematic design is the second step in the process (in the UK, RIBA describes this process slightly differently, but the essentials are the same).