Skip to main content
Verslay
All Use Cases
Operations

Notion Decision Log Compiler

Recover decisions buried across Notion.

Helps teams preserve decision history without rereading every project note and meeting page.

Best forConsultingMarketing AgencyProfessional ServicesSaaS
Agents7 required
Duration3-5 minutes

Searches project pages and meeting notes, extracts decisions and rationale, and returns a structured decision log for teams.

How it runs

Multi-agent orchestration — here's the flow, step by step.

01

Call verslay_recall to retrieve the prior decision log snapshot and tracked decision-makers from memory. Then query the configured Notion decisions database and any linked meeting-notes pages to extract all decisions recorded since the last compile date — pulling decision title, date, decision-maker, options considered, chosen option, rationale, and linked projects. Also scan any 'Action Items' databases for decisions embedded in meeting notes. Store raw decision corpus as Phase 1 output.

notion knowledge base operator
02

Consume Phase 1 decision corpus. Categorize decisions by domain (product, engineering, operations, finance, hiring). Identify decision clusters — groups of related decisions that form a strategic pattern. Flag any decisions lacking documented rationale or with missing 'options considered' fields (decision debt). Produce a structured decision taxonomy with completeness scores.

knowledge synthesizer
02

In parallel with knowledge-synthesizer, call verslay_web_search and verslay_news_search targeting 'decision log best practices' and 'architectural decision records' to surface recommended documentation frameworks (e.g., ADR format, DACI). Call verslay_scholar_search targeting 'organizational decision documentation' for evidence-based practices. Pass framework recommendations to Phase 3.

web researcher
03

Consume Phase 2 decision taxonomy and completeness scores. Compute decision-log health metrics: total decisions logged this period, completeness rate (decisions with full rationale), domain distribution, most-active decision-makers, and average time-to-document (decision date vs. log-entry date if available). Call verslay_chart_create to generate a decision-domain distribution donut chart and a completeness-rate trend bar chart.

data analyst
04

Consume Phase 3 health metrics and charts, Phase 2 taxonomy, and Phase 2 framework recommendations. Format the compiled decision log: (a) a period summary with metrics and charts; (b) decisions organized by domain with standardized fields; (c) a 'decision debt' list of incomplete records with recommended follow-up owners; (d) cross-references linking related decisions.

report formatter
05

Consume Phase 4 compiled decision log. Write an executive decision log summary: key strategic decisions this period, emerging patterns across domains, decisions that may warrant revisiting, and a note on documentation health (completeness rate vs. target). Call verslay_memorize to store the updated decision log state, domain taxonomy, and completeness metrics in memory.

executive briefing writer
05

Receive the executive decision summary from executive-briefing-writer. Deliver to the configured Slack channel or email the leadership team. Confirm delivery and log send timestamp.

distributor

Required Agents

7
  • notion-knowledge-base-operator
  • knowledge-synthesizer
  • web-researcher
  • data-analyst
  • report-formatter
  • executive-briefing-writer
  • distributor

Connections

Required

notion

What it does

  • Decision extraction
  • Rationale summary
  • Owner and date capture
  • Open-question list
  • Structured log output

Example prompt

Compile a decision log from these Notion project pages. Include decision, rationale, owner, date, and open questions.

Ready to deploy Notion Decision Log Compiler?

Start free. One click, full agent orchestration.

Get Started Free →