What Are the Phases of a Construction Project?

Schematic design settles the big moves: massing, arrangement, circulation, structural concept, the code strategy. Drawings are diagrammatic and decisions are cheap to reverse. Design development resolves the systems: structural sizing, mechanical and electrical distribution, envelope assemblies, key details, outline specifications. By the end of it, the building is defined even if it is not fully drawn.

Construction documents translate all of that into instruments that can be built from and enforced: a coordinated drawing set, a full project manual, schedules that agree with the plans. The distinction that matters commercially is that a change in schematic design costs drafting time, while the same change during construction documents ripples through every discipline, and after issue it becomes a change order.

Preconstruction is not a slot in the sequence so much as a parallel track. Estimating, constructability review, procurement planning and long-lead identification start during design and intensify as the documents firm up, which is the only point at which they can still change the outcome.

A constructability comment raised during design development gets absorbed into the documents. The same comment raised after issue for construction becomes an RFI, and possibly a change order. That difference in cost is the entire argument for bringing the builder in early.

Bidding or negotiating the work and obtaining the building permit usually happen in the same window, and both can hold the project. Permit plan review runs in comment cycles that the applicant does not control, and long-lead equipment cannot be released until its submittal clears review, which pushes a document process onto the critical path.

Teams that treat this phase as paperwork lose weeks. Teams that treat the submittal register as a procurement schedule, and the quality of the permit submittal as schedule insurance, generally do not.

Once construction starts, the design team shifts from authoring to answering. RFIs arrive when the documents are unclear or the field finds a conflict. Submittals arrive to prove products match the specification. Change orders record scope, cost and time that move. Every one of those is a question about what the contract documents actually say.

This is the longest phase and the one that generates most of the project record. It is also where the cost of a poor handover from design shows up, in RFI volume and in the time spent reconstructing intent that was clear to the author and to nobody else.

Substantial completion triggers the punch list, and the remaining work is largely documentary: as-built drawings, operation and maintenance manuals, warranties, attic stock, training, commissioning records, and the final payment and lien releases that depend on them.

Closeout is routinely underestimated because the building looks finished while the record is not. The owner inherits whatever the record contains, and gaps in it become facilities problems years later, when nobody involved is still reachable.

Each transition moves a project between teams: programming to designers, designers to builders, builders to operators. Knowledge that was obvious inside one phase becomes an unanswered question in the next, and the only thing that crosses reliably is what was written down.

That is why the document set, and the ability to search it, does more for delivery than any single phase process. The question a field engineer asks in month fourteen was usually answered in a design development meeting in month three.