Notes That Become the Record

Notes That Become the Record

Rewrite an AI meeting summary into four blocks, check every name and number against the transcript, then send it so corrections land in the thread instead of surfacing weeks later.

fathom meetings follow-up email accuracy client-comms

What it is for

A rewrite-and-verify pass that turns a raw AI meeting summary into a four-block recap: agreed, owners and dates, still open, not discussed. Use it before any notes leave your company. It catches the two things that cause disputes — commitments attributed to people who never accepted them, and mis-transcribed numbers — and it invites the correction now, in the thread, instead of three weeks later.

The skill

Use this after a recorded call, before you send anyone the notes.

Never forward the raw AI summary to a customer, a candidate or a
manager. It contains everything the call contained - asides, half-
formed positions, the thing someone said before changing their mind -
and it attributes all of it with total confidence.

Rewrite into four blocks, in this order:
1. What we agreed - only where someone actually said yes.
2. Who does what by when - name, verb, date. No "we'll look into it".
3. What is still open - with who decides, and by when.
4. What we did not discuss - the thing they will raise later.

Then run three checks against the transcript, not against memory:
- Every name attached to a commitment: find the sentence where that
  person accepted it. If you cannot find one, move the item to block 3.
- Every number, price and date: read it in the transcript. Digits and
  units are what transcription gets wrong most.
- Every quote you plan to use: copy it verbatim, and keep the
  timestamp beside it in your own copy.

Keep it under two hundred words. Put the deadline in the first two
lines. Link the recording instead of pasting the transcript - nobody
reads a transcript, everybody skims four blocks.

Close with one question: "Anything here you'd correct?" Send it to
everyone who was on the call, including whoever dropped early, and
keep every correction in that one thread, so the last message in it is
the record. A correction that comes back by reply-all the same day is
cheap. The same correction three weeks later is a dispute.

The failure this prevents: a recap claiming a client approved
something they only thought about out loud, discovered three weeks
later by someone who was not on the call.

How to install it

1. Open the tool and start a new conversation, project or template.
2. Paste the text below wherever the tool keeps standing instructions
   — usually called system prompt, instructions, or persona.
3. Save it so it applies to every run rather than a single message.

Did it work for you?

Where it came from

Skills app Original