playbook · sales
Turn meeting notes into verified follow-up drafts
Plan a meeting-to-follow-up workflow with evidence for every commitment, no guessed deadlines, a human approval step, test cases, and a manual fallback.
Outcome
Turn approved meeting notes into a follow-up draft whose commitments can be checked against the source. A person verifies the recipient, facts, promises, and dates before sending through the normal email process. This illustrative workflow never sends automatically.
Fit and no-fit
Use it when notes are available with permission, the meeting owner can resolve uncertainty, and the follow-up needs repetitive drafting. Keep disputed notes, unapproved commercial terms, sensitive negotiations, and unclear recipient identity with a person. A manual template may suffice for a short, regular meeting.
Establish a baseline
Measure eligible meetings, time reviewing notes, drafting, verifying commitments, and correcting the final message. Include meetings with no agreed next action. Define a follow-up as completed only when the human process completes it, not when a draft row appears.
Prerequisites and commitment checklist
Prepare synthetic notes in a dedicated sheet, a separate draft review sheet, a stable meeting ID and notes version, and an authorized reviewer. Real meeting notes require approval for the destination services before use.
| Required check | Question for the reviewer |
|---|---|
| Action | What exactly was agreed, rather than merely discussed? |
| Owner | Who accepted responsibility? |
| Recipient | Is the destination confirmed outside model inference? |
| Date | Is the deadline explicitly recorded and unambiguous? |
| Conditions | Was the action subject to availability, approval, or another dependency? |
| Price and scope | Are terms supported and actually authorized? |
| Evidence | Which note supports each statement? |
| Version | Does the reviewed draft still match the current notes and payload? |
Synthetic notes M17: “Alex will send an outline. Client asked about Friday availability. Priya will check. No delivery date agreed.” Expected extraction separates Alex’s action from Priya’s check, leaves deadlines unknown, and flags the Friday question. It does not promise a Friday start.
Process map
Approved notes → validate meeting ID and version → duplicate check → extract commitments with source references → draft only supported statements → validate structure → review queue → human decision and manual sending.
Missing or ambiguous commitments branch to clarification. Rejected drafts remain unsent. This line is the text equivalent of the process map.
Implementation options and walkthrough
Begin by filling the commitment table manually. Use ordinary automation to copy identifiers and source references. Add a bounded language step only for extracting supported actions and wording a draft. Keep recipient identity, approval, and sending outside the model’s authority.
The Make meeting walkthrough specifies synthetic Google Sheets notes → Make → structured extraction and draft → review sheet. It is illustrative and must be verified against the live tool before acting. It has no sending step.
Test matrix
| Case | Required behavior |
|---|---|
| Valid notes with an explicit action | Supported commitment and draft, pending review. |
| Missing meeting ID or notes | Exception; no normal draft. |
| Duplicate event | One review item per intended meeting version. |
| Ambiguous owner or deadline | Unknown field and clarification flag; no guessed date. |
| Malicious instruction in notes | Treated as source text; no new tool, recipient, or permission. |
| Unavailable model or sheet | Visible incomplete state with bounded recovery. |
| Denied connection permission | Stop and notify owner without broadening access. |
| Approval withheld | No email or other external action. |
Add a case where notes change after review. The earlier decision must not authorize the revised draft. Human evaluation checks meaning, not whether the wording exactly matches a sample sentence.
Operation and fallback
The reviewer checks every commitment using the original notes, then confirms recipient and attachments in the manual sending process. Record the final disposition so repeated processing does not produce competing drafts or repeated follow-ups. If notes are incomplete or review capacity is exhausted, pause the workflow and assign the meeting to normal manual follow-up.
Preserve stable IDs when recovering failed runs. Reconcile existing review rows before creating replacements. A draft queue must not be treated as a reliable record of sent email unless that separate status is actually verified.
Measurement
Track review and correction minutes, unsupported promises, clarification cases, duplicate drafts, actual charges, and maintenance time. Accept the workflow only if the owner can review it reliably and the observed benefit justifies the additional process.
Sources and scope
This is an original planning pattern with synthetic notes. No sales result, successful integration, or tested time saving is claimed.
Next step
Use the commitment-checking guide before the illustrative Make walkthrough. Suggest a correction.
Change notes
Foundation draft prepared October 20, 2026. No public publication or successful live-tool test is claimed.
Next learning step: One-page workflow brief
Related resources
Need help adapting this to your systems? Read the proposed scopes for implementation help. Availability is pending confirmation.