Skip to content
Free tools

Decision log template

A template for writing decisions the next person, and the next AI tool, can use.

A decision made in a meeting reaches the people in the room. A decision written with where it applies and who confirmed it reaches everyone after them.

The tools run in your browser. What you type stays on your device.

Write one decision

Fill in what you know. The file on the right updates as you type, and empty fields show as prompts, so you can also take the blank template.

A few words the next person can search for.

One sentence, in plain words.

The product, the part of it, the client or market. And where it does not apply.

A name and a role, so the next person knows who to ask.

The day it was confirmed, such as 3 Oct 2026.

A link or a note: the meeting, the ticket or the thread.

Status

Active while it applies. Replaced when a newer decision takes over. Stopped when it no longer applies.

Your file

# [Short title]

- **Status:** Active
- **Decided:** [What was decided, in one sentence]
- **Applies to:** [Where it applies: the product, the part of it, the client or market. And where it does not]
- **Confirmed by:** [Name, role]
- **Date confirmed:** [Date confirmed]
- **Came from:** [Link or note: the meeting, the ticket or the thread]

What every decision needs

Five things. Leave one out and the next person has to ask.

What was decided

One sentence, in plain words. Someone who was not in the room should be able to act on it.

ExampleMembers on legacy NSW policies keep paper statements until June 2027.

Where it applies

Name the product, and the part of it, the client or the market when the decision is narrower. If it could be read more widely than you mean, say where it does not apply. This is the line people skip, and the one that keeps a decision out of the wrong place.

ExampleMember Portal.

Who confirmed it

A name and a role. The next person knows who to ask, and an AI tool can tell the decision was checked.

ExampleHead of Claims Operations.

When

The day it was confirmed. Decisions change, and the date shows which one is newer.

Example3 Oct 2026.

Where it came from

A link or a note: the meeting, the ticket or the thread. When someone doubts the decision, this is where they look.

ExampleQuestion on “Digital statements for members”.

The same decision in Rivora

This is how Rivora keeps the decision above. The five things are all there, and Rivora adds where the decision is used.

Decision · Active

Members on legacy NSW policies keep paper statements until June 2027.

Applies to
Member Portal
Confirmed by
Head of Claims Operations · 3 Oct 2026
Came from
Question on “Digital statements for members”
Used in
Backend and Platform · Delivery Backlog · Implementation Handoff

Illustrative example

Paste it into Confluence or Notion

Confluence

Paste the Markdown into a new page and check how it looks. If the # and ** marks show as plain text, or it lands as one block of code, make a two-column table instead: the five field names down the left, your answers on the right.

Notion

Paste the Markdown into a new page and check how it looks. If the formatting does not arrive, make a table, or a database with a column for each field. Notion can also import the downloaded .md file from Settings, under Import, as Text & Markdown.

In either tool

  • Use one page for each decision, or one row for each decision in a table.
  • Keep the date in its own column, so you can sort by it.
  • Link each decision to the ticket or thread it came from.

Keep the log useful

  • One decision to an entry.
  • Keep every decision in one place the whole team can find.
  • When a decision changes, mark the old one Replaced and link the new one. Keep the old one.
  • Mark a decision Stopped when it no longer applies, and say why.

Rivora keeps every answer this way: the decision, where it applies, who confirmed it and where it came from. You can replace or stop one later, and nothing is learned silently.

Bring one real feature you’re planning in the next month.

Four weeks, with Anurag alongside your team. Or start with a free 30-minute conversation about your setup.