AI Tools, Session Recordings, and Client Consent: What the ICF Code of Ethics Actually Requires

Quick answer. The ICF Code of Ethics (in effect since April 1, 2025) never uses the word "recording," and its only operative mention of consent sits in a definition. What it does do is bind you through five standards at once: co-create the agreement before coaching begins (1.1), keep the strictest confidentiality (2.1), agree explicitly on what information goes where (2.2), store and dispose of records — "including electronic files" — securely and lawfully (2.4), and, in a brand-new standard, fulfill your ethical obligations "through any technology systems I may utilize (i.e. technology-assisted coaching tools, databases, platforms, software, and artificial intelligence)" (2.5). Put together: you can use AI tools on session content, but only with informed, written client consent, a clear story about where the data goes, and secure storage. For credentialing recordings, ICF is more direct — written permission before you record is mandatory, and submitting without it "is a violation of the ICF Code of Ethics."

The debate has been loud this month. A widely shared post from a prominent voice in executive-coaching research argued that coaching with confidential content is no longer ethical "if there are more intelligences listening in" — passers-by, colleagues, or AI agents — and drew dozens of replies from working coaches. Some agreed and want AI-free rooms written into ethics codes. Others pushed back: their clients ask for AI read-backs and session insights, and see no problem when it's contracted upfront. In between sat the practical questions this article answers: What does the ICF code actually require? Does an AI note-taker that "doesn't share data" change anything? What exactly do I put in my coaching agreement?

The anxiety isn't hypothetical, and it isn't limited to coaching. In adjacent professions, practitioners who dug into popular AI scribe tools found that session audio often passes through three or four vendors before a note comes back, and that "we don't train AI on your data" can quietly mean "we don't train on data that still contains identifiers." Clients, for their part, post consent forms they've been handed and ask strangers whether signing is safe. If your clients haven't asked you yet what your tools do with their words, they will.

This article lays out what ICF actually says — in the Code of Ethics, in its AI Coaching Framework, and in the credentialing rules — plus the legal backdrop and a concrete consent checklist. It matters double if you record sessions for ACC/PCC credentialing or are preparing for the 2027 shift to mentor-observed assessment, because 2027 doesn't remove recordings from the process — it moves them.

Important disclaimer. Mentor Coaching AI is not affiliated with or endorsed by the International Coaching Federation, and nothing here is legal advice. This article summarizes the publicly available ICF Code of Ethics, the ICF AI Coaching Framework and Standards, and ICF credentialing pages. Rules change and jurisdictions differ — verify against coachingfederation.org and local law before relying on any of it.

Is it still ethical to use AI tools in coaching at all?

ICF's answer, on the plain text of its own documents, is: yes, conditionally — the obligations travel with the technology rather than forbidding it.

The revised ICF Code of Ethics took effect on April 1, 2025 (the currently published document carries a May 2026 revision note). Among its changes is a standard that didn't exist in the 2020 Code, and ICF's own "Overview of Changes" flags it as brand new. Standard 2.5 commits every ICF professional to:

"Fulfill my ethical and legal obligations to my coaching client(s), sponsor(s), colleagues, and to the public at large directly and through any technology systems I may utilize (i.e. technology-assisted coaching tools, databases, platforms, software, and artificial intelligence)."

The Code's appendix even defines artificial intelligence — "any algorithm or machine-based technology that enables computers and other digital devices to simulate human intelligence and problem-solving skills" — and points the definition back at Standard 2.5.

A code that intended to ban AI from the coaching room would not define it and assign it an obligations standard. What 2.5 does instead is close a loophole: you cannot outsource confidentiality to a tool and disclaim what the tool does. If the transcription service leaks, retains, or repurposes your client's words, that is your ethical problem.

So the honest framing of the current debate is not "AI: yes or no?" but "can you meet your existing obligations through this particular tool, and has your client genuinely agreed?" For some clients and some engagements — high-sensitivity executive work, for instance — the answer may still be no, and several voices in the debate make a strong case that an AI-free room is itself something clients should be able to choose. That choice is exactly what a proper consent process gives them.

What does the ICF Code of Ethics actually say about recording and consent?

Something surprising: almost nothing by name — and that's worth understanding precisely, because coaches on both sides of the debate misquote it.

No standard in the Code uses the word "recording." No operative standard uses the word "consent." The duty most coaches assume is written somewhere as "get consent before recording" is actually assembled from five pieces:

• Standard 1.1 — before coaching begins, "co-create a coaching agreement regarding roles, responsibilities, confidentiality, financial arrangements, and other aspects of the coaching engagement." A tool that captures session content is plainly an "aspect of the engagement."
• Standard 2.1 — "Maintain the strictest level of confidentiality with all parties involved, regardless of the role I am fulfilling."
• Standard 2.2 — "Have a clear agreement about what information is exchanged and how it is exchanged among all parties involved." An AI vendor processing your transcript is an exchange of information.
• Standard 2.4 — "Maintain, store, and dispose of any records, including electronic files and communications, in a manner that promotes confidentiality, security, and privacy, and complies with applicable laws and agreements."
• Standard 2.5 — the technology-systems standard quoted above.

The word "consent" appears in the Code's definition of confidentiality: protection of information obtained in or around the coaching relationship "unless there is a legal reason or requirement, a threat of harm, or written consent to release is given by the client." Note the adjective — the release valve ICF's own definition contemplates is written consent, not a nod at the top of a call.

Two practical consequences. First, "the Code doesn't mention AI note-takers, so I'm fine" was never a defensible reading, and since April 2025 it's explicitly wrong. Second, "the Code forbids AI" is equally unsupported — what it forbids is confidentiality you can't actually guarantee and agreements your client never made.

What consent does ICF require when I record for credentialing or mentor coaching?

Here ICF stops deriving and starts stating. For performance-evaluation recordings, the ICF credentialing pages are unambiguous:

"Before recording a client, you must receive their written permission to use the recorded session for performance evaluation purposes."

ICF offers a sample Release of Confidential Information form for exactly this, and warns that submitting a recording without client permission "is a violation of the ICF Code of Ethics and may result in the denial of an ICF credential and/or other disciplinary actions." (The mechanics — audio-only, 20–60 minutes, verbatim transcript — are covered in our recording and transcript guide.)

The same written-permission logic now runs through mentor coaching. The ICF Mentor Coach Handbook (April 2026) requires the coach being mentored to:

"Request and receive written permission from one of their current coaching clients to either record a coaching session and share it with their mentor coach, or to allow the mentor coach to observe a live coaching session."

And it places a matching duty on the mentor coach, who must ensure "mentor coaching recordings and sensitive coaching client data are securely stored in compliance with the ICF Code of Ethics and local data protection regulations."

The 2027 changes make this more relevant, not less. From April 1, 2027, the performance evaluation retires for ACC and PCC Portfolio applicants, replaced by enhanced mentor coaching documented on Session Observation Forms and a cumulative Competency Review Form — which, in ICF's words, "replaces performance evaluation recordings and transcripts" in the application itself. But the recordings don't vanish; they stop going to an anonymous ICF assessor and go to your mentor coach instead, session after session, under the formative model. Client consent is still required for every one of those recordings, and the storage burden now sits explicitly and personally with the mentor coach. One thing we could not find: an ICF-published model consent wording specific to mentor-coaching recordings — the sample release form is framed around performance evaluations. Until that gap closes, adapting the release form's purpose language to name mentor coaching is the sensible move.

My client asked what the AI tool does with their words. What do I need to be able to answer?

In November 2024 ICF published the Artificial Intelligence Coaching Framework and Standards — written primarily for AI system providers, not as rules binding individual coaches. That makes it the single best due-diligence checklist a coach can hold up against any vendor. The standards a client-facing coach should care about most:

• AI disclosure (A.1.1): "The user should know when they're interacting with an algorithm and not a person."
• Data transparency (A.1.6): "All parties involved in AI coaching are concerned about where and how their data is stored, as well as who will have access to it." At the advanced tier, the provider publishes documentation of all parties with access and where data is stored.
• Consent (A.1.7, F.13.2): the system "shall obtain explicit consent from the Client for any data processing activities" — at the advanced tier through an interactive process with "granular control over their data."
• Disclosure before service (F.13.1): data-management practices must be explained "before providing Coaching Services," not buried in terms discovered later.
• Security (F.12.1, F.12.2): encryption for storage and transmission, secure sign-on.

Turn those into vendor questions and you have your answers for the client: Who transcribes the audio, and is a third-party model provider involved? Where is data stored, and in which jurisdiction? How long are recordings and transcripts retained, and can you trigger deletion? Is any content — even "de-identified" — used to train or improve models? Is there a signed data-processing agreement? A vendor that can't answer these is making promises on your license that you can't verify. That is precisely the pattern practitioners in neighboring professions keep finding: a reassuring marketing page, and a privacy policy that quietly reserves the right to retain de-identified transcripts for "product improvement."

If a tool passes, Standard 2.5 is satisfiable. If it can't answer, the Code — not caution — says don't put client content into it. (For how AI tools fit into a coach's development workflow more broadly, see our guide to AI mentor coaching technology.) EMCC members will find the same direction of travel in EMCC Global's Digital Ethics Guidelines (v1.0, July 2023) from its Digital & AI Centre for Excellence.

Is recording even legal without asking?

Ethics aside, recording law exists and differs sharply by place. Two well-established generalities (not legal advice):

In the United States, federal law and most states require the consent of only one party to a conversation — which can be you. But roughly a dozen states, California, Florida, Illinois, and Washington among them, require all parties to consent to recording private conversations. For remote sessions across state or national lines, the standard prudent assumption is that the stricter law applies. Since ICF requires written client permission for credentialing recordings anyway, the ethical bar already clears the strictest legal one — another reason to treat written consent as your default everywhere.

Under the GDPR, a coach recording an EU-based client is processing personal data — typically as the data controller, with the transcription/AI vendor as a processor. That implies a lawful basis (consent being the natural one here), data minimization ("adequate, relevant and limited to what is necessary" — do you need video, or does audio suffice?), storage limitation (delete when the purpose is served), and a written data-processing agreement with the vendor under Article 28. Coaching conversations that touch health or other special-category data raise the bar further. Consent under GDPR must also be withdrawable — which your agreement should say out loud.

What belongs in an AI/recording consent clause

Synthesizing the Code, the AI Framework, the Mentor Coach Handbook, and the legal backdrop, a consent clause or conversation that meets the bar covers:

• What is captured — audio, video, transcript — and by which named tool.
• Why — credentialing submission, mentor coaching, your own development — in words that match what actually happens.
• Who will hear or read it — mentor coach, ICF assessor, AI processor and its sub-processors.
• Where it's stored, for how long, and when it's deleted.
• Security — encryption at rest and in transit, access control.
• Whether any content is used to train or improve AI models — including "de-identified" content.
• That consent is written, given before recording starts, and withdrawable — with deletion on request.
• The limits of confidentiality ICF Standard 2.3 already requires you to agree: legal disclosure obligations and risk of harm.
• Which jurisdiction's recording law applies, especially for cross-border video sessions.

Then re-confirm verbally at the top of the recorded session. The written form is what ICF requires; the thirty-second verbal reprise is what keeps the trust. And your client's "no" — to AI specifically, or to recording at all — must be a real option that costs them nothing. That's what makes the "yes" informed. Live observation by a mentor coach, which the handbook explicitly allows as the alternative to recording, is worth keeping in your pocket for exactly this case.

Where MCAi fits

MCAi analyzes coaching-session recordings and transcripts against the ICF competency framework, which means everything in this article applies to us before it applies through us: sessions are uploaded only with the client's consent, analysis output goes to you (and, if you choose, your mentor coach) — and we're built for the GDPR reality coaches actually work in. If you're building the consent step into your workflow anyway for the 2027 mentor-observation model, a consented recording can do double duty: one for your mentor coach, and one free ICF-aligned analysis to sharpen what you bring to that hour. The confidentiality promise stays yours; the tooling just has to deserve it.

Sources

• ICF Code of Ethics (in effect April 1, 2025; rev. May 2026)
• ICF Code of Ethics — overview page
• ICF Code of Ethics — Overview of Changes
• ICF Artificial Intelligence Coaching Framework and Standards (V1.01)
• ICF — Performance Evaluations
• ICF — Release of Confidential Information form (sample)
• ICF Mentor Coach Handbook (April 2026)
• ICF — Mentor Coaching Requirement Replacing ACC & PCC Performance Evaluations
• Reporters Committee — Reporter's Recording Guide (one-party vs. all-party consent)
• GDPR Article 28 — Processor
• EMCC Global — Digital & AI Centre for Excellence