Digital PMO and reporting
We connect the schedule, the cost data and the project team's status into dashboards, workflow tools and report packs, and we build them with the same people who understand the programme. Everything is configured in your own Microsoft 365 tenant.
What feeds the dashboard
| Information | Source | Refreshed |
|---|---|---|
| Activity dates, float, progress | Primavera P6 or Microsoft Project | Weekly, after the schedule update |
| Budget, commitments, actual cost | Your cost system or cost ledger | Monthly, at period close |
| Milestones, variations, notices | Contract administration app | As entered by the team |
| Status, issues, actions | Weekly capture form for project managers | Weekly |
The dashboard on the right is built with sample data to show the format. The real build reads from your systems, with the refresh cadence agreed in the scope.
Illustrative dashboard using sample data. Each bar shows earned value as a percentage of the package budget; the white mark shows planned value to the data date on the same scale. Package SPI is earned value divided by planned value for that package: Package A 82% against 78% planned, B 61% against 70%, C 74% against 73%, D 45% against 44%, enabling works 100% against 100%, fit-out 28% against 40%. Programme SPI is total earned value divided by total planned value; CPI is earned value divided by actual cost.
Three outputs, one data model
A dashboard on its own is a picture. The value comes when the same data also drives the workflow and the report, so nobody retypes a figure three times.
Executive dashboard
Schedule, cost, risk and milestone status for a programme or portfolio, with drill-down from the board summary to package detail. Refreshed on the agreed cadence from the live schedule and cost data.
Example: sample dashboard
Milestone and contract workflow
A Power Apps tool holding contract milestones, variations, notices and payment applications, with reminders ahead of contractual dates and an audit trail that is ready if a claim ever arises.
Example: sample milestone register
Generated report pack
Weekly and monthly report packs assembled by Power Automate from the same data, with the narrative written by people. The team's time goes into the commentary and the decisions, not the formatting.
Example: sample report extract
What is included in a build
Configuration and data mapping
We agree the controls process and reporting cadence first, then map each field in the dashboard to its source and refresh rule.
Testing with your data
The build is tested against a full period of your real data before it goes live, with the figures reconciled to the schedule and cost reports.
Documentation and training
A short operating guide for the people who update it, and a handover session so the dashboard keeps working after the engagement ends.
Your tenant, your ownership
Workspaces, apps and data sit in your Microsoft 365 tenant from day one. Your administrators control access, and the solution runs where your other Microsoft data runs. We hold no copy of your data beyond the engagement unless you ask us to support it.
Licensing and administration
Power BI and Power Apps licences, and the administrator roles needed to run the solution, are confirmed with your IT team during scoping. They are your licences, not ours.
Support after handover
Optional support on a retainer for changes, new packages or new reports. Without it, the solution still runs; it simply stops changing.
What we need from you
- Access to a Microsoft 365 tenant, or a decision to create one, with an administrator we can work with
- The schedule files and cost reports the dashboard will read, and who updates them
- The report formats and the questions your board or client asks each period
- One owner on your side for the data, and one for the process
- A full period of real data for testing before go-live
Common questions
Does the data leave our environment?
The workspaces, apps and data sit in your Microsoft 365 tenant. During the build we work inside it under accounts you control. We keep no copy of your data after handover unless you ask us to support the solution, and then only what support needs.
What licences are needed?
Power BI and Power Apps licences for the people who use them, confirmed with your IT team during scoping. They are your licences, held in your name.
Can it read from Primavera P6 directly?
Yes, from P6 exports or, where your IT team allows, from the database or the P6 web services. The refresh cadence is agreed in the scope.
What happens after you leave?
The solution keeps running in your tenant. Documentation and a handover session cover routine updates; changes and new reports are available on a support retainer.
Is this software development?
It is configuration of Microsoft tools around your controls process, delivered as management information. We do not develop or sell software products.
Tell us about your task
Tell us what you report today and who reads it. We aim to reply within one working day. We confirm the scope and fee once we have the information needed to assess the work.