One job. Three ways to plan it.

There is no single correct way to build a construction schedule. There are several, and each one fits a different kind of work.

Pick the wrong one and you'll fight your schedule all year. Pick the right one and the plan almost runs itself.

Let's walk through the three that matter most on site.

The backbone: Critical Path Method

Critical Path Method — CPM — is the method construction runs on.

You break the job into activities. You link them by real, physical logic: you can't strip the formwork before the concrete cures; you can't backfill before the pipe is laid and tested. The software then finds the longest path through that logic. That path is your project duration. Touch anything on it, and the finish date moves.

CPM is at its best when the scope is fixed and the sequence is physical. A bridge. A foundation. A structural frame. You know what has to happen, and in what order, before you start.

It's deterministic: give it the durations and the logic, and it hands you the date. That's its strength. It's also its blind spot.

When one resource controls everything: Critical Chain

CPM makes one quiet assumption — that you always have every resource you need, exactly when you need it.

Real sites don't work that way.

Imagine one tower crane serving three work fronts. Or a single post-tensioning crew needed in four places the same month. CPM will happily schedule them all at once. The crane can't be in three places. The plan is a fiction.

Critical Chain Method fixes this by planning around the limiting resource, not just the logic.

It also does something clever with time. Under CPM, every engineer pads their own activity — a little extra, just in case. That safety gets buried inside dozens of tasks, and it quietly gets wasted. Critical Chain strips the padding out of each activity and pools it into a few visible buffers.

A project buffer sits at the very end, protecting the contract completion date. Feeding buffers guard the main chain where side activities join it. There's even a resource buffer — with no duration at all — a simple signal that tells your specialist crew to be ready before the chain reaches them.

The safety is still there. It's just out in the open now, where you can manage it — instead of scattered across every task, where it disappears.

When you can't plan it all yet: Rolling Wave

Some projects are simply too long to plan in full detail on day one.

Take a two-year job. The earthworks you'll start next month, you can plan hour by hour. The fit-out eighteen months out? You'd be guessing — and a detailed guess only looks like a plan.

Rolling wave planning handles this honestly. You detail the near term, and you deliberately leave the far term coarse — as planning packages. As each package approaches, you break it down into real activities.

One warning. A planning package is not an empty box. It still carries a budget, a duration, and assigned resources. It's a considered placeholder — not a blank you'll fill in "later." The detail arrives later; the commitment does not.

Real projects are hybrids

Here's what the training course won't tell you: you don't pick one method and marry it.

A real construction schedule is usually all three at once. CPM is the backbone. Rolling wave handles the far horizon. Critical-chain buffers protect the few spots where a single crane or crew decides the outcome.

The point isn't loyalty to a method. It's fit.

The method is a tool. The job decides which one you reach for. Force one method onto every project, and you become the planner with a hammer, treating every problem as a nail.

And this is exactly why construction stays predictive at its core. You can rewrite a piece of software next sprint. You cannot re-pour a foundation. On site, the plan comes first — because the concrete is permanent.

Practical insight

Before you build the next project's schedule, ask three questions:

Is the scope fixed, or will the far end still be taking shape while I build? Is there one resource — a crane, a crew, a batching plant — that everything leans on? How far ahead can I honestly plan in real detail?

Your answers point straight at the method. Fixed and physical → CPM. One resource rules everything → protect it with buffers. Too long to detail → roll the wave.

You won't choose just one. You'll choose the mix that fits the job.

Key takeaways

✔ There's no single way to schedule — the method must match the work.
✔ CPM is the construction backbone: fixed scope, physical sequence, one calculated finish date.
✔ CPM's blind spot is resources — it assumes you always have what you need.
✔ Critical Chain plans around the limiting resource and pools safety into visible buffers.
✔ Rolling wave details the near term and leaves the far term as considered planning packages.
✔ A planning package still carries budget, duration and resources — it's never an empty box.
✔ Real schedules are hybrids: CPM backbone, rolling-wave horizon, buffers at the bottlenecks.

What's coming next

In Week 4, we set the strategy and the rules before opening the software. This week, we chose the method that fits the work.

Next week, we turn strategy into structure. We'll take a project charter — the contract's promise of what, when, and for how much — and begin turning it into a real, buildable schedule.

Because a method is only a way of thinking. Next, we start building.