PMOpackFree check
Project reporting, kept connected.

Your next reporting pack, prepared for review — and easier to stand behind.

Start a new programme or take over existing reporting. Turn the information you supply into a reporting candidate, review the captured facts, work through supported checks, and keep the source and decision record with what you issue.

Beta priority: SteerCo, Status, RAID and Milestone. Supported formats, available checks and limitations are shown in the relevant journey. Full reporting routes require existing workspace access. The free scan checks one supported file and does not issue a pack. Invited beta is separately by request. 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.

For either route, confirm scope and supported formats, review sources, request missing source material, correct facts and rerun checks. A candidate is not issued; an authorised person makes the final decision.

Planned preview: compare with an explicitly selected prior issued record and copy a factual change summary. Email us to ask about future comparison access; emailing us grants no access.

Request a live walkthrough

Or email [email protected]

Change since last update · Week 32 · demo2 changed1 unchanged
Go-live milestone
Last update 14 Nov · This update 28 Nov
Moved 2 weeks
Open critical risks
Last update 4 · This update 5
1 new
Budget at completion
Last update £4.20m · This update £4.20m
Unchanged
  • Prepare from reviewed facts
  • Work through supported findings
  • Issue with an accountable record
01 · The proof, documented

We tested an AI assistant on 30 April 2026. Here’s what it gave us.

We asked it for a SteerCo pack, the request a PM runs every week. The deck looked right. The assistant told us it was done, then said it could not apply the edit. That gap, between a document that looks right and a record that is right, is the whole reason PMOpack exists.

No one wants beautifully formatted wrong answers. So we built the checking first.

› where are the slides?
“The full 11-slide deck is now pushed… You should see all of them now.”
△ “I couldn’t apply the edit you requested. Please try again.”
says done. wasn’t done. unreliable reporting.

Restated from a test run on 30 April 2026. Shortened for this page. Not a claim about any vendor’s product today.

02 · Fair question

Why not just ask a general AI chat tool to write the pack?

You can, and it will look good. Here is the same request, two ways.

You ask
"Build the Q3 SteerCo pack from these four files."
A general AI chat answers
A polished 12-slide pack. Budget at completion shown as £4.20m on slide 3. Slide 9 says £4.65m. Nothing mentions the gap, and it cannot show where either figure originates.
What a buyer needsA general AI chatPMOpack
Checks supported reports against one anotherIf you think to ask — and it cannot show its working.Runs on every pack, by fixed rules.
Shows where a figure originatesUsually not, and it cannot prove it.Supported extracted figures retain their captured source details.
Gives the same verdict on the same dataWording and judgement can vary run to run.Rules, not a model, decide what passes.
Leaves a record an auditor can readA chat log.An immutable, hash-verified issued pack.
Records who accepted a conflictNo.Acceptances need a named justification, per period.

PMOpack still uses AI to read your files and draft narrative. It never decides what passes. Fixed rules do.

What to expect

What it checks. And what it does not.

It checks
  • That dates agree across the documents in the pack.
  • That supported figures in a report agree with the supplied source and other supported reports.
  • That the overall RAG is consistent with the risks and workstreams under it.
  • That recorded decisions have an owner and a due date.
  • Milestone slippage, against tolerances that depend on the type of milestone.
  • Public holidays and the blackout periods you declare.
  • What is missing, shown as a completeness score.
It does not
  • Know whether your project is sound.
  • Prove your numbers against your source system. It checks that your files agree with each other.
  • Sign for you, or replace your judgement.
  • Claim certification, or any speed we have not measured.
  • Quote a count of rules.
03 · Who it is for

Built for everyone who answers for the pack.

PMO / Delivery Lead

The pain: you build the pack the night before, the numbers do not match, and you answer for it in the room.

How PMOpack helps: it builds the pack from your files, shows where the documents disagree, and leaves every decision to you.

Director with a team

The pain: every PM builds a different pack, and you find the surprise in the meeting.

How PMOpack helps: every pack goes through the same checks, and each exception is accepted in writing and kept on the record.

MD, COO or sponsor

The pain: you cannot tell if reporting across programmes can be trusted, and a steering committee, a client or your boss will ask how you know.

How PMOpack helps: an immutable record behind every issued pack, and one standard, whoever prepared it.

04 · The market

Your steering committee is already sceptical. That is the right instinct.

The trust gap around AI-produced information is measured, and so is how often delivery misses its dates and budgets. All figures below are from research published in 2025 or later. PMOpack is built for the side of that gap that answers to a steering committee, a sponsor or a client.

Global trust study
66%
of people rely on AI output without evaluating its accuracy (2025).
KPMG and University of Melbourne, “Trust, attitudes and use of AI: a global study 2025”, April 2025.
Responsible AI study
25%
of companies have fully mature responsible AI frameworks, though 85% are now implementing them (2026).
BCG and MIT Sloan Management Review, “Responsible AI Needs More Than Good Intentions”, May 2026.
AI sentiment index
43%
of consumers surveyed trust companies to manage AI-related data effectively (2026).
EY, “AI Sentiment Index 2026” (UK press release), May 2026.
NISTA
34
UK government major projects were rated Red for delivery at 31 March 2026.
NISTA, “Major Projects Annual Report 2025-26”, July 2026.
Technology leaders survey
43%
of technology leaders rank safety, risk and governance guardrails as the top enabler for scaling agentic AI (2026).
Bain & Company, “The Missing Architecture for Agentic Software Development”, September 2026.
Wellingtone
38%
of organisations deliver projects on time most of the time or always (2025).
Wellingtone, “State of Project Management 2025”, March 2025.
State of AI survey
27%
of organisations using gen AI review all of its output before use; 30% review less than a fifth (2025).
McKinsey, “The state of AI: How organizations are rewiring to capture value”, March 2025.
PMOpack
When AI is used, how do you know the pack is consistent and traceable?

Third-party research, not PMOpack results. Each source is under its card. These studies describe the problem PMOpack is built for.

05 · The journey

Bring the update you already have. Carry the record forward.

The steps it takes, in order. Start new or take over, then follow the same path to a published pack. You see what needs support and what needs a person's decision. It is not a promise to create every project document.

  1. Choose your way in

    Start a new delivery with guided questions, or take over a delivery that is already running.

  2. Bring what you know

    Answer guided questions after you consent, or upload the one file that matters most: Excel, CSV, PowerPoint, or one of two supported project-tool CSV exports.

  3. See what was found

    Detected columns or captured answers are shown for review before use.

  4. Confirm and correct

    Set the targets and currency, fill in the key details, fix anything misread, and say the data is yours to use.

  5. Resolve overlaps

    Where a file clashes with itself, both values are shown. You decide which stands.

  6. Lock the baseline

    The programme and its first snapshot are set up and kept, ready for reporting.

  7. Generate and check

    The pack is built and its documents are checked against each other. Each problem is fixed, or accepted in writing.

  8. Publish with a record

    An issued PDF the issuer can download, with the decision record.

  9. Upcoming comparison preview

    Upcoming preview: compare the latest update with the last issued pack, and keep the record going.

06 · The real product

PMOpack flags what does not add up, and shows you exactly why.

Coherence report

SteerCo pack · Blocked · Demo programme · Snapshot 2026-09-v3
Blocked
Publish blocked: 1 critical finding unaccepted
Resolve or accept each with written justification before this can publish.
1CRITICAL

Findings

D1● CRITICAL
AFFECTED · milestones[3].planned_date
Go-live date inconsistent: SteerCo shows 2026-11-02 but Milestone Report shows 2026-11-16.
Update one artefact so both show the same go-live date. If a change request is in flight, accept with justification and regenerate both next cycle.
Accept with justification
See what accepting looks like
ACCEPTED EXCEPTION
Change request approved at SteerCo; both documents to be aligned next cycle.
R4● CRITICAL
AFFECTED · workstreams[0].rag
Missing Path to Green: "Workstream: Data migration" is RED with no Path to Green populated.
Populate all four Path to Green fields: what's wrong, what needs to happen, when it will be Green, and the accountable owner.
PATH TO GREEN
WHAT IS WRONG
Legacy extract failed reconciliation on 3 of 14 ledgers.
WHAT NEEDS TO HAPPEN
Re-run extract with corrected mapping; reconcile remaining ledgers.
TARGET DATE OR TRIGGER
2026-10-17
ACCOUNTABLE OWNER
A. Okafor
Built from the real coherence report screen, in the light theme, with demo data. PMOpack does not approve the pack: a person fixes each critical finding or accepts it in writing, and until then it holds the pack back from publishing.
Start with the free scan

Free coherence check: sign in, upload one file. No card.

  • 9
    steps from first file to published pack
    Each one shown, so nothing is hidden.
  • 8
    report types on the roadmap
    SteerCo, Status, RAID, Milestone, Working Group, Risk Heat Map, Budget Tracker, Plan on a Page.
  • 4
    kinds of file to start from
    Excel, CSV, PowerPoint, or one of two supported project-tool CSV exports.
  • 3
    PDF styles for your audience
    Precision, Enterprise or Narrative.
  • 1
    hash-verified record per issued pack
    Kept with the exceptions a person accepted, and why.
  • 0
    AI guesses in the pass or fail call
    Fixed rules decide. The same input gives the same result.
07 · See it catch it

Four things a tired reviewer misses at 11:21 pm.

Date reconciliation

If your SteerCo says 1 September and your Milestone Report says 1 October, that is a critical flag.

A reviewer can miss that between two reports at 11pm. PMOpack checks this supported comparison before either page reaches the steering committee.

DATE RECONCILIATION · GO-LIVE
SteerCo cover14 Sep
Milestone Report07 Sep
Which date is right?You decide
Phantom number

If a RAID entry mentions £50K, check what the supplied source supports.

Compare the RAID statement with the supplied source and the Status report. Where a supported figure disagrees, review the source and resolve the difference before issue.

“…residual exposure of £50Kpending mitigation.”
● Source evidence for this figure needs review
Verified source marking

Supported extracted figures retain captured source details, and where the PM has marked a source verified, who signed it off and when.

Trace a number back to the file you uploaded and the PM's verification note, where one has been recorded. Not “we used your file”, but “this file is verified, by this person, on this date.”

£2.41m● VERIFIED
SOURCE · finance_export.xlsx
uploaded and marked verified by R. Patel
matches your uploaded Excel · attested by R. Patel, 28 Jun
Critical-path primacy

One red critical-path task turns the workstream red. That is not a setting.

Generic tools roll up status by volume. PMOpack rolls up by delivery reality: a single red task on the critical path drives the whole workstream red, before any percentage threshold.

SCHEDULE
● Red
COST
● Green
QUALITY
● Amber
SCOPE
● Green
1 red task on the critical path → workstream ● Red
08 · The moat

Review mappings before a snapshot is created

For Excel, CSV and PowerPoint uploads, your source file is saved on upload. You review its proposed column mappings before confirming them. Once you do, a programme snapshot records those mappings and the transformations applied.

● SOURCED

Supported extracted figures retain captured source details, including the row where the parser captured one.

● CONFIRMED

For Excel, CSV and PowerPoint uploads, your source file is saved first. You review proposed column mappings before a programme snapshot is created.

● ON RECORD

Once you confirm, the journey (source, transformations applied, confirmed mapping) is saved with the snapshot. Cancel the review and no snapshot is created.

What gets checked

Four questions the steering committee will ask. Answered before they ask them.

Not a spell-check on your prose. A reconciliation across the whole reporting pack, run the same way on supported figures from an uploaded file, before a report renders.

Dates

Key dates reconciled across the reports

Go-live, milestone sets and period ends checked against each other, plus weekends, public holidays and your declared blackout periods.

Money

Figures from an uploaded file traced back to the budget

Workstream totals, forecast at completion and contingency draws reconciled, including figures quoted in prose, where no reviewer looks.

Status

A RAG that matches the detail underneath it

Programme and workstream status reconciled against the register beneath it, with a path to green required on every amber and red.

Decisions

Decisions that actually happened

Approved decisions carried into this period's action log, each with a named owner and a due date. One recorded as not enacted is raised, not buried.

09 · Two ways in

Two ways in. The same record behind both.

Pick a door to see its line. Both lines end at the same stop: one reporting record.

Brownfield path · Take over a live deliveryBest when the programme is already running and the data lives in files.
  1. Upload what you already run

    Start with one supported file: Excel, CSV, PowerPoint, or one of two supported project-tool CSV exports. Review the extracted facts before use.

  2. See what was found

    Every detected column is shown with a preview of its values and its proposed target.

  3. Confirm and attest

    Set the targets and currency, fill in the key programme details, and attest that the data is yours to use.

  4. Resolve overlaps

    Where the file clashes with itself, both values are shown. You decide which stands.

  5. Lock the baseline

    The snapshot is frozen with the captured source details for supported extracted facts.

  6. Generate, check, publish

    Review applicable checks on the candidate. An authorised person decides whether to issue a PDF.

  7. One reporting record

    Baseline, checks and published packs. Both lines stop here.

No file to hand? You can also start from the information you have, in a guided conversation.

Run the free coherence scan

Free coherence check: sign in, upload one file. No card.

With a file
Upload a source file
Drop in the programme file you already use. PMOpack detects its format, extracts the useful fields, and lets you confirm the mapping before a programme snapshot is created.
Choose your programme file
Choose fileNo file chosen
  • Excel
  • CSV
  • PowerPoint
  • Supported project-tool CSV exports
PMOpack detects the format automatically. You will review every mapped field before a programme snapshot is created.
Upload and review
No file
Nothing to upload?
Start the guided conversation instead. PMOpack asks one focused question at a time, offers suggested answers where they help, and shows a concise review before it creates a programme.
What is the programme called, and when does it go live?
Atlas Programme, 14 March
Start a guided conversation
Or type it in
Enter programme data
No file and no time to talk? Type the key facts into a short form, step by step. You review the whole set before the baseline is locked.
Programme name
e.g. CRM platform migration
Sponsor
e.g. Jane Smith
Step 1 of 4. Budget, reporting cycle and your sign-off follow.
Next
Three doors on the same take-over screen: upload a file you already run, answer one question at a time, or type the facts in. Built from the real screen’s wording, with demo data. Whichever door, you review everything before it counts.
10 · What you get · the artefacts

What is available and what is planned.

SteerCo, Status, RAID and Milestone are available in the beta. Budget Tracker, Risk Heat Map, POAP and Working Group are planned for later. The wheel and rhythm below show the planned eight-artefact roadmap.

Eight-type reporting roadmap
One set of facts sits at the centre. Four report types are available in the beta; the other four are planned for later.
See the planned rhythm ↓
Benefits

What each artefact set gives you

A cross-artefact conflict check
Disagreements surfaced with both values before anything ships.
Captured source details
Supported extracted figures retain the source details the parser captured.
An immutable issued record
The issuer can download the hash-verified PDF and review its checks.
Review before a snapshot is created
Every proposed column mapping is shown to you first. No snapshot is created until you confirm it.
Conflicts accepted by name
Accepting a serious conflict needs a written justification, recorded for that period only.
Critical path first
Milestone slippage is judged against the critical path, so the slip that moves your date is not buried.
Three PDF design styles
Precision, Enterprise or Narrative, to suit the audience reading the pack.
11 · What you get · the rhythm

A reporting rhythm built around your SteerCo.

This is a planned four-week example for the eight-artefact roadmap, with a SteerCo in week 3 and the next in week 6. SteerCo, Status, RAID and Milestone are available in the beta; the other four report types are planned for later.

Planned eight-artefact publication rhythm
ArtefactWeek 1Week 2Week 3Week 4Frequency
Working GroupWeekly
RAIDWeekly
StatusWeekly
Risk Heat Map––Every 2 weeks
Milestone–––Monthly
Budget Tracker––Every 2 weeks
POAPEvery 1 to 2 weeks
SteerCo–––Every 3 weeks
Scheduled publicationPlanned extra POAP when change is activeSteerCo meeting

In this planned rhythm, the week 2 Milestone view feeds the week 3 SteerCo pack. Budget Tracker, Risk Heat Map, POAP and Working Group are planned for later. The extra POAP weeks illustrate periods when the plan is changing.

12 · The record

Governance is a record, not a slide.

A slide shows one moment. PMOpack keeps your files, the checks that ran, the exceptions a person accepted, and the pack you published. So you can show how you got there for that reporting period.

“Where did that number come from?”
Supported extracted figures retain their captured source details.
“Who accepted that conflict?”
The exception, the reason and the name, kept with the pack.
“What exactly did we publish?”
The issuer can download the immutable pack and verify its hash.

Join the beta. By request.

BETA

We are working with a small group of delivery professionals to prove the reporting journey on real work. Request to join the beta.

One active workspace per person during the beta. Built for the delivery work you own and maintain.

The scan includes
a completeness readout of one supported file: which reports it can support and what is missing. It uses no AI, saves nothing and does not issue a pack.
PMOpack adds
the reporting journey for SteerCo, Status, RAID and Milestone: reviewed facts, the checks across reports, accepted exceptions kept with a reason, human issue and the hash-verified record.
Enterprise conversations cover
running several programmes in one workspace. The checks, the source record and human issue are part of PMOpack itself.
Request to join Beta Workspace

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.

Or email [email protected]

Questions people ask first

Can I not just do this with my own prompts, or my team's?

You can get a good-looking pack. What you cannot get from a prompt is a check you can prove ran, a record of where each supported figure came from, and a verdict that does not change with the wording. Keep your general AI for thinking and drafting. Use PMOpack when your weekly update has to become a consistent reporting pack, with the last version, the sources, the checks and the decisions carried with it.

Does AI decide what passes?

No. AI reads your files and drafts narrative. Fixed rules decide pass or fail.

What if it still gets a number wrong?

Figures come from your files, and you confirm how each column maps before a snapshot is created. Rules hold the pack when artefacts disagree. One limit to be straight about: if a number is wrong in the same way everywhere in your source, a consistency check cannot know. It makes disagreements visible, it does not replace your judgement.

Where does my data go?

The database is in London, UK, with access controlled per workspace. Details are on the Trust page.

Will you train AI on our programme data?

No. PMOpack uses an AI model provider to read your files and draft narrative. The provider's commercial terms state that it may not train models on customer content. We do not use your programme data to train any model. Details are on the Trust page.

Will my auditor or steering committee accept this?

PMOpack provides captured source details, applicable findings and recorded human decisions for review. Acceptance remains their decision; PMOpack makes no claim of certification.

How much work is it to set up?

There is nothing to install and no integration to build. You upload a file you already have, confirm the mapping, and see the result.

How do I get access?

Access to the beta is by request, for the first group of delivery professionals. Request to join and we reply to those who fit. The details are shared when you are invited. One active workspace per person.

What does the free scan include?

A completeness scan of one supported file (Excel, CSV, PowerPoint, or one of two supported project-tool CSV exports): which artefacts it can support and what is missing. It uses no AI and saves nothing. The cross-artefact conflict check, generating and publishing are on the paid plan.

Is this only for FCA-regulated teams?

No. The checks and the record apply to any programme. Working to a specific regulator, or have a specific reporting requirement? Contact us and we will tell you what fits today and what we can build with you.

Find the conflict before your board, sponsor or client does.

See where your packs disagree. The free scan shows what your pack is missing. The full product shows where your documents disagree.

The check is open to everyone: no invite, no card. The beta is by request. 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.

Or email [email protected]

A record an auditor can follow.

P.S. The coherence scan reads one file, uses no AI and saves nothing. The worst case is you learn your file is already ready.