In most projects, the problem is not a lack of data, but that the data is scattered and disconnected: the schedule in Primavera, progress in a spreadsheet, the daily report in another sheet or on paper, pending items in an email and a status report that someone rebuilds every Friday. With that dispersion, two things happen: the planner loses hours formatting instead of analysing, and the different versions start contradicting each other.
The solution has two parts that go together: centralise the data in a single source of truth and automate the report so that it stops being rebuilt manually.
Centralise: one single source of truth
In a project, the natural candidate for the single source of truth regarding dates, scope and completed tasks is the Primavera schedule: it is the structure that already contains the activities, logic, dates, resources and baseline. Everything else, lookahead, curves, progress reports and KPIs, should not be an independent document maintained separately, but a view derived from that schedule.
The practical rule is simple: the moment you copy an activity from P6 into an Excel file that then lives on its own, you have created a second truth that from then on begins to diverge. Centralising means that data is entered and maintained in one place, and the rest feeds from it.
Automating reporting: from Excel with macros to online control
Once the single source has been defined, the objective is for the report to generate itself. There are several levels, from lower to higher automation:
Excel macros (VBA): the accessible route
If the team already works in Excel, VBA macros are a very reasonable and low-cost first step. They allow repetitive work to be automated: importing the XER or CSV exported from Primavera, cleaning and reorganising data, refreshing pivot tables, applying the lookahead format and generating the report with one click instead of half a day of copying and pasting.
It is a valid solution that produces immediate results. But its limits should be understood: the result is still a local file, it is not real time, the macro must be run to update it and, if that Excel becomes a file forwarded by email, the version problem returns. Macros automate report production; they do not by themselves solve centralisation or shared access.
Power BI
The next level is to build a data connection that links Primavera with an analysis layer such as Power BI and refreshes dashboards automatically. It is the right option when many projects must be reported frequently. We address it in detail in the article on how to integrate Primavera P6 with Power BI.
Online control with updated data
In an online environment, data is centralised and the whole team consults the same version. Planning information is updated when the Primavera schedule is updated, so its currency depends on that update.
Daily report against the schedule
In practice, the daily report, what really happened today on site, almost always lives disconnected from the schedule. It is recorded in a report, archived, and the comparison with what was planned, if it is made, is made late and manually. And yet that comparison is the heart of control: was the work that the plan said should happen actually executed?
Connecting daily field progress with the schedule allows actual work to be compared with planned work once the data has been incorporated. It follows the same principle as Last Planner PPC: the plan and reality, side by side, using the information from each update.
The PlanBuilt online control tool
This is exactly what we have built at PlanBuilt: an online control tool whose planning data is updated when the Primavera schedule is updated and where daily report data is entered and compared directly with the schedule. Instead of rebuilding reports from scattered sources, the team works in a single centralised environment, fed by the Primavera schedule, where planned and executed work coexist on the same screen.
The result is the practical application of everything described above: fewer hours spent formatting, one single version of the truth and the ability to detect deviations using the information from each update.
Centralising on Primavera and automating reporting, whether with macros, Power BI or online control, is not about having prettier charts, but about shortening the distance between what happens on site and the information used to make decisions.