Why decisions disappear after the meeting
A leadership meeting can produce a clear choice and still leave no usable record. The discussion ends, people return to their calendars, and the decision survives only in memory. Two weeks later the same question returns because nobody can say what was agreed. A decision log prevents that loop by giving each choice a durable home.
The log is not a transcript and it is not a task list. It records the choice, the owner, the date, the reasoning, and the conditions that would reopen it. Tasks belong in the project system, while the decision record explains why the work exists. Keeping the two separate makes both more useful.
Choose one log and one owner
Pick a single location that the leadership team can reach and that supports access controls. A shared document, a database, or a page in the existing workspace can all work if people know where it is. Avoid creating a second log for each committee, because the office will soon disagree about which one is authoritative. One canonical log is easier to maintain.
Name one owner for the log and one backup who can update it during absence. The owner does not make the decisions, but they ensure the record is complete and current. The support desk often fits this role because it already sees the meeting materials and the follow-up. Give the owner the authority to ask a chair for a missing detail.
Capture the decision in a fixed shape
Use the same fields for every entry so the log can be scanned quickly. Record the date, the meeting, the question, the decision, the owner, the effective date, and any conditions. Add a short reason that explains the choice in the decision maker's own terms. A fixed shape makes comparison possible and reduces the temptation to write an essay.
Write the decision as an instruction rather than a topic. Instead of recording that the team discussed vendor consolidation, record that the team approved a single vendor for the next two years. The precise wording prevents later disagreement about what was actually decided. Ask the chair to confirm the wording before the meeting closes.
Keep the field labels stable even if the tool changes, because people learn the shape of the record. A new template that reorders the fields creates unnecessary friction. If the team needs an extra field, add it at the end and explain why. Consistency is more valuable than a perfect form.
Record the reasoning and the dissent
A decision record should explain enough context that a new leader can understand the choice. Note the options considered, the evidence used, and the main trade-off that the team accepted. This is not a minute-by-minute account, but it should preserve the reasoning that would otherwise be lost. Future decisions often depend on why the earlier one was made.
Record material dissent without attributing it to an individual unless the chair wants that on the record. A summary such as the finance team preferred a staged rollout captures the concern without turning the log into a political document. The point is to preserve the alternative view, not to settle it again. If dissent was strong, note the condition that would trigger a review.
Link actions to the decision
Every decision that requires work should create at least one action with an owner and a due date. Put the action in the project system and reference the decision identifier in the task. That link lets a new owner trace the work back to the choice that authorised it. It also stops old actions from surviving after the decision changes.
When an action is complete, do not delete the decision entry. Mark the action as done and leave the decision visible for the period the team has agreed. Decisions often need to be cited months later during audits, onboarding, or a dispute. Retention should follow the organisation's records policy rather than personal convenience.
Review open decisions every week
Add a short decision review to an existing leadership or support meeting. Scan the entries from the last two weeks and confirm the wording, the owner, and any missing action. This takes a few minutes and catches errors while the participants still remember the discussion. It also signals that the log is a live record rather than an archive.
Use the review to close decisions that have been superseded or that never actually reached agreement. A question that keeps returning without a decision should be rewritten or escalated. The log should not preserve ambiguity as if it were a choice. A clear status field helps the team see what is open, decided, or withdrawn.
Use the weekly review to ask whether any decision needs to be communicated outside the leadership team. A decision that affects staff, customers, or partners may need a separate message with a different level of detail. Record that communication as an action rather than assuming the meeting note will reach the right people. A short entry is enough if it names the decision and the owner.
Close the log at quarter end
At the end of each quarter, review the decisions that are still open and the ones that changed direction. Note any pattern, such as repeated delays on the same type of choice or decisions that are remade every month. The pattern is often more valuable than any single entry. Share the short summary with the leadership team.
For related guidance, see our article on tracking board resolutions and our consultation page. A maintained decision log gives the executive office a memory that survives turnover and a practical way to explain why the organisation chose its current path. A short entry is enough if it names the decision and the owner. Review the log at the next quarterly planning session.
Key takeaways
- Keep one canonical log with a named owner and a backup.
- Record the decision as an instruction, not as a discussion topic.
- Preserve the reasoning, the main trade-off, and any material dissent.
- Link every required action to the decision that authorised it.
- Review open entries weekly and summarise patterns each quarter.