Free tool · works now

Decision Log Compiler

Compile ratified choices across meeting notes into a chronological record and CSV matrix.

Runs 100% in your browser. Extract explicit decisions across notes, filter out conversational chatter, sort chronologically, and export formula-guarded CSV logs.

8Total extracted
4Ratified agreements
2Tentative / deferred
4Dated entries
2Chatter filtered
2 line(s) mention the word "decision" during discussion without explicit agreement markers; kept out of ratified log.
2 decision(s) contain tentative wording ("pending", "deferred", "TBD"); ratify before archiving.
2 decision(s) lack an explicit ISO calendar date (YYYY-MM-DD).
Input notes & minutesEditable
Compiled decision logMarkdown table

Extracted decisions ledger

Granular accounting of ratified commitments, dates, and discussion context
DateDecision descriptionDeciderStatusFlags & rationale
UndatedWe need to make a decision about database caching next week.UnspecifiedDiscussionDiscussion mentioning "decision" (no explicit agreement marker)
UndatedThere was broad discussion on whether Redis or Memcached makes sense, but no decision was reached.UnspecifiedDiscussionDiscussion mentioning "decision" (no explicit agreement marker)
2026-10-10Adopt SQLite FTS5 for local desktop search because it eliminates network dependencies@alexRatifiedReason: it eliminates network dependencies @alex 2026-10-10; None
2026-10-08Deprecate v1 REST telemetry API endpoints by@sarahRatifiedNone
2026-10-05Maintain ScreenCaptureKit loopback as default macOS audio capture path@elenaRatifiedNone
2026-10-02Cloudflare Workers KV selected for global edge session tokens@marcusRatifiedNone
Undatedpending on OAuth2 provider selection TBDUnspecifiedTentativePending decision
Undateddeferred regarding multi-region database failover until security audit completesUnspecifiedTentativeDeferred decision

The organizational burden of lost decisions

In engineering organizations and product teams, decisions are the core currency of progress. Architectural compromises, database selections, protocol migrations, and security postures are agreed upon during intense meetings and recorded across disparate notes.

However, within a few weeks, context decays. New team members re-open settled debates because nobody remembers why a choice was made, when it was finalized, or who consented to it. Even worse, unresolved topics that were merely “discussed” are occasionally mistaken for firm commitments, causing engineering teams to build features against phantom consensus.

A durable decision log solves this by gathering explicit agreements into a single, chronologically sorted ledger with clear provenance, deciders, and rationales.

The critical boundary between discussion and agreement

Meeting minutes frequently contain passages like:

“We spent twenty minutes debating the decision regarding database failovers, but could not agree before the call ended.”

Naive automation tools search for the keyword “decision” and indiscriminately pull this line into a project summary. This creates catastrophic miscommunication: conversational hesitation is codified as an architectural commitment.

The Decision Log Compiler strictly enforces an agreement barrier:

  • Explicit Marker Requirement: Only lines carrying affirmative decision markers (such as ! Decision:, **Decision:**, or - [x] DECISION:) are admitted to the ratified log.
  • Tentative Language Screening: Lines containing words like pending, deferred, TBD, or tabled are quarantined under a “Tentative” status to prevent premature implementation.
  • Discussion Filtering: Lines that mention the word “decision” in passing without an affirmative marker are filtered into a separate chatter tally and excluded from the ratified markdown matrix.

Chronological sorting and provenance tracking

Architecture Decision Records (ADRs) and executive logs require temporal anchors. By extracting ISO 8601 calendar dates (YYYY-MM-DD), this utility sorts choices chronologically so stakeholders can trace how a system evolved over time. Decisions lacking dates are gathered into an undated review section so team leads can anchor them to real milestones.

Every entry retains its original line provenance, enabling collaborators to cross-reference decisions directly back to the original meeting minutes.

Local browser security and formula injection defense

Architecture logs contain sensitive system blueprints, roadmaps, and staffing details. Exporting these records should never involve third-party SaaS cloud parsers. This compiler executes entirely within your browser tab using native TypeScript logic.

Additionally, exported CSV files are protected against CSV Formula Injection. Any cell beginning with =, +, -, or @ is shielded with a leading apostrophe, protecting management spreadsheets from accidental formula execution.

Discover companion engineering tools including our Action-item & task validator, Meeting record builder, and Markdown table formatter in our browser tools catalog.

Questions

How does the Decision Log Compiler identify decision markers in notes?

The engine scans for explicit line-level markers including exclamation marks (`! Decision:`), markdown bold tags (`**Decision:**`), checklist markers (`- [x] DECISION:`), and architecture heading lines (`# Decision:`). Code fences and script snippets are strictly shielded.

Why does the tool reject conversational sentences containing the word "decision"?

In meeting minutes, phrases like "we had a long discussion about the decision" or "decision pending next week" describe conversational context or indecision rather than ratified consensus. Treating such sentences as agreements introduces false commitments into team records.

How are tentative and deferred decisions categorized?

Lines marked with words like "pending", "deferred", "tabled", "TBD", or "draft" are classified as Tentative. They are cataloged separately from ratified agreements so that teams know which architectural choices remain unresolved.

Can the compiled log extract decider handles and ISO dates?

Yes. The parser automatically detects `@username` handles, explicit assignees (`by: alex`, `lead: sarah`), and ISO 8601 calendar dates (`YYYY-MM-DD`). Decisions with dates are ordered chronologically, while undated choices are collected in an open backlog.

Does this tool transmit private engineering notes to external servers?

No. All parsing, categorization, chronological sorting, and document compilation execute 100% locally inside your browser memory. No text or notes ever leave your machine.

Want structured decision records on your local Mac?

Complete Obsidian vault compatibility, plain text Markdown on disk, and private on-device meeting recording in Oyma.

tools decision log compiler downloadDownload for Mac

No account needed. Intel Mac build