Any tool can write it. This is the layer that checks it.
Start with guided facts or upload an existing report. Review the captured facts and applicable checks, including what did not run and why. A candidate remains unissued until an authorised person resolves findings or records a permitted acceptance and issues it.
Both full reporting routes require existing workspace access. The invited beta is separately by request. Ask for a missing file or source, correct the facts, then rerun the supported checks before the human issue decision.
Request a live walkthroughCompare supported figures across reports and sources.
The same number in your SteerCo pack, your RAID log and your status report — or a flag telling you precisely where they diverge. No more three documents quietly disagreeing.
Supported extracted figures retain captured source details — and, where the PM has marked a source verified, who signed it off and when.
Trace any number back to the file you uploaded and the PM’s verification note, where one has been recorded — see exactly which document backs it and, where the PM has marked it verified, who signed off and when. Not “we used your file” — “this file is verified, by this person, on this date.”
We catch the report that lies by looking healthy.
The headline RAG is reconciled against the underlying risks, issues and figures. A programme green on the cover and red in the detail does not get published.
Every critical flag is resolved or accepted on the record — with a 0–100 completeness score beside it.
A critical flag is either resolved or accepted with a written justification that is recorded, not hidden. The completeness score and the integrity check are two separate, deterministic answers — an unresolved critical always blocks publish, whatever the completeness score reads.
Append-only by construction. Every exception a written reason.
Append-only by construction — enforced by triggers in the committed database schema, service-role callers included. Accepting a critical flag requires a justification recorded with the snapshot version. Every change to the audit record writes a new row; corrections supersede, never silently edit; publishing fingerprints the pack with SHA-256 and freezes that fingerprint from then on. That digest is shown on the artefact's coherence report, so you can check it against your own copy.
What happens to a figure from an uploaded file
- 1
Pulled from a named source
File, field and, where the parser captured one, the row — recorded, never retyped.
- 2
Checked by the engine
Applicable coherence checks show where supported facts disagree and where coverage is limited.
- 3
Recorded before it's used
For Excel, CSV and PowerPoint uploads, your source file is saved before mapping review. You confirm proposed column mappings before the programme snapshot is created; your confirmed mappings and transformations are saved with it.
Printed with its source
Printed with its source, verification status and integrity result.
What we check — and what we don't.
WE CHECK
PMOpack runs a deterministic rule engine over the whole pack: dates reconciled across artefacts, money checked against supplied budget data, RAG statuses checked against the evidence beneath them, decisions linked to owned actions, and registers checked for quality and escalation. Fixed, inspectable, identical every run.
WE DON'T
We don't make the governance judgement for you, and we don't use an AI to decide whether a figure is right — the rules do that, deterministically. The PM stays accountable; PMOpack makes sure they're accountable for figures that actually reconcile.
Anonymised, integrity-checked SteerCo, RAID and Status artefacts will be published here once beta customers consent.
Beautifully formatted is easy.
Correct is the hard part.
For people who run project reporting for a living. Not for students, personal projects or coursework. We read every request and reply to those who fit.