The critical path is the sequence of linked activities, from start to finish, that takes the longest total time. Activities on it have zero (or the least) total float, so if any one of them slips, the finish date slips. The critical path method (CPM) is the scheduling technique that calculates it from activity durations and logic links (finish-to-start, start-to-start and so on).
Why it matters
Not every delay matters equally. A late delivery on a task with three weeks of float may cost nothing; a one-day slip on the critical path costs a day of the whole job, extended general conditions and possibly liquidated damages. Delay claims and time extensions are argued with critical path analysis.
Worked example
Illustrative: on Riverside Medical Center, the path Level 3 MEP rough-in → fire damper install → above-ceiling inspection → ceiling close-in → finishes → substantial completion is critical. If the damper submittal for CO #14 slips two weeks and the dampers can’t be installed, close-in slips two weeks, and so does substantial completion, unless the team re-sequences or accelerates.
Common mistakes
- Schedules with missing logic links, so the “critical path” is meaningless.
- Not updating the schedule, so the critical path drifts silently.
- Asking for time on change orders without showing critical path impact.
How os.construction handles it
We’re building schedule data on the same core as RFIs, submittals and change orders, so an item that touches a critical activity can be flagged as a schedule risk.