Ending Cut-and-Paste Consolidated Reporting
A programme manager or PMO manager typically oversees a number of project managers at once. Each of those project managers produces a status report — in Word, or Excel, or PowerPoint, depending on preference. Those reports arrive at different times, in different structures, with different definitions of "amber."
The PMO manager's job then becomes reassembly: extracting the relevant sections, reconciling the numbers, normalising the language, and pasting the result into a portfolio report for sponsors, executives or external clients.
It is time-consuming, tedious, and — this is the part worth dwelling on — it produces a document that is already out of date by the time it is distributed.
The real cost is not the hours
The hours are bad enough. But the deeper cost is what the reporting cycle does to the PMO's role.
When a PMO's month is structured around collecting and compiling, the PMO becomes a reporting function. Its output is a document. Its value proposition to the executive is "we tell you what happened." And because compilation takes time, what the executive receives is a description of a problem rather than a chance to intervene in one.
The alternative is a PMO whose output is decisions — but that only becomes possible when the reporting stops being a task.
Escalation instead of transcription
The first change is to stop moving information upward by copying it.
UniPhi's escalation function lets a project manager tag an issue or a risk for escalation to programme, portfolio or sponsor level. The item does not get retyped into a summary. It becomes visible to the senior group, on screen or in report form, as the same record — with the same owner, the same history, and the same open tasks.
Two things follow. First, the escalation is immediate rather than monthly. Second, because the senior stakeholder is looking at the live record rather than a paraphrase, the conversation is about resolution rather than clarification. That materially changes the odds of the issue actually getting closed.
Document-within-a-document reporting
The second change addresses formal reporting, which does not disappear — boards, clients and funding bodies will continue to require documents.
UniPhi's document-within-a-document capability lets a programme manager compose a consolidated report that incorporates ten project management reports rather than transcribing them. The child reports are referenced, not copied. When a project report is updated, the consolidated report reflects it. There is no version drift between the project view and the portfolio view because there is only one set of content.
For the PMO, the monthly consolidation task changes from days of assembly to a review of an assembled document.
Roll-up across financial and time data
Beyond narrative reporting, the same principle applies to numbers — and this is where the leverage is largest.
Because cost and time data are captured at project level in a common structure, they can be aggregated along effectively any dimension. Questions that would previously have required a data request and a week of waiting become a single query:
- How much did we spend on road construction in this electorate last financial year?
- How much is committed against budget for the far north of the state?
- What was our total national spend on bitumen?
UniPhi was used to manage exactly this class of question on the Queensland Flood Road Recovery Program, where a very large number of geographically dispersed works packages had to roll up into a single funded programme view. The reporting requirement there was not unusual in kind — only in scale.
What the PMO does with the time
This is the point of the exercise. Eliminating cut-and-paste reporting does not just save hours; it changes what the PMO is for.
Instead of documenting the reasons a project is struggling, the PMO spends its time managing and leading programmes toward outcomes — intervening early, rebalancing resources, killing the initiatives that no longer earn their place, and coaching the delivery teams that need it.
That is a materially more valuable function than report production, and it is available to any PMO willing to stop producing the ten reports.
Next in this series: Automated Portfolio Cost Reporting for the PMO
Related: UniPhi and the PMO · No Reports, No Email, No Inbox · The Five Problems Every PMO Faces
How long does your consolidation cycle take? Email sales@uniphi.com.au.