PMOpack
Verification

The bit competitors don't have.

Any AI tool can write a governance document. PMOpack is the verification layer that proves it's correct — one reconciled set of numbers across every board artefact. Here is exactly how it works, and exactly what it checks.

One figure. One source. The same number everywhere.

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.

01LINEAGE + VERIFIED SOURCE

Every figure has a paper trail — and a human who signed it off.

Trace any number back to the file you uploaded and the PM's verification note — see exactly which document backs it. Not “we used your file” — “your PM signed off on this file, on this date.”

12 Sep✓ VERIFIED
● source · phoenix_plan.xlsx · go-live
● uploaded and marked verified by the PM
● value · 12 Sep
✓ matches your plan
02THE WATERMELON TEST

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.

🍉Green cover, red detail
cover RAG · Green
data migration · Red
→ blocked · cannot publish
03CLAIM STATUS + COMPLETENESS

Every claim is verified, flagged, or accepted on the record — with a 0–100 score on top.

Nothing sits in an unexamined middle. Each figure is checked; if a PM overrides a flag, the justification 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.

86
2 critical · must resolve or accept
1 warning
11 verified to source
04IMMUTABLE AUDIT TRAIL

Immutable by construction. Every exception a written reason.

Append-only, enforced by Postgres triggers — including from service-role callers. Accepting a critical flag requires a justification stored permanently with the snapshot version. Even we can't rewrite the record.

15:24 · published · RAID Log P4 · integrity ✓
15:22 · exception · F3 accepted · note logged
15:21 · integrity run · rule engine · 2 critical
15:20 · generated · SteerCo P4 · 42s
append-only · enforced by Postgres triggers
The verification path

What happens to every figure

1
Pulled from a named source
Row, cell, file — recorded, never retyped.
2
Checked by the engine
Board-defensibility checks — does it add up, does it agree with every other artefact?
3
Tagged for certainty
Verified, logged, or an inference you accept or reject. Never auto-written.
Printed with its source
Defensible under board, auditor and regulator scrutiny.
Methodology

What we check — and what we don't.

WE CHECK

PMOpack runs a deterministic rule engine over four categories: date alignment, financial reconciliation, RAG consistency, and decision-action linkage. 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.

Public proof

See real, checked artefacts.

SteerCo PackIntegrity-checked ✓anonymised · coming post-beta
RAID LogIntegrity-checked ✓anonymised · coming post-beta
Status ReportIntegrity-checked ✓anonymised · coming post-beta

Beautifully formatted is easy.
Correct is the hard part.

That's the part we built.
PMOpack