In many projects, it is not practical to use the master schedule, with hundreds or thousands of activities, to define and show the next tasks to be performed. A site manager does not need to see the entire project critical path to know what is due this week; they need a clear, filtered and actionable extract. That is why the lookahead report exists: a report that facilitates communication of the next activities to be executed.
The lookahead allows information to be handled more simply and efficiently. It is normally prepared by the contractor to coordinate short-term works, with a horizon ranging from 2 weeks to several months depending on the project and the level of detail. It is probably the planning document most people read on a construction site, and precisely for that reason it should be taken seriously.
Why the lookahead works
Its advantages are what have made it a widely adopted standard:
- It is simple and easy to understand, accessible to all project participants, not only to the planning engineer.
- It is quick to update and allows the level of detail to be increased or reduced as needed.
- It gives a clear view of the activities required to achieve the next milestones.
- It is easy to share.
- It can be segmented into several reports by contractor or discipline.
- It allows feedback to be received from people outside the planning function but expert in each area, on execution times and interfaces that the planner may not see from the office.
That last point, feedback from those at the workface, is where the lookahead adds the most value and where it is most often wasted. A schedule that only flows from the office to the field is a monologue; a well-managed lookahead is a conversation.
The traditional formats and their limits
This report can be created in several formats:
From the planning software itself. A filter is applied, the relevant columns are activated and a Gantt chart is generated for export to PDF. It has one major advantage: it comes directly from the real schedule.
In PowerPoint. Less common, but it allows text, images and contextual information to be organised in a very visual way. Useful for steering committees more than for daily coordination.
In Microsoft Excel. Without doubt the most common format, because of its flexibility and because everyone in engineering knows how to use it. And this is where a red line should be drawn: in some cases people make the mistake of thinking that a large project can be planned with a simple list of activities, dates and a chart. That is not planning. It ignores relationships between activities, calendars, resource management and the baseline against which performance must be compared.
What the report should contain
Lookahead reports should be simple, light and visual. As a minimum:
- Project information (name, location)
- Date
- List of activities
- Duration
- Responsible party
- Status
- Notes
- A graphical element that makes visualisation easier
It is advisable to issue this report at least once a week, while the master schedule is updated and reviewed daily for optimum control by the planning engineer.
Up to this point, that is the classic theory. It still applies. What has changed, and changed a lot, is how this report is produced.
The change in mindset: the lookahead is not written, it is generated
Here is the most common process error I see on site: the planner spends several hours every week rebuilding the lookahead manually in Excel, copying activities from the schedule, adjusting dates, changing colours and fighting with formatting. Even when the Excel file has formulas, it is manual, repetitive work and, worst of all, prone to error.
The underlying problem is not the time wasted. It is that the moment you copy an activity from P6 into an independent Excel file, you have created a second version of the truth. And the two versions start diverging immediately: the schedule is updated on Monday, the Excel was sent on Friday, and suddenly the field is working with dates that no longer exist. Multiply that by five contractors, each with their own copy, and you have version chaos: is this the latest one? I received another one yesterday by email.
The modern principle is simple: the lookahead is not a separate document, it is a filtered view of your single source of truth. The planner's job is not to rebuild the report every week, but to design once the process that generates it automatically from the schedule. Filter, time window, columns, format: define it once and regenerate it automatically. This allows the planner to stop formatting and return to the work that truly adds value: analysing, anticipating constraints and releasing the work.
From static snapshot to live dashboard
A PDF or an Excel file is a snapshot: it is born out of date. The moment you send it, it no longer reflects reality. For pure coordination that may be enough, but for improving communication between office and field it falls short:
- It does not connect with the baseline, so it does not show real deviation.
- It does not capture status from the field: Done / Not Done has to be entered manually.
- It does not allow filtering by discipline or contractor on the fly; a file has to be generated for each one.
- And it lives in email, with all the fragmentation that implies.
That is why today the recommendation for teams that are serious about coordination is to move to tools designed specifically for this: online dashboards where the lookahead is updated from the schedule, where everyone sees the same live version, where status is captured from the workface and where anyone can filter by discipline in one click, without asking for a new file.
The whole team accesses the same online board, with data from the latest update of the Primavera schedule.
How we approach it at PlanBuilt
This is precisely the philosophy behind the way we work at PlanBuilt. Our methodology starts from a non-negotiable principle: one single source of truth, the schedule, from which everything else, lookahead, curves and metrics, is derived automatically, without double entry or diverging versions.
The dashboard data is updated when the Primavera schedule is updated. On that basis, we deliver an online interactive dashboard where the project team can see in one place:
- The lookahead for the coming weeks, filterable by contractor, discipline or area.
- The weekly plan with Done / Not Done status captured from the field and its reliability measured through PPC (Percent Plan Complete), the Last Planner metric that turns missed commitments into data rather than an argument.
- The actual progress S-curve against the baseline, to see at a glance whether the project is ahead or behind.
- Performance indicators (SPI/CPI) and interference detection before they reach the workface.
The objective is not to produce more reports, but fewer: one single access point, linked to the latest Primavera update, replacing the storm of Excel files sent by email. Because a lookahead only fulfils its purpose if everyone looks at the same version, and looks at it in time.
