Decision log template for founders
A decision log template gives every decision the same short shape: what you decided, why, who agreed and when you will look at it again. Founders make dozens of small calls a month, and most are forgotten until someone asks "why did we do it this way?"
Copy the template below into a doc, a spreadsheet or a notes app, one entry per decision.
In short
A decision log is a dated list of decisions, each with the context, the options you considered, what you chose, why, who decided and when to review it. Write one entry per decision on the day you make it, and read the recent ones in your weekly check-in.
How to create a decision log
Pick one place for it
One doc, sheet or notes folder you can both open, not decisions scattered across chats.
Use the same fields every time
Copy the template below for each entry. Short entries are fine; a missing "why" is not.
Log the decision the day you make it
Right after the call or chat where you agreed. Memory of the reasons fades within days.
Review it on a schedule
Read the week's decisions in your weekly check-in, and revisit any entry whose review date has come up.
The decision log template (copy this)
- Decision: one sentence, written as what you will do.
- Date: the day you decided.
- Decided by: who made the call, and who was consulted.
- Context: the problem or question, in two or three lines.
- Options considered: the alternatives, including doing nothing.
- Why this option: the reasons and the trade-off you accepted.
- What would change our mind: a signal that means it is time to revisit.
- Review date: when you will check whether it worked.
- Links: the task, doc or thread it came from.
A filled-in example
- Decision: we will charge $29 a month for the first plan and drop the free tier.
- Date: 2026-10-05.
- Decided by: both founders; two early users were asked first.
- Context: free users take most support time, and none of the first ten upgraded.
- Options considered: keep the free tier, offer a 14-day trial, paid only.
- Why this option: paid only keeps support small while we have no support staff; we accept slower sign-ups.
- What would change our mind: fewer than five paid sign-ups in the first month.
- Review date: 2026-11-05.
- Links: the pricing task and the call notes.
What a decision log should look like
Newest entries first, one entry per decision, and short enough to scan in a minute. Do not log every small choice; log the ones you might argue about later, the ones that cost money, and the ones that are hard to undo.
Keeping the log in Pair North
In Pair North, any note can be marked as a decision. Decision notes have their own filter on the Notes page, appear in the weekly check-in for the week they were made, and are added to your journey.
When a step on a task is a question (its title ends with a question mark), answering it saves the answer as a decision note that links back to the task. If you answer it again later, the note keeps the earlier answers.
AI agents connected over MCP can write decisions too, by creating a note with the decision kind, and that change shows in the AI Inbox for both of you.
Questions people ask
What is a decision log?
A dated record of the decisions a team or a pair has made, with the reasons and the options that were rejected. It answers "why did we do this?" months later, when nobody remembers the call.
How do you create a decision log?
Choose one shared place, copy the same fields for every entry (decision, date, who decided, context, options, why, review date), and write each entry on the day of the decision.
What should a decision log look like?
A list with the newest entry on top, each entry a few lines long. A table works if the fields stay short; a notes folder works better when the context needs a paragraph.
What are the 7 steps of decision making?
A common version is: identify the decision, gather information, list the alternatives, weigh the evidence, choose, act, and review the result. The template follows the same order, so filling it in walks you through those steps.
Keep reading
- A shared to-do list for twoOne list for the two of you, with small steps and clear hand-offs.
- A task manager for co-foundersPlan, decide and keep the pace as a founding pair.
- A task manager your AI agents can useClaude Code, Codex or any MCP client, in your shared workspace.
- Claude Code as a task managerIts built-in task list, and a shared list over MCP.
- To-do apps with MCPTodoist, Trello, Asana, Notion and Linear MCP servers, checked.
- Dividing work between co-foundersSplit by area, one owner each, and review it weekly.
- Weekly check-in templateA 30-minute agenda for two partners, with prep questions.
- PricingSolo, Agency and Agency Unlimited plans.
- Pair North homeThe shared workspace for two partners and their AI agents.
Start building it together
Tell us a little about you and what you're building, and we'll send you an invite or a short demo. We usually reply within a day or two.
Already have an account? Sign in


