Flownote resourcesAI meeting notes
How to Use an AI Note Taker for In-Person Meetings
Published Reviewed
By Flownote Editorial1 source checked
Flownote resourcesAI meeting notes
Published Reviewed
By Flownote Editorial1 source checked
Short answer
For an in-person meeting, place a consented phone or computer centrally, reduce room noise, select the correct microphone, keep the device powered, and capture the conversation. Afterward, review speaker labels, names, decisions, and tasks before sharing a recap.
Online meeting audio arrives as a relatively direct signal. In a room, one microphone must hear people at different distances while handling air conditioning, keyboard noise, side conversations, and echo. Placement matters as much as the transcription software.
The best setup is deliberately boring: one stable device near the center, a clear announcement, a short audio test, and a backup note of the decisions that matter most.
Use a supported phone or computer with enough battery and storage for the full meeting.
Keep the microphone uncovered and away from laptop fans, projectors, coffee cups, and people typing.
Explain that the meeting will be transcribed and summarized, who will receive the result, and what happens if someone opts out.
Ask people at the nearest and farthest seats to speak, then confirm that the audio level is usable.
Say decisions and owners clearly: “Decision: we will use option B. Ana owns the revised timeline.”
Correct speaker labels and ambiguous passages. Do not treat automatic identification as definitive.
Overlapping speech and distant voices can make speaker segmentation uncertain. A reviewer should resolve important attributions from context or ask the group rather than guessing.
| Meeting | Useful output | Review closely |
|---|---|---|
| 1:1 | Topics, commitments, follow-up questions | Sensitive personal details and agreed confidentiality |
| Team sync | Updates, blockers, decisions, owners | Similar names and rapid handoffs |
| Client update | Progress, decisions, risks, next steps | Commercial commitments and dates |
| Interview | Themes, evidence, follow-up questions | Consent, access, and hiring-policy requirements |
| Workshop | Ideas grouped by theme plus final choices | Distinguishing proposals from decisions |
Flownote provides purpose-built output styles for several of these conversations. Select the closest style before or after capture, then edit the result into the shared record your team actually needs.
If a participant declines, the topic is unusually sensitive, or policy is unclear, stop the recording workflow. Assign a human note taker to capture only decisions, actions, owners, due dates, and open questions. Send that short recap for confirmation.
| Room | Placement | Main risk | Practical adjustment |
|---|---|---|---|
| Two to four people | Center of the table, close to normal speaking distance | Table vibration and an obstructed microphone | Use a stable surface and keep cases, paper, and cups away from the microphone |
| Five to eight people | Near the center rather than beside the note taker | Distant or quiet speakers | Run a test from every side and repeat decisions clearly |
| Large conference room | Use the organization’s approved room-audio path when compatible | Echo and uneven coverage | Test the full system or use manual notes if reliable capture is not possible |
| Workshop with people moving | Near the main discussion area | Side conversations and changing distance | Pause for report-backs and state final decisions at the center |
| Hybrid room | Capture the room and remote audio through a tested, approved setup | Echo, duplicated audio, or one audience missing | Avoid improvised dual-speaker setups and test both directions |
These are starting points, not guarantees. Room acoustics, device hardware, cases, microphone direction, and the meeting’s format all affect the result. A 30-second test with the actual setup is more informative than a specification sheet.
Use the conference room’s normal microphone and speaker path instead of several nearby laptops producing feedback.
Ask someone at the farthest seat to speak and confirm the remote participant can hear them.
Ask the remote participant to speak and confirm their voice is audible in the room and in the recording path.
A facilitator can identify a person before a decision or report-back, which makes later attribution easier.
End with decisions, owners, and deadlines so both audiences hear the same record.
These practices help manual note takers too. AI can organize clearer input, but it cannot reliably infer a decision the room never made or an owner the group never named.
If you discover a problem during the meeting, pause capture and fix it only if doing so will not derail the conversation. Otherwise, switch to a named human note taker and record the minimum operational facts.
Copy and edit
Meeting objective — [Why the group met]
Confirmed decision — [Decision, including any conditions]
Action — [Person] will [deliverable] by [agreed date]
Open question — [Question] | Owner: [person]
Missing context — [What the failed recording did not preserve]
Confirmation — [Who reviewed the recovery note and when]
Send the recovery note soon and ask attendees to correct it. Do not describe it as a transcript or imply that uncertain speaker attribution has been verified.
Put the guide to work
Flownote captures online and in-person conversations, then gives you a transcript and structured record to review before you share or act on it.
Place it on a stable surface near the center of the group, away from fans, typing, and other noise. Test the farthest participant before starting.
Not always. Distance, similar voices, interruptions, and background noise can make labels uncertain. Review important attributions manually.
Do not record them. Use manual notes or another approach approved by everyone and consistent with your organization’s policy.
Use one tested room-audio system, confirm that room and remote voices both reach the recording path, avoid feedback-producing duplicate speakers, and read back decisions at the end.
Switch to manual notes, capture confirmed decisions and actions, label missing context, and send a correction-friendly recap. Do not invent exact wording or speaker attribution.
Try Flownote with your next meeting. It's free to get started.