The 7 Phases of Architectural Project Delivery

Whether you follow AIA's framework or your own adapted version, most architecture projects move through a predictable sequence of phases. Understanding these phases — and tracking them properly — is the difference between a studio that delivers on time and one that's constantly firefighting.

Phase 1: Pre-Design

Before pencil hits paper, you need to understand the project. This phase covers programming, site analysis, feasibility studies, and initial client meetings. It's where scope gets defined and expectations get set.

What to track: Client requirements, site constraints, zoning research, preliminary budget ranges, and go/no-go decision criteria.

Common mistake: Rushing through pre-design to start designing. Studios that skip proper programming end up redesigning in DD — which costs 3-5x more.

Phase 2: Schematic Design (SD)

This is where the big ideas take shape. Floor plans, massing studies, material palettes, and initial structural concepts. The client sees the vision for the first time.

What to track: Design options presented, client feedback per round, consultant input, and SD budget estimate vs. project budget.

Common mistake: Too many design options without clear decision gates. Set a maximum number of rounds and document approvals.

Phase 3: Design Development (DD)

SD gets refined into a coordinated design. Systems get integrated — structural, MEP, building envelope. Materials get specified. The design becomes buildable.

What to track: Consultant coordination meetings, specification development, DD cost estimate, and any scope changes from SD.

Common mistake: Treating DD as "more SD." DD is about coordination and resolution, not exploration. New ideas at this stage are expensive.

Phase 4: Construction Documents (CD)

The most labor-intensive phase. Every detail gets documented — dimensions, details, schedules, specifications. This is what the contractor builds from.

What to track: Drawing set completion percentage, QA/QC review status, code compliance checks, permit submission deadlines, and team hours vs. budget.

Common mistake: Not tracking hours against the phase budget. CD is where most projects go over budget because the scope of documentation is underestimated.

Phase 5: Permitting

Drawings go to the authority having jurisdiction (AHJ). Reviews happen. Comments come back. Revisions get made. Resubmissions happen.

What to track: Submission dates, review cycles, plan check comments, required revisions, and resubmission deadlines.

Common mistake: Treating permitting as passive waiting. A delayed permit blocks bidding, which blocks construction start, which cascades through the entire project timeline. Track it actively.

Phase 6: Bidding & Negotiation

The project goes out to contractors. Bids come in. Alternates get evaluated. The construction contract gets negotiated.

What to track: Bid packages sent, addenda issued, bid results, value engineering options, and contractor selection criteria.

Common mistake: Not having a structured process for evaluating bids. Price isn't everything — contractor experience with your building type matters.

Phase 7: Construction Administration (CA)

The building gets built. Your role shifts to oversight — reviewing submittals, responding to RFIs, conducting site visits, and processing change orders.

What to track: RFI log, submittal review status, change order impact on budget, site visit reports, and substantial completion milestones.

Common mistake: Underestimating CA hours. Studios frequently budget 10-15% of fees for CA when the actual effort is 20-25%, especially on complex projects.

Why phase tracking matters

Each phase has its own budget, timeline, deliverables, and dependencies. When you track projects as a flat list of tasks, you lose the structure that makes architecture projects manageable.

Phase-level tracking gives you:

• - Budget accuracy: Know how much you've spent on SD before you start DD. Catch overruns early.
• - Timeline realism: If permitting takes 12 weeks instead of 8, you can cascade that delay through downstream phases immediately.
• - Resource planning: CD requires more staff than SD. Knowing when projects transition between phases lets you plan team allocation months ahead.
• - Client communication: "We're 60% through DD" is more meaningful than "we have 47 tasks completed out of 120."

The phases are the backbone of every architecture project. Your project management should reflect that.