Summarise a meeting and record the decisions and actions

What you get

A summary of one meeting that you can keep as its record. It starts with five sentences about what was discussed. Then it lists each decision and who made it, and each action with its owner and due date. It ends with the questions that the meeting left open and the name of the document it came from.

When the meeting did not give an owner or a date, the summary says "not stated". When no record of the meeting is saved, Sasha says so plainly. You do not get a made-up summary.

Before you start

Sasha uses a meeting record or transcript that is saved in one of your projects. A meeting transcript saved in Sasha is a document in the project's meetings folder. Notes or minutes that you saved in a project also count.

You need access to the project that holds the record. From Claude, Sasha searches only what you can reach.

Name the meeting in the words the record uses, such as the organisation, the subject and the date.

Start it

From Claude

Connect Claude to your Sasha first (Connect Claude to your Sasha). Then choose Summarise a meeting and record the decisions and actions from the prompt menu. Type the name and the date of the meeting.

What Sasha does

1. Searches the projects you can reach for the record of the meeting you named, by its words and its date.
2. Makes sure that the document is the record of that meeting, not a document that only mentions it.
3. Reads the whole record, to the end.
4. Writes five sentences about what was discussed.
5. Lists each decision and who made it, and each action with its owner and due date.
6. Lists the questions that the meeting raised but did not settle, and names the document used.
7. Says plainly when no record of the meeting is found.

Check the result

• Open the meeting record and confirm that each owner and due date matches what was said.
• Send the decisions and actions to the people who attended, so they can correct anything before work starts.
• If a meeting is missing, check that its transcript or notes were saved in a project you can reach, then ask again and name the project.
• To find what your organisation knows about a topic across many documents, use Find what we already know about a topic, with sources.
• If decisions in the meeting change a policy, run Find gaps and contradictions in our knowledge on that topic.