Skip to content

What AI should never touch in coaching

On this page

Automate the admin, keep the coaching human. Every coach who thinks about this for a minute arrives at that shape, and the instinct behind it is sound. Software touches a practice in five separate ways, though. It reads. It keeps what it read. It forms judgments. It writes. It sends. The boundary sits in a different place for each of those. Set one permission for all five and you end up careful in four places and wide open in the fifth.

  • The verb matters more than the tool. You’d happily let some software read your whole mailbox and never let it send a word. Other software can send confirmations all day and should keep no record of what a client told you.
  • The material to hold back is narrower and stranger than “client information.” It’s mostly things that were never yours to hand over in the first place.
  • The expensive boundary is memory. A summary is a record, coaching has no privilege behind it, and automation quietly manufactures records of conversations that used to leave no trace.
  • Some of what gets called a never belongs on your yes list. Saying so is part of having a list you’ll actually keep.

Five verbs hiding inside one question

Start with the definition, because the professional body has one and it’s broader than most coaches expect. The ICF Code of Ethics is marked “Board approved October 2024” and “Revised May 2026” (checked September 6, 2026). Its appendix defines artificial intelligence as “any algorithm or machine-based technology that enables computers and other digital devices to simulate human intelligence and problem-solving skills.” The 2025 Core Competencies glossary goes further. Under technology it calls out “AI systems that facilitate goal tracking, communication, and progress monitoring.”

Read those honestly and “do you use AI in your practice” stops being a yes or no question. Your scheduling tool sorts. Your inbox ranks. Your video platform captions. You’re already inside the definition, and you’re fine. What’s left to decide is which of five things a given piece of software gets to do.

Read. What material it sees at all.

Keep. What it writes down, what it infers, and how long any of that lives.

Judge. Which calls it makes, and which ones stay yours whether or not it could make them well.

Write. What it composes with your name on top.

Send. What leaves without you having looked.

Those five come apart cleanly in practice. A tool can be entirely safe to read a thread and entirely wrong to keep a summary of it. It can be right to draft the message and wrong to send it. Most of the worry in this subject goes into arguing about the tool when the argument is about one verb. Most of the real exposure comes from a verb nobody checked.

The rest of this works through them in order. Then it names three things that get called nevers and belong on your yes list.

Material that was never yours to hand over

Everything in a coaching mailbox is sensitive, so sensitivity sorts nothing. The useful question is whose permission you’d need. That splits the mailbox into piles quickly.

Almost everything a client writes you is yours to handle as you see fit, within what you told them in the agreement. Three piles sit outside that.

What a third party gave you about your client. In a corporate engagement, the Code defines a sponsor as “the entity (including its representatives) or individual paying for and/or arranging or defining the coaching services to be provided.” Sponsors supply things. A 360 report. An assessment. A scope document that describes an employee’s performance problem in writing. An HR contact’s account of why the coaching was bought. That material arrived under the sponsor’s terms, and often under the sponsor’s own vendor rules, which increasingly name what systems may hold data about their employees. It reached you from somebody other than the person it describes, so your client’s agreement with you says nothing about where it goes. If it lives in the mailbox at all, it should live somewhere you’ve checked against the contract you signed with the organization. An attachment otherwise lands wherever the mail client puts it, and that’s a decision made by default.

Anything that has entered the disclosure categories. Standard 2.3 asks you to have a clear agreement about “what confidential information may need to be disclosed to the appropriate authorities, e.g., illegal activity, required by law, valid court order or subpoena; or imminent/likely risk of danger to self or to others.” Once a thread crosses into one of those, other people are going to read it, on a timetable somebody else sets. That’s the moment to stop making copies of it. Move the conversation somewhere you’ve chosen on purpose. A litigation hold treats an automatic copy exactly like one you made by hand.

Mail about a client that is not from the client. This is the pile people forget, and in a small practice it’s a real one. A spouse who writes to you. A colleague of the client’s who has views. Your own correspondence with a coach supervisor, which is about a named person and belongs to you rather than to them. The agreement your client signed covers what your client sends. Your client sent none of this, and sometimes doesn’t know it exists.

The principle underneath is settled, and this guide takes it as given. Your obligations reach through whatever you use, and the Code says so in as many words, about software and about the people you hire. Handing coaching admin to AI and staying yourself works through the standards that establish it.

One thing is worth adding here, which is the place where the comparison to a human assistant runs out. The Code treats support personnel and technology alike, and for most purposes that’s the right instinct. An assistant forgets, though. Software remembers, and it indexes. Ask an assistant, two years later, for everything they ever saw about one client and you’ll get part of it, slowly. Ask the software and you’ll have all of it in under a second. The comparison holds for the read verb. It stops at the next one.

A summary is a record, and nothing privileged sits behind it

This is the section that changes decisions, and it’s the one most coaches meet for the first time here.

Start with the protection your files actually have. In Jaffee v. Redmond, 518 U.S. 1, decided June 13, 1996, the Supreme Court recognized a federal psychotherapist-patient privilege. It held that “The conversations between Redmond and her therapist and the notes taken during their counseling sessions are protected from compelled disclosure under Rule 501.” It extended that to “confidential communications made to licensed social workers in the course of psychotherapy.” The privilege is drawn around licensure. Coaching in the United States is not a licensed profession, there is no coach-client privilege, and nothing in Jaffee reaches your files.

So the honest picture is this. What a client tells you is protected by your ethics, your contract and your care. That’s the whole list. In a contested divorce, an employment claim, a dispute between a coachee and the sponsor who paid for the coaching, or a subpoena aimed at somebody else entirely, your records are ordinary discoverable documents. Coaches are frequently surprised by this. They’ve absorbed the therapy frame, which arrives without the licensure that holds it up.

Now put automation next to that fact. Software running your mailbox changes how many records exist. Who can compel them stays exactly the same. Three kinds appear that weren’t there before:

  • Summaries. A conversation used to exist as a thread. Now it also exists as a two-line account of what the thread was about, in plain declarative prose, written by something with no sense of what is going to look bad in a year.
  • An inferred profile. Standing preferences, learned habits, notes about how a particular client likes to be handled. One at a time, these are settings. Together they’re a written description of a person’s manner, kept by you.
  • Logs. What you were told, when it arrived, and what was done about it, with timestamps. Excellent for running a practice. Also a timeline somebody else could read.

Every one of those is useful, which is exactly the problem. Nobody sets out to build a file on a client. You turn on summaries because forty threads read faster that way, and the file is a side effect.

Hold this against the Code’s records standard. Standard 2.4 asks you to “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.” The word people skip is dispose. A retention policy for a solo practice can be short. It does need an answer for anything a system generates about a client. Can you delete it? Does deleting it delete it everywhere? Does anything build it back afterward?

And one working rule transfers here whole. It’s old, and it belongs to lawyers rather than coaches. Do not put anything into a system that you would not want read aloud with the client in the room. The room is unlikely to happen. The point is that a record that would embarrass you there is a record you never needed to create.

The judgments that are the job

The judge verb is where the boundary rests on principle rather than practice. Software makes some of these calls tolerably well. They stop being coaching the moment something other than you makes them.

Whether this is coaching at all. Sub-competency 1.07 asks you to refer “clients to other support professionals, as appropriate.” That call rests on things that live outside the email. A ranking system reads the message correctly and files it wrong. Picture a client who writes, between sessions, that they haven’t been sleeping and can’t really see the point of the job question anymore. Every classifier on earth reads that as a low-urgency personal note. On the words, it’s right. You know better, and what you know sits outside the mailbox.

Whether somebody is at risk. The same shape, and here the mistake stays made. Assume every system is blind to this one and work accordingly. In practice that means you go on reading everything a client sends, long after you’ve handed over the writing.

Whether the engagement is working. Standard 4.3 asks you to “Remain alert to indications that there might be a shift in the value received from the coaching relationship and discuss this with the client.” Software can tell you a client’s replies got shorter and slower. A client who got busy and a client who is finished produce identical data. The difference is yours to read.

The pattern. Sub-competency 6.06 asks a coach to notice “trends in the client’s behaviors and emotions across sessions to discern themes and patterns.” This one deserves a second look, because pattern-finding is what automation does best. Being handed a pattern and having noticed one are two different things. The noticing is where your attention sat for six weeks. A summary that hands you the theme on a plate has taken the six weeks out, and the six weeks were the instrument.

There’s a fifth that sits slightly apart, because it belongs to the client’s work rather than yours. Sub-competency 2.01 has the coach acknowledge “that clients are responsible for their own choices,” and 8.03 has you support “client autonomy in the design of goals, actions and methods of accountability.” Feed a client’s situation into a general model, send back the plan that comes out, and you’ve failed both. The plan might be good. Authorship has moved to something that will walk away from the consequences. That’s the difference between coaching and advice with a coaching accent, and keeping your voice when AI drafts your email replies works through how it shows up sentence by sentence in ordinary correspondence.

What must not go out with your name on top

Which of your client emails can start from a draft is a practical question with a practical answer, and the guide above owns it. Two categories are different in kind. They belong here.

Anything to a third party about a client. The progress update to the sponsor. The note to an HR contact about how the engagement is going. A reference. Anything that ends up in an employee’s file. In these messages, and only these, your assessment of a person becomes a document held by somebody with power over them. The Code’s own definition of confidentiality draws the line at exactly this point. It protects information from 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.” Written consent. Compose every sponsor communication yourself, deliberately, knowing what you agreed to say and what you agreed to hold back. A drafted first pass saves a few minutes and costs far more than that.

Anything that ends something or moves money. Terminating an engagement. A refund. A referral out. The message declining to renew. These get read four times, kept, and occasionally forwarded. Be the first careful reader of a message other people will read that carefully.

Then the send rule. If you keep one line from all of this, keep this one:

Nothing goes to a client on a thread you have not personally read.

Read, rather than answered. That difference is what makes the whole arrangement survivable. Reading a day of mail takes minutes when every thread opens with a line telling you what it is. Answering a day of mail takes your evening. Automation takes the answering and leaves you the reading. A boundary that says “review important replies” hands you the sorting instead, and it collapses on a Thursday with four sessions in it.

The session itself

Most coaches feel this question hardest about the hour rather than the inbox, so it’s worth being clear about here, even though it sits outside what an email tool does. The question is whether to put an AI notetaker in a coaching session.

The legal part genuinely depends on where everybody is sitting. Federal law is permissive to a participant. Under 18 U.S.C. 2511(2)(d), it is “not unlawful under this chapter for a person not acting under color of law to intercept a wire, oral, or electronic communication where such person is a party to the communication or where one of the parties to the communication has given prior consent,” absent a criminal or tortious purpose. Several states are stricter, and they bind you rather than the platform. California Penal Code section 632 makes it an offense for a person to intentionally record a confidential communication “without the consent of all parties.” The fine runs to $2,500 per violation. The statute defines a confidential communication as one carried on in circumstances indicating that any party “desires it to be confined to the parties thereto.” A coaching session is that, by construction. Work remotely and you’ll often be guessing which state your client is in this week, which makes asking every time the rule that scales.

The coaching half matters more, and it stands up whatever the law says. Competency 4 asks you to partner with the client “to create a safe, supportive environment that allows the client to share freely.” A client who knows the hour is being transcribed shares differently, and they’re right to. The material worth the session fee is mostly the material somebody would rather keep off the page. There’s a smaller irony worth noticing too. A transcript renders silence as nothing, so the best ten minutes of a session arrive in your notes as a gap.

Recording can be the right call. Make it a consent decision with the client, in the agreement and again in the room, rather than a default you switch on. And if you want the transcript because what was said between sessions keeps going missing, the cheaper fix is usually a written commitment you make at the end of the hour.

Three that get called nevers and are not

A list of prohibitions works only when it’s short enough to remember, so it pays to be equally clear about what stays off it. These three come up constantly, and all three are safe.

Times. Your authenticity lives somewhere other than a calendar slot. Proposing, confirming, moving and reminding make the largest pile in a coaching mailbox. It’s also the one kind of message where an instant reply reads as honest rather than as a giveaway. Booking links that show what you are genuinely free for removes most of it, and catching a reschedule request buried in a reply covers the harder half.

Reading your own mail with help. A summary written for you, of a message addressed to you, is you reading your mail faster. Nobody else is in the room. This one lands on never lists through a category error, and that’s an expensive place to put it. Keeping it off the list is what makes the rest affordable, because a plain summary of every email before you open it is precisely the mechanic that lets a coach go on reading everything after handing over the replying.

The answer you have written two hundred times. What the discovery call involves. The cancellation policy. Where the reading is. What a package costs. Prepared for you and sent by you, that beats the version you’d have written at 9:40 at night.

Where Point’s line actually sits

Point runs on the mailbox you already keep, Gmail or Microsoft 365, so your mail stays where it is and there’s nothing to migrate. Here’s where each of the five verbs sits.

Read. Move a conversation onto a channel locked end to end and it stays between the two people in it, where Point has no way to read it. The cost is real and worth stating: a locked thread gets no summary, no ranking and no draft. Save it for the conversation that needs it. Mail from senders Point doesn’t recognize is held at the door instead of being read into anything. And isolation works between separate businesses you operate, because the ranking inside one practice depends on seeing all of it. Keeping one business isolated from another sets out what that boundary does cover.

Keep. What Point has learned about how you work lives as ordinary sentences. You read down the list, change a line, delete a line. That’s the surface where the record question gets answered in practice, and seeing what an AI learned about you is about reading it back. Each action taken on your behalf is written down with the time and the reading behind it. That’s the activity log, and most entries can be turned back from there.

Judge. Ranking tells you what looks consequential and orders your day around it. The client whose messages got shorter might be busy or might be done, and ranking leaves that one with you. Name the clients you’ve committed hours to and what they send stays visible. That’s a standing instruction from you, and it stays yours to change.

Write and send. You set how far Point goes per kind of action, one row at a time. Each row runs from suggest-only, through preparing the work and waiting for you, to handling that kind of work outright. A new account starts every action type in the middle. Against everything above, the mapping is plain. Times and filing are the rows worth raising. Anything a client will read as a personal message from you is the row that should sit in the middle far longer than feels necessary. The dial’s own page sets out what each position reaches. A message that has already gone out is sitting on somebody else’s server, here or anywhere, and it stays there. That’s the limit on undo, and it’s why the sending row moves slowest of all.

One more thing, since the section above raises it. Point works on email and stays there. Your calls and your sessions run without Point in the room. The recording decision is yours to make with your client and your video platform.

The full inventory lists everything Point handles, and the coaching page walks the same ground one week at a time.

What a list of nevers will not do for you

Three honest limits, because a list that promises more than this gets dropped by the second busy week.

It won’t tell you the moment. Boundaries are categorical and failures are situational, and the ones that hurt look like ordinary Tuesdays. The client’s real sentence sits at the bottom of a scheduling email, in the same font as the rest.

It needs to be short to survive a busy week. Five lines you can recite beat a policy document you wrote once. If you take three things from this, take the send rule, the disposal question, and writing every sponsor message about a client yourself.

And it sits apart from your disclosure policy. What you tell clients about any of this is a separate decision with separate reasoning behind it. Whether it belongs in the agreement or in a conversation, and what to say when somebody asks you outright, belongs there too. That one goes to whether AI is okay for a coaching business at all.

Common questions

Does the ICF Code of Ethics prohibit using AI in coaching?

No. The Code defines artificial intelligence in its appendix and then folds it into your existing obligations, alongside databases, platforms and the people you hire. You seek no permission and follow no special procedure. What the standards give you is a set of specific duties that reach through the software, most usefully the records standard at 2.4 and the disclosure agreement at 2.3.

Is what my coaching clients tell me legally privileged?

Not in the way therapy is. The federal psychotherapist-patient privilege recognized in Jaffee v. Redmond in 1996 is drawn around licensed clinicians, and the Supreme Court extended it to licensed social workers on the reasoning that their treatment was equivalent. Coaching is not a licensed profession in the United States and has no equivalent privilege. Your contract, your ethics and your practices protect your records. Past that they’re ordinary documents, and that’s the strongest reason to be deliberate about what a system writes down.

Can I use an AI notetaker in coaching sessions?

Yes, with consent, and ask for it out loud rather than through a banner on a screen. Federal law under 18 U.S.C. 2511(2)(d) generally permits a participant to record. A number of states require every party to consent, and California’s statute is the well-known example, with penalties attached. Coach clients in other states and you’ll often be guessing which rule applies. The professional argument is the stronger one anyway. A client who knows they’re being transcribed shares differently, and what they hold back is usually the part worth the hour.

Is my coaching practice covered by HIPAA?

Almost certainly not. HIPAA covers health plans, clearinghouses and health care providers who submit standard transactions such as claims electronically, plus the business associates who handle protected health information for them. A business coach sits outside all of those, even when clients discuss stress, burnout or health. So HIPAA is the wrong place to look. The obligations that actually govern you are the Code, your coaching agreement and, in a corporate engagement, whatever the sponsor’s contract says.

Can I send a progress update to the sponsor who is paying?

Send what you agreed with the client you’d send, and settle the shape of it before the first session rather than when the first request arrives. The Code’s confidentiality definition treats written consent from the client as the thing that releases information. Whatever you do agree to, write those particular messages yourself. That’s the one email where your judgment of a person becomes a document somebody with authority over them keeps.

What if a client replies to an automated message with something serious?

Assume it will happen, because clients put the real sentence at the end of the administrative one. Two things protect you, and both are plumbing rather than model settings. The reply path from any automated message has to reach somewhere you actually look. An action taken on a thread has to leave the thread in your view. Handle the booking, keep the message.

If I keep only one rule, which one?

Nothing goes to a client on a thread you have not read. It’s the cheapest of the five verbs to hold. It fails loudly rather than quietly when you stop holding it. And it keeps you in contact with the thing the rest of this is trying to protect.

The short version

Touching is five different acts, so the line sits in five places. Reading is the permissive one, with three narrow exceptions. Material a third party gave you about your client under their terms. Anything that has crossed into the disclosure categories. Mail about a client from somebody who is not the client. Keeping is where the real exposure lives, because summaries, learned profiles and logs are records, coaching has no privilege behind it, and your answer to standard 2.4 has to include disposal. Judging is where the principle is sharpest. The referral, the risk, whether the work is still working, and the pattern you were supposed to notice yourself. Writing has two absolutes: the sponsor communication, and anything that ends something. Sending has one rule that carries the others. Nothing reaches a client on a thread you have not read.

Here’s the test a year from now. Take the file you’ve accumulated on each client and picture reading it out loud with them sitting there. Then picture the week a client quietly stopped being all right, and ask whether you were still the one who noticed. Those two, rather than whether your inbox got faster or whether anything embarrassing was sent.

Ready for a calmer inbox?

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.

Private beta

What you're joining

It runs on the mail you have

Point sits on top of Gmail or Outlook. Your address, your history and your contacts stay exactly as they are, so there is nothing to migrate.

You set how much Point does

Out of the box everything waits for your review, replies included. You hand over only what you trust, one kind of work at a time.

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.