The monthly review is on Thursday. On Monday morning you start building the pack.
You open eleven .mpp files, one after another. You copy percent complete, cost to date and the next milestone out of each one into a spreadsheet. Some plans use custom fields the others do not, so three of them need a judgement call. By Tuesday afternoon the spreadsheet is consistent. Wednesday goes into charts and slides, and into the two projects whose numbers looked wrong enough to be worth a phone call.
Thursday morning the pack is ready. It is accurate, it is well made, and it describes the portfolio as it stood on Monday.
Nobody in the room will say that out loud. Everybody in the room knows it.
The age of a report is not an accident
There is a temptation to treat the delay as a productivity problem — the analyst was slow, the PMs sent their files late, the template needed rework. Speed up the people and the report gets fresher.
It does not, because the age is structural.
Whenever a report has to be assembled by hand, its minimum age is the time it takes to assemble it. Two days of work means the data is at least two days old before anyone reads a word. Add the wait for the last plan to arrive, and the gap between the world and the picture of the world settles somewhere around a week.
That gap does not shrink by working faster. It shrinks only by removing the assembly. Removed entirely, it becomes a job that runs at two in the morning.
What the gap actually costs
A stale project report is not merely inelegant. It changes decisions in three specific ways.
It hides what happened this week. The events most likely to need a decision — a delivery that slipped on Tuesday, a resource who went sick on Wednesday — are precisely the ones that land after the data was frozen. The report is systematically blind to the newest news, which is the news that matters.
It makes questions unanswerable. Someone asks what happens if the commissioning package moves by three weeks. The honest answer is that finding out means another two days of assembly, so the question goes into the minutes as an action instead of being answered in the room. Decisions get deferred by a month because the data cannot keep up with the conversation.
It quietly encourages rounding. When a figure costs two days to produce, nobody reproduces it to check. The number that took effort acquires authority it has not earned, and small transcription errors survive because verifying them is more expensive than believing them.
Copying is where the errors live
The assembly is not only slow. It is the single least reliable step in the whole chain.
Every project plan is already a database: tasks, dates, costs, assignments, baselines, earned value. All of it is structured, and all of it is correct at the moment you open the file. Then a human reads it on screen and types it somewhere else.
That retyping is where a column gets misaligned, where a cost is taken from the wrong baseline, where one project’s percent complete means work and another’s means duration. None of these are failures of care. They are the ordinary yield of doing by hand, eleven times, something the machine already knows.
Removing the assembly, not speeding it up
This is where a different arrangement helps, and it is worth being precise about what it changes.
OneClickExporter opens the plan — a single project or a master plan with its linked subprojects and a shared resource pool — and extracts what is in it into a set of clean, validated files: projects with consolidated earned value, tasks, assignments, resources, milestones, and the time-phased series behind them. No file is opened by hand and nothing is retyped.
OneClickReport is the Power BI side: fourteen report pages that read those files and draw the portfolio. Progress, budget against planned and actual, milestones and their deadlines, resource load against availability, the earned value curve with CPI and SPI over time.
The important word is refresh. Once the connection exists, producing this month’s report is not a smaller version of the work you used to do. It is a different act: you press refresh, and the picture is current. Pointing that refresh at your own folder is a single setting: how to change the data sources of the dashboard.
What changes in the room
The obvious gain is the days you get back. It is not the interesting one.
The interesting change is that the report stops being a deliverable and becomes a view. When the pack takes two days, you look at it monthly, because that is what it costs. When it takes a minute, you look at it on Tuesday because something felt off — and again on Thursday morning before the meeting, so the numbers on the screen are this morning’s numbers.
And the question that used to become an action item gets answered while everyone is still in the room, which is the only time an answer is worth anything.
None of this makes the projects go better on its own. But it moves the conversation from what did the plan look like last week to what do we do now — and the second conversation is the one you were trying to have all along.
OneClickReport turns Microsoft Project plans into Power BI dashboards. The extraction runs on your machine and reads your plans without changing them; your files never leave your network.
#PMO #ProjectReporting #PowerBI #MicrosoftProject