Bodies Steering committee minutes
Steering committee minutes are written quickly when you know what to put in them. The web explains at length how to structure them, and that is useful. But the question that decides their value lies elsewhere, and almost nobody asks it: who approves them, and what are they worth if nobody challenges or signs them.
The structure that holds.
Seven blocks, in this order. None is decorative: each answers a question that will be asked again in six months.
| Block | What it contains | What it is for |
|---|---|---|
| The frame | Date, participants present and excused, purpose of the session. | Establish who was there when the decision was made. |
| The recap | Decisions of the previous committee, status of the actions that followed. | Keep a decision from getting lost between one session and the next. |
| Progress | Real status at the date of the session, milestones met and milestones slipped. | Fix the status on which the decision relies. |
| Risks | What threatens the deadline, the scope or the budget, and since when. | Show that a risk had been brought to attention, and on what date. |
| Decisions made | What was decided in session, and by whom. | Make the decision attributable, and therefore enforceable. |
| Decisions pending | What could not be decided, and who must do so. | Avoid a non-decision passing for tacit agreement. |
| Actions | Each with a named owner, a dated due date, a requester. | Allow closure by the one who asked, not by the one who executes. |
SOURCE Template drawn from orgatypik practice, tested on projects supervised in an IT services company. It can be reused as is.
Five mistakes, and they repeat everywhere.
They have nothing to do with the quality of the writing. They all concern what is missing.
A decision with no owner
"It was decided that..." Six months later, nobody knows who decided, or on what basis. The decision cannot be relied on against anyone.
An action with no date
An action with no due date is not an action, it is an intention. It can be neither late nor closed.
A disagreement not recorded
We prefer to write down what we agree on. The unrecorded disagreement resurfaces when the invoice arrives, and then it has no trace.
A late send
Minutes that arrive two weeks after the session are no longer reread. They are filed without having been read, and they prove nothing.
Who approves, and what is silence worth?
Minutes sent by email and left unanswered are one-way proof. You know what you wrote; you do not know what the client read, or whether they dispute a point. The day the invoice is discussed, this document weighs only what a unilateral statement weighs.
Project governance describes the bodies: who decides, at what pace, on what agenda. Operational commitment management describes what these bodies hold: what was promised, by whom, by what date, and on what dated proof. One is the frame. The other is the substance.
Minutes that are approved, or rejected with a reason, change in nature: they become a trace that can be relied on by both sides. This is exactly the gap that operational commitment management closes.
Minutes approved on both sides.
Four states, and the move from one to the next is dated.
Submitted
The minutes go to the client for review, on a date. From that moment, the supplier can no longer edit them.
Approved
The client signs off. The document freezes and joins the project history, with the financial and operational status of the session.
Rejected with a reason
The client disputes, and says why. The disagreement becomes project data instead of remaining an unease.
Corrected
Through a new cycle, never by rewriting. You can see that a correction took place, when, and on what.
Preparing the session itself is covered on steering committee software. The complete product tour is on the product page, and the contractual frame on the commitment levels.
What we are asked about minutes.
What should steering committee minutes contain?
The frame of the session, a recap of previous decisions, progress, risks, decisions made, decisions pending, and actions with owner, due date and requester. Seven blocks, in this order.
Who writes the steering committee minutes?
The supplier, usually the person in charge of follow-up or the project manager. It is not a matter of courtesy: the one who steers writes, and the one who receives approves. Reversing the roles blurs responsibility.
How soon should they be sent?
As early as possible after the session, while everyone remembers what was said. Minutes produced from the project data rather than retyped from scratch can go out the same day, which settles the question.
Do steering committee minutes have contractual weight?
It depends on what your contract provides, and we will not say more here: the applicable framework is yours. What we observe is simpler. A document submitted, read and approved on a date establishes what both parties knew at that moment; an unanswered email establishes nothing of the sort. See the terms and conditions.
How do you get minutes approved by the client?
By submitting them in the tool where the client already follows the project, rather than as an attachment. They approve, or reject with a reason. The act is dated, and access costs them nothing.
What if the client disputes six months later?
Reopen the history of the session concerned: what was presented, what they approved, on what date. The discussion becomes a finding again. Without this frozen history, it remains a negotiation between two memories.
Going further.
- Steering committee software: preparing the session without spending the evening before on it.
- The project client portal: where the client approves, and what they see.
- Operational commitment management: the definition of the category.
- The product tour: committees, action logs, history.