Keep a Decision Log So Your Team Stops Re-Arguing
Teams often reopen the same debate because nobody wrote down what was decided or why. A one-line decision log records the choice, the reasons, the owner and a review date, so new joiners catch up quickly and old arguments stay settled.
Who this is for
This is for small teams, project groups, volunteer committees, clubs and even households that make shared choices and then forget the details. Use it when you hear "Didn't we already decide this?", when someone new joins, or when a choice has consequences that you will want to understand in six months. It is a memory aid, not a bureaucracy: one line per decision is often enough.
What a decision log is
A decision log is a simple running list of choices the group has made. Each entry says what was decided, when, by whom, why, what else was considered and when the decision should be reviewed. It differs from meeting notes, which record a whole conversation. The log pulls out only the decisions, so people can find them quickly. If you already keep meeting notes that turn into actions, copy each decision into the log at the end of the meeting.
The fields to record
- Date. When the decision was made.
- Decision. One clear sentence in plain words.
- Options considered. The main alternatives, so nobody has to propose them again.
- Reasons. The two or three factors that mattered most, including any constraint such as budget or time.
- Owner. The person responsible for carrying it out, and the person or group who decided it. The clear roles for group decisions guide helps with this.
- Review date. When you will check whether it is still right, or "none" if it is final.
Where to keep it
Choose something every member can find and add to: a shared document, a spreadsheet, a notes page or even a paper notebook on a shelf. Put the newest entries at the top, or keep one row per decision so you can sort by date. Agree who is responsible for adding entries, ideally the note-taker from each meeting. If the log holds sensitive information, limit who can see it and follow your organisation's rules on personal data.
What counts as a decision worth logging
Not everything needs an entry. Log decisions that affect several people, that cost money or time, that are hard to reverse or that people have argued about before. Skip small day-to-day choices. A useful test is: "Would a new person be confused or tempted to redo this?" If yes, write it down. Spend extra care on the choices that are hard to undo; see run a 30-minute team meeting for finishing each meeting with a clear read-back of decisions.
Date: 9 March. Decision: Plot fees stay at 20 a year for this season. Options: raise to 25; keep at 20; charge by plot size. Reasons: the tool shed repairs are already covered by the grant, and changing fees mid-year would confuse members. Owner: Asha (treasurer); decided by the committee vote of 5 to 2. Review: January, before renewals. Six months later, a new member asks about raising the fee, and the answer is one line away. Names and figures are invented.
Revisiting a decision
A log does not freeze choices forever. It makes revisiting deliberate. When the review date arrives, or when circumstances change, check the original reasons: do they still hold? If so, keep the decision and note that it was reviewed. If not, make a new decision and add a new entry that mentions the old one, rather than deleting it. Keeping the history shows how the group's thinking developed and prevents quiet reversals.
Edge cases
- Disagreement. Record that the decision was not unanimous if that matters, and describe the concern fairly, without naming individuals unless they agree.
- Households and families. Keep it light: a note on the fridge or a shared note for choices like the holiday budget or chore changes.
- Volunteer groups with changing members. A log is especially valuable here; add a link to it in the handover for new committee members.
- Decisions made outside meetings. Ask whoever decided to add the entry, or send it to the note-taker.
- Confidential decisions. Keep these in a separate, restricted place, and reference them only by a neutral label.
Decision log template
DECISION LOG Team/group: ____________ Entry no.: ____ Date: ____________ DECISION (one sentence): ______________________ OPTIONS CONSIDERED: ______________________ MAIN REASONS (2-3): ______________________ DECIDED BY: ____________ OWNER: ____________ REVIEW DATE (or "final"): ____________ LINKS (notes, documents): ____________ Entry no.: ____ Date: ____________ DECISION: ______________________ OPTIONS: ______________________ REASONS: ______________________ DECIDED BY: ____________ OWNER: ____________ REVIEW DATE: ____________
Write down each significant decision with its date, options, reasons, owner and review date in one place everyone can find. Revisit decisions on purpose and add new entries rather than quietly changing the old ones.
Open a shared page today and log the last decision your group made, from memory if needed. Make the log part of every team meeting, feed it from your meeting notes and be clear about who decides. You may also find After-Action Review useful.