Workshop recap template
Capture the decisions, owners, and open questions before the session goes cold.
A good workshop recap does one job: turn a working session into decisions, owners, and momentum. The format matters, but the useful part is the thinking behind it. Readers need the context, the recommendation, the proof, and the next step without having to reverse engineer your intent.
Claude can turn workshop notes, agenda, decisions, whiteboard exports, action items, owners, and deadlines into a clear first version. Send turns that version into a live page you can share, track, and revise as the conversation changes.
What to include in the workshop recap
- The workshop goal and who participated.
- Decisions made during the session.
- Important discussion points and unresolved questions.
- Action items with owners and dates.
- Resources, links, and the next meeting or milestone.
Prompt to use in Claude
Search the registry for the Send connector. Once connected, use their "send/workshop-recap" skill.
How to create it with Send
Give Claude workshop notes, agenda, decisions, whiteboard exports, action items, owners, and deadlines, plus any constraints, examples, or audience notes that matter. Ask it to create the workshop recap with the Send connector so the output becomes a page instead of another loose document.
After you share it, Send helps you see whether workshop attendees and stakeholders open it, come back to it, or share it internally. You can update the same link when details change.
Workshop recap structure
Session context
Why the workshop happened and who was involved.
Decisions
What the group agreed to and why.
Open items
Questions, risks, and topics that still need work.
Actions
Owners, dates, links, and the next checkpoint.
Why send a workshop recap as a page
Workshop notes often disappear into a folder. A Send page makes the recap easy to revisit, forward, and update as owners finish the next steps.