Governance and Review Calendar: Keep the Improvement Alive Long After Handover

The Governance and Review Calendar does one thing. It schedules the recurring governance and review forums that sustain oversight of the improved process. Each row is a forum. Each forum has a frequency, an owner, the inputs it needs, the outputs it produces, and a next date.

You reach for it in the Sustain phase, at the point where the project team is about to step back. Control plans tell you what to monitor. The governance calendar tells you who meets, how often, and what happens when the numbers move. Without it, monitoring becomes a document nobody opens.

The tool is also useful earlier, as a draft. If you sketch the calendar during Improve, you discover whether the people you are relying on already meet, or whether you are asking an organisation to invent five new meetings on your behalf. That is a very different conversation, and it is better had early.

Everything in this guide uses the sample data built into the tool. It is a fictional case, included so you can see the shape of a finished calendar before you build your own.

The sample describes governance around an accounts payable process that has just been improved. Five forums sit on the calendar. A daily huddle run by the AP Manager. A weekly operations review run by the Process Owner. A monthly audit run by the Black Belt. A quarterly steering meeting and an annual review, both owned by the Sponsor.

The ladder is deliberate. The daily huddle catches exceptions within a shift. The weekly review turns patterns into decisions. The monthly audit checks that the controls themselves still work. The quarterly steering forum weighs benefits against risk. The annual review sets the roadmap. Each rung handles what the rung below it cannot.

The table asks for six fields per forum. Three are mandatory: the forum name, the owner, and the next date. Frequency, inputs and outputs are optional in the tool, but leaving them blank costs you most of the value.

Inputs and outputs are the fields people skip. Do not skip them. In the sample, the daily huddle takes SPC and exceptions in and produces action items. The weekly operations review takes the KPI dashboard in and produces decisions. The monthly audit takes audit results in and produces corrective actions. Writing this down forces a test: if nobody produces the input, the forum has nothing to discuss. If nobody consumes the output, the forum changes nothing.

Owners should be named roles, not teams. The sample uses AP Manager, Process Owner, Black Belt and Sponsor. Four owners across five forums, because the Sponsor carries both the quarterly steering and the annual review. That concentration is visible in the output, which is the point.

The tool sorts the forums by next date and returns a short set of counts. In the sample, it reports 5 forums, 5 of 5 with a next date, an earliest next date of the daily huddle on 2025-06-03, 4 owners, and 5 past due date.

The cadence summary reads: Daily 1, Weekly 1, Monthly 1, Quarterly 1, Annual 1. Next dates run from 2025-06-03 for the daily huddle to 2026-06-01 for the annual review. One forum at each frequency, covering just over a year of oversight.

Then the number that matters. All 5 forums are past their date. The daily huddle on 2025-06-03, the weekly operations review on 2025-06-09, the monthly audit on 2025-07-01, and the rest. A calendar where every entry has fallen behind its next date is not a calendar. It is a record of intent.

The tool also offers an AI review that explains the result in plain language if you want a second read before you take it to a sponsor.

The first decision is whether the cadence matches the risk. One forum at each frequency is a clean structure, but it means there is no redundancy. If the weekly operations review lapses, nothing between the daily huddle and the monthly audit picks up a drift that takes two or three weeks to show.

The second decision is about owner load. Four owners for five forums tells you the Sponsor holds two. Those two are the quarterly steering and the annual review, which are the forums most likely to be deferred when a sponsor gets busy. If the strategic layer stalls, the operational layer keeps running but nobody is deciding whether the process still deserves the attention.

The third decision follows from the past due count. With 5 past due, you are not tuning a calendar. You are restarting one. That means picking new next dates, confirming each owner still holds the role, and checking that the inputs still exist. A KPI dashboard that stopped being produced three months ago cannot feed a weekly review you are about to reinstate.

Slippage rarely announces itself. It shows up as small gaps in the fields you already track. The past due count is the loudest signal, but it is not the first one.

Watch the direction of decay. Governance tends to fail from the top down and from the inside out. The annual and quarterly forums slip first because they are easy to defer. Then inputs stop being prepared. Then outputs stop being recorded. The meeting still appears in diaries, but nothing enters it and nothing leaves it.

Reviewing the calendar itself on a set rhythm is the simplest defence. Reopen the tool, refresh the next dates, and look at the counts again. If the past due figure is anything other than zero, you have a question to answer before the next cycle.

The first is inventing forums. If the daily huddle already runs for other reasons, add your SPC and exceptions to it rather than scheduling a second meeting. A calendar of new meetings has a short life.

The second is naming a person instead of a role. People change jobs. The sample uses AP Manager, Process Owner, Black Belt and Sponsor, which survive a handover. A calendar built on individual names needs rewriting every time someone moves.

The third is leaving outputs vague. Action items, decisions, corrective actions, strategic decisions and a roadmap are all specific enough to check later. Discussion is not. If a forum cannot name what it produces, it probably does not need to exist.

The fourth is treating the calendar as a one-off artefact from handover. The next date field is there to be updated. A calendar that has not been touched since the project closed will show the pattern you see in the sample.

The Governance and Review Calendar schedules forums. It does not run them, and it cannot tell you whether a meeting that took place was any good. A forum can be on time, fully attended, and still decide nothing.

It does not know whether your cadence is correct. The sample shows one forum at each of five frequencies. The tool counts that cadence but does not judge it. Deciding whether a monthly audit is often enough for your risk is your call, informed by the control plan, not by this output.

It does not verify owners, inputs or outputs against reality. If you type a KPI dashboard into the inputs column, the tool records a KPI dashboard. Whether anyone builds it is outside the tool entirely. The past due count is a check on dates, not on substance.

Finally, it does not measure the improvement. Benefits tracking, control charts and audit findings live elsewhere. Use this tool to make sure the forums that read those things keep happening, and read the past due number honestly when they do not.