Decision Register

What it does

Automatically captures decisions from meetings, emails, and discussions into a searchable log so teams stop re-litigating settled questions.

Why I recommend it

Most teams waste hours redebating decisions because nobody remembers what was decided or why. A decision register creates institutional memory.

Expected benefits

  • Less time re-deciding settled questions
  • Clearer accountability for decisions
  • Better onboarding with decision context
  • Faster resolution of “didn’t we already decide this?”

How it works

Meeting ends or decision made → AI extracts decision statements from notes/transcript → captures who decided, what was decided, why, when → logs in searchable register → optionally links to affected tasks/projects.

Quick start

After meetings, manually write 2-3 bullet points of key decisions in a shared doc. Date and tag them. Once habit is established, add AI extraction from notes.

Level-up version

Make register searchable by keyword or topic. Link decisions to tasks they spawned. Flag when new discussions contradict old decisions. Track decision velocity and reversals.

Tools you can use

Storage: Notion, Google Docs, Airtable

AI: ChatGPT, Claude

Meeting tools: Zoom, Google Meet (for transcripts)

Automation: Zapier, Make, n8n

Technical implementation solution

  • No-code: Meeting transcript or notes uploaded → AI extracts decisions → append to decision log doc → tag and date.
  • API-based: Meeting platform webhook provides transcript → AI API extracts structured decisions → database API logs with metadata → search interface queries log.

Where it gets tricky

  • Distinguishing decisions from discussions
  • Capturing enough context without verbosity
  • Maintaining the register as single source of truth