Working together
Meeting notes that lead to next steps.
Use your own notes to guide the summary, then turn decisions into work you can follow.
The most useful meeting notes tell the next person what changed. A transcript can help you check the conversation, but it does not decide which commitments deserve attention.
Integrity puts live transcription, your own notes, and the finished summary in a meeting node. The notes remain editable workspace content. You can keep them beside the project they concern.
Write down what matters while you listen
Create a meeting and start recording. Check the capture indicator before relying on the transcript. On desktop Chrome or Edge, capturing the other side requires sharing the meeting tab with tab audio enabled. Other browsers or a declined share can leave you recording only your microphone.
Tell participants that you are transcribing the conversation. Then write sparse notes as you listen. You do not need to reproduce every sentence. Capture the decision, a disagreement, a name attached to a next step, or a question nobody answered.
For a fictional launch review, your notes might be:
- Keep the first campaign focused on small teams.
- Sam will bring two visual directions to the next review.
- Launch date still depends on the demo being ready.
Those lines give the summary a useful emphasis. They also make uncertainty explicit.

Stop, then summarize
Stopping recording ends transcription. Summarize is a separate action. It uses the transcript and your notes to produce structured notes in the meeting itself.
You can choose a document as a summary template when you want a particular focus. A short instruction such as “Emphasize decisions, owners, and unanswered questions” is often more useful than a long formatting specification.
Read the result. Check names, dates, and whether a suggestion became a decision. If the conversation did not settle an owner or deadline, leave that field unresolved rather than letting polished prose conceal the gap.
Separate decisions from actions
“We will focus on small teams” is a decision. “Sam will bring two visual directions” is an action. “When will the demo be ready?” is an open question. They need different follow-up.
Put agreed actions into the project’s task database with the relevant owner. Keep the meeting as context you can mention from elsewhere. Avoid making a second task list that nobody checks once the meeting page is closed.
Ask the assistant to help with a bounded handoff:
Read these meeting notes. List the agreed actions and identify any missing owners. Do not infer a deadline. Wait for my corrections before adding the tasks to our launch board.

Keep the evidence available
The transcript remains accessible after summarization, so you can check a disputed detail. Integrity stores the transcript text rather than retaining the meeting audio as a recording library. If you need an audio archive, plan for that separately.
Transcription and note generation use workspace AI credits. Manual review and editing remain part of normal workspace work.
A useful final check is simple: could someone who missed the call tell what changed, what they own, and where to ask a question? If so, the notes have done their job.
Try it with your next project.
Start free