Decision Log Template: How to Record and Share Team Decisions
Quick Answer
A decision log is a running record of important team decisions: what was decided, why, who decided, when, what options were considered and who needs to act. Keep it in one shared place, add decisions right after they're made, share them with everyone affected and review the log when questions come up. A good log stops teams from re-debating settled decisions and makes the reasoning behind them visible.
"Wait, didn't we already decide this?" If that question comes up in your meetings, you're not alone. Teams make dozens of decisions every month, about prices, processes, vendors, schedules and priorities, and most of them live only in the memories of the people who were in the room. A few weeks later, nobody is sure what was decided, why, or whether it still stands.
A decision log fixes that. It's a simple shared record of what was decided and why. This guide explains what to record, a free template, examples, how to share decisions with your team and how to keep the log from becoming one more thing nobody updates.
What Is a Decision Log?
A decision log, sometimes called a decision register or decision record, is a running list of a team's important decisions. Each entry captures the decision, the reasoning, who made it, the date and what happens next. It's different from meeting notes, which capture everything discussed. A decision log captures only the outcomes that matter later.
| Meeting notes | Decision log | Action item list | |
|---|---|---|---|
| Captures | What was discussed | What was decided and why | What needs to be done |
| Organized by | Meeting date | Decision | Owner and due date |
| Useful for | Remembering a meeting | Explaining and revisiting decisions later | Getting work done |
The three work together: notes record the meeting, action items drive the work and the decision log keeps the reasoning. See how to take good notes in meetings.
Why Teams Need a Decision Log
- No re-debating. Settled decisions stay settled unless something changes.
- Transparency. People who weren't in the room can see what was decided and why.
- Faster onboarding. New team members learn why things are done the way they are.
- Accountability. Every decision has a named owner.
- Better decisions over time. Looking back at past reasoning shows what worked and what didn't.
- Less confusion when people remember a decision differently.
Which Decisions Belong in the Log?
Not every choice needs to be logged. "We ordered more printer paper" doesn't. A good rule: log any decision that affects more than one person, costs real money, changes how work is done or is likely to be questioned later.
| Log it | Skip it |
|---|---|
| Changing prices or discounts | Routine supply orders |
| Hiring, role changes or new positions | Day-to-day task assignments |
| New policies or process changes | One-time scheduling swaps |
| Choosing a vendor or software | Small purchases within normal limits |
| Changing priorities or dropping a project | Minor wording changes |
| Saying no to a customer request type | Individual customer replies |
What to Record for Each Decision
| Field | What to write |
|---|---|
| Date | When the decision was made |
| Decision | What was decided, in one or two clear sentences |
| Why | The main reasons |
| Options considered | The alternatives and why they weren't chosen |
| Decided by | Who made the call |
| Input from | Who was consulted |
| Affects | Teams or people impacted |
| Next steps | Actions, owners and dates |
| Status | Active, revisit on [date], or replaced |
Free Decision Log Template
| # | Date | Decision | Why | Options considered | Decided by | Affects | Next steps | Status |
|---|---|---|---|---|---|---|---|---|
| 1 | [date] | [decision] | [reasons] | [alternatives] | [name] | [teams] | [action, owner, date] | Active |
| 2 | ||||||||
| 3 |
This works well as a simple spreadsheet or a table in a shared document. If you want one entry per decision with more detail, use this format instead:
Decision #[number]: [short title]
Date: [date] | Decided by: [name]
Decision: [what was decided]
Why: [main reasons]
Options considered:
• [option], not chosen because [reason]
• [option], not chosen because [reason]
Input from: [names]
Affects: [teams or people]
Next steps:
• [action], owner: [name], due: [date]
Revisit: [date or condition, such as "if costs rise 10%"]
Status: [Active / Replaced by #__]
Decision Log Examples
| Date | Decision | Why | Decided by | Status |
|---|---|---|---|---|
| Jan 8 | Raise service call fee from $89 to $99 | Fuel and labor costs up; competitors at $95 to $110 | Owner | Active |
| Jan 15 | Move weekly team meeting from Monday to Tuesday | Monday mornings are our busiest call time | Operations manager | Active |
| Feb 2 | Stop offering same-day installs | Same-day jobs caused overtime and callbacks | Owner, with input from crew leads | Revisit in Q3 |
| Feb 20 | Switch parts supplier to a regional vendor | Faster delivery and better pricing on top 20 parts | Operations manager | Active |
| Mar 5 | Require overtime approval before staying past shift | Unplanned overtime up 30% last quarter | Owner | Active |
Notice how short each entry is. A decision log doesn't need paragraphs. It needs enough that someone reading it in six months understands what happened and why.
How to Share Decisions With Your Team
A decision log only builds transparency if people know about the decisions in it. Share decisions in ways that fit how your team works:
- Announce big decisions directly, in a team meeting or huddle, with the reason.
- Post a weekly summary of new decisions in your team channel.
- Link the log in meeting agendas so it's easy to check.
- Tell affected people first. Anyone whose work changes should hear it from their manager, not discover it in a log.
- Explain what didn't change, too, when a decision might cause worry.
Sharing a decision: "Quick update: starting February 2, we're no longer offering same-day installs. They were causing overtime and too many callbacks. We'll offer next-day installs instead, and we'll look at this again in the summer. Questions? Ask me or check the decision log."
Who Decides? Making Decision Rights Clear
A decision log works best when it's clear who has the authority to make which decisions. Many teams use simple decision types:
| Decision type | How it works | Good for |
|---|---|---|
| Leader decides | One person decides, with or without input | Urgent or clearly owned decisions |
| Leader decides after input | Leader gathers views, then decides | Most important team decisions |
| Team agrees | The group reaches agreement | Team norms, shared schedules |
| Delegated | Someone closer to the work decides within limits | Day-to-day operational choices |
Write down who decides what, for example in a team charter or a RASCI chart. When people know who decides, decisions get made faster and second-guessed less.
When to Revisit a Decision
A decision log isn't meant to lock decisions in forever. Revisit a decision when:
- The reasons behind it have changed, such as costs, staffing or customer demand.
- The results aren't what you expected.
- A revisit date in the log arrives.
- New information comes up that wasn't available before.
When you change a decision, don't delete the old entry. Mark it "replaced," add the new decision and link the two. That history is often the most valuable part of the log.
How to Keep a Decision Log Useful
- Name an owner for the log, often whoever runs the team meeting.
- Log decisions immediately, ideally before the meeting ends.
- Read new decisions back at the end of each meeting to confirm everyone agrees on what was decided.
- Keep it in one place that everyone can open.
- Keep entries short. A few lines per decision is enough.
- Review it quarterly to update statuses and spot decisions to revisit.
Common Decision Log Mistakes
- Logging everything, so the important decisions get lost.
- Leaving out the "why," which is the part people need most later.
- No named decision-maker, so no one owns the outcome.
- Logging but not sharing, so the people affected still don't know.
- Deleting old decisions instead of marking them replaced.
- Letting it go stale. A log that stopped three months ago does more harm than good, because people assume it's complete.
Decision Logs for Different Teams
| Team | Decisions worth logging |
|---|---|
| Leadership | Pricing, hiring plans, budgets, company priorities, major vendor choices |
| Operations | Process changes, equipment purchases, scheduling rules, safety procedures |
| Sales | Discount policies, territory changes, which customers to pursue or decline |
| Customer service | Refund rules, response standards, how to handle common complaints |
| HR | Policy changes, benefits decisions, pay structure changes |
| Project teams | Scope changes, deadline changes, design choices, budget approvals |
Each team can keep its own log, or a small business can keep one shared log with a column for the team. Start with one log; split it only if it gets too long to scan.
Running a Decision Into the Log During a Meeting
The easiest way to keep a decision log current is to make it part of your meeting routine. When a decision is made:
- Say it out loud: "So the decision is that we'll stop same-day installs starting February 2."
- Confirm the why in one sentence.
- Name the decision-maker and anyone who needs to act.
- Write it in the log before moving to the next topic.
- Create action items with owners and dates.
At the end of the meeting, read back the new decisions. It takes a minute and catches most misunderstandings before they spread. Pair this with the decision step in the Level 10 meeting template or your team meeting agenda.
Decision Logs and Accountability
A decision log shows who decided what, but its purpose isn't to assign blame when a decision doesn't work out. Good decisions can still lead to bad results when circumstances change. The log helps you ask a better question: "Given what we knew at the time, was this a reasonable call, and what would we do differently now?" That approach encourages people to make decisions instead of avoiding them, which is exactly what a growing business needs.
Over time, reviewing the log can also show patterns: decisions that were made too slowly, decisions that kept getting reversed, or areas where nobody was sure who had authority. Each of those is a chance to improve how your team works.
Getting Started This Week
- Create a simple table with the fields from the template.
- Add the five most important decisions from the last month, from memory and notes.
- Share the log with your team and explain how you'll use it.
- Add new decisions at your next team meeting.
- Review it after a month and adjust the fields if needed.
Starting small makes it easy to build the habit. Once the team sees how often the log answers "didn't we already decide this?", keeping it up becomes second nature.
Decision Log vs. Policy Document
Some decisions become policies, such as a new overtime approval rule or a refund limit. When that happens, log the decision and then update the policy itself, linking the two. The decision log explains why the policy changed; the policy document explains what the rule is now. Employees should never have to read through a log to find a current rule. See how to create an HR policy.
Small Decisions Still Need Owners
Even decisions too small for the log benefit from a clear owner. If your team regularly asks "who decides this?", that's a sign your decision rights need writing down. Start with the five decisions that come up most often, name who makes each one and share the list. It speeds up daily work, cuts down on unnecessary meetings and gives people the confidence to act without waiting for permission every time.
Decision Logs for Remote and Multi-Location Teams
When people work in different places or on different shifts, decisions are easy to miss. A decision log becomes the single source of truth. Post new decisions where everyone already looks, such as your team channel, and include a short summary with a link to the full entry. For decisions that change how front-line work is done, have each location or shift lead confirm their team has heard about it. That one extra step closes most communication gaps between locations.
Record Decisions and Follow Through With Updoot
Updoot's meeting agendas help you capture decisions and action items as the meeting happens, with an owner and due date on every action. Those actions flow into project management, so what was decided actually gets done, and everyone can see where things stand.
Related Reading