Scheduling & the Critical Path

Welcome

Hello, and welcome. This is Super Structures General Contractors — a national general contractor headquartered in Powhatan, Virginia — here to help you and your clients build something that lasts. We're glad you're with us, and we look forward to connecting with you.

Alright, Scheduling & the Critical Path. Don't let the plain title fool you. Here's the part that actually matters on the job: Build a sequenced schedule, find the critical path (the chain that sets the finish date), and protect it with look-ahead planning. Learn it well and you'll know exactly which delays matter, which ones don't, and where to spend your attention every week.

A schedule turns the work into a sequence of tasks with durations — and shows what has to happen when, and what has to happen first. It is the PM's most important planning tool and, when it comes to delays, the most important piece of evidence on the job. This lesson covers how a schedule is built, how to find the critical path, and how to manage the schedule once the job is running.

Building the schedule

• Break the work into activities. Start from a work breakdown — site, foundations, structure, enclosure, rough-ins, finishes, site finishes, closeout — and break each into tasks small enough to track, usually a few days to a few weeks each.
• Estimate durations. Base them on crew size, production rates, and quantities, not hope. A 20,000-square-foot slab with a known crew has a known duration.
• Add the logic. Each activity gets predecessors. The most common relationship is finish-to-start (framing starts when the foundation is done), but start-to-start (drywall can begin on floor one while rough-in continues on floor two) and finish-to-finish relationships let you overlap work realistically. Lags add waiting time, such as seven days of cure before stripping forms.
• Include procurement and approvals. Submittal review, fabrication, and delivery are activities with durations. A schedule that ignores them is the reason steel "shows up late."
• Add milestones. Notice to proceed, dried-in, permanent power, substantial completion, and any contract dates with liquidated damages attached.
• Account for calendars. Workdays, holidays, and a weather allowance by season.

Finding the critical path

Once the logic is in, scheduling software (or a careful hand calculation) runs a forward pass to find the earliest each activity can start and finish, and a backward pass to find the latest each can start and finish without delaying the end. The difference is float (slack).

• The critical path is the longest chain of dependent tasks from start to finish. Those activities have zero float; a one-day delay on any of them delays the whole job one day.
• Activities off the critical path have float you can use — but float is shared along a chain, and once it is used up, that chain becomes critical.
• Near-critical paths (a few days of float) deserve almost as much attention as the critical path, because a small slip makes them critical.

The critical path moves. A rain delay in sitework, a slow steel delivery, or a fast framing crew can shift which chain is longest. That is why the schedule has to be updated.

Managing the schedule

• Set a baseline. Once the owner accepts the schedule, save it. Every update is compared against it, which is how you see slippage and prove delay.
• Update regularly — monthly at minimum, with actual start and finish dates and remaining durations, so the finish date is honest.
• Run a look-ahead. A rolling two- to three-week look-ahead pulls the next few weeks out of the master schedule and adds detail: which crew, which area, what material and equipment, which inspection, what has to be answered first. The super runs it with the trades; the PM clears the constraints.
• Protect the critical path above all. When resources are short, they go there first.

Going Deeper (Intermediate)

Read a Gantt chart (bar chart) for what it shows and what it hides. Bars show when; the logic lines show why. A schedule with bars and no logic cannot calculate a critical path, which is why most commercial contracts require a CPM (critical path method) schedule with logic, not a picture.

Understand the difference between total float (how long an activity can slip without delaying the project finish) and free float (how long it can slip without delaying the next activity). A sub with five days of total float can still make the next trade wait.

Resource leveling smooths out the plan so you are not asking for three crane picks at once or two trades in the same room. It is the difference between a schedule that calculates and a schedule that can actually be built.

Advanced / Pro-Level

Running a schedule like a PM:

• Baseline versus updates is how delay is measured. Keep every update; the sequence of updates tells the story of the job.
• Long-lead procurement belongs in the schedule, tied to the submittal log, with submit, approve, fabricate, ship, and deliver activities.
• Delay analysis methods include impacted as-planned, collapsed as-built, windows analysis, and time-impact analysis (TIA), which inserts a delay event into the current update and measures how far the finish moves. TIA is the most widely accepted method for a change-order time extension on a running job. Know what your contract requires.
• Recovery and acceleration — adding crews, overtime, second shifts, or re-sequencing — cost money, and who pays depends on who caused the delay. Document the cause before you accelerate, and get direction in writing if the owner wants a recovery schedule.
• Float ownership is a contract question. Some contracts say float belongs to the project (whoever uses it first), others reserve it for the owner. Read the clause before you argue about it.
• Weather is excusable in most contracts only when it is unusually severe compared to normal conditions for the season, and only when it affects the critical path. Keep daily weather records.
• An updated CPM schedule is both a management tool and a claims tool; "the schedule" is how delay disputes are won.

Practice Challenge

Task A (5 days) is followed by B (10 days), then D (4 days). In parallel, A is also followed by C (6 days), which must finish before D starts. What is the critical path, the total duration, and C's float — and what happens if C slips a week? (Answer: A-B-D is 5+10+4 = 19 days and is the critical path; A-C-D is 5+6+4 = 15 days, so the project finishes in 19 days and task C has 4 days of float; if C slips 7 days it uses its 4 days of float and pushes D by 3, so the project finishes in 22 days and the C chain has become the critical path.)

In Practice

A PM who knows the critical path spends Monday morning on the three activities that actually set the finish date and lets a two-day slip on a non-critical task ride. A PM who does not know it treats every delay as an emergency, burns overtime on work that had float, and still finishes late because the slow steel delivery that really mattered was never on anyone's list.

Common Mistakes to Avoid

• Not identifying the critical path, or building a bar chart with no logic so it cannot be found
• Leaving procurement, submittal review, and inspections out of the schedule
• No look-ahead planning, so the master schedule never reaches the crews
• Failing to update the schedule with actuals, so it stops matching the job and loses its value as evidence
• Accelerating before documenting who caused the delay

Takeaway: Build a sequenced schedule, find the critical path (the chain that sets the finish date), and protect it with look-ahead planning.

Educational content — not legal, accounting, safety, or contractual advice. Follow your contract's specific procedures and deadlines, your company's policies, and the codes and requirements that apply in your jurisdiction.