Recording Coaching Sessions for ICF Credentialing

You've finished your coaching hours, your education is done, and you sit down to assemble your ICF credential application. Then you hit the one item that isn't a number on a form: the recorded session. You scroll back through months of calls looking for one that runs the right length, with a client who consented, where the coaching was genuinely some of your best — and you realize the session you're picturing was never saved, or you can't tell which file it is anymore. The work was real. The evidence of it wasn't kept.

This post is about the half of that problem you can actually engineer away: making sure a qualifying session — and a usable transcript — is always there when it's time to submit. We'll cover what ICF asks for, why coaches get caught out, and where a reliable archive fits. (We'll also be clear about what an archive doesn't do: meeting ICF's criteria is on you, not your storage.)

What ICF actually asks for

For some credential paths, ICF's performance evaluation requires you to submit recorded coaching session(s) and a written transcript of each. The specifics depend on your credential and your application path, and they're set by ICF — so treat the summary below as orientation and confirm the current rules against ICF's own documentation before you rely on them.

As of this writing, ICF's performance evaluation requirements work roughly like this:

• How many recordings. The ACC Portfolio path calls for one recorded session with a transcript. The PCC Portfolio path and the MCC paths call for two. If your ICF-accredited education program already included a performance evaluation in its curriculum — the Level 1 and Level 2 program paths for ACC, and the Level 2 path for PCC — you may not need to submit one separately at all. Know which path you're on before you assume you need a recording.
• Session length. The recording must be a full, unedited session running between 20 and 60 minutes. A session longer than 60 minutes won't be scored, so a sprawling call doesn't count — you need one that lands inside the window from start to finish.
• The audio file. ICF accepts common audio/video formats (MP3, WMA, MP4, or M4A) as a single file, and caps the upload size (95 MB at the time of writing). A 20–60 minute audio-only export comfortably fits that budget; a full-resolution video usually doesn't, which is why the audio file is the one you want.
• The transcript. This is the part coaches underestimate. ICF asks for a verbatim (word-for-word) transcript, with the coach and client identified and placed on separate lines, timestamps at every change of speaker, in the same language as the session, submitted as a Word document (.doc or .docx). A rough auto-summary doesn't satisfy this; it has to be the real exchange, formatted ICF's way.

The headline: the requirement isn't just "have a recording." It's "have a specific kind of recording, with a specifically formatted transcript, for the right session." Which is exactly why finding it after the fact is so painful.

The practical problem: you don't know in advance which session counts

Here's the trap. You can't reliably pick your qualifying session ahead of time. The call where the coaching really sings — clean agreement, a real shift, the kind of session an assessor wants to see — isn't something you schedule. It happens, and you notice afterward. By then, if you weren't recording, it's gone.

So the only safe posture is to capture consistently: record the sessions you have consent to record, keep them all, and choose the best one when it's time to apply. That turns "did I happen to save the right call?" into "which of these saved calls is strongest?" — a much better problem to have.

The second half is retrieval. Cloud recordings are easy to lose track of. They expire under retention policies you set months ago and forgot, they get bumped when storage fills, and a folder of meetings named only by date tells you nothing about which one had the breakthrough. Doing the save-and-organize step by hand is the part that quietly breaks during a busy stretch — and a busy stretch is exactly when your best sessions tend to happen.

If you're weighing where recordings should live long-term, the comparison of Drive vs. cloud-recording storage covers the retention and cost side in detail.

How RecordFlow fits

RecordFlow does one narrow thing: the moment a Zoom cloud recording is ready, it copies the files — video, the audio-only file, the chat log, and the transcript — into a Google Drive folder you own, in a per-meeting folder named with the date and the meeting topic. Every session you record is archived automatically and stays findable, so when application time comes you're choosing from a complete set rather than hoping the right call survived.

Two pieces map directly onto the ICF requirements, with one honest caveat. The audio-only file Zoom produces is already in an accepted format and small enough to fit the upload cap, so it's the file you'd submit. Alongside the raw .vtt, RecordFlow also uploads a clean Google Doc transcript — consecutive lines from the same speaker merged into paragraphs, each prefixed with a timestamp, the speaker's name in bold (the full mechanics are in the transcript-to-Doc post). That Doc is a strong starting point: you'd open it, export to Word, and format it to ICF's exact spec — verbatim, coach and client on separate lines, a timestamp at every speaker change.

What RecordFlow does not do is hand you a finished, ICF-compliant submission. It is not affiliated with or endorsed by ICF, and it doesn't certify that a recording or transcript meets the evaluation criteria. It stores and retrieves your sessions reliably; verifying length, audio quality, verbatim accuracy, and transcript formatting — and meeting every current ICF rule — is your job as the coach.

The goal is simple: never let "I didn't keep it" be the thing standing between you and a credential you earned. Record consistently, keep every session somewhere you control, and the one you need will be there when you reach for it.