A three-week lookahead schedule is a short-term plan that pulls the next three weeks of work out of the master programme and shows it in enough detail for the site team to prepare and carry it out. It answers one question for foremen, supervisors and trade partners: what are we doing next week, and is everything ready for it?
The lookahead must stay a filtered view of the master schedule, refreshed every week from the latest update, not a separate plan. Its job is to expose and clear the constraints on near-term work before the crews arrive, which is the make-ready practice that the Last Planner System made standard.
What is a lookahead schedule and why do you need one?
The master schedule may hold hundreds or thousands of activities and is usually updated monthly. Field teams often ignore it because it feels abstract or out of date. A lookahead extracts a rolling window, typically three weeks and sometimes up to six, and adds the short-term detail the master does not carry: who is doing the work, what they need, and what is still blocking it.
It bridges high-level planning and day-to-day execution. Week one should be firm and ready to commit to. Weeks two and three are where constraints are found and removed so that the work can move into week one with nothing missing.
Where does lookahead planning come from?
Lookahead planning as a formal step comes from the Last Planner System, developed by Glenn Ballard and Greg Howell through the Lean Construction Institute in the 1990s. It plans at several levels: the master schedule, phase (pull) planning, the lookahead, and the weekly work plan. In the lookahead window each activity is screened for constraints such as design information, materials, labour, equipment, permits, access and completed prerequisite work, and the team acts to remove them. Only work that is ready is committed to the weekly work plan, and the share of commitments completed each week is tracked as Percent Plan Complete (PPC).
You do not need to run the full Last Planner System to benefit from a lookahead, but the make-ready idea is what turns a filtered list into a working plan.
How do you build a 3-week lookahead from Primavera P6?
- Update the master schedule first. Status the schedule to the progress cut-off and reschedule, so the data date in P6 is current and nothing incomplete sits before it.
- Apply a window filter. Show activities that are in progress, plus activities not yet started whose start falls between the data date and three weeks after it. P6 filters can use dates relative to the data date, so the same filter rolls forward with each update.
- Separate field work from make-ready items. Keep construction, installation and testing activities on the crew list. Do not simply delete procurement, submittals and approvals: move the ones that feed the window into the constraint log, because they are what will stop the field work.
- Sort and group. Order by early start, and group by area or trade with activity codes so each foreman sees their own work.
- Export or print. Use a P6 layout or report to produce a simple table with the columns below.
What should a three-week lookahead template include?
| Column | Purpose |
|---|---|
| Activity ID | Same ID as the master schedule, so progress can be traced back |
| Activity description | As in the master, with a site note if needed |
| Area or location | Where the work happens |
| Responsible party | The trade, crew or foreman who owns the work |
| Start and finish (forecast) | From the current update |
| Remaining duration | From the current update |
| Days across the three weeks | A simple bar or tick per working day |
| Constraints | What must be in place first (information, materials, labour, equipment, permits, access, predecessor work) |
| Ready (yes / no) | Whether every constraint has been cleared |
| Notes | Date constraints from the master, hold points, inspections |
A separate constraint log, with an owner and a date needed for each constraint, keeps make-ready actions visible between meetings.
How do you keep the lookahead tied to the master schedule?
- Update the master first. Always status the master before generating the lookahead, so completed work, delays and logic changes flow into the short-term plan.
- Use the same activity IDs. Never rename or renumber activities in the lookahead. Extra detail can sit below a master activity, but it should reference that activity's ID.
- Flag constraints. If a lookahead activity carries a date constraint such as Start On or After (often called "start no earlier than"), note why. Constraints the field cannot see often cause confusion.
- Review weekly. Hold a short lookahead meeting every week. If the lookahead shows work that is not in the master, or the field plans to sequence work differently from the logic, find out why and reflect it in the next update.
Common lookahead mistakes and how to fix them
| Mistake | Consequence | Fix |
|---|---|---|
| Including too many activities | Crews ignore the list and it becomes noise. | Keep it to what the crews can act on. As a working guide, 20 to 40 activities per area or trade, focused on critical and near-critical work. |
| Out-of-date data date | Work that should have started is missing, or finished work still shows. | Generate the lookahead only from a schedule statused to the latest progress cut-off. |
| Ignoring prerequisites | Work is planned before predecessor work, information or materials are in place. | Screen every activity in the window for constraints and mark it ready only when all are cleared. |
| No responsible party | Crews do not know who does what. | Give every activity a responsible party (a resource or activity code in P6) before exporting. |
| Not refreshed weekly | The lookahead goes stale and the field loses trust in it. | Produce a new three-week window every week, on a fixed day ahead of the weekly meeting. |
How do you make the lookahead actionable?
- Make it visible. Post a copy in the site office or on the coordination board. A file attached to an email is easily missed.
- Give it an owner. One person, often the project engineer or site planner, owns the weekly refresh, the constraint log and the meeting.
- Ask for commitments. In the meeting, ask each foreman whether they can start and finish their week-one work as shown. If not, record the reason, assign the constraint to someone, and carry the change into the next schedule update.
- Measure reliability. Track how much of what was committed last week was actually completed, and the reasons for misses. Recurring reasons point to the constraints to manage earlier.
Done this way, the three-week lookahead becomes the main tool for weekly site coordination while staying anchored to the master programme. Project Assure sets up lookahead and weekly planning routines tied to the P6 programme as part of its project planning work.
