Recording conversations at work: writing a policy

Two gates, not one

The most common confusion is treating legality and policy as the same question. They are separate, and both apply.

The first gate is law: state and federal statutes govern recording private communications, and they vary. The second is the organisation's own rule, which can be stricter than the law — an employer in a one-party state may still prohibit recording internal meetings, and that prohibition can be enforceable as an employment matter even where the recording itself would not be unlawful.

A policy that only says follow the law has not done its job, because it leaves every employee to work out fourteen statutes on their own. A policy that only says never record has usually not thought about the field technician who narrates job notes.

What a policy usually has to address

The list below is what tends to come up. It is not a template and it is not advice — a policy should be written with counsel who knows your jurisdictions and your industry's rules.

• Scope: internal meetings, client conversations, calls, in-person, video, and whether personal devices are covered differently from issued ones.
• Whether disclosure or consent is required, and from whom, in states where the law does not require it.
• Who owns and can access recordings made in the course of work, and where they are stored.
• Retention and deletion — how long recordings are kept and who decides.
• Legitimate work uses that should be permitted rather than accidentally banned: field notes, inspection narration, shift handovers, accessibility accommodations.
• Jurisdictions where the organisation operates, and how the rule changes across them.
• What happens when a recording is requested in litigation or by a regulator.

Where device choice matters

Two properties tend to decide whether a policy can permit a tool at all.

The first is whether it can record without anyone knowing. An always-on wearable or a background application creates a category of question a policy has to handle: what else was captured, for how long, and who could know. A device that records only while a button is physically held does not create that category — chit has no wake word and no always-on microphone, so a capture is a deliberate, visible act with a beginning and an end.

The second is where the data goes. For most organisations the blocking question is not whether people take notes, it is whether the audio of internal conversations leaves the environment. chit's enterprise deployments keep captures, transcripts and digests resident in your own VPC rather than ours, which is usually the answer that makes a policy writable. See hichit.com/enterprise.