The CPM Schedule Is Not Your Look-Ahead

By Leonard Kogan  |  November 10, 2026  |  In Practical Terms

They’re both schedules. They’re not the same tool.

The look-ahead runs the next three weeks. It covers crews, areas, and daily moves. It changes constantly, and it should. That’s its job.

The CPM schedule runs the project. It manages strategy, logic, sequence, and the critical path. Its job is to stay credible, telling the truth about where the project is going and what’s driving it.

Confuse the two, and you slowly destroy the one that’s harder to rebuild.

How the Confusion Starts

It usually begins reasonably. Work opens up in some areas and stalls in others. The team wants the master schedule to reflect what’s really happening in the field, with new forecast dates for this floor, that trade, or this inspection.

Next month, conditions shift again, and the requests return. More new dates, more adjustments, activity by activity.

Each request sounds like precision. Together, they’re something else.

Changing dates in a CPM schedule is not simply entering new dates in a cell. Every forecast date is an output of durations and logic. To force a date, you have to change the durations and logic behind it, and those changes ripple downstream through everything they touch.

Do this for most activities every month, and the schedule’s logic stops being a model of how the project gets built. It becomes a collection of forced answers.

Every forced date is a small cut to the logic. Enough cuts, and the schedule stops telling you the truth.

The Reliability Paradox

Here’s the part that surprises people. Making the master schedule track every short-term field movement doesn’t make it more accurate. It makes it less reliable.

A CPM schedule earns trust by being right about what matters, including the sequence, the drivers, and the critical and near-critical paths.

When its logic is continuously rewritten to chase near-term dates, the critical path shifts with every revision, not because the project changed, but because the model did.

Before long, nobody can say with confidence what’s actually driving completion, which is the one question the CPM schedule exists to answer.

And the short-term dates it was bent to show? Many of them don’t hold anyway. Field conditions move faster than any monthly update cycle. You’ve traded the schedule’s long-term credibility for short-term precision it can’t actually deliver.

Two Tools, Two Jobs

The solution isn’t discipline for its own sake. It’s using each tool for what it’s built to do.

The look-ahead, a two- or three-week rolling schedule managed at the superintendent level, is where the daily and weekly reality lives. Crews, areas, access, sequencing adjustments, and the plan for Thursday all belong here.

It’s supposed to change every week. Updating it costs nothing in terms of CPM logic integrity because it isn’t meant to replace the master schedule’s underlying logic.

The CPM schedule absorbs what’s structural, including real impacts, real resequencing, and genuine changes to the plan. It gets updated on a disciplined cycle, with changes that preserve the integrity of the logic.

That way, when it moves, the movement means something. And when leadership asks what’s driving the date, the answer is credible.

The two reconcile naturally. The look-ahead operates within the windows the CPM defines, while persistent deviations in the field, not weekly noise but meaningful patterns, flow back into the master schedule as considered logic changes.

The Principle

When a project leans on its master schedule to do the look-ahead’s job, it’s usually a sign of something deeper. The team needs better short-term visibility and is reaching for the only schedule it has.

The fix isn’t to bend the CPM. It’s to stand up the tool that’s actually built for the job.

Steer the week with the look-ahead. Protect the path with the CPM.

Different tools. Different jobs. Both essential.

← Back to All Insights