Decant

Every recap, the same clear shape

What Decant pulls out of your notes, and how it comes back.

Recap anatomy

  1. 1

    Explicit decision extraction

    Isolates approved directions and resolved questions from multi-speaker discussions.

  2. 2

    Assigned action tracking

    Structures tasks with identified owners and clear delivery deadlines.

  3. 3

    Email-ready formatting

    Outputs clean markdown for client emails and chat threads.

  4. 4

    Permanent recap archive

    Search and reference past meeting summaries whenever follow-up questions arise.

Client Call · example

Acme Corp: Website Redesign Sync

Decisions

  • D1Launch date moved to October 15.
  • D2Project budget approved at $45,000.
  • D3Visual direction set as modern minimalist.

Action items

Deliver updated Figma filesSarahFriday
Update API endpoints for reviewMarkMonday

Email-ready

# Acme Corp: Website Redesign Sync
**Decisions Made**
- Launch date moved to October 15.

Saved to your library

Searchable by title, summary and meeting type

Output structure

The same six parts, every run.

Rough blocks locking into an ordered cube

Sarah to send Figma files by Friday.→ task · owner · deadline

Title

A clear name for the meeting.

Acme Corp: Website Redesign Sync

Meeting type

Client call, team sync, 1-on-1, project review or general.

Client Call

Executive summary

The objective, topics and outcome in a short paragraph.

The team agreed on a minimalist visual direction and approved a revised Oct 15 launch within the $45k budget.

Decisions

Agreements only; open discussions are called out as open.

Launch date moved to October 15.

Action items

Each task with its owner and deadline, marked Unassigned or TBD when missing.

Sarah · Deliver updated Figma files · Friday

Email-ready recap

Everything above, formatted to paste into email or chat.

# Acme Corp: Website Redesign Sync

$ decant --features all

Clear your post-meeting backlog

Get Started