Schematic Design Architecture

The work that makes options comparable. That means site and zoning analysis, program and area studies, and massing options. It also means preliminary plans, sections and elevations, circulation and egress diagrams, and the 3D studies used to explain a scheme to a client. They also assemble the area tabulations and the comparison material that lets a principal choose between options on evidence rather than instinct. The design direction stays with your firm. What a remote architect adds is the capacity to test three schemes properly instead of one, which is usually what a schematic phase is missing. Presentation quality output for the client meeting comes out of the same model. Where the scheme needs a persuasive image rather than a study, that is visualization work, which is a different specialist.

Partly, and it is the phase firms delegate last, for a good reason. Schematic design is where a practice's judgment shows, and it is the phase clients are paying a specific architect for. What can be delegated is everything around the judgment. The site and zoning research, the area studies, the option modeling, the diagrams, and the presentation set. What should not be delegated is the direction. The useful test is whether a task produces a decision or supports one. Supporting work travels well. Decisions do not. Firms that try to hand over the whole phase usually get schemes that are competent and not theirs, then spend the DD phase correcting it. Start with one role on the supporting work and see how it holds before you widen the brief any further.

The brief, the site, and the constraints. Specifically: the program with areas, the client's requirements and any non-negotiables, the survey and site information, the zoning designation, and the budget range. Then your own material, which matters as much. Recent projects that show how your firm designs, your presentation template, and the drawing conventions you use at this stage. A short conversation about what the client responds to is worth more than another document. Where the site has an existing building, an accurate as-built model or set changes everything. It is the difference between studies that hold up and studies that shift later. We would rather start with a smaller brief that is real than a full one that is assumed. Send what you have and we will tell you what is missing.

As the envelope the options are drawn inside, not as a check at the end. At schematic stage the binding constraints are usually zoning rather than building code. Setbacks, height limits, floor area ratio, lot coverage, parking, and any overlay or historic district rules. On the code side, fewer decisions matter this early. Occupancy classification, construction type, allowable area and height, egress arrangement, and accessibility at the level of plan organization. Those come from the code cycle your jurisdiction has adopted, which the ICC publishes and each state amends. A remote architect can research and document that envelope, then keep every option tested against it as the design moves. What a remote architect does not do is interpret the code for you. Your architect of record makes the interpretation and carries it, exactly as before.

One approved scheme, documented well enough that the next phase develops it rather than reconstructs it. That usually means preliminary plans, elevations, and sections at a consistent scale, plus a massing or 3D model. With them travel the area tabulations, the zoning and code summary, and the presentation set the client approved. The handover matters more than the drawings. What has to travel forward is the reasoning. Which options were rejected and why, what the client committed to, and which constraints are driving the scheme. When the same professional continues into design development, that context comes with them. When they do not, it has to be written down. Ask us how the handover is documented before the phase starts. That gap between phases is where most rework on a project is quietly created.