DECISION LOG

Decision log keeps every team decision in one trusted record

However a decision is made, by hand, by vote, by structured approval, between meetings, or proposed from the meeting's AI summary, it lands in one shared record, in one wording everyone reads the same way. That record lives in your own Microsoft 365, inside Microsoft Teams where your team already works.

WHAT CHANGES

From reconstructing decisions to relying on the record

Today, what a team decided lives in scattered notes and fading memories, and the answer changes depending on who you ask. The decision log makes it one record, written once and relied on afterward.

Today, when the record varies

  • Decisions end up scattered across meeting notes, chats, summaries, or someone's memory, with no single record to rely on.
  • Ask what was decided and people reconstruct the answer from different sources, often coming back with different versions.
  • As time passes, settled decisions become harder to find, easier to forget, and more likely to be reopened.

With the decision log

  • Every decision lands in one shared record, with the wording, status, and context the whole team can see.
  • Everyone comes back to the same agreed decision, however it was made or captured.
  • Months later, the team can still find what was decided, where it happened, and its status, so settled decisions stay settled.

Bottom line: minutes and AI summaries capture what was said. The decision log holds what the team stands behind.

HOW IT WORKS

Log it once, however the decision was made

Logging works the same every time. How a decision reaches its final status follows the process your team already uses.
  1. Log the decision

    Log the decision where it's made: on the agenda item, during the meeting, or in the log between meetings. It can go straight in as final, or start as a proposal the team reviews first. Decisions a meeting summary picks up arrive the same way, as proposals to edit and send to the log.

  2. The status follows your process

    Every decision carries one clear status: proposed, final, or rejected. How it gets there follows the process you already use: an admin sets it, a vote settles it, or a structured approval decides it.

  3. Find it again

    Open the log from a channel tab and search by keyword, or filter by status, date, tag, and origin: whether the decision came from a meeting, a circular resolution, or no meeting at all.

  4. Rely on the record

    The log is where you go back to: open a decision and you can reach the meeting it came from, the minutes it was recorded in, and the documents around it. When the question comes back months later, everyone lands on the same answer, not five versions of it.

HOW IT'S BUILT

Built to keep the whole decision, not just the title

Many ways in, one record out

Log a decision by hand, from a vote, from a structured approval, or between meetings, and turn the decisions a meeting summary picks up into proposals for the log. However it's made, it lands in the same log, in the same format.

One decision, one wording

The decision text is one agreed wording the whole team shares, with the status and the meeting behind it, not a reconstruction from memory. Everyone reads the same decision instead of their own version of it.

A status you can trust

Every decision is proposed, final, or rejected, and the log shows how it got there: the approvers and their roles for a structured approval, the results for a vote.

A decision can replace an earlier one

When a decision needs to be updated or corrected, a new one can replace it, and both stay in the log. The team sees what stands now and what it replaced, instead of losing the history to an edit.

Every decision keeps its context

A decision is the decision text itself, plus whatever the team gave it: a title, tags, the supporting documents. It stays connected to the meeting it came from, so the reasoning is recorded rather than remembered.

Findable for as long as it matters

Search and filters bring back any decision by status, keyword, date, or origin. Import past decisions so the record doesn't start from zero, and export to Excel when it needs to travel.

Secure by where it lives

Everything stays inside your own Microsoft 365 tenant. No third-party bots, nothing leaves your tenant. SOC 2 Type II and ISO 27001:2022 certified.

Learn more about our Trust Center
WHO IT'S FOR

For teams whose decisions need to hold up over time

From leadership forums to project teams, the decision log gives teams one shared record of what was decided, when, and with what context.

Leadership and management teams

A year of decisions adds up, and the ones made months ago still matter. The decision log keeps them easy to find, so each meeting starts from what's already settled.

Boards and committees

Formal decisions need to remain clear and answerable long after the meeting. The decision log preserves the agreed outcome, status, and context in one record the group can return to.

Project and steering groups

Project decisions shape what happens next across phases, teams, and milestones. The decision log keeps everyone aligned on what was settled and when, without relying on who attended.

Employee representation bodies

Works councils and similar bodies decide on matters that affect many people, and the exact wording matters. The decision log keeps that wording in one record the body can return to, with its status and where it was agreed.

FREQUENTLY ASKED QUESTIONS

Questions about the decision log

The decision log is your team's shared record of its decisions: what was decided, by whom, and with what context, in one agreed wording the whole team sees. It's part of how teams work in Decisions, not a separate tool to maintain, and it spans the team's meetings over time, so what was decided a year ago is still answerable today.
Log it on the agenda item where it's made, on the meeting itself, or straight in the log between meetings, and turn the decisions a meeting summary picks up into proposals for the log. Proposed decisions can come from the team as well as from meeting admins, and where case submission is used, from people elsewhere in the organization bringing a case to the team. However it's logged, it's the same record the team sees in the log and in the minutes, with nothing re-entered afterwards.
They work together rather than competing. A decision is logged once and appears in the minutes of the meeting it belongs to, in the same wording. The difference is scope: minutes are the record of a single meeting, the decision log is the record of your decisions across all of them. When you need to know what was decided but not which meeting it happened in, the log is where you look.
An AI summary captures what was said. When you generate one, the decisions it picks up come back as proposals you can edit before sending them to the log. What lands there is the wording the team stands behind, with a status and a link to where it was decided. A summary of the conversation is not a record the team agreed on.
Yes. Decisions made between scheduled meetings as circular resolutions follow the team's same decision-making process and appear in the same log, alongside the meeting decisions. Many ways in, one record out.
The decision log is each team's own record. Where your organization uses Advanced Reporting, the people who need oversight get a read-only view of decisions across the teams that choose to share, without joining each team.
Inside your Microsoft 365 tenant. Decisions is M365-native: no third-party bots join your calls, and your data never leaves your tenant. It's SOC 2 Type II and ISO 27001:2022 certified.
Yes. The decision log comes with Decisions rather than as a separate purchase, and you can start free to try it in your own meetings. If you want to set up the decision-making processes behind it, like voting and structured approvals, talk to your Customer Success Manager or email support@meetingdecisions.com.
Still have questions?
GET STARTED

Get started with the decision log

Included with your Decisions business license. Start free and try it in your own meetings.