PMOpackFree check
Article

How often should I report, and to whom?

Report weekly to the people doing the work, fortnightly to the working group that unblocks them, and monthly to the steering committee that decides. Each audience gets its own artefact. The same facts flow up; only the detail and the questions change.

Cadence is the part of governance people argue about most and think about least. Too often and nobody reads it. Too rarely and the board finds out late. This is a rhythm to use as a starting point. Adjust it to your programme. Do not skip the reasoning.

The three audiences

  • The team and workstream leads need to know what is due this week, what is blocked, and who is waiting on whom. Weekly. Short.
  • The working group (the leads together, plus the people who can unblock them) needs to see dependencies, risks that crossed a line, and decisions that are theirs to make. Fortnightly.
  • The steering committee needs decisions, headline status, milestones, budget, top risks, and what happened to last month’s decisions. Monthly, or at each gate. The page order is in What should a SteerCo pack include?

A suggested four-week rhythm

WeekArtefactReaderWhy this week
1Status ReportTeam, leadsSets the period. What is due, what is blocked.
1RAID log refreshLeadsEvery open row touched at the start of the cycle.
2Working Group ReportWorking groupDependencies and cross-workstream calls, mid-cycle.
2Milestone ReportLeads, sponsorForecast dates settled before the SteerCo is drafted.
3SteerCo packSteering committeeDecisions, with two weeks of settled facts behind them.
3Budget TrackerSponsor, financeIssued with the SteerCo so the numbers are the same.
4Risk Heat Map, Plan on a PageSponsor, wider orgThe summary views, after the decisions are made.
4Status ReportTeam, leadsCloses the period. What changed, what carries over.

The SteerCo sits in week three on purpose. The milestone forecast and the budget are settled the week before, so the pack is built on numbers that have stopped moving. Packs drafted the night before the meeting are where most disagreements between documents come from.

Rules that make a cadence work

  1. Every artefact has one named reader. If you cannot say who reads it and what they do with it, stop producing it.
  2. The same fact appears once, then flows. The go-live date is set in the Milestone Report. The SteerCo pack quotes it. Nobody retypes it.
  3. Late is a status. If a report slips, say so in the next one. A gap in the record is a question later.
  4. Decisions have a home. Working group decisions go in the Working Group Report. Board decisions go in the SteerCo pack. Both are carried forward until closed.
  5. Change the rhythm on purpose. Weekly SteerCos in a crisis are fine. Write down when they go back to monthly, and why. If you have just inherited the crisis, start with How do I take over a programme that is in trouble?

The week-one RAID refresh is the step most teams drop first. The rules for keeping it alive are in What is a RAID log, and how do I keep it honest?

A real example

A programme I joined reported to its board every week. Every pack was 40 slides. The board had stopped reading them, and the leads spent two days a week writing them. We moved the board to monthly with a decision-first pack, put a fortnightly working group in between for the cross-workstream calls, and kept a one-page weekly for the team.

Writing time dropped to under a day a week. The board started making decisions again, because the pack asked for them. The working group caught two dependency slips that would have reached the board late under the old rhythm.

Where PMOpack fits

PMOpack builds the eight artefacts in this rhythm from the data you already keep, each with the same vocabulary, so a fact set in the Milestone Report is the same fact the SteerCo pack quotes. Fixed checks run across the set at generation time and flag where two artefacts in the same period disagree. A critical finding blocks publish until a person fixes the data or accepts it with a written reason, and the acceptance is stored. The rhythm itself is yours to set; this one is a suggestion, not a rule. PMOpack does not manage the project, update the plan, or decide when the board meets. It keeps the artefacts honest with each other whenever you choose to issue them.

Questions people ask

How often should a steering committee meet?
Monthly, or at each gate, as a starting point. Weekly in a crisis, with a written note of when it returns to monthly and why.
What is a working group report for?
Dependencies, risks that crossed a line, and decisions the workstream leads can make together without the board. Fortnightly works for most programmes.
Why issue the SteerCo pack in week three?
So the milestone forecast and the budget are settled the week before. A pack built on numbers that have stopped moving disagrees with the other reports far less often.
What if a report is late?
Say so in the next one. Late is a status. A silent gap in the record becomes a question a board or reviewer will ask later.

See the checks on your own pack.

We are working with a small group of delivery professionals to prove the reporting journey on real work. One active workspace per person.

Or email [email protected]

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.

Want to know where your data goes and who can see it? Read the Trust page.