Recording a meeting is easy. Recording in a way that preserves trust is harder. Scriba gives you excellent capture and transcription; it doesn't replace the social work of telling people what's happening and why. The best teams treat consent as part of the agenda, not a footnote after someone asks awkward questions.
Start with disclosure
At the top of the call, say you're recording and what the recording is for. Notes for yourself, a summary for the team, an archive for compliance — each purpose lands differently. A ten-second preamble prevents a ten-minute repair conversation later. Write it into your meeting template if you run the same sync every week.
- Name the tool: 'I'm using Scriba on my Mac to transcribe this.'
- Offer an out: 'Happy to turn it off if anyone prefers.'
- Repeat when someone new joins mid-call.
- Confirm in chat for async participants who missed the verbal notice.
Know your jurisdiction
Consent laws vary. Some regions require all-party consent; others allow one-party recording if you're a participant. HR, legal, and healthcare contexts often have policies stricter than the law. Cross-border calls compound the problem — the strictest reasonable standard usually wins. When in doubt, ask counsel. Scriba is a tool, not legal advice.
Ethical recording isn't about hiding the recorder. It's about aligning capture with what everyone in the room reasonably expects.
Built-in consent tracking
Scriba logs recording session consents in your local database so you have an audit trail per session. It's not a substitute for verbal agreement, but it helps teams that need to show a pattern of practice — especially when recordings feed summaries shared asynchronously. Pair the log with a consistent spoken script and you have both human courtesy and a paper trail.
Sharing after the call
Before you paste a transcript into Slack or email a summary to a client, consider who spoke and what they expected. Trim sensitive sections. Redact names when quotes go outside the room. Use project-level sharing inside Scriba when the audience is the working team, not the entire company. A searchable archive is powerful; treat exports like forwarding someone else's words.
When not to record
Some conversations shouldn't be captured at all — venting sessions, preliminary legal strategy, health disclosures someone shared in confidence, or early brainstorming where people censor themselves on mic. The best etiquette is sometimes leaving Scriba paused. You'll remember the human moment; you don't need a searchable transcript of it.
Team norms that stick
Document which meeting types your org records by default and which require explicit opt-in. Rotate the duty of reading the disclosure so it isn't always the most junior person in the room. Review recordings the way you'd review shared drives: if you wouldn't forward the audio, don't forward the summary. Consent isn't a checkbox; it's a habit that scales when the whole team practices it.