Clone Support

meeting-notes-style.md

How you want meeting recaps written, so every summary from every clone looks the same.

Version 1 · updated Nov 14, 2026

# Meeting notes and recap style

> How to use this template: describe the recap you wish you always got. Your clones use this for meeting recaps, call summaries and follow-up emails. Edit the sections and order to match how your team works.

## Recap structure (in this order)
1. **One-line summary**: what the meeting was for, and the outcome
2. **Decisions**: bullet list; write "No decisions" if there were none
3. **Action items**: a table of Owner | Task | Due date
4. **Open questions**: what still needs an answer, and who will get it
5. **Key details**: numbers, dates, names and quotes worth keeping

## Rules
- Lead with outcomes, not a minute-by-minute account
- Use names, not "someone"
- Dates in [Nov 14 / 14 Nov] format
- Keep internal recaps under [200] words; customer-facing recaps under [150]
- Never include [pricing discussed internally / personal remarks / side conversations] in recaps sent outside the company

## Who gets the recap
- Internal meetings: [all attendees / me only]
- Customer meetings: [me first for review, then attendees]

## Example of a great recap
**Summary:** Kickoff with Acme to plan the Q1 rollout. Agreed on a 3-phase launch starting Jan 12.
**Decisions:** Phase 1 = support team only; weekly check-ins on Tuesdays.
| Owner | Task | Due |
|---|---|---|
| Dana (Acme) | Share the admin list | Nov 18 |
| Sam (us) | Send the training schedule | Nov 20 |
**Open questions:** SSO timeline (Dana to confirm with IT).

Was this useful?