Decision Log Builder

Overview

Decisions get made in meetings every day, but most of them are never written down. A week later, nobody can remember what was agreed, who owns it, or why that option was chosen over the alternatives. The result is relitigated decisions, wasted meeting time, and teams that feel stuck in loops.

This tool helps you build a structured decision log during or after a meeting. Each entry captures the decision title, owner, context, options considered, final decision, rationale, and impact level. When you are done, you can generate a clean, formatted log and copy it to your clipboard for pasting into documents, wikis, or project management tools.

Everything runs in your browser. Nothing is stored or sent to a server.

Builder

How to Use

• Fill in the form for each decision made during the meeting. The title, date, owner, and final decision are the most important fields.
• Add options considered by clicking the "+ Add option" button. Documenting the alternatives you rejected is just as valuable as recording what you chose.
• Set the impact level so the team can quickly see which decisions carry the most weight when scanning the log later.
• Click "Add Decision" to save the entry. It will appear as a formatted card below the form. You can add as many decisions as you need in a single session.
• Generate the log once all entries are added. The output is plain text, formatted for easy pasting into Notion, Confluence, Google Docs, or any other tool your team uses.
• Copy to clipboard and paste it wherever your team keeps its records.

Example Entry

Best Practices

• Log decisions as they happen. Do not wait until after the meeting. Context fades quickly, and "we will write it up later" rarely happens.
• Always record the rationale. The "why" is more valuable than the "what." Six months from now, the team will not remember the reasoning unless it is written down.
• Document rejected options. This prevents the team from revisiting the same alternatives and re-running the same debates. It also helps new team members understand the thinking.
• Assign a single owner. Every decision needs exactly one person accountable for follow-through. Shared ownership is no ownership.
• Set review dates for high-impact decisions. Not every decision needs revisiting, but the big ones benefit from a scheduled check-in to see whether the expected outcomes materialised.
• Keep the language clear and specific. "We decided to go with Option B" is not useful on its own. State the decision in terms that someone outside the room would understand.

Common Mistakes

• Recording the decision but not the rationale. Without the "why," the log becomes a list of facts with no context. Future you will not remember why Option A was rejected.
• Vague decision statements. "We agreed to improve the onboarding process" is not a decision. "We will redesign the first-week onboarding flow by 30 April, led by Product" is one.
• Skipping low-impact decisions. Small decisions add up. Logging them takes seconds and prevents the "did we ever actually decide that?" conversation.
• No owner assigned. If no one owns it, no one follows up. Every entry should have a named individual, not a team or department.
• Letting the log go stale. A decision log only works if people trust it. If entries are missing or outdated, the team will stop consulting it and go back to asking around in Slack.
• Treating the log as a formality. The value is not in having a document. The value is in avoiding repeated debates, providing clarity to new joiners, and creating accountability for follow-through.

Related Tools

Related Templates