Recording, transcripts, and highlights
Recording preserves interviews, meetings, and field discussions. The workflow includes recording, submission, processing, review, and reuse. Stopping the microphone does not mean the material has been delivered to the team.
1. Check consent and destination
Obtain appropriate consent and check microphone access, battery, and storage destination. Use a date and topic to make the recording recognizable later.
2. Record and submit
Start recording before the interview. Use pause and resume for breaks. Check completeness before submission and monitor upload and processing. Retain the local original during poor connectivity until the upload result is confirmed.
3. Review the transcript in details
Check names, numbers, and specialist terms against the audio. Request highlights through the available action when absent. A completed label does not guarantee that every tab already contains an output.
4. Use highlights and the meeting document
Highlights help locate material. Check the original before quoting it formally. Have a person supply missing owners or deadlines. Confirm the destination when adding meeting notes to knowledge for later retrieval.
5. Check before handoff
Verify playback, transcript readability, accurate summaries, contextual quotations, and team access. Submit the recording or notes to a task, or use the assistant for the next draft.
Connect audio, transcript, summary, and actions
Audio retains sound, transcripts support detailed reading, summaries provide orientation, and actions suggest continuation. Each layer condenses the original, so check conditions, tone, and unresolved points as you move downstream.
Verify the transcript
Start with names, figures, dates, and decisions. Replay surrounding context for uncertain wording. Overlapping speakers or noise may require confirmation from participants; do not guess identities or commitments.
| View | Use | Check |
|---|---|---|
| Summary | Understand main points | Missing limitations or dissent |
| Chapters | Locate topics | Appropriate topic boundaries |
| Quotations | Find possible excerpts | Meaning, context, permission |
| Actions | Prepare follow-up | Actual owners and deadlines |
Turn actions into tasks
If an item says to confirm the venue next week, verify that it was agreed and has an owner. Keep missing details pending, then use task controls for real assignment or delivery. An action in a summary is not proof of assignment.
Verify saved records
Retain source, topic, and scope. Check knowledge destination after saving. For task delivery, determine whether requirements call for audio, transcript, summary, or several items.