The steering pack that writes itself (so nobody has to at 11 p.m.)

Every steering pack I have ever seen was made the same way. It is 11 p.m. the night before. The programme manager has the plan open in one window, the risk log in another, last week's status in a third, a finance extract that arrived at 17:58 in a fourth, and their own memory in the fifth, which is the least reliable of the five and the one doing most of the work.

The pack goes out at 23:40. It is circulated too late to be read, so it is read in the room, by twelve senior people simultaneously, for the first twenty minutes. Someone asks what a slide means. The programme manager explains. Someone else asks whether the number on slide seven is the same as the number on slide four. It is not, because slide four came from Tuesday.

The meeting then has forty minutes left for decisions, and makes them against information that was a week old when it was pasted in.

The problem is assembly, not judgement

Nobody in that room lacks judgement. They lack a current picture that everyone read before arriving. The reason they lack it is that assembling the picture is manual: five sources, one person, one evening, one glass of something. That person cannot also be current on every source, so the pack is a snapshot of what they managed to gather before midnight.

If the plan, the governance log, the status reports, the health assessment, the delivery backlog and the value tracker are all part of one record, the assembly problem simply goes away. The pack is a view over the record, not a copy of it, and views do not go stale at 17:58.

What the steering workspace does

TransformRadar's steering workspace treats each steering meeting as an event with a date. When a meeting is scheduled, the pre-meeting pack is drafted from the live record, and its organising principle is change: what moved since the last time this group met.

• Status — the latest weekly RAG on delivery, budget and confidence, and

how it compares with what the group saw last time.

• Health — the Programme Health score by dimension, its movement, and

the assessment responses behind any dimension that dropped.

• Governance — decisions taken and pending, risks that changed, actions

overdue, change requests awaiting approval, straight from the RIDAC log.

• Plan — milestones reached or slipped, Planning Gates due, and the plan

lines whose derived progress moved.

• Delivery execution — sprint goal, velocity and what the teams closed,

where the Delivery workspace is switched on.

• Value — benefit trajectories and the readings owners reported since

last time.

Each section carries an AI-drafted narrative that connects the facts — the slipped milestone to the blocked delivery items to the risk someone raised about them — and each narrative is drawn only from the record. The chair reviews the pack before it is circulated, edits what needs editing, and sends it. Nothing goes out unreviewed, and nothing goes out at 23:40.

What changes in the room

The first change is that the pack gets read beforehand, because it arrives in time and because it is short: only what changed. The twenty minutes of establishing the facts disappear, and with them the question about slide four.

The second is that every agenda item has its evidence attached. A request for a decision comes with the governance log entry, the plan line it affects and the value driver it protects. The sponsor is not asked to trust a summary; they are shown the record.

The third is the one CIOs notice most. Because every project in the portfolio uses the same pack structure, a portfolio steering meeting can read six programmes on the same footing. Amber means the same thing on each. Health is scored the same way. The conversation moves from "what is this saying" to "what do we do".

What the meeting produces

A steering meeting produces decisions and actions, and the value of the workspace depends on those landing back in the record rather than in minutes that are circulated, filed and never opened again. Decisions taken and actions assigned in the meeting go into the governance log with an owner and a date, which means the next pack opens with whether they were done. The loop closes, and it closes on someone's name.

Less time preparing, more time deciding

The honest measure of a steering tool is not how good the pack looks. It is how much of the meeting is spent deciding. When the assembly is done by the record and the review by the chair, the answer approaches all of it, and the programme manager gets an evening back. They may not know what to do with it at first.

The Programme Health page explains the score that anchors the health section, and the product overview shows the steering workspace alongside the workspaces it draws from.

• steering
• governance
• AI
• CIO