What to Expect in Each Phase of an Architectural Project

Starting an architectural project, whether it’s a private villa, a commercial building, or a renovation, can feel overwhelming if you don’t know what’s coming next. Clients often arrive with a vision but little understanding of the journey between that vision and a finished building. Knowing what happens at each stage doesn’t just ease anxiety, it helps you make better decisions, ask the right questions, and avoid costly delays.

This guide follows a typical design, tender and construction sequence. Its nine headings are an explanation for clients, not a universal contract or mandatory programme. Stages can overlap or be grouped differently, and the appointment must define deliverables, responsibilities, review rounds and fees. Our design process describes how analysis and interdisciplinary coordination inform that work.

Phase 1: Discovery and Briefing

Every project begins with conversation, not drawings. This is where the architect listens more than they speak. Expect to be asked about your lifestyle, your daily routines, your budget range, your site, and your long-term goals for the space. A good architect will probe beyond the obvious: not just “how many bedrooms” but “how do you actually use a living room” or “do you entertain often.”

Early work combines a site visit with the information needed to test feasibility: measured surveys, relevant constraints and specialist investigations where required. A visual visit cannot establish soil bearing capacity or replace a geotechnical report. Agree a brief, an initial cost framework, outstanding information and a programme suited to the actual project, rather than assuming a standard one-to-three-week duration.

Phase 2: Concept Design

This is where ideas start to take visual shape. The architect translates the brief into massing studies, preliminary plans and spatial options. These are not construction drawings, but they should still test area, circulation, orientation and key constraints. Images help explain the proposal; they do not demonstrate that its technical interfaces are resolved.

Agree the number and depth of alternatives in the appointment; two or three concepts are not an automatic entitlement. Compare proposals against the same brief and budget assumptions, then record the chosen direction and unresolved questions. Early changes are generally less disruptive than changes after coordinated documentation or procurement, but additional redesign still takes time.

Phase 3: Schematic Design

Once a concept is approved, it gets refined into something closer to a real building. Floor plans become more accurate, room sizes solidify, and the design starts to reflect actual structural and mechanical logic. Expect to see more detailed plans, elevations, and possibly an early 3D model or walkthrough.

This is the stage where the architect engages with structural and MEP (mechanical, electrical, plumbing) considerations, even if those disciplines aren’t fully designed yet. Clients are typically asked to confirm key decisions: window placements, ceiling heights, general material direction. Changes are still possible but start to come with more cost and time implications than in the concept phase.

Phase 4: Design Development

This is where the project moves from “what it looks like” to “how it actually works.” Material selections become specific, structural systems get defined, and the architect coordinates with engineers and specialist consultants. Expect detailed floor plans, sections, elevations, and a much clearer picture of finishes, fixtures, and technical systems.

Allow time to resolve interfaces between architecture, structure and building services. This is not necessarily the longest stage. Review materials, layouts, access for maintenance and significant technical choices against an updated cost plan. More detail can reduce uncertainty, but the estimate remains dependent on scope, allowances and current pricing; it is not a guaranteed tender sum.

Phase 5: Construction Documentation

The architect and the appointed engineers prepare and coordinate their respective drawings, schedules and specifications. Structural and building-services design remain the work of the responsible specialists, not automatically the architect alone. Clients should receive a clear explanation of the decisions being approved even when the documents are technically detailed.

Distinguish information issued for approval, tender and construction. A permit package does not necessarily contain every detail required to build or procure the work. Agree who completes specialist design and shop drawings, how they are reviewed and which revision is authorised for use. Changes to an approved design should identify their effects on other disciplines, cost and programme before issue.

Phase 6: Permitting

Approval requirements should be investigated early rather than treated as a step that only starts after all construction documents are complete. The submission sequence depends on the project and jurisdiction; some reviews overlap design development. Confirm who prepares each submission, which approvals are needed before work begins and what remains conditional.

Allow for authority review and possible resubmission without promising a generic duration. The appointed team can control the completeness and coordination of its information and its responses, but cannot promise another body’s decision date. Keep the approval programme distinct from both design completion and construction readiness.

Phase 7: Bidding and Contractor Selection

Before construction starts, contractors are invited to bid on the project based on the construction documents. The architect typically helps evaluate bids, not just on price but on the contractor’s understanding of the project, proposed timeline, and track record.

Compare bids on a common scope, including exclusions, provisional allowances, programme and proposed substitutions. An unusually low total calls for clarification, not an automatic rejection or award. The client makes the appointment decision with the agreed professional advice. The wider overview of architecture phases provides context for the transition from design to procurement.

Phase 8: Construction Administration

The architect’s construction-stage service depends on the appointment. It may include periodic site visits, review of submissions, responses to queries and reporting on observed work; it does not automatically mean continuous resident supervision. Define the separate roles of the architect, engineers, site team and contractor, including responsibility for execution and site safety under the project arrangements.

Agree reporting intervals and inspection points before work is concealed. A site change is not acceptable merely because it is common: record the reason, obtain the relevant technical review and required authorisations, and update affected information. Our discussion of quality in villa design and construction explains why inspection records and traceable decisions matter as much as the finished appearance.

Phase 9: Pre-Delivery and Handover

Prepare handover requirements before the last weeks of construction. Walkthroughs identify incomplete or defective work, while the relevant specialists check testing and commissioning against the specified requirements. A clean finish or a set of keys does not establish that the building’s systems operate as intended.

The agreed handover package should identify outstanding items, responsible parties and follow-up dates, together with relevant as-built information, warranties, operation and maintenance manuals and user training. Distinguish occupation or practical completion from final contractual close-out where the contract makes that distinction. Defects follow-up and seasonal checks may continue after occupation.

Why Understanding This Process Matters

Problems can arise from design, incomplete information, procurement, execution or conflicting expectations. At each review point ask three practical questions: what is approved, what is still unresolved, and what information must be ready before the next commitment? An approval record is useful only if the team can identify the drawing revision and scope to which it refers.

The most useful outcome is not a sequence of attractive presentations but a record that remains usable after the project team leaves. A future maintenance decision should be able to draw on what was specified, what was installed and how it was checked. That continuity is what turns handover from an event into the beginning of informed building use.

Updated on 17 October 2026