Practical team guide
Decision log: template, example and review method
A decision log is a record of what a team chose, who approved it, when and why. It keeps the alternatives and original evidence beside the outcome. Use it when decisions keep reopening or a new colleague needs to understand the reasoning.
What should a decision log include?
| Field | What belongs in the record |
|---|---|
| Decision ID and question | Stable reference and the choice being settled |
| State | Proposed, approved, rejected or superseded |
| Decision and approver | Chosen option and the person authorized to approve |
| Decision date | When approval actually occurred |
| Rationale | Recorded reason, including the tradeoff |
| Alternatives | Options considered and why they were set aside |
| Sources and confirmation | Discussion, supporting file and approval reference |
| Follow-through | Links to separately accepted action items |
| Review or amendment | Trigger for reconsideration and any replacement decision |
Keep an unknown rationale marked unknown. A plausible explanation written afterward should not become the historical reason unless the decision maker confirms it.
Download the decision-log template
Open the decision-log CSV in your spreadsheet application. It contains a fictional approved decision and a later amendment, plus a blank row. The sample source labels are examples, not working links.
Start with one recurring meeting and one person maintaining the log. Link it from the meeting notes so the team can find the same record next time. Give each decision an ID that stays stable when its wording changes.
Worked example: a launch decision is amended
Fictional example. Maya approves a limited pilot on November 16 because testing covers only the pilot group. A wider release is rejected until further validation. Record Maya’s approval and the actual test evidence beside that choice.
On November 12, a test failure prompts a proposal to delay pilot access to November 23. That proposal does not immediately replace the approved date. Keep the original decision approved until Maya decides. If she accepts the delay, mark the earlier entry superseded and link the new entry, its reason and her confirmation.
The preparation owner must separately accept any changed delivery date. Approval of a launch plan does not automatically establish acceptance of someone’s assignment.
How to maintain the log in five steps
- Name the question. Write the choice the team must settle, not a vague agenda topic.
- Record options and evidence. Include missing information that could change the choice.
- Confirm authority and outcome. Capture approval, rejection or a request for more work from the right person.
- Link accepted actions. Use an action item tracker for delivery owners and deadlines.
- Review on a trigger. Revisit the choice when an assumption changes, evidence arrives or the agreed review date is reached. Retain the previous record.
Decision log, meeting notes and task tracker
Meeting notes explain the discussion. The decision log records the choice and rationale. The task tracker records the work people accepted. Keep links between them so a weekly report can distinguish “approved” from “delivered.”
For reporting across these records, use the project status reporting worksheet. Avoid copying the same text into three places that can drift independently.
Where Roomcord fits
A Roomcord project room keeps conversations, meetings, files and AI teammates together. Ask AI to draft candidate decisions from the available material, then have a person review and maintain the confirmed log in a shared document or room record.
The dedicated Roomcord decision ledger describes the developing decision-engine experience. This template works as a human-maintained record today; it is not evidence that automated ledger history, approval ballots or cross-room management dashboards are released. Confirm the available setup when scoping a pilot.
Your first AI operating room
Bring one recurring workflow
Tell us which meeting, decision or approval creates repeated follow-up work. We can assess a scoped Roomcord pilot, the sources it needs, the human review steps and what to measure.
Request a demo
Share a little context. Our team will reply by email to arrange the next step.