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 walkthroughOr email [email protected]
- Prepare from reviewed facts
- Work through supported findings
- Issue with an accountable record
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.
Restated from a test run on 30 April 2026. Shortened for this page. Not a claim about any vendor’s product today.
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.
| What a buyer needs | A general AI chat | PMOpack |
|---|---|---|
| Checks supported reports against one another | If you think to ask — and it cannot show its working. | Runs on every pack, by fixed rules. |
| Shows where a figure originates | Usually not, and it cannot prove it. | Supported extracted figures retain their captured source details. |
| Gives the same verdict on the same data | Wording and judgement can vary run to run. | Rules, not a model, decide what passes. |
| Leaves a record an auditor can read | A chat log. | An immutable, hash-verified issued pack. |
| Records who accepted a conflict | No. | 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 it checks. And what it does not.
- 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.
- 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.
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.
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.
Third-party research, not PMOpack results. Each source is under its card. These studies describe the problem PMOpack is built for.
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.
Choose your way in
Start a new delivery with guided questions, or take over a delivery that is already running.
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.
See what was found
Detected columns or captured answers are shown for review before use.
Confirm and correct
Set the targets and currency, fill in the key details, fix anything misread, and say the data is yours to use.
Resolve overlaps
Where a file clashes with itself, both values are shown. You decide which stands.
Lock the baseline
The programme and its first snapshot are set up and kept, ready for reporting.
Generate and check
The pack is built and its documents are checked against each other. Each problem is fixed, or accepted in writing.
Publish with a record
An issued PDF the issuer can download, with the decision record.
Upcoming comparison preview
Upcoming preview: compare the latest update with the last issued pack, and keep the record going.
PMOpack flags what does not add up, and shows you exactly why.
Coherence report
Findings
See what accepting looks like
Free coherence check: sign in, upload one file. No card.
- 9steps from first file to published packEach one shown, so nothing is hidden.
- 8report types on the roadmapSteerCo, Status, RAID, Milestone, Working Group, Risk Heat Map, Budget Tracker, Plan on a Page.
- 4kinds of file to start fromExcel, CSV, PowerPoint, or one of two supported project-tool CSV exports.
- 3PDF styles for your audiencePrecision, Enterprise or Narrative.
- 1hash-verified record per issued packKept with the exceptions a person accepted, and why.
- 0AI guesses in the pass or fail callFixed rules decide. The same input gives the same result.
Four things a tired reviewer misses at 11:21 pm.
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.
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.
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.”
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.
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.
Supported extracted figures retain captured source details, including the row where the parser captured one.
For Excel, CSV and PowerPoint uploads, your source file is saved first. You review proposed column mappings before a programme snapshot is created.
Once you confirm, the journey (source, transformations applied, confirmed mapping) is saved with the snapshot. Cancel the review and no snapshot is created.
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.
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.
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.
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 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.
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.
Agree to the guided setup
You consent before the guided conversation begins. AI helps you capture details; it does not decide anything.
Talk it through
One rolling conversation covers scope, milestones, budget and risks. No fixed number of questions.
Review what was captured
See the programme set-up as the conversation understood it, and correct it before it counts.
Your programme and baseline are created
The programme and its first period snapshot are set up, ready for artefacts.
Generate and check each period
Artefacts are built and checked against each other every reporting period.
Issue with a verified record
Issued PDF the issuer can download, with the decision record.
One reporting record
Baseline, checks and published packs. Both lines stop here.
The messages you write and the confirmed facts in this interview. Uploaded source files are not sent.
PMOpack validates the draft and you review it before any programme is created.
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.
See what was found
Every detected column is shown with a preview of its values and its proposed target.
Confirm and attest
Set the targets and currency, fill in the key programme details, and attest that the data is yours to use.
Resolve overlaps
Where the file clashes with itself, both values are shown. You decide which stands.
Lock the baseline
The snapshot is frozen with the captured source details for supported extracted facts.
Generate, check, publish
Review applicable checks on the candidate. An authorised person decides whether to issue a PDF.
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.
Free coherence check: sign in, upload one file. No card.
- Excel
- CSV
- PowerPoint
- Supported project-tool CSV exports
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.
What each artefact set gives you
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.
| Artefact | Week 1 | Week 2 | Week 3 | Week 4 | Frequency |
|---|---|---|---|---|---|
| Working Group | Weekly | ||||
| RAID | Weekly | ||||
| Status | Weekly | ||||
| Risk Heat Map | – | – | Every 2 weeks | ||
| Milestone | – | – | – | Monthly | |
| Budget Tracker | – | – | Every 2 weeks | ||
| POAP | Every 1 to 2 weeks | ||||
| SteerCo | – | – | – | Every 3 weeks |
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.
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.
Join the beta. By request.
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.
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.