The three-week look-ahead: every project has a master schedule, and almost no crew works from it

The weekly meeting that makes it real

The look-ahead is worthless as a document produced by the office and distributed. It works as a conversation, and the format is consistent:

• Who attends: the superintendent, the project manager and the foreman of every trade working in the next three weeks — not the sales contact, the person who will actually run the crew.
• What is reviewed: last week's commitments and whether they were met, this week's tasks, and the constraints on weeks two and three.
• What each trade commits to: specific tasks with specific completion, said aloud in front of the other trades that depend on them.
• How long it takes: forty-five minutes, weekly, at a fixed time. A meeting that expands stops being attended by the people who matter.

The commitment in front of peers is the mechanism. A trade that has told the electrician, out loud, that the corridor will be clear on Thursday behaves differently than one that received an email with a schedule attached.

Measuring whether the plan is worth anything

The one metric that makes short-interval planning self-correcting is the percentage of committed tasks completed as promised. Count the tasks committed for the week, count how many were finished, and divide.

The number itself matters less than the reasons behind the misses. Recording a cause for every incomplete task, week after week, produces the most useful management report on a construction project — and the pattern is remarkably consistent across jobs:

• Prerequisite work not complete — the largest single category on most projects.
• Material or equipment not available.
• Information not received — RFIs, submittals, owner decisions.
• Manpower short — the crew was moved elsewhere.
• Access or area not available.
• Weather.

Most builders assume manpower dominates and discover it does not. When prerequisite work and information are the top two causes — which they usually are — the productivity problem is a coordination problem, and the crews being implicitly blamed were the ones standing around waiting.

Pulling procurement into the look-ahead

The constraint that most often stops a task three weeks out is material, and material is decided months earlier. Connecting procurement to the look-ahead means working backwards from the need date through four steps:

• Installation date from the schedule.
• Delivery date, allowing time for site storage, inspection and staging.
• Fabrication and lead time, which for long-lead items dominates everything else.
• Submittal and approval time, including the possibility of a rejection and a resubmittal — the step that is almost never allowed for.

Working backwards frequently reveals that a submittal due next month is already late for an installation four months out. Finding that in week two is a phone call; finding it in month four is an acceleration claim, a substitution request or a delay that belongs to nobody.

A project in numbers

A fourteen-month commercial project that introduced a weekly look-ahead meeting and a constraint log in month three.

• Month 3 baseline: 54% of committed tasks completed as planned. Top causes: prerequisite work 31%, information not received 24%, material 18%.
• Month 5: 68%, after the constraint log added named owners and dates and the RFI backlog was worked in the same meeting.
• Month 8: 79%. Procurement pulled into the look-ahead; two long-lead items identified as already late and resolved with expedited fabrication rather than schedule loss.
• Month 12: 84%, with weather and access — the two least controllable causes — making up most of the remaining misses.

The project finished eleven days ahead of the contract date. The number that explains it is not the completion rate itself but the composition of the misses: information and prerequisite work fell from 55% of causes to 19%, which is coordination work done in a forty-five minute meeting rather than crews absorbed by waiting.

One detail worth keeping: the two long-lead items found in month eight would have stopped the project for roughly three weeks each. They were discovered because someone worked backwards from an installation date that was still four months away — the least dramatic and most valuable habit in construction planning.

The version that fits a small builder

Everything above describes a commercial project with multiple trades and a superintendent. A residential remodeler with two crews and six active jobs faces the same problem in a different shape — and the same method scales down to something that takes twenty minutes a week.

• One page per job, three weeks out. What happens this week, next week and the week after, with the constraint on each.
• Friday afternoon, not Monday morning. Planning the week ahead on Friday means Monday starts with material staged and questions already asked, instead of a crew standing in a driveway while somebody makes phone calls.
• The homeowner is a constraint owner. Selections, decisions, access, pets and vacations belong in the log with dates, because in residential work the client is the most frequent source of delay and the least likely to be tracked.
• Inspections planned backwards. Small projects lose more days to inspection scheduling than to any trade, and the fix is booking against the look-ahead rather than after the work is complete.

The gain in small-project work is disproportionate, because a two-day delay on a six-week job is felt immediately by a client who lives in the building — and because a crew idle for half a day is a much larger percentage of a small builder's week than of a large project's.

Why it fails, and it is never the format

Short-interval planning is not complicated, and companies still abandon it. The reasons are consistent and none of them are about the template:

Commitments are made for people who are not present. A project manager promising that the plumber will be finished on Wednesday is not a commitment, it is a prediction. Only the person who controls the crew can commit, which is why attendance is the method.

Misses are treated as failures rather than data. The first time a foreman is criticized in the meeting for a task he did not complete, the commitments become conservative and the plan stops being useful. The correct response to a miss is the question of what caused it — and, frequently, an apology from whoever caused it, which is often the office.

The constraints are never actually cleared. A log reviewed weekly with the same overdue items produces cynicism faster than no log at all. Someone must own clearing them between meetings, and that someone is usually the project manager rather than the field.

It is imposed rather than adopted. The trades that benefit most are the ones who spend the most time waiting, and framing the meeting as their protection — a way to stop being sent to a site where they cannot work — is what turns attendance from a requirement into a preference.

Six mistakes in short-interval planning

• Producing the look-ahead in the office and emailing it. It is a conversation, not a document.
• Inviting the wrong people. The person who runs the crew must be in the room; the account manager is not a substitute.
• Vague constraints. "Waiting on the architect" cannot be chased; "RFI 114, needed by September 8" can.
• Skipping the reasons for misses. Without causes, the completion rate is a score rather than a diagnosis.
• Letting the meeting grow. Ninety minutes weekly and the foremen stop coming, which ends the method.
• Leaving procurement out. The most damaging constraints are decided months before they appear in a three-week window.

Five numbers to track

Five metrics keep planning honest. Percentage of committed tasks completed, weekly, by trade. Causes of incomplete tasks, categorized, which is where the actionable information lives. Constraints open past their required date, with the name attached, since an aging constraint is a future delay with a date already on it. Average age of open RFIs and submittals, the leading indicator of the information category. And long-lead items with a verified delivery date against need date — the small list that prevents the delays nobody sees coming.

Frequently asked questions

What is a three-week look-ahead schedule?

It is the bridge between the master schedule and the work that will actually be performed. It takes the next three weeks of the master schedule, breaks the activities into tasks small enough to be started and finished, and asks one question of each: is this task ready? A task is ready when the design question is answered, the material is on site, the area is available, the crew and equipment are assigned, the prerequisite work is complete and any permit or inspection is in hand. Anything failing one of those tests is not a plan — it is a hope with a date on it, and putting it in front of a crew is how weeks are lost. The master schedule remains the contractual instrument; the look-ahead is the operational one, and it is where coordination actually happens.

What is a constraint log and how is it used?

It converts the schedule into a list of obstacles with owners and dates, and it needs only five columns: the task that cannot proceed, the constraint stated specifically, the person who owns clearing it, the date it must be cleared working backwards from when the task must start, and status reviewed weekly. The value is in the specificity and the name. Waiting on the architect is not a constraint; RFI 114, submitted August 12, needed by September 8, owner named, is a constraint that can be chased, escalated and documented. The log doubles as the most useful delay record a project can produce, because it captures what was known, when it was known and who was asked — which is exactly the evidence a delay claim requires and almost never has.

Who should attend the weekly look-ahead meeting?

The superintendent, the project manager and the foreman of every trade working in the next three weeks — the person who will actually run the crew, not the sales contact or account manager. The meeting reviews last week's commitments and whether they were met, this week's tasks, and the constraints on weeks two and three, with each trade committing to specific tasks out loud in front of the other trades that depend on them. That peer commitment is the mechanism: a trade that has told the electrician the corridor will be clear on Thursday behaves differently than one that received an email with a schedule attached. The meeting runs forty-five minutes at a fixed weekly time, because a meeting that expands stops being attended by the people who matter.

How do you know whether the look-ahead is working?

By measuring the percentage of committed tasks completed as promised, and — far more importantly — by recording a cause for every task that was not. The pattern is consistent across projects: prerequisite work not complete, material or equipment unavailable, information not received, manpower short, access not available and weather. Most builders assume manpower dominates and discover it does not. When prerequisite work and information are the top two causes, which they usually are, the productivity problem is a coordination problem, and the crews being implicitly blamed were the ones standing around waiting. The completion percentage is a score; the distribution of causes is the diagnosis, and it is what tells the office which of its own processes to fix first.

Does look-ahead planning work for a small residential builder?

It scales down to about twenty minutes a week and the gain is proportionally larger, because a half-day of idle crew is a much bigger share of a small builder's week. The version that fits is one page per job covering three weeks, with the constraint on each item. Plan on Friday afternoon rather than Monday morning, so the week starts with material staged and questions already asked instead of a crew waiting in a driveway. Treat the homeowner as a constraint owner, with selections, decisions, access and vacations logged with dates, since in residential work the client is the most frequent source of delay and the least likely to be tracked. And plan inspections backwards, because small projects lose more days to inspection scheduling than to any single trade.