Consent and Recording Governance (Onboarding)
A checklist with 7 steps: Map every jurisdiction your client's participants join from before the first bot-enabled call.
By InnovaAI ResearchPublished
What are the steps?
Consent and Recording Governance (Onboarding)
- 01
Map every jurisdiction your client's participants join from before the first bot-enabled call
Two-party consent states and EU member countries treat recording differently, and a single all-hands can span four time zones. Build the list at kickoff, not after a participant objects.
- 02
Decide the default recording posture per meeting type and write it into the client's engagement terms
Internal standups, client status calls, and discovery interviews rarely warrant the same default. State which categories are recorded, which are transcribed only, and which are never captured.
- 03
Configure the assistant to announce itself audibly at join rather than relying on a silent bot
Fireflies, Otter, and Fathom all support a spoken join notice. A visible participant name plus an audible announcement gives you a defensible record that consent was requested.
- 04
Assign a named human owner for the consent log, not a shared inbox
One person reconciles who attended, who acknowledged, and which sessions were excluded. Rotating ownership is how consent records go missing during a dispute.
- 05
Set retention windows per client and enforce deletion on schedule
A 90-day default for routine status calls and a longer window only for contractual deliverables keeps storage costs and discovery exposure bounded. Document the exception approvals.
- 06
Route any client that prohibits third-party processing to an on-device option
Scrieb processes audio locally on Mac and Windows so recordings never leave the machine, and Keen Bean captures through the Mac's own audio without a bot joining the call. Both are viable when a client contract bars cloud transcription.
- 07
Reconfirm consent posture at each contract renewal and whenever a new stakeholder joins the account
Personnel changes at the client are the most common trigger for a consent gap. Add the reconfirmation to the renewal checklist so it does not depend on memory.