How to keep a decision log
· 4 min read
A decision log is a running record of the decisions a team has made: what was decided, by whom, when, and why. It stops teams re-arguing settled questions and lets new people understand why things are the way they are. Record each decision in one or two sentences at the moment it is made.
What to record
- The decision, in one clear sentence.
- Who made or approved it.
- The date and the meeting it came from.
- The reason, in a line, and the main alternative that was rejected.
- Any follow-up action it creates.
What not to log
Do not log every opinion or brainstorm. Log a decision only when the group would be surprised if it were reversed without discussion.
Template
Date: [date]. Decision: [what we decided]. Decided by: [name(s)]. Why: [reason]. Alternatives considered: [option]. Follow-ups: [task, owner, date]. Source: [meeting link].
Keeping it searchable
A log nobody can search is not used. Keep it in one place, use plain words, and link each entry to the source meeting so the context is a click away.
Building it automatically
Notemaker extracts decisions from every meeting with who decided and where in the meeting it happened, and makes them searchable in a decision log. Assistants can query it through the MCP server.
Frequently asked questions
What is the difference between a decision log and meeting minutes?
Minutes record what happened in one meeting. A decision log collects only the decisions across all meetings, so it can be searched later without reading every set of minutes.
Who should own the decision log?
Whoever runs the meeting should capture decisions, but one person (often a project lead) should own the log's quality and make sure it stays current.