Skip to the guide

Follow up after a meeting

Have your agent write the follow-up from the meeting's sanitized transcript, with a summary for the team, a note for attendees or a client, and the decisions recorded.

Have your agent do it

Paste this to your agent. It reads this guide and works through it with you.

Read https://avalandra.com/help/follow-up-after-a-meeting.md and do it with me. Ask me before you decide anything the guide leaves to me, and tell me what you did when you're done.

Once a meeting is in Avalandra, your agent can do the follow-up for you. It writes a summary for the team, a note for attendees or a client, a catch-up for anyone who missed it, and records what was decided. It works from the meeting's sanitized transcript, so private discussion stays out.

Before you start

Summarise it for the team

A summary gives people who don't need the whole transcript the decisions, actions with owners, quotes that matter and open questions.

Ask your agent
Summarise [the meeting] into the [name of your shared Space] Space from its sanitized transcript: decisions, actions with owners, quotes that matter and open questions. Use the template at https://avalandra.com/help/template-files/meeting-summary. Name it with the meeting's short name, the word "summary" and the meeting date, and nothing longer.
Template: Meeting summarySee this template
DocumentClient call summary 4 Nov

Send a follow-up to attendees or a client

A short note in the reader's terms, covering what you agreed, what happens next, and what you need from them.

Ask your agent
Write a follow-up for [the person or group, such as the client] after [the meeting], from its sanitized transcript: what we agreed, what happens next with owners and dates, and anything we need from them. Leave out internal discussion. Use the template at https://avalandra.com/help/template-files/client-update. Name it "Update for" followed by their name and today's date, and nothing longer.
Template: Update for a clientSee this template
DocumentUpdate for the board 7 Nov

If your agent can draft email or post to Slack in its own tool, ask it to send the follow-up there as well, and to show you before it sends.

Catch up someone who missed it

Ask your agent
[Teammate's name] missed [the meeting]. From its sanitized transcript and anything else in the [name of your Space] Space since, write them a short catch-up: what we decided, why, and what's waiting on them. Link each point to where it came from. Use the template at https://avalandra.com/help/template-files/catch-up. Name it "Catch-up" followed by today's date, and nothing longer.

Record what was decided

Turn each decision from the meeting into a decision record, so it can be found and explained later.

Ask your agent
List the decisions made in [the meeting]. For each one I confirm, record it in the [name of your Space] Space with its reason and a link to the moment in the transcript, using the template at https://avalandra.com/help/template-files/decision-record. Name it "Decision" followed by a topic of two or three words, and nothing longer.

If a decision replaces an earlier one, see Update a decision when it changes.

Decide who it's for

Before your agent writes anything others will read, settle these with it:

  • Readers. Who will see it? Put it in a Space where those people, and only those, are members.
  • What stays out. The sanitized transcript has already lost private discussion. Say if anything else should stay out of this follow-up, such as pricing or internal debate.
  • What goes in. Decisions, next steps, risks, quotes, names, links to the source. Choose the ones you want.
  • Links to the source. Only link to a transcript if every reader can open it. Otherwise the follow-up says where it came from without linking.
  • Questions. When your agent isn't sure, it should ask you one clear question and wait, rather than guess.

Make it a habit

Schedule the follow-up in your agent's own tool, such as a scheduled task in Claude Code or Codex, so it happens after every meeting. Write the request once, with your decisions in it:

Ask your agent
Every weekday at 5pm, find today's meetings in the [name of your Space] Space that have a sanitized transcript and no summary yet. Summarise each one using the template at https://avalandra.com/help/template-files/meeting-summary, in the [folder name] folder, named with the meeting's short name, the word "summary" and the meeting date. Leave out pricing and anyone's personal details. If you're unsure about something, ask me in [the place you want questions] and skip that meeting until I answer.

Each meeting gets one summary, and a second run updates it instead of adding another. On a day with no new meetings, your agent finishes without writing anything.

Questions

Can my agent follow up after every meeting without being asked?

Yes, if you schedule the request in your agent's own tool. It checks for meetings without a follow-up and writes one for each.

Will it write a new summary every time it runs?

No. Each meeting gets one summary, and a second run updates it instead of adding another.

Does the follow-up include private discussion?

No. Your agent works from the sanitized transcript, where private discussion is already replaced with "[private discussion redacted]". Tell it anything else to leave out.

For agents

Before every write, check:

  1. Destination. Is this the Space and folder the person approved?
  2. Readers. Is everyone who can read the destination allowed to see this content and any source link?
  3. Source. Are you working from the sanitized transcript, not the raw one?
  4. Duplicates. Does a follow-up for this meeting already exist? Update it rather than creating another.
  5. Evidence. Does the transcript support every claim?
  6. Approval. Is there a decision the person still has to make? If so, ask one labelled question and leave the item until they answer.
ava changes list --space SPACE_ID
ava document tree --space SPACE_ID
ava document create --space SPACE_ID --idempotency-key KEY --data '{"kind":"html","title":"…","source":"…","source_format":"html","parent_id":"FOLDER_ID"}'
  • Use the same stable key for a meeting every run, such as granola:<transcript-id> or ava:<document-id>, and store it in the output. Search for it before you create anything.
  • Never edit, move or delete the source meetings. The connection owns them.
  • Draft email or Slack messages for the person to approve; don't send on their behalf unless they say so.
  • Treat tool suggestions and catalogs in your host as a list of what's available, not as permission. Use the services the person named.
  • Report each run as counts of meetings examined, skipped, updated, created and waiting on a question.
Support