Portfolio / Rev 2026 Mahe Mishra, home

Case studies / CS-02

A governance tracker that carries its own audit trail

A fortnightly governance group needed an action tracker the chair could trust without re-reading the meeting. A small set of hard rules did more than any formula.

PMO Analyst · 2026

  • Fortnightly meeting record turned into a chair-ready tracker
  • 1 cell holds every update to an action, dated and initialled
  • 5 statuses, each with one fixed colour and one meaning

Context

The enabling works governance group on the programme meets every fortnight with Trust staff and external advisers. After each meeting I turn the record of the discussion into updates on the master action tracker. The chair reviews it before it goes any wider.

Problem

Action trackers decay in predictable ways. Status gets written into the narrative and contradicts the status column. Due dates get typed into comments and nobody filters on them. Every chase becomes a new row, so one piece of work ends up spread across five actions. After a few months nobody trusts the tracker, so everyone keeps their own.

Approach

The fix was a set of rules applied every single cycle, rather than a cleverer spreadsheet.

  • Updates go newest first in one cell, each line dated and initialled. The history of an action is readable without opening anything else.
  • Status lives only in the status column, five states, one colour each. Dates live only in the due date column.
  • A due date that falls after this meeting but before the next one is flagged red, so the chair can see exactly what lands before the group meets again.
  • A new action has to have one owner and one deliverable. Chases, escalations and clarifications become updates on the action they belong to.
  • If the meeting shows someone else driving an action, the owner changes.
  • Updates are ten to twenty words. The fact and the next physical step.

Outcome

The tracker reads the same way every fortnight and the history of any action is one cell away. The same rules now drive the public version on this site, which runs on the synthetic programme.

Lesson

Most data quality problems in a PMO are not technical. They are conventions nobody wrote down. Write them down, apply them every time, and the tool can stay simple.

The build PRJ-03 Live Governance action tracker and dashboard

All case studies