How to Turn a Meeting Recording Into Verified Minutes With AI

Start with the transcript from your meeting platform, or transcribe the recording with a tool your team allows. You will need the recording, its transcript, the meeting date, and any agenda or attendee list you have. The Project Harbor example below shows how to turn these sources into a readable set of minutes.

For a short team meeting, one document containing the decisions, an action table, and unanswered questions is enough to start. Add a timestamp beside each outcome, replay the relevant discussion, and ask participants to resolve the unanswered questions. The separate file lists, correction logs, and chunk-by-chunk review below help when a meeting is longer or more difficult; you do not need a spreadsheet for every step.

What counts as verified minutes

For this workflow, verification means that the decisions, assigned work, deadlines, amounts, conditions, and unresolved questions in the minutes have been compared with their source passages. The document also identifies gaps that still need a participant's answer. This is a working definition for preparing a review draft; use your organization's own rules for approving official minutes.

A transcript records speech. Minutes record the meeting's outcomes and the context needed to understand them. Keep the transcript as a separate reference so the minutes can stay readable without losing the path back to the discussion. A reader should be able to find the relevant passage when they question an owner, a date, or whether the group actually agreed.

Label the document “Draft for participant review.” Checking it against the recording establishes what was said; approval establishes whether it is an acceptable record under the team's process. If someone disputes a decision or commitment, mark that item as disputed until the designated reviewer resolves it.

Choose a transcription route for the recording you have

Start with the transcript already available in your approved meeting system. Preserve its original export before correcting it. If you have only an audio or video file, choose a transcription route that can return timestamps and that your organization permits for this material.

In Teams, open the past meeting chat, select Recap, then Transcript, and use the menu beside Download to choose DOCX or VTT. Organizers and co-organizers can download by default; other access depends on policy. Microsoft documents these steps in its transcript guide. Keep VTT when you need its time references for replay.

Zoom's cloud-recording audio transcription produces a separate VTT file with timestamped sections. Its documentation says that this feature supports English and applies to cloud recordings, so a locally saved recording does not automatically have that transcript. Check the cloud transcription requirements before relying on it. Other Zoom transcription features have their own requirements.

Before processing a real meeting, confirm permission to record and the approved uses of its contents. Record the intended reviewers and recipients, where the recording and transcript will be stored, and who handles retention. Follow the applicable rules and your organization's process, including its treatment of late joiners. When permission is unresolved, use authorized notes while the responsible person resolves it.

Check where your chosen tool stores the audio and transcript and who can access them. A local tool leaves files on your computer; a cloud service has its own storage and sharing settings. If you remove sensitive passages before an allowed use, note the missing coverage in the restricted review copy.

Give the AI the transcript and the meeting context

In the AI assistant your team permits, attach the transcript if it supports that file type, or paste the timestamped text. If it cannot open VTT, copy the VTT's text and time ranges into the message. Keep the original file. Uploading an audio file is useful only when the selected tool supports transcribing it; a file attachment alone does not establish that the assistant has heard the recording.

Provide the meeting date and timezone as context, and label the agenda and attendee list separately. State whether the transcript covers the whole recording. Then run the prompts below one at a time: inspect the transcript, extract outcomes, review them, draft the minutes, and compare the draft with the sources. Correct the result before moving to the next stage. If the assistant loses access to the earlier transcript, supply it again with the reviewed table.

Meeting date and timezone: [Known value, or not confirmed]
Recording: [Filename and available duration]
Transcript coverage: [Whole recording, or the available time ranges]
Agenda and attendee list: [Attach or paste separately, if available]
Transcript: [Attach the supported file or paste the timestamped text]

Use the transcript for what was said. The agenda describes planned topics;
the attendee list does not prove who spoke or accepted a task.

1. Preserve the sources and check coverage

Keep the original recording, original transcript export, agenda, and attendance information together in a restricted source folder. Work on copies. Give the recording a stable filename and record the meeting's date, timezone, and any known gaps. A timezone matters when a deadline depends on the participants' locations; a recording filename alone may not establish the meeting's date.

Play the beginning, a middle section, and the ending before drafting. Check that you have the intended meeting and audio track. Look for a transcript that stops early, starts after the opening discussion, or omits a stretch that is audible in the recording. These spot checks establish a starting inventory. To claim that the whole recording was checked, someone needs to listen through it against the transcript.

Keep pauses and missing sections distinguishable. A silent recording segment and a failed transcript segment require different recovery: the first may need another source, while the second can be retranscribed. If you have two recording files, establish their order and whether they overlap before joining their transcripts.

If you have several files, list each filename, the part of the meeting it covers, and any known problem. Use the agenda to find intended topics, then check what happened in the conversation. Mark an agenda item that was not discussed. When the group agrees to change the original plan, record the change and the passage where it was accepted.

2. Make the transcript useful for replay

Retain timestamps when you transcribe or export. TXT is convenient for reading, but it may lose the time references needed for checking a disputed sentence. Preserve VTT, SRT, or a structured export alongside it when available. Add stable source IDs to your working transcript without changing the original export.

For each passage you will cite, retain its start and end time, speaker label, text, and any uncertainty. A short ID is useful if several minutes refer to the same passage. Correct an audible word in the working copy and note the change. Use “inaudible,” “overlapping speech,” or “speaker not identified” when you cannot establish the missing detail.

If the transcript has no timestamps, add time ranges yourself while replaying the relevant passages. Use the player's elapsed time and record the filename beside it. Do not ask AI to estimate when a sentence occurred. If you have only a transcript and cannot access the audio, describe the result as checked against that transcript; leave possible transcription errors for participant confirmation.

Speaker separation, often called diarization, identifies different voices. Attaching a participant's name is another check. Compare labels with an introduction, a confirmed turn, or participant review. A guest name or a shared room microphone may identify an account or location without identifying the person speaking. If the identity is uncertain, preserve a stable anonymous label and leave the owner unresolved.

The Project Harbor example uses IDs M-01 through M-10 in a manually prepared reference transcript. Those IDs help compare claims with the example's script. For your own recording, add actual time ranges from its transcription output. Asking a text model to invent plausible timestamps would destroy the value of the references.

Organize the supplied transcript into a table.
Columns: Passage ID, Start time, End time, Speaker, Text, Unclear details.
Keep supplied timestamps and speaker labels. If a time or identity is
missing, write "not confirmed"; do not invent it.
Preserve unclear words and overlapping speech. Do not summarize,
create decisions, or assign action owners.
List gaps in the supplied transcript. Do not claim to have checked audio
that has not been provided or that you cannot process.

Keep long recordings in order

If the complete transcript will not fit comfortably in the tool, divide it at agenda transitions or speaker-turn boundaries. Make each portion short enough to review against its audio. Give every portion a chunk ID and preserve its original start time. Include the neighboring turns when a sentence or decision crosses a boundary, and label those repeated turns so they are counted once.

Extract the possible decisions, actions, conditions, and open questions from each chunk before merging. Keep the supporting passage for every item. During the merge, compare repeated items, later corrections, and the closing recap. Summarizing summaries alone can leave you without the wording needed to resolve a conflict.

If a tool resets timestamps within each chunk, add the chunk's starting offset when locating a passage in the full recording. For example, in an illustrative chunk beginning at 00:30:00, a local timestamp of 00:05:12 corresponds to 00:35:12 in the full file. Keep both times in the review table. Verify the mapping at a recognizable spoken turn before using it throughout.

3. Check the details that change the meaning

Make a review list before asking for the minutes. Include participant names, project codes, amounts and units, quantities, dates, owners, decisions, exclusions, and conditions. Pay particular attention to words such as not, until, unless, and only. Replay the surrounding turns as well as the sentence containing the field; acceptance or correction may follow it.

Use a glossary of known names and terms to find likely transcription errors. A glossary can help establish spelling after the audio has been checked. It cannot establish that a listed person spoke, accepted work, or attended the meeting.

For a disputed or consequential correction, note the original wording, corrected wording, source passage, and who checked it. A comment in the document can serve this purpose for a short meeting; a separate log helps when several reviewers are making changes. In the fictional example, “four hundred eighty dollars” can be written as $480, but the minutes must also retain that it is a budget cap.

Resolve relative dates only when the source supports a single interpretation. Knowing the meeting date does not always settle what a speaker meant by “next Friday.” Preserve that phrase, note the possible ambiguity, and ask the owner to confirm. If you resolve a date during participant review, record the confirmation as a later source.

When the audio and agenda differ, inspect the discussion for an explicit change. Record a clearly agreed change with its source. If the conflict is unexplained, flag it. The agenda is useful context, but treating it as the answer can erase a decision made during the meeting.

4. Extract outcomes before writing the minutes

Ask AI to list the proposed outcomes with their supporting passages before writing the minutes. This makes ownership and agreement easier to inspect. Separate decisions, actions, proposals, constraints, and open questions so that a suggestion does not appear as agreed work.

In Project Harbor, Theo proposes reducing the original 20-user idea to 12 consenting adult volunteers in M-02. Ava states the group decision and beta date in M-03; Mira confirms them in M-04. The adopted count is 12. The 20-user idea remains relevant as a proposal that was superseded, so the minutes should identify its status instead of presenting two competing approved counts.

Ownership needs its own evidence. M-05 contains Theo's commitment to draft the invitation email. M-08 explicitly declines ownership of the accessibility review. Mentioning a task or offering to answer questions does not establish acceptance. If your organization permits a chair to assign work directly, record that explicit assignment and its source; do not convert it into a claim that the person volunteered.

Use the corrected transcript as the source for what happened.
Use the agenda and glossary only as labeled context.
Extract possible decisions, actions, proposals, conditions,
open questions, and material disagreements.
For each row include:
Type | Outcome | Owner | Date and what it means | Condition |
Supporting passage ID, time range, and words | What needs confirmation.
Separate discussion from agreement. Include the passage establishing
acceptance or an explicit assignment. Preserve later corrections.
Distinguish action deadlines from scheduled events and dates of approval.
Write "not confirmed" for unsupported owners, dates, or identities.
Do not invent timestamps.
Do not infer approval from silence, expertise, availability, or a recap
that conflicts with the earlier discussion.

Check the results against both the agenda and the transcript. Each agenda topic should have a traceable outcome, an unresolved status, or a note that it was not discussed. Also scan for off-agenda decisions and commitments. Counting extracted rows cannot establish that the extraction is complete.

5. Draft minutes that a participant can check

Use the reviewed outcome table to write a short meeting record with a separate action table. Include the meeting's identity and date, attendance where established, decisions, essential context, open questions, and review status. Put source IDs or time ranges beside the outcomes. The reader should not need to decode the entire transcript to find the origin of a deadline.

Choose the detail according to the meeting. A routine project check-in may need a compact decision list and action register. A contentious planning meeting may need the alternatives considered, the reason for the adopted option, material objections, and unresolved conditions. For formal minutes, use the organization's template and approval procedure, including any required attendance or vote records. Fill those fields only from supported sources.

Omit greetings, repeated arguments, and side conversations that do not affect an outcome. Retain the reason for a decision when it explains the choice, and record an objection when it affects approval, scope, or the work someone has committed to do. A concise record can group related conditions under one decision without turning every sentence into a separate task.

The following action register comes from the fictional Project Harbor transcript. It separates work that people accepted from items whose owners remain unknown. The dates belong to the practice meeting, not to your project.

Put the condition beside the action it affects. Theo can draft the email while sending remains blocked. A single status such as “in progress” would hide that distinction. Write “owner not confirmed” beside an unassigned item so the reviewer knows what needs an answer. The original practice CSV uses UNKNOWN for these missing values.

Draft meeting minutes from the reviewed outcome table.
Include meeting details, decisions and necessary context, actions,
open questions, and material disagreements.
Attach source IDs and supplied time ranges to each outcome.
Retain conditions, exclusions, superseded proposals, and unconfirmed details.
Keep drafting an item separate from approval or permission to send it.
Use the organization's template if supplied.
Label the result "Draft for participant review."
Do not create facts to fill empty template fields.

A complete example of the review minutes

This readable version uses the fictional transcript's facts and the action table above. Its passage IDs refer to the practice transcript; add actual recording time ranges when preparing your own minutes.

6. Audit accuracy and omissions separately

Compare the draft with the corrected transcript and replay the passages that establish each outcome. An AI review can help locate possible problems, but the reviewer still needs the underlying sources. Starting a fresh conversation or using a different model does not establish that the result is independent or correct.

Check in both directions. First, start with each minute entry and find support for its wording, owner, date, amount, and conditions. Then start with the source discussion and check that its decisions, commitments, unresolved issues, and meaningful objections appear in the minutes. The second pass catches omissions that an otherwise accurate draft can hide.

Compare these draft minutes with the corrected transcript and outcome table.
Pass 1: For each decision, action, date, amount, condition, and attributed
statement, locate source support. Flag unsupported or contradictory wording.
Pass 2: Walk through the transcript's outcomes and identify anything material
missing from the draft. Check earlier proposals against later changes.
Return one row per issue:
draft_item_or_missing_topic | issue | source_IDs | exact_source_excerpt |
consequence | minimum_supported_correction | human_replay_needed.
Keep unconfirmed details unresolved; do not fill them by inference.
If the supplied source is incomplete, state the missing coverage.
Do not mark the minutes approved or sent.

Replay the full exchange around a decision, including the response. A sentence proposing a date may be followed by an objection and a different accepted date. For ownership, find the commitment or explicit assignment itself. For a condition, check whether later discussion changed it or merely repeated the planned action.

Correct only what the evidence supports. If two participants disagree about what was decided, give the designated reviewer the disputed wording and relevant time ranges. Record the question, who will resolve it, and whether it prevents approval. Revise the item after that person has resolved the disagreement.

Handle the problems a real meeting introduces

Overlapping speech and uncertain speakers

Mark the exact span where voices overlap and replay it with the turns before and after. If separate participant tracks are available through your permitted recording route, review those tracks. Keep their time alignment with the main file. Avoid assigning an action solely because the transcript places a name next to unclear speech.

If the words are audible but the speaker is uncertain, retain the words under an anonymous label and ask who spoke. If the speaker is known but the commitment is inaudible, keep ownership unconfirmed. These are different missing facts. Ask the participant a focused question about the action or decision; do not ask them to approve an invented sentence.

Noisy audio and repeated or invented transcript text

Keep the original audio when you prepare a cleaned copy or retranscribe a difficult passage. Compare the new text with the original recording around names, numbers, and negations. Clearer playback is useful, but an edited audio file still needs a source comparison before you accept a changed word.

When text appears during silence, repeats unrelated phrases, or stops matching the conversation, mark the span and inspect the audio. Retranscribe that section if speech is present. If no intelligible source remains, record the gap and seek authorized notes or participant clarification. Do not ask the model to finish the missing sentence from context.

Two languages or a translated transcript

Keep the original-language transcript beside the translation, with shared source IDs. Check critical decisions and commitments with someone who understands the original language. Preserve names, product terms, units, and dates across both versions. Specify which version participants will approve and who resolves a disagreement between the translation and the original.

Check that transcription used the intended spoken language before drafting. A multilingual meeting may need separate review of the passages where languages change. Translate the reviewed content for the intended audience after the source checks. If reviewers cannot assess a consequential passage in its original language, leave it unresolved and arrange a qualified review.

Conditional commitments and changed decisions

Capture the trigger for a conditional action, its owner, and the dependent work. Project Harbor's invitation draft has a deadline, but sending has an approval condition. Keeping both in the action record prevents a completed draft from appearing to authorize distribution.

For a changed decision, retain the relevant earlier proposal and the passage that supersedes it. Check whether the later statement was actually accepted. A closing recap is useful for comparison, but a recap that contradicts the discussion needs confirmation. Do not use whichever statement occurs last as an automatic rule for resolving disagreement.

If an action is withdrawn later in the meeting, keep the cancellation with its supporting passage and mark the item canceled. Check that the cancellation concerns the same deliverable and owner. Repeated mentions of one commitment should become one action, while a later cancellation should not disappear during the merge.

A meeting ends before agreement is clear

Mark the topic as unresolved and retain the options or question that remain open. Avoid phrases such as “the team agreed” when the source contains only suggestions. Record any supported next step, such as seeking an owner or bringing the topic back for a decision. Leave the follow-up owner unknown if none was established.

If you lack the final portion of the recording, state its missing coverage in the review draft. A participant's later account can help resolve the gap, but identify that account as a later confirmation. It cannot establish that the available audio contained a decision it never recorded.

A participant changes a deadline or commitment afterward

Separate a correction of the record from a new agreement. If the recording shows that the draft misheard a date, correct the minutes and log the source. If someone agrees to a new date after the meeting, preserve the original decision and record the later change with its own confirmation date and source.

Maintain the action register accordingly. An action can have a meeting deadline and a revised deadline, but the register should identify which is current and why. This prevents a reader from assuming that a later concession was part of the original agreement.

A client copy needs less detail than the internal record

Prepare the internal review copy first, with the evidence needed to resolve disputes. Then create a version for the authorized external audience. Remove restricted discussion according to the organization's sharing process while retaining the obligations and conditions relevant to that recipient. Check that removing context has not changed a decision's meaning.

Keep both versions identifiable. An external reader may not have access to the recording, so put the necessary operational conditions in the minutes themselves. Use source references for internal review without exposing a restricted recording through a public link.

7. Review with participants and export the agreed version

Give reviewers specific questions alongside the draft. Ask whether the decision entries describe agreement, whether owners accepted the listed work, whether dates and conditions are correct, and whether any material objection or outcome is missing. Attach the disputed source time ranges so reviewers can check the relevant exchange.

Track each response against the version reviewed. Silence should remain a missing response unless the team's established process explicitly treats it otherwise. Where a designated chair or reviewer approves the minutes, record that approval under the applicable process. Agreement by every attendee is not a substitute for a required approval procedure.

Export an editable document for corrections and, if useful, a PDF for a stable reading copy. Export the action register as CSV when it will be imported into another system. Open the actual exported files. Check that the last action is present, conditions remain attached, unknown values are visible, source references survive, and long table rows are readable.

After participant changes, create a new version and check the affected entries against the corresponding sources or later confirmations. Keep the approved version, approval record, and recipient list together. If a file hash is useful for identifying the exact version, record it at this point. A matching hash establishes file identity; it does not establish the accuracy or approval of its contents.

Once minutes are accepted, the meeting-notes-to-action-items guide covers preparing the action register for follow-up. Keep evidence for the underlying decisions accessible to the authorized reviewers when moving tasks into a project system.

Practice with the Project Harbor meeting

Project Harbor is a fictional three-speaker planning meeting with about 89 seconds of synthetic audio. Its names, budget, dates, and commitments are practice material. The reference transcript was prepared from the scripted example. The exercise helps you recognize ownership and approval errors; it does not measure performance on long, noisy, or multilingual meetings.

Use the practice WAV alongside the raw transcription and reference transcript. Compare the example DOCX and action register with the sources. The complete practice kit contains the original exports, correction ledger, run record, and demonstration script.

Check M-05 and M-08 first. M-05 establishes Theo's invitation-drafting commitment and the condition preventing invitations from being sent. M-08 says he did not accept accessibility ownership. The correct register therefore keeps accessibility ownership unknown and keeps invitation sending blocked until consent copy approval.

For an optional practice audit, make a separate copy labeled PRACTICE WITH DELIBERATE ERRORS. Change the accessibility owner to Theo and change the sending condition from “approved” to “drafted.” Compare that copy with M-05, M-08, and M-09. A useful review identifies both unsupported changes and points to their source passages. Keep this exercise separate from a real meeting's review draft.

What the example script actually checks

The optional Python checker examines selected file properties and known values in this practice packet. Its 14 checks and eight deliberately changed test copies demonstrate those specific checks. It cannot determine whether a real meeting's decisions or tasks are complete, and replacing the WAV does not adapt it to another meeting. Compare every expected action with the transcript even when the checker reports a pass.

To inspect the demonstration after extracting the practice kit, run:

mkdir meeting-minutes-review-kit
unzip meeting-minutes-review-kit.zip -d meeting-minutes-review-kit
cd meeting-minutes-review-kit
python3 meeting-minutes-evidence-gate.py

The script writes a JSON results file into the extracted directory. Its status means the example is ready for participant review. It does not approve or send the minutes.

Optional local transcription on an Apple-silicon Mac

The practice example used mlx-whisper 0.4.3 with mlx-community/whisper-base-mlx. The MLX Whisper instructions describe FFmpeg setup, model selection, and timestamp options; the pinned package is available on PyPI. Install Python and FFmpeg before running the commands below. The model may need to download on the first run.

python3 -m venv .meeting-asr-env
.meeting-asr-env/bin/python -m pip install "mlx-whisper==0.4.3"

whisper_cli=".meeting-asr-env/bin/mlx_whisper"
model_id="mlx-community/whisper-base-mlx"
"$whisper_cli" project-harbor-synthetic-meeting.wav \
  --language en \
  --output-name project-harbor-base \
  --word-timestamps True \
  --model "$model_id" \
  --output-format all \
  --output-dir asr \
  --verbose False

For this command, expect TXT, VTT, SRT, TSV, and JSON outputs under asr/. Preserve them before editing. Use .meeting-asr-env/bin/mlx_whisper -h to inspect options if your installation differs. These instructions are for the English practice WAV; choose an appropriate language configuration and review route for your own recording.

This command produces a transcription. Establish participant identities and commitments through the source checks above. For a video with multiple audio tracks, inspect the intended track before transcription; the local video transcription guide explains that preparation in more detail.

Use this template for your next review draft

Copy the structure below into your team's editor and replace the placeholders from checked sources. Keep unknown fields visible until the responsible reviewer resolves them. Use the organization's required template when it has additional fields.

Meeting title:
Meeting date and timezone:
Recording ID and available coverage:
Participants confirmed by:
Minute version:
Status: Draft for participant review

DECISIONS
ID | decision and necessary context | conditions/exclusions |
source IDs and time ranges | review status

ACTIONS
ID | action | owner | due date | dependency or sending condition |
source IDs and time ranges | status

OPEN QUESTIONS AND DISAGREEMENTS
ID | unresolved point | relevant sources | confirmation needed |
person responsible for resolving it, if established

REVIEW RECORD
Reviewer | version reviewed | correction or confirmation | date |
remaining issue

APPROVAL AND DISTRIBUTION RECORD
Approved version | authorized approver | approval date |
authorized recipients | distribution date, when sent

Before requesting approval, check that every recorded outcome has a source, that the source discussion has been checked for omissions, and that disputed owners, dates, and conditions remain visible. Send the designated reviewer the draft version and the specific unresolved questions. Record approval against that exact version before the authorized person distributes it.