Two-party consent and recording a supervision session

This post is about recording supervision sessions between a supervisor and a supervisee, not therapy sessions between a clinician and a client. Client recording is a separate and higher-stakes question involving HIPAA, client privacy law, and clinical consent standards that this post does not cover. If you're asking whether you can record a client session for supervisory review, talk to your compliance officer or an attorney before you do anything else. Everything below is about the conversation you have with your own supervisor or supervisee.

Also, read this carefully: nothing here is legal advice. Recording consent law is set state by state, it changes without much warning, and how it gets enforced varies by jurisdiction. Confirm the current law in your specific state, ideally with an attorney, before you record a live session. Treat this post as orientation, not a substitute for that check.

Why this question comes up

Supervisors increasingly want a recording of a live supervision session, usually for one of three reasons: it's easier to write an accurate session note afterward, it gives a second set of ears if a competency or ethics issue comes up, or it just feels like stronger evidence than a written log if a board ever asks questions. All three reasons are reasonable. None of them override consent law.

One-party vs. all-party consent, at a high level

US states split into two rough camps for recording conversations.

One-party consent states allow a recording as long as one participant in the conversation, including the person doing the recording, agrees to it. The other party doesn't need to be asked.

All-party consent states, sometimes called two-party consent, require every participant to agree before a recording can legally happen. A supervisor recording a session without the supervisee's knowledge in one of these states isn't just an ethical problem. It can be a criminal one.

A commonly cited list of all-party consent states in current sources includes California, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania, and Washington, with a couple of states applying a split rule (for example, requiring all-party consent for phone calls but a different standard for in-person conversations, or the reverse). That split-rule detail is exactly why a static list is risky to lean on: the label "two-party consent state" doesn't always mean the same thing from one state to the next, and the list itself is not something this post is going to assert as settled fact. Confirm your own state's current rule, including whether it distinguishes phone, video, and in-person recording, before you rely on any list you read online, including this one.

The practical takeaway that doesn't change: if you supervise or are supervised in an all-party consent state, or you aren't sure whether yours is one, get explicit consent from everyone in the room before you record, every time.

Does a standard supervision contract clause cover this?

Most supervision contracts include a line somewhere about documentation: something like "sessions will be documented for compliance purposes." That line is doing real work, but it is not the same thing as consent to record audio or video.

Consent to be recorded needs to be specific enough that the person agreeing to it understands what they're agreeing to: that a recording will happen, roughly what it will be used for, how long it will be kept, and who can access it. A boilerplate clause signed once at the start of a supervision relationship, months or years before any specific session, doesn't carry that weight on its own. If recording is part of how you supervise, put it in the contract in plain language, and treat the moment before each recorded session as its own consent checkpoint, not a formality you already handled on page one.

This is also why AuditHalo's own recording flow asks both parties to actively acknowledge consent before a recording starts, rather than inferring it from a contract signed weeks earlier. A checkbox at the moment of recording is a much cleaner record of what was actually agreed to.

What happens if the supervisee says no

Sometimes they will, and that's a legitimate choice, not an obstruction. Maybe they're uncomfortable being recorded. Maybe they've had a bad experience with a recording being used against them somewhere else. Either way, in an all-party consent state their refusal ends the discussion about recording that particular session.

It does not end your documentation obligation. You still need a session record: who attended, what was covered, session type and duration, and signatures from both of you. Losing the recording doesn't mean you've lost your evidence. It means your evidence takes a different, and in most states equally acceptable, form.

What most state boards are actually checking for

Here's the detail that gets lost in the consent-law conversation: most state boards do not require an audio or video recording of a supervision session at all. Read our deep dive on documenting a supervision session and the pattern holds across very different states: what's required is a signed session record with the right metadata, not a media file.

A recording, where you can legally get one, is a nice supplement. It's almost never the artifact standing between you and a defensible record. That distinction matters more than the consent-law question itself for a lot of supervisors, because it means you're not stuck if a recording isn't possible or a supervisee opts out.

A signed evidence package as the fallback (or the default)

This is where a documentation system does more than a recording can. A sealed record that captures the date, duration, session type, topics covered, and both parties' signatures, all timestamped at the moment of signing, satisfies the same requirement a board is checking for when it asks whether a session happened and was properly documented. No audio required.

AuditHalo builds this record automatically every time a session is signed. The evidence packages behind each session are sealed with a cryptographic hash the moment both signatures land, so the record can't be quietly edited later. For sessions where recording makes sense and both parties consent, the in-app recording flow logs that consent as its own event and generates a transcript you can review and attach. For sessions where recording isn't happening, whether by choice, by state law, or because someone in the room said no, the signed evidence package stands on its own. Either way, you end up with something a board can check.

If you want to see the full range of what the platform tracks beyond a single session record, the features overview covers the rest of the compliance surface: hour totals, credential tracking, and audit readiness across your whole caseload.

The short version

Recording a live supervision session is never the only path to a defensible record, and in some states it isn't a path you can legally take without explicit, specific consent from everyone involved. Confirm your state's current law before you record anything. Build your documentation so it doesn't depend on a recording existing at all, and treat any audio or video you do capture, consensually, as a bonus, not the foundation.

Ready to see what a signed, sealed session record looks like without touching a microphone: create your AuditHalo account.