A project status meeting agenda that makes decisions

Most status meetings are a report read aloud. Each owner says what they did, everyone else waits for their turn, and an hour later the only thing that has changed is the time. The information could have been read in five minutes, and the one conversation that needed the whole room did not happen because the hour ran out.

A status meeting is worth holding for one purpose: to make the decisions that need more than one person. Everything else is reading.

Write the status before the meeting

Each owner writes a short update for each commitment the day before. Four lines are enough:

• On track, at risk or off track, as a judgement, with the reason.
• What changed since the last update.
• What decision or help is needed, and from whom.
• Any change to the date, scope or people that was promised.

That is the same shape as a status report people read, and it takes its owner a few minutes. The colour is a judgement, not a calculation: what matters is that a person stood behind it this week.

Everyone reads the updates before they arrive. If your organisation will not do that, spend the first five minutes of the meeting reading in silence. It is still faster than hearing them one by one.

A thirty-minute agenda

1. What changed colour (5 minutes). Only the commitments that moved since last time, in either direction. A commitment that was green and is still green is not discussed.
2. Decisions needed (15 minutes). Every "help needed" line from the updates, one at a time: what is being asked, who can answer, and the answer or the date of the answer. This is the meeting.
3. Changes to what was promised (5 minutes). Any date, scope or capacity that has to move. Decide it here, in front of the people it affects, and record it as a change with a reason.
4. What is missing (5 minutes). The commitments with no update this period. Silence is the most reliable early sign of trouble, and it is invisible in a meeting where only the present speak.

There is no "round the table". If nothing changed colour, nobody needs a decision and nothing has to move, the meeting takes five minutes, or is cancelled that morning with a one-line note saying so.

How often to review project status

Match the rhythm to how fast the work can go wrong, not to the calendar.

• Written update: every week or two for anything committed. Two weeks is about the longest a commitment should go without its owner looking at it and saying where it stands. Longer than that and the first sign of a slip is the slip.
• Meeting: weekly while something is at risk, every two weeks otherwise. A portfolio that is all green for a month can meet monthly and lose nothing, as long as the written updates keep coming.
• Leadership: monthly or at quarter boundaries, from the same updates rolled up, not from a separate deck. Reporting delivery to leadership covers what belongs in it.

Do not raise the frequency because a project is in trouble and leave the content the same. A daily meeting that hears "still working on it" is more status and no more information. Raise it only when there is a decision to make each time.

What the meeting is not for

• Solving the problem. Name who will solve it and by when, and take it out of the room.
• New requests. They go through the intake door, not the any-other-business slot, or the meeting becomes the side channel.
• Reviewing people. The unit is the commitment. The moment status becomes a judgement on its owner, the updates turn green and stay green.

If you use DeliverySheet

The written update is the product's check-in on a committed demand: on track, at risk or off track, what changed, and what decision or help is needed, with the next milestone, risk changes and confidence available when wanted. The Reports page lists what needs attention across the workspace, including commitments with no check-in for more than fourteen days and decisions past their date, and its status update can be copied as text for the people who are not in the tool. A change to what was promised is recorded as a re-baseline with its reason. The meeting itself stays yours.