A steering committee decision log is a table with a row for each decision the committee agrees: what was decided, why, who made the call, when, and where it stands now. Copy the row template below into a shared document or spreadsheet, complete each row at the meeting where the decision is agreed, and read the open rows before each later meeting so agreed decisions stay agreed.
What fields belong in a steering committee decision log?
A steering committee decision log needs the decision, its rationale, the decision owner, the date, the agenda item it was agreed under, and a status on every row. Add options considered, the basis for the decision, who was consulted, an action owner, and a review date when the decision rests on an assumption, was delegated, or commits spending.
Bottom.pub's archived working file records each decision with a number, a date, the decision, who made it, the information it was based on, who was consulted, and a review date. The page is marked as a historical working document, so treat its fields as a starting point rather than a standard. Stakeholdermap's decision log template gives each decision a unique identifier so that it can be traced, and it names the project board or project sponsor as examples of a responsible party. Check that page before you adopt it. It is marked as reviewed in 2021, and its text says Word and PDF while its download links are spreadsheet files. Open the file and confirm its columns before you copy them.
Copy this block as the row template. Replace each [bracket], and delete any field your committee does not need.
Decision ID: [committee prefix]-[year]-[running number]
Decided at: [committee name], [meeting date]
Agenda item: [agenda item number and title]
Decision: [one sentence, in the sponsor's words]
Rationale: [why this option was chosen]
Options considered: [option B, set aside because ...]
Basis: [FACT or ASSUMPTION, and where it came from]
Decision owner: [name and role of the person who made the call]
Consulted: [names of people whose input was taken]
Action owner and due date: [name], [date]
Status: [Decided / Under review / Superseded / Reversed]
Review date: [date, or 'not needed']
Notes: [where the minutes, email thread, or papers are kept]
Each field answers one question:
| Field | Question it answers |
|---|---|
| Decision ID | Which row is this, using an identifier that stays the same once assigned? |
| Decided at and agenda item | Which meeting and which agenda item agreed it? |
| Decision | What exactly was agreed, in the sponsor's words? |
| Rationale | Why was this option chosen? Elium's decision log template records decisions with context and rationale so teams remember why. |
| Options considered | What else was on the table, and why was each set aside? Stakeholdermap asks for alternatives considered. |
| Basis | Is it a FACT or an ASSUMPTION, and where did the information come from? Bottom.pub's file labels each source as FACT or ASSUMPTION. |
| Decision owner | Who made the call? Name that person, not the one who recommended the option. Acta's steering committee template has a Decisions needed section that asks for options and a recommendation. |
| Consulted | Whose input was taken? Keep these names apart from the decision owner. |
| Action owner and due date | Who does the follow-up, and by when? |
| Status | Where does the row stand now? |
| Review date | When should someone look at the row again? |
| Notes | Where are the minutes, email thread, or papers kept? Stakeholdermap lists meeting minutes and background information as related documentation. |
Which status should a row have?
Every row has one of four statuses: Decided, Under review, Superseded, or Reversed. Decided means the decision owner has confirmed the wording and no later row has changed it. The other statuses mark a row that is waiting for confirmation, has been replaced, or has been undone.
| Status | Use it when |
|---|---|
| Decided | The decision owner has confirmed the wording, and no later row has changed it. |
| Under review | The decision is waiting on written confirmation, a review date, or a new fact. |
| Superseded | A later approved row replaced it. Put that row's ID in Notes. |
| Reversed | A later decision undid it, with no replacement. Put that decision's ID in Notes. |
The status words, their meanings, and the review rule below are this guide's recommendation, not a standard from the listed pages. Agree them with the sponsor before the first meeting, then use them the same way in every row.
When does a decision need a review date?
A decision needs a review date when it rests on an assumption, was delegated, is a public statement, or commits spending. Bottom.pub's archived file gives these triggers in its section on decisions that always require a review date.
Open that page and read the full section before you adopt the list. The page names four kinds of decision: those based on assumptions, delegated authority, public statements, and spending. Use the list as the page gives it.
This guide adds one rule of its own: a row marked Under review also gets a review date, because the row should be looked at again once its basis is confirmed or tested.
The row below is illustrative. Its names, dates, and references are placeholders.
Decision ID: [committee prefix]-[year]-[running number]
Decided at: [committee name], [meeting date]
Agenda item: [agenda item number and title]
Decision: The [deliverable name] review moves from [original date] to [new date].
Rationale: [client contact] cannot attend on [original date].
Options considered: Keep [original date], set aside because [reason].
Basis: ASSUMPTION. [client contact] said by email that [new date] works. Not yet confirmed in writing.
Decision owner: [sponsor name], [sponsor role]
Consulted: [names]
Action owner and due date: [name], [date]
Status: Under review
Review date: [date], because the basis is an assumption
Notes: [email thread name and location]
The status is Under review because the basis is not yet confirmed in writing. When the client contact confirms in writing, change the status to Decided and link the confirmation in Notes.
How do you record a decision during the meeting?
Record each decision in the meeting as soon as the committee agrees it, using the sponsor's own words, and read the row back before the meeting closes. Keep the team's recommendation out of the Decision field, because a recommendation shows what was proposed, not what was agreed.
Bottom.pub's archived file says its rows are 'completed at the meeting, not before it', and the same timing works for a live committee log.
- Put the log on the agenda as a standing item, ahead of other business.
- When the committee agrees, read the decision aloud and ask whether that is the wording to record.
- Ask who has authority to make the call, and enter that name as Decision owner. If the answer is unclear, set the status to Under review until the decision owner confirms in writing.
- Enter the agenda item number. Write the basis, and set a review date if the row falls under the triggers above.
- Read the new rows aloud before the meeting closes.
If the sponsor decides outside the meeting, add the row at the next meeting and name the message in Notes. Do not mark it Decided until the decision owner has confirmed the wording.
Who decides, and who only recommends?
The decision owner is the person with authority to make the call, and each row names that person. Recommenders go in the agenda paper, and people who were consulted go in their own field. The pages reviewed for this guide do not set out decision rights, quorum, delegated authority, or reversal rules, so confirm them with the sponsor.
Acta's template has a Decisions needed section for options and a recommendation, which places the recommendation in the agenda rather than the log. Stakeholdermap names the project board or project sponsor as examples of a responsible party. Neither page says who may decide alone, what quorum applies, or how a decided row is reversed, so the committee needs to settle those points itself.
- At the next meeting, ask the sponsor: 'Which decisions are yours to make alone, and which need the committee?'
- Ask whether a quorum applies, and who can reverse a row that is marked Decided.
- Write the answers as one line each at the top of the log, for example: '[decision type] is decided by [role].'
- If the sponsor passed a decision to someone else, enter the delegate as Decision owner, name the person who delegated it in Notes, and set a review date.
If the committee decides as a group, enter the committee's name as Decision owner, and keep the minutes or a written note of the agreement in Notes.
How does each row link to the agenda and minutes?
Each row should carry its meeting, its agenda item, and the location of the minutes, so anyone can trace the row back to the committee's own record. Stakeholdermap's template lists meeting minutes and background information as related documentation to keep with each decision.
- Use the committee's own agenda numbering in the Agenda item field, so the row matches the agenda paper.
- Write the file name or location of the minutes in Notes, for example '[committee name] minutes, [meeting date], item [number]'.
- Do not paste the discussion into the Decision field. The row carries the agreed wording, and the minutes carry the discussion.
Who maintains the log and who can edit it?
A named maintainer keeps the decision log, and the decision owner confirms each row's wording before it is marked Decided. Give members view access and give edit access only to the maintainer, so each row changes in one place. Link the log from the meeting agenda.
- Name the maintainer in the first lines of the log.
- Ask members who spot an error to raise it with the maintainer rather than edit rows themselves.
- Update rows in the meeting where possible, so the wording matches what was agreed rather than what someone recalls later.
- Open any downloaded template before you rely on it. The Stakeholdermap page describes Word and PDF files, but its download links are spreadsheet files.
How do you stop agreed decisions being reopened?
Keep the open rows in front of the committee before each meeting, and change a decided row only through a written request that names its decision ID. Elium notes that without a log, teams waste time relitigating decisions that were already made.
- Send the open rows with the agenda, so members can see which items are marked Decided or Under review before the meeting.
- At the start of the meeting, state the rule: a decided row changes only through a written request that names its ID.
- Use this wording for a request:
I'd like the committee to revisit [decision ID]: [decision in short].
Since it was decided, [what has changed].
The evidence is [link or file name].
The decision I'm asking for is [new decision].
- When the request is approved, add a new row. Set the old row's status to Superseded or Reversed, and point to the new ID in Notes. Leave the old wording in place.
- Check review dates at every meeting. A row whose review date has arrived goes on the agenda.
If new evidence overturns a decision, use the same request and put the evidence in the 'The evidence is' line.
What are the common mistakes with a decision log?
The common mistakes are writing rows from memory after the meeting, entering a recommendation as the decision, marking an email approval as Decided, and deleting superseded rows. Each one makes the log look settled when the record behind the log is not.
Writing rows from memory
Rows written after the meeting drift from what was agreed, and members may not recognise the wording. Read each row back before the meeting closes, and correct it while the committee is still in the room.
Recording a recommendation as the decision
A row that says the team recommends an option reads as a committee decision to anyone who opens the log later. Keep the recommendation in the agenda paper, and record only the option the decision owner chose.
Marking an email approval as Decided
When the sponsor approves by email, add the row as Under review, name the thread in Notes, and ask the decision owner to confirm the wording in that thread. Change the status to Decided once the written confirmation is in the record.
Deleting superseded rows
Deleting an old row erases the record of what was agreed before. Keep it, set its status to Superseded or Reversed, and point to the new ID in Notes.
Before the next committee meeting, open the log and check that every row has an ID, a status, a decision owner, and an agenda item.