Every construction schedule an owner receives is built on the Critical Path Method, whether it arrives as a 40-page Primavera P6 printout or a single-page Gantt chart. CPM decides which activities can slip without consequence and which ones move your opening date. Owners who understand how it works can tell a credible schedule from a decorative one in about ten minutes. Owners who don't end up taking the contractor's word for it.
This guide explains CPM in plain terms, walks through a worked example, and covers what owners should actually look for when a schedule lands on their desk.
Where the Critical Path Method came from
CPM was developed in the late 1950s by Morgan R. Walker of DuPont and James E. Kelley Jr. of Remington Rand. Around the same time, Booz Allen Hamilton and the U.S. Navy developed PERT, a related technique. The original CPM software is long gone, but the term now describes any method that analyzes a network of logically linked activities to find the longest path through a project.
That last part is the whole idea. A project is a network of activities joined by logic: foundations can't start until excavation finishes, interior finishes can't start until the building is closed in. CPM adds up the durations along every possible route through that network. The longest route is the critical path, and its length is the shortest time in which the project can be finished.
The four numbers behind every activity
CPM calculates four dates for each activity:
- Early start (ES) and early finish (EF): the soonest an activity can start and finish, given the logic before it. These come from a forward pass through the network, working left to right from the project start.
- Late start (LS) and late finish (LF): the latest an activity can start and finish without delaying project completion. These come from a backward pass, working right to left from the finish date.
The gap between the early and late dates is total float: how long an activity can slip before it pushes out the end date. Activities on the critical path have zero total float. Delay one of them by a week and, unless something else changes, the project finishes a week late.
A worked example
Take a simplified commercial building with eight activities. Durations are in working days:
- A. Mobilization and excavation: 10 days
- B. Foundations: 15 days, after A
- C. Underground services: 8 days, after A
- D. Structure: 30 days, after B
- E. Site works: 12 days, after C
- F. Building envelope: 20 days, after D
- G. Interior fit-out: 25 days, after D
- H. Commissioning and turnover: 10 days, after E, F and G
Forward pass. A runs from day 0 to day 10. B and C can both start at day 10, so B finishes at day 25 and C at day 18. D starts after B, at day 25, and finishes at day 55. E starts after C and finishes at day 30. F and G both start at day 55, finishing at days 75 and 80. H can't start until all three predecessors finish, so it waits for the latest, G, and runs from day 80 to day 90. The project takes 90 days.
Backward pass. Start at day 90 and work back. H must start by day 80. G must finish by day 80, so it must start by day 55: zero float. F must also finish by day 80, but only needs 20 days, so it can start as late as day 60: five days of float. E only has to finish by day 80, so it has 50 days of float, and so does C ahead of it. D must finish by day 55, the earlier of F's and G's late starts, so it has zero float. So do B and A.
The critical path is A–B–D–G–H. Every day lost on foundations, structure or fit-out is a day lost at turnover. The envelope has a small cushion. The underground services and site works have a large one.
View the data
| Activity | Duration | ES | EF | LS | LF | Total float |
|---|---|---|---|---|---|---|
| A. Mobilize/excavate | 10 | 0 | 10 | 0 | 10 | 0 |
| B. Foundations | 15 | 10 | 25 | 10 | 25 | 0 |
| C. Underground svcs | 8 | 10 | 18 | 60 | 68 | 50 |
| D. Structure | 30 | 25 | 55 | 25 | 55 | 0 |
| E. Site works | 12 | 18 | 30 | 68 | 80 | 50 |
| F. Envelope | 20 | 55 | 75 | 60 | 80 | 5 |
| G. Interior fit-out | 25 | 55 | 80 | 55 | 80 | 0 |
| H. Commissioning | 10 | 80 | 90 | 80 | 90 | 0 |
Why owners should care about the critical path
It tells you where to spend your attention. On a typical building, a small share of activities sit on or near the critical path. Those activities deserve weekly scrutiny. If a decision, a submittal review or an owner-supplied item touches the critical path, treat its deadline as the project deadline.
It tells you where acceleration is worth paying for. Paying for overtime on an activity with 50 days of float buys nothing. Paying to recover time on a critical activity can protect an opening date. Owners sometimes approve acceleration costs without asking that question.
It tells you who caused a delay. When a contractor claims an extension of time, the first test is whether the delaying event affected the critical path. An owner-caused delay to an activity with plenty of float may not justify any extension at all. CPM logic is the starting point for almost every delay claim and every defence against one.
Near-critical paths matter as much as the critical one
In the example, the envelope has only five days of float. That's a near-critical path. Lose six days on the envelope and it becomes the new critical path, and the project now finishes a day late even though nobody touched the original critical activities.
Real projects often have several parallel paths within a week or two of each other. That's why a schedule report that only lists critical activities isn't enough. Ask for activities with low total float as well, so you can see which paths are one bad week away from driving completion.
Resources complicate things further. CPM assumes unlimited crews unless the scheduler adds resource constraints. If the same drywall crew is needed on two floors at once, the logic may say both can proceed in parallel while reality says they can't. A path that looks comfortable on paper can become "resource critical" once crews are levelled.
A short glossary of CPM terms
Schedule reviews go faster when everyone uses the same words. These are the terms owners hear most often:
- Relationship types. Finish-to-start (FS) is the default: B starts when A finishes. Start-to-start (SS) lets two activities run in parallel with an offset, like drywall following framing floor by floor. Finish-to-finish (FF) ties two finishes together. Start-to-finish (SF) is rare and usually a red flag.
- Lag. A built-in wait between linked activities, such as concrete curing time. Long or unexplained lags can hide float, so ask what each one represents.
- Milestone. A zero-duration event such as "building enclosed" or "substantial performance." Contract milestones should appear in the schedule exactly as defined in the contract.
- Constraint. A date imposed on an activity rather than calculated from its logic. Some are legitimate, like a utility connection date. Too many make the critical path meaningless.
- Data date. The "as of" date of an update. Everything before it is actual progress, and everything after it is forecast.
What makes CPM schedules go wrong
A CPM schedule is only as good as its logic. On programs we've supported, the same problems come up again and again:
- Missing logic. Activities without a predecessor or successor ("open ends") don't push anything when they slip. The schedule looks healthier than it is.
- Hard constraints instead of logic. A "start no earlier than" or "finish on" date pins an activity to a calendar instead of letting it move with its predecessors. Overused, constraints hide the true critical path.
- Durations that are too long. A single 90-day "interior finishes" activity can't show what's actually driving the work. Long activities hide sequence problems until it's too late.
- Owner activities left out. Design approvals, permit reviews, owner-supplied equipment, tenant decisions and IT installation are often missing. These are exactly the activities that end up on the critical path.
- Calendars that don't match reality. Winter conditions, statutory holidays, noise by-laws and working-hour restrictions in occupied buildings all change how many working days fall in a month.
How to read a CPM schedule as an owner
You don't need to be a scheduler to ask the right questions. When a baseline or update arrives, work through this list:
- Ask for the critical path on one page. Ask for a filtered view showing only critical and near-critical activities, for example everything with less than ten working days of total float. If the contractor can't produce it quickly, the schedule probably isn't being used to manage the work.
- Check that the critical path makes sense. On a building, it usually runs through excavation, foundations, structure, envelope or major MEP rough-in, and commissioning. If the critical path runs through landscaping or signage, something is wrong with the logic.
- Find your own activities. Look for every owner decision, review and supply item. Check their dates, their float and what they drive. These are the delays you'll be responsible for.
- Compare the finish date to the contract. A schedule that shows completion exactly on the contract date with zero float everywhere is often worked backward from the deadline, not forward from the logic.
- Watch how the critical path moves. Each monthly update should explain why the critical path changed, if it did. An unexplained shift is worth a conversation.
The bottom line
The critical path is the project's real deadline, broken down activity by activity. Owners who know where it runs make faster decisions on the things that matter and push back on claims that don't hold up. A schedule nobody on the owner side can read is a schedule that only protects the contractor.
Want an independent review of the critical path on your next project? Book a 30-minute call with Benjamin R. Consulting.
Sources: Critical path method: history, definitions and near-critical paths (Wikipedia); AACE International, Recommended Practice 29R-03, Forensic Schedule Analysis (2011). The worked example is illustrative. This article is general information, not legal advice.