A practical workflow for recording an in-person meeting, checking speaker labels, and turning the audio into notes and actions you can verify.
To record an in-person meeting, put one device near the middle of the table, confirm that everyone knows it is recording, and check the speaker labels before you trust the transcript. A phone can be a practical starting point; whether it works in your room depends on distance, noise, and a short playback test. Capturing audio does not establish owners, dates, or the difference between a suggestion and a commitment. Those need a separate check before the notes become agreed work.
Choose the device before the room
Start with the session you need to capture. Will everyone sit around one table? Will people move to a whiteboard? Does the person recording need their phone for another task? Decide these things before choosing a phone or a dedicated recorder. Neither device can compensate for a microphone that is too far from the person speaking.
For a small discussion, try the phone you already carry. Check available storage, battery, microphone permission, and the recording app's session limits. For a longer meeting or a room where you need your phone free, consider a separate recorder. Check how its files can be exported and whether your transcription workflow accepts that format. Extra hardware adds a transfer step; it does not guarantee that every seat will be audible.
In CoHear, the workflow starts with recording on an iPhone or Android phone, or importing existing audio. The recording can become a transcript and follow-on materials such as a summary, slides, an infographic, a report, or a study plan. Keep the original audio available for checking those outputs.
how the capture routes compare
dedicated recorder vs the phone you already own
Place the device for the voices you need
Put the microphone where the important voices can reach it. Near the middle of a table is a useful starting position, but test it rather than treating it as a rule. Ask someone in the farthest seat to say a sentence at their normal volume. Play it back before the discussion starts. A recording-level indicator moving on screen does not establish that the words are understandable.
Keep the device away from a fan, an air-conditioning outlet, a vibrating laptop, or papers that will be shuffled. Avoid placing it against a wall or covering its microphone. Ask people to leave it still once the meeting begins: tapping the table or moving a case can become part of the recording.
If someone moves to a whiteboard, ask them to describe what they draw and repeat their conclusion near the microphone. When distant speech is unclear, pause and adjust the setup with everyone's knowledge. Do not assume software can reconstruct words the device did not capture.
Confirm consent before you press record
Check the rules that apply to your location and your employer before recording. Requirements vary, and this checklist is not legal advice. Explain why you want a recording, who will receive it, and where the audio and notes will be kept. Confirm any restrictions on confidential material, access, and deletion through the appropriate workplace process.
A practical opening is: “I'd like to record this discussion so I can check the notes afterward. The recording will be available to the people we agree on. Is everyone comfortable with that?” Give people a real opportunity to respond before starting. A late arrival should receive the same explanation.
If someone objects, stop and agree on an acceptable alternative, such as written notes. If the conversation moves into a restricted topic, pause the recording before that discussion. Recording discreetly is not a substitute for meeting the applicable requirements or respecting the agreement in the room.
consent rules for recording a meeting
Capture the context in the first minute
Once recording is agreed, say the meeting name, date, and purpose aloud. Ask participants to introduce themselves briefly if that is appropriate. These spoken references help a reviewer connect voices, names, and the meeting record. They do not guarantee that automatic speaker labels will be correct.
Keep a short written note of unusual names, project terms, and documents mentioned. Say enough to distinguish “the draft proposal” from an approved decision. When someone refers to “this number” or “that slide,” ask them to state the relevant value or conclusion aloud. Audio alone does not capture a screen or recover a presentation that nobody describes.
If the meeting is interrupted, note the pause and resumption. For a long session, check that recording is still active at a natural break. Follow the app's documented limits; do not assume a paid plan means an unlimited session. Save the recording before starting another task on the device.
Check speaker labels before you trust the transcript
Treat a speaker label as a suggestion until you have checked the voice. Similar voices, overlapping speech, and people speaking from different positions can make labels unreliable. An incorrect label can turn a reasonable transcript into an incorrect claim about who accepted a task.
Spend a focused five-minute review on passages that matter. Choose a moment when each participant introduces themselves, a passage involving two similar voices, and a passage where someone makes a commitment. Listen to the original audio while reading. Check that the label stays consistent when the same person speaks again.
CoHear supports tapping a transcript sentence to jump to that point in the audio. Use that source check before attributing a statement. If you still cannot identify the speaker, mark the attribution as unconfirmed and ask a participant. Do not replace uncertainty with the name that seems most likely. Keep uncertain statements out of a person's confirmed action list.
Turn the audio into notes you can verify
Separate decisions, suggestions, and accepted commitments before organizing the notes. “We could ask procurement” is a proposal; it does not establish that anyone will contact procurement. A summary should preserve that distinction even when a shorter sentence would sound more decisive.
For each proposed action, record five fields: the task, owner, explicit date, dependency, and source quote or timestamp. Use “not stated” when an owner or date is missing. Use “needs confirmation” when the statement is ambiguous. A date inferred from the next meeting is still an inference, not an agreed deadline.
CoHear can organize a conversation into notes covering points, decisions, risks, actions, and open questions. Review those notes against the recording before distributing them. Keep a source reference beside important claims, and resolve uncertainty with the people involved. For a detailed extraction workflow, continue with the action-items guide rather than asking a second summary to fill gaps in the first.
turning a recording into action items
A ten-minute check before you send anything
Use ten minutes as a review structure, not a promise that every meeting can be checked that quickly. Start with decisions and actions that could change someone's work. Find the sentence supporting each one. Confirm the speaker, listen to the surrounding exchange, and check whether a later comment changed the agreement.
Then review owners, dates, and dependencies. Keep unresolved fields visible. Check any figures or names that were difficult to hear against the relevant document or participant. If the source does not support a statement, remove it or label it as an open question.
Copy this confirmation message when sharing the draft: “Please check the decisions and actions below. Have I attributed your commitments correctly? Items marked not stated or needs confirmation are still open. Please confirm an owner or date rather than treating the suggested fields as agreed.”
Share the recording only with the agreed audience. Put confirmed work into your team's usual task system, and retain or delete the audio according to the policy you checked before recording.