Project Schedule Feasibility: Phasing, Duration, and Milestone Planning

Assessing whether a project's schedule is realistic given scope, budget, delivery method, and site constraints. Covers phasing strategies, duration estimation using the Critical Path Method, milestone identification, schedule control baselines, and how architects compare client timelines to available project information during the programming phase.

ARE · Programming & Analysis

Overview

Clients show up with a date circled on a calendar. Your job is to figure out whether that date is real.

Schedule feasibility is the process of comparing a client's desired timeline against everything you actually know about the project: its scope, its budget, the site conditions, the delivery method, regulatory approvals, and the sequencing of design and construction phases. During programming, this comparison happens before design begins, which makes it one of the most consequential assessments an architect performs.

The ARE tests your ability to understand how project schedules are structured, what determines their duration, and how phasing decisions affect whether the timeline holds. You need to grasp how the Critical Path Method (CPM) identifies which activities control the total project length, how milestones serve as progress checkpoints, and how a Work Breakdown Structure (WBS) organizes project scope into schedulable pieces.

Schedule, scope, and cost form a triangle. Change one side and the others shift. A client who wants a faster schedule without reducing scope is asking for higher costs. An architect who can't explain that relationship during programming will struggle to set realistic expectations, and that disconnect causes problems all the way through construction.

This topic connects directly to how you advise clients on project feasibility and provide recommendations when the timeline doesn't match the scope.

Essential

Schedule feasibility comes down to one question: can this project actually be built within the time the client expects? Answering that question during programming requires understanding how schedules are built, what drives their length, and where they typically break down. ## The Scope-Cost-Schedule Triangle Every project has three interdependent constraints: scope, cost, and schedule. The FTA Construction Project Management Handbook presents these as three sides of a triangle. A change to one side impacts one or both of the others. A client who adds program space (scope increase) is also adding cost and time unless something else gives. A client who compresses the schedule without reducing scope needs more resources, which means more money. During programming, your role is to map the client's expectations onto this triangle and flag mismatches before design starts. The fundamental control principles work the same way for scope, cost, and schedule: 1.

Professional

When the Client's Timeline Doesn't Work An architecture firm is retained for a 120,000 SF medical office building. The owner wants to open in 24 months from the programming kickoff. The architect's preliminary CPM analysis shows a 30-month critical path based on standard design phases, a competitive bid procurement, and typical construction productivity for the region. That 6-month gap is the feasibility problem. The architect's job is to identify realistic options for closing it. Option A: Fast-track delivery. Overlap design and construction by issuing early packages (sitework, foundations) while interiors are still in design development. This might recover 3-4 months, but it increases coordination risk and limits the owner's ability to make late design changes without costly rework. Option B: Reduce scope. Defer a wing or floor to a future phase. This shortens construction duration and reduces the design effort.

TLDR

Scope, cost, and schedule form a triangle. Changing one side forces adjustments to the others.
The Work Breakdown Structure (WBS) decomposes project scope into schedulable work packages organized in 5 hierarchical levels.
The Critical Path Method (CPM) identifies the longest sequence of dependent activities. That sequence determines the project's total duration.
Float is the time buffer on non-critical activities. Zero float means any delay extends the project. Float belongs to the project, not to individual parties.
Milestones have zero duration. They mark phase completions, approvals, and contractual deadlines.
Phasing plans are developed during pre-design, not during construction. They must account for operational continuity, long lead items, and regulatory approvals.
Schedule baselines are established at the end of preliminary engineering. All future performance is measured against them.
Monthly schedule updates track actual vs. planned dates and feed 60-day look-ahead reports.
Schedule risk analysis uses Monte Carlo simulation at 70-90% confidence to determine schedule contingency needs.
Fast-tracking overlaps design and construction, saving time but increasing coordination risk and rework potential.

ELI5

Think about planning a cross-country road trip with your family. You know when you want to arrive at your destination, but you need to figure out if that timeline actually works given all the stops, detours, and rest breaks along the way. That's schedule feasibility for a building project. The client says "we want to move in by September 2028." The architect's job is to work backward from that date and figure out if it's actually possible. First, you break the whole trip into legs. For a building, those legs are phases: design the building, get permits, hire a contractor, build it, test all the systems, and move in. Each phase takes a certain amount of time, and some can't start until the previous one finishes. You can't build until you have construction documents. You can't get construction documents until you finish design development.

AREProgramming & Analysis

Project Schedule Feasibility: Phasing, Duration, and Milestone Planning

2 min read218 words

Project Schedule Feasibility: What Architects Need to Know

Clients show up with a date circled on a calendar. Your job is to figure out whether that date is real.

This topic connects directly to how you advise clients on project feasibility and provide recommendations when the timeline doesn't match the scope.

Want to track your progress and access more study tools?

Create a free account