The Debrief

The meeting ended. Now figure out what actually happened.

What did we actually decide? Who's doing what? And what still needs follow-up? Paste your meeting transcript or notes. We'll pull out the decisions, commitments, deadlines, and loose ends.

See what The Debrief gives you

This is the complete, real output from an actual The Debrief run on the sample meeting note below — nothing here is invented or shortened.

Sample meeting transcript (excerpt)

Weekly v2 product review. Sarah (Eng Lead) flags a 3-week slip risk on the full analytics dashboard due to slow aggregation queries and a customer-level data exposure issue. Priya wants the dashboard in given direct customer feedback. Marcus proposes shipping a simplified version (top-line metrics only, no drill-down) at launch, with the full version as a fast-follow. Priya agrees. PM will write up the simplified scope by end of day; Sarah will give a real engineering estimate tomorrow.

Real run, 2026-09-23 — the tool's own built-in example scenario, Distill mode.

Meeting summary

Product scope alignment meeting — a structured weekly review that moved from status update into a live scope decision. Duration: 15–25 minutes, based on transcript volume and the focused single-topic resolution. Weekly v2 product review where the team resolved a scope conflict over the analytics dashboard, deciding to ship a simplified version at launch with a full version to follow.

At risk

  • The fast-follow full analytics dashboard has no named owner, no deadline, and no definition of what distinguishes it from the v1 version being shipped — it could drift without a follow-up commitment.
  • Sarah's estimate for the simplified dashboard ('about a week') is a rough read, not a confirmed scope — her real estimate is not due until tomorrow, meaning the launch date has not actually been validated yet.

Decisions made (2)

  • The analytics dashboard will ship as a simplified version (top-line metrics only, no drill-down) at v2 launch rather than being cut or delayed. Engineering flagged a three-week slip risk due to slow aggregation queries and a security issue; Marcus proposed a scoped-down version, which Priya preferred over shipping nothing. Proposed by PM, confirmed by Priya, accepted by Sarah. Can this still change? Probably — could reopen if Sarah's real estimate tomorrow shows the simplified version is also not achievable in the launch window.
  • The full analytics dashboard with drill-down capability is deferred to a fast-follow release after v2 launch. The security issue with customer-level data exposure and slow aggregation queries made the full version infeasible for the current launch timeline. Proposed by PM, agreed by Priya. Can this still change? Probably — timing and ownership of the fast-follow have not been set.

Action items (2)

  • [High] Write up the v2 scope — specifically what is in scope for the simplified analytics dashboard. Owner: Me (PM). Due: end of day today (Wednesday, September 23, 2026).
  • [High] Provide a real engineering estimate for the simplified dashboard. Owner: Sarah (Eng Lead). Due: tomorrow (Thursday, September 24, 2026). Depends on: PM scope write-up may inform the estimate boundary.

Tensions detected

Analytics dashboard at launch: include vs. cut. Priya wanted the dashboard in given direct customer feedback; Sarah had flagged a multi-week slip risk due to technical issues. Resolution: resolved by Marcus's suggestion to ship a simplified version — both positions partially accommodated.

Open questions (3)

  • What is the exact scope of the simplified dashboard — which top-line metrics are included, and what is explicitly excluded? The concept was agreed on but the content was not defined in the meeting. Suggested owner: Me (PM), with input from Marcus and Sarah.
  • What is the timeline and owner for the full analytics dashboard fast-follow? The meeting focused on resolving the immediate launch decision; the fast-follow was named but not planned. Suggested owner: Me (PM) to initiate, Sarah and Marcus to estimate.
  • Has the security issue with customer-level data exposure been resolved or just deferred by descoping drill-down? Sarah raised it as a reason for the slip but the conversation moved to scope options without confirming whether the simplified version is clear of the same issue. Suggested owner: Sarah (Eng Lead).

Parking lot

  • Full analytics dashboard with drill-down — deferred to post-launch fast-follow, needs its own planning.
  • Security issue with customer-level data exposure — raised but not confirmed resolved by the scope change.

What this meeting revealed

Tight and focused — the meeting moved quickly from status to a concrete decision with no extended tangents, though the simplified dashboard scope and fast-follow details were left to be worked out separately. Ownership is clear for the two immediate actions — PM owns the scope write-up today, Sarah owns the estimate tomorrow — but the fast-follow dashboard has no owner and no deadline attached to it yet. The analytics dashboard has been a point of disagreement between engineering and the CEO heading into this meeting; if the simplified scope or fast-follow timeline is not pinned down quickly, this topic may resurface at the next review.

Ready-to-send follow-up

Hi all — quick recap from today's v2 review. We decided to ship a simplified analytics dashboard at launch (top-line metrics, no drill-down), with the full version as a fast-follow. Two actions coming out of this: I will send a scope write-up for the simplified dashboard by end of day today, and Sarah will have a real engineering estimate by tomorrow. Open item to schedule: we still need to assign ownership and a timeline for the full dashboard fast-follow — I will propose a path on that once the estimate is in.

What happens with your meeting

Paste your transcript or notes and choose the kind of debrief you need. The Debrief separates what was decided from what was merely discussed, flags what's still at risk, and turns commitments into a ready-to-send follow-up you can use.

This is a real, complete tool run against a realistic sample meeting transcript.

Overview

The Debrief is The Crux's professional sibling — same core mechanic (long transcript → extract what matters), but purpose-built for meetings instead of talks and long reads. Where lectures need concepts and testable material, meetings need decisions, owners, deadlines, and accountability. The tool distinguishes between 'someone said we should' (not a decision) and 'we agreed to' (a decision), flags action items with no owner or deadline, detects tensions, and grades meeting health. Series mode is the killer feature — paste your last 3 weekly standups and see which action items disappeared without resolution.

How to use it

  1. Pick a mode: Distill (decisions & actions), Follow Up (draft messages), or Series (cross-meeting patterns)
  2. Paste your transcript — from Zoom captions, Teams, Otter.ai, Google Meet, or typed notes
  3. Select meeting type for better extraction (standup vs. planning vs. client meetings need different outputs)
  4. Optionally add attendee names and context
  5. Review results — Distill gives you the full meeting output, Follow Up gives you ready-to-send messages

Example

Scenario: Your team just finished a 45-minute sprint planning meeting. Three decisions were made, several tasks assigned, and one disagreement was tabled for later.

What you do: Paste the Zoom transcript, select 'Planning', add attendee names.

Result: Distill produces: 3 decisions (with who drove each), 7 action items (2 flagged as UNASSIGNED — nobody actually took ownership), 2 open questions (one deferred because the PM was absent), detected tension between engineering and design on the timeline, and a meeting health score of 65% efficiency. The ready-to-send follow-up email lists all action items with owners and deadlines.

Tips