Flow Summaries in Notetaker
Last updated: November 21, 2026
Available on: Mac and Windows. Business and enterprise subscriptions need organization access, and organization settings can disable Notetaker. If recording is restricted, the recorder explains the restriction and offers next steps.
Flow Summaries turn finished Notetaker recordings into structured recaps of discussions and follow-ups. Find yours in the Summary tab, separate from your typed notes.
Note: An active HIPAA Business Associate Agreement does not prevent recording. BAA-covered accounts get summaries and automatic meeting titles, and summary text is only processed by AI providers covered by Wispr's BAA; transcript, typed notes and meeting chat are unaffected. Organization restrictions still apply, and BAA-covered accounts cannot submit meeting reports.
Generate and open a summary
Stop your recording, including any recording of the same meeting on another device.
Open the Summary tab in the meeting notepad.
Click Generate summary if the top bar says Not auto-generated. The control sits above the meeting footer on every tab after recording stops, and on the Hub meeting row.
Clicking while Flow saves audio waits for saving to finish; a failed start shows an error with Retry. Generation typically takes 5–20 minutes depending on call length, and the Summary tab shows a rough quick summary, which does not name speakers, until the full summary replaces it.
Automatic generation: More than 5 minutes of audio across all meeting segments triggers processing at stop; exactly 5 minutes does not. Choosing Offline mode at recording start also triggers processing at stop with any audio. An account switch, a failed start, or a summary held for updating still requires manual generation.
Manual generation: Recordings of 5 minutes or less stopped from the notepad, and retained failed starts, wait for Generate summary. Deferred uploads are picked up 24 hours after the stop, subject to connection, sync and audio availability.
Working offline: Manual generation works while local audio remains; upload resumes on reconnect without relaunching or uploading the same audio twice. Turning off Notetaker cloud sync does not prevent recording, but meetings stay on your device until sync permits processing. Local audio stays on your device until the stop has been saved and the audio encoded.
Older and imported meetings: Older meetings do not get summaries retroactively. Imported meetings keep their imported summary; an import without one shows This meeting came without a summary.
The one-time Your summary is ready! notification with View summary appears for your first meeting longer than 60 seconds, not for every summary. If that meeting's notepad is focused, Flow prepares the Summary tab there instead.
Warning: Deleting a meeting immediately discards its audio. An empty session with no audio or transcript, or a failed start with under 10 seconds of audio, is discarded unless you typed notes or resumed an existing meeting.
Note: Local-audio retention and the Resume window default to 7 days; unprocessed audio is kept 30 days by default for retry or recovery, never shorter than ordinary retention. These periods can vary, the recovery period does not extend Resume, and transcript-deleted meetings use ordinary retention. Expiring local audio does not delete the meeting, notes, transcript or summary.
What the summary covers
Recap: A one- to two-sentence TL;DR leads with the meeting's outcome — the decision, result or finding — with the project or product and any numbers, followed by thematic points carrying the reason, condition or caveat behind each one. Short meetings still get a TL;DR; longer meetings get longer summaries. Empty sections are omitted, and a completely empty result produces no summary.
Follow-ups and decisions: Next Steps contains verb-first commitments, not work already underway, status reports, personal FYIs or unclaimed intentions. Decisions Made contains settled outcomes reached in this meeting, not advice or decisions relayed from elsewhere. Items requiring action appear in Next Steps only, and either section can be absent.
Owners: Individual commitments identify the responsible person; group assignments use (Everyone) or the group's name, not the assigner. Unknown appears only alongside identifiable owners; otherwise owner labels are omitted. Steps are grouped by owner, chronological within each group, with unidentified owners last.
Language: By default the summary, including the Next Steps and Decisions Made headings, follows the dominant spoken language — not app language, notes or calendar context. Names, technical terms and quotations keep their transcript language and script, except identified participants use their listed names, and numbers, units and currencies stay as spoken.
Speaker names: Your own speech is named from your account profile name, including in Microsoft Teams calls, unless a saved name already exists. Other speakers need clear identity evidence; invitee lists alone are not proof of who spoke. Otherwise speakers appear by role, action or a numbered label such as Speaker 2, used only where who said or owns something matters. The summary never addresses you as "you."
Automatic speaker naming from the meeting app supports Google Meet and the native Zoom app on Mac and Windows; on Mac, Google Meet works in Chrome, Arc and Dia, including their picture-in-picture mini windows. Windows Zoom requires an English-language interface, and Windows Teams does not use this method. Uncertain identities remain anonymous.
Fix a wrong name
Rename a speaker: Renaming the speaker corrects existing summary references without regenerating.
Change the summary language
The Summary toolbar language picker lists your own languages first, plus Auto for the meeting's own summary language.
If it's your meeting: Picking a language rewrites the summary in that language; the finished summary stays editable. Choose Auto to go back to the meeting's own language.
If no spoken language was determined: The picker is still offered, and the summary shows as Auto with no language code. Switching to another language keeps the first summary, listed as Original, so you can switch back to it at any time.
If the note was shared with you: Picking a language shows you a read-only version in that language alongside the note's original summary, which is left untouched for everyone else.
Copy and export: Both use whatever summary text is on screen, so they follow the language you are currently reading.
If a version is out of date, unavailable, or you switch languages repeatedly in a short time, the toolbar explains what happened. Right-to-left languages are laid out correctly in the summary editor.
Edit, copy, and search
Edit the summary once generation finishes and the text has finished appearing. Summary edits, Notes edits and speaker names sync across devices with the rest of the meeting, and regenerating a summary does not rewrite your typed notes. If Flow shuts down with unsaved summary edits, look for Your unsaved summary is in Docs.
Copy: Copy summary in the Summary toolbar copies only the body you are reading — not the title, notes, transcript or attendees — as formatted and plain text where supported, otherwise plain text. Copied summary confirms success; a failed summary-only copy shows no error. With no text selected and focus outside the search input, Cmd+C (Mac) or Ctrl+C (Windows) copies the whole summary, including from its editor.
Search: On Summary, press Cmd+F/Ctrl+F, or / outside a text input, and enter at least 2 characters. Enter or ↓ selects the next match, Shift+Enter or ↑ the previous, Escape clears and closes search.
Copy and search need an existing summary body — they work during updates and update failures, but not before generation, after a first-generation failure, or for a too-short result.
Update after resuming a recording
If you have not edited the existing summary and the resumed portion added at least 20% more audio or 5 new minutes, Flow uploads the full recording on its own and replaces the partial transcript and summary once the new ones are ready — no click needed, and your old summary stays visible in the meantime. The generation conditions above still apply.
Flow keeps an edited summary for an explicit Update Summary click. It also waits when edits have not synced or finished saving, when it cannot confirm an unchanged original summary, or when earlier processing is still running behind the latest recording.
The notices New recording since this summary. or New audio since this summary. indicate an available update; Transcript can show New recording since this transcript. Update Summary requires a meeting recorded in Flow, cloud sync enabled and the saved recording still available; the offer disappears if the recording is gone, and deleted meetings or transcripts cannot be retried. A resume that captured no new audio closes out with no duplicate summary and no update offer, and an existing summary is kept if the meeting is processed again with only short or silent audio.
Warning: Updating replaces your summary edits, including a summary synced from another device, so review your changes first.
Click Update Summary above the meeting footer after recording stops; it is available from any tab.
Wait while the old summary remains visible but read-only.
Review the replacement summary and transcript, regenerated from all recording segments; the summary becomes editable again.
A newer update replaces an older update in progress. If an update fails, the error replaces the Update Summary offer and the previous summary stays visible and editable.
When Resume is unavailable
Resume continues the same meeting, appending new audio without overwriting the earlier live transcript; paused and resumed segments contribute to one summary. The Resume control is hidden when unavailable.
A deleted transcript or an exhausted recording allowance always blocks Resume — start a new recording instead. Missing, empty, expired or unreadable local audio blocks Resume only when the meeting has previous processing evidence, such as uploaded audio, a summary or an improved transcript. Deleted or unreadable meetings, recording locks, incomplete onboarding and organization calendar-domain restrictions can also prevent it; if another meeting is recording, declining the switch confirmation cancels the resume.
While Flow saves the preceding recording, Resume may wait briefly or be refused. If you see Still finishing the last recording. Try again in a moment., retry after saving finishes.
If a summary or transcript is missing
After any fix below, check that processing advances and the summary appears on the Summary tab. If it does not, report the meeting. Retry processing wakes a stalled upload without creating a duplicate meeting or upload; upload-notice retries are available once every 15 seconds. Automatic retries have a limit, and manual Retry allows one attempt beyond it.
Waiting for a connection
Waiting for a connection means saved local audio is waiting to upload while offline.
Restore your connection while keeping Flow open; upload resumes automatically.
Click Retry processing if the upload remains stalled after reconnecting.
If Flow shows Servers are busy. Flow will retry at {time}. or Servers are busy. Flow will retry automatically. in the Meeting Recorder window or on the Notetaker Failed. Retry row, leave Flow open; no action is needed.
Clicking Retry while offline waits for reconnecting. Signing out or switching accounts while offline cancels that pending retry.
Your network is blocking the upload
A VPN, proxy or firewall can prevent upload. Flow shows Can't reach our servers to upload this meeting. If you're on a VPN or work network, try turning it off or switching networks, then retry. A one-time notification says Can't upload your meeting. Your network may be blocking it. Your recording stays saved locally, subject to the retention and deletion limits above.
Turn off your VPN, or switch to another network.
Click Retry on the notice.
Your connection is too slow
Flow shows Your connection is too slow to upload this meeting. Your recording is saved. Retry when you're on a faster network. The notice stays available between attempts until the connection issue clears.
Move to a faster or less congested network.
Click Retry on the notice.
Storage full
For a stopped meeting, the Hub row shows Storage full. and Free up space on your computer, then retry.; the meeting window shows Your computer is out of storage. Free up space, then retry. Both offer Retry.
Free up space on your computer.
Click Retry on the meeting row or meeting window.
Generation or an update failed
We hit a snag processing your meeting offers Retry processing with an empty Summary body. We couldn't process your meeting offers no retry.
Update failed. Showing the previous summary. offers Retry only when recovery is possible, audio remains available and neither the meeting nor transcript was deleted. If it adds The full recording is no longer available to retry., no retry is offered.
Click the offered retry control, available with the error on every tab.
Report the meeting if retry fails or is unavailable.
The meeting was too short, or had no audio
Short or silent meetings can finish processing without a summary, showing The meeting was too short to summarize. With no usable audio, the toolbar can instead say No transcript or audio available for a summary. These are completed results, not errors, and offer no Generate summary or retry.
Record more spoken content, resuming the same meeting if eligible or starting a new one.
Click Update Summary if offered after resuming; sufficient new content replaces the notice with a summary.
Your computer went to sleep or switched accounts
By default, Mac sleep ends recording at the sleep boundary; saved audio, transcript and displayed end time match it. On wake, Flow finishes processing under the generation rules above and shows a recovery notice — use Resume or start a new recording to keep going. Windows does not end recordings this way.
Without automatic stopping on sleep, recording continues on wake but sleep audio is missing. Gaps of at least 5 seconds are marked Your device slept for <duration>.
Switching macOS user accounts immediately stops recording and saves it locally. Length does not trigger automatic generation: click Generate summary while audio remains, unless the existing summary is being kept for Update Summary. An already-triggered sleep stop takes priority; locking the screen or starting a screensaver is not an account switch.
A transcript is missing after a connection or saving problem
If the improved transcript is still missing after a few minutes, sign out and back in. A connection drop during a meeting does not end your recording: capture continues. At least 10 seconds of audio avoids the failed-start discard rule, but does not by itself guarantee automatic processing. Recordings where microphone audio was withheld for privacy are not recovered. A failure to start local audio saving is different: recording continues without an improved transcript and with no saving-error notification.
Note: While you are signed out, meetings waiting to upload pause; their speaker data and live transcripts stay on your device and upload shortly after you sign back in. Audio already recorded stays saved on your device.
Warning: If audio saving fails during a meeting started with live transcription and not in Offline mode, recording continues but partial local audio is discarded: only the live transcript remains, and audio absent from it is lost. A full drive produces a storage notification; other saving failures produce a general error. If the meeting started offline or had no live transcript, it stops with Recording stopped because Wispr couldn't save audio to this device. Free disk space before recording again.
Still stuck?
Report the meeting if generation cannot finish, an update fails again or content is missing. Reporting requires Notetaker cloud sync to be on; otherwise sending shows Failed to send report.
Open the meeting's row menu in the Hub.
Choose Report.
Select the matching Issue type: Missing data or stuck processing, Summary quality, Speaker labels, Notifications, Auto-stop or Other.
Describe your meeting app, device and attempted fixes in What went wrong?
Click Send feedback; both an issue type and description are required. Thanks for the feedback! confirms submission; choose Done to close it.
Note: Reports automatically include platform, app version, processing status and meeting diagnostics — transcripts, notes and title — plus available device and audio details. The meeting app's selected microphone is included only when Google Meet, Zoom or Teams was detected and its microphone picker could be read.