Every architecture project moves through the same five phases, and every studio knows them by heart: pre-design, schematic design, design development, construction documents, and construction administration. Yet knowing the phases and actually managing them cleanly are two different things. The phases are where the fee lives, where the client approvals happen, and where projects quietly fall behind, so learning to manage the five phases of an architecture project without chaos is close to the whole job of running a studio.
The chaos usually comes from treating a project as one long undifferentiated to-do list. Deadlines blur, it becomes impossible to say whether you are on track, and work from one phase bleeds into the next before anything has been approved. This piece walks through each phase and how to keep it under control.
Why phases are the right unit of management
A phase is not just a label. It is a gate, with its own deliverables, its own approval, and usually its own slice of the fee. Managing at the phase level means you are always able to answer the question that matters: are we where we are supposed to be, and has the client signed off on what came before? When you anchor planning to the phase first and break tasks out within it, progress stays meaningful instead of dissolving into an endless list.
Pre-design: get the constraints straight
Pre-design is where scope, program, budget, site constraints, and zoning get established. It is tempting to rush it to get to the drawing, but this is the phase that sets up everything after it. The management job here is capture: record the program requirements, the site conditions, the client's real priorities, and the constraints, so the whole team is designing against the same brief. Decisions made loosely here become expensive surprises in DD.
Schematic design: keep options visible
Schematic design is exploratory, and that is exactly why it needs light structure rather than none. You are generating options, testing them against the program, and moving toward a direction the client will approve. The risk is losing track of why an option was set aside, or presenting to the client without a clear record of what they are approving. Keep the studies and the reasoning attached to the project, and make the client's schematic approval an explicit gate before you move on.
The cleanest projects treat each client approval as a real gate, not a formality you assume happened.
Design development: coordinate the consultants
Design development is where coordination becomes the main event. Structural, mechanical, electrical, and civil consultants are all working against your drawings, and their inputs have to land in the right sequence. This is the phase where invisible dependencies cause the most damage: a task waiting on a structural markup that no one knows is blocked, a consultant set that arrived and is sitting unopened.
- Track what you are waiting on from each consultant, and who owns the follow-up
- Keep every consultant PDF attached to the project, not scattered across inboxes
- Make blocked work visible so it surfaces early instead of at the deadline
- Confirm the client sign-off at the end of DD before committing to CD
Construction documents: manage the sheet set
Construction documents is the most detail-heavy phase, and the volume of work is where studios drown. You are producing a full sheet set, coordinating revisions, and often preparing a permit set on a separate track. The management challenge is revision control and completeness: knowing which sheets are done, which are in progress, and which are blocked, without holding it all in one person's head. A visible board where every sheet or package is a tracked task keeps the set from turning into a guessing game two days before submission.
The permit set deserves special attention. It is often a hard external deadline with a jurisdiction on the other end, so treat it as a fixed date and work backward from it, the same way you would a client presentation.
Construction administration: stay responsive
Construction administration looks nothing like the earlier phases, which is exactly why generic tools handle it so poorly. Now the work is reactive: RFIs come in from the contractor, submittals need review, site visits generate observations and follow-ups. The management job is responsiveness and record-keeping. An RFI that sits for a week can stall the site, so tracking each one with an owner and a status, and capturing site-visit observations before you leave the site, is what keeps CA from becoming a flood of email.
The thread that runs through every phase
Across all five phases, the same principles hold: make the work visible, tie deliverables to the phase, treat approvals as real gates, keep drawings and decisions attached to the project, and protect the hard external dates. Do that consistently and the chaos mostly disappears, because problems become visible while there is still time to fix them.
Running the phases in Spreadbox
Spreadbox is built to run projects this way. Project status tracking lets you manage against your phases so you can always see where a project really stands, while Kanban task boards and a team queue make the work inside each phase visible and ordered. File and PDF attachments keep consultant sets, sheets, and markups with the project, and a shared calendar with two-way Google Calendar sync protects your hard dates like permit submissions and client presentations. Team chat keeps coordination attached to the work instead of leaking into email, and Spreadie, the built-in AI assistant, can turn a quick note into a phase checklist or draft the update you owe a client. From pre-design through construction administration, the studio keeps one clear picture of every project.