I have a client I've been working with for three years. Her client file is 47 pages. Not because I'm obsessive about documentation, because the file has earned every page.
When she comes in stuck on something, I can look back and find the moment, usually six months or a year ago, when a version of this same thing surfaced and how we worked through it. She doesn't always remember. I do. That's not magic. It's a good file.
There's a scene I kept replaying in year two of my practice. I'm about four minutes from a session. I pull up my notes from the last call and they're three bullet points and something I wrote that says "ask about the CFO thing." I have no idea what the CFO thing was. I've completely lost the thread. I'm walking into a conversation with someone who's been thinking about this all month, and I'm essentially starting from zero.
I didn't want a better note-taking app. I wanted a system that made the knowledge accumulate, stay accessible, and actually improve my coaching over time. Those are different problems.
Here's what I've figured out after three years of iterating on this.
What a client file actually is (and isn't)
A client file is not a transcript. It's not a journal. It's not session notes copied into a folder and called a system.
It's a living document that holds everything you know about a client in a form that you can actually use. The operative word is "use." Information you can't retrieve under pressure before a session isn't information, it's just storage.
The question I kept asking myself when I was designing this: if I were handing this client off to a trusted colleague, what would they need to know to walk in and not lose ground with this person? That mental exercise surfaced what actually belongs in the file and what doesn't.
I keep my client files in Notion because I've been there for years and I'm not moving. But the structure I'm about to describe works in any text format. A plain markdown file. A Google Doc. A Notes file on your phone if that's where your life is. The structure is the thing, not the container.
The five sections
Every file I maintain has exactly five sections. That's not a constraint I imposed, it's what remained after I stripped out everything that sounded like it should be there but never got used.
Background and goals
This is the foundation, and a lot of it comes directly from my intake form. The presenting issue. The original goals. Relevant context about their role, their organization, their life situation. What they said they wanted when we started working together.
It also has a "working goals" subsection that I update as the engagement evolves, because the goals people start with are almost never the goals that end up mattering. Keeping both lets me see the gap, which is often where the real work lives.
Session log
One entry per session, in reverse chronological order so the most recent is always at the top. Each entry is short: date, main theme of the session, one or two things that surfaced, and any commitments or next steps the client named.
I don't write the session notes here. That's a separate document with its own structure and its own workflow. What the session log captures is the thread, the bare-bones narrative of the engagement so I can scroll through and see the arc at a glance.
If you want to understand how the session log connects to the notes themselves, I wrote about that workflow here.
Pattern tracker
This is the section that takes the longest to get right and does the most work once it does.
Every client has patterns. The recurring theme they keep bumping into from different angles. The type of situation that reliably derails them. The way they respond to authority, or to uncertainty, or to success. The thing they say they've addressed that keeps resurfacing in a new costume.
When I notice a pattern, I write it down here. Just a few sentences. Sometimes a question the pattern raises. Over the course of six months, a client's pattern tracker starts to look like a character study, the kind of thing that would take a therapist two years to develop but that I can actually see because I've been paying attention.
I'll say more about this section and AI in a minute, because this is where the combination gets genuinely useful.
Open loops
Things I'm tracking that aren't resolved. A conversation they were going to have. A decision they were sitting with. Something they mentioned in passing that I want to return to. A hypothesis I'm holding about what's underneath something.
Open loops are different from session commitments. Commitments are things the client said they'd do. Open loops are things I'm paying attention to that the client may not even know I'm tracking.
When something from the open loops list gets resolved, I don't delete it. I move it to the session log entry where it closed out. The history of what you were tracking and how it resolved is part of the record.
Direct quotes
This is the section coaches undervalue most and regret not having.
When a client says something that cuts to the heart of something, I write it down exactly as they said it. Not paraphrased, not cleaned up. The exact words.
"I'm not afraid of failing. I'm afraid of failing in front of people who expect me to know what I'm doing."
"Every time I say yes to this person, I'm saying no to myself, and I keep doing it anyway."
These moments are irreplaceable. The client usually doesn't remember saying them. You can quote it back months later and watch them sit with what they said when they were less defended about it. That's not a technique. It's just having paid attention and written it down.
---
Here's the template, ready to copy:
# Client File: [Name or Code] **Engagement start:** [Date] **Format:** [Frequency, session length] **Presenting issue:** [In their words, if possible] --- ## Background and Goals ### Initial goals [What they said they wanted when we started] ### Working goals [How goals have evolved] ### Context [Role, organization, relevant life situation, anything that shapes the work] --- ## Session Log ### [Date] — [Theme] [2-3 sentences: what we worked on, what surfaced] Commitments: [what they said they'd do] --- ## Pattern Tracker [Patterns you've noticed, with approximate first-observed date] [Questions these patterns raise] --- ## Open Loops - [Thing being tracked] — [date noted] --- ## Direct Quotes > "[Exact words]" — [approximate date, context]
How AI makes pattern-tracking feasible
Maintaining a pattern tracker manually is doable for a client you see weekly. For 12 clients, it starts to feel like a part-time job.
What I've started doing is a quarterly review where I paste the pattern tracker, the session log, and any notable quotes into Margaret and ask her what she's seeing. The prompt I use:
Here is everything I've tracked about a client over the past [X] months. Read through it and tell me: 1. What patterns are you seeing that I may not have named yet? 2. Are there any patterns I've named that look like they might be the same thing in different forms? 3. What questions does this raise about what might be underneath the surface? 4. What thread would you want to pull on if you were walking into the next session? This is executive coaching, not therapy. Think in terms of professional identity, leadership behavior, and relationship dynamics. Not clinical diagnosis. [Paste session log, pattern tracker, quotes]
The output is not a diagnosis and I don't treat it as one. It's more like talking to a smart colleague who's read the chart. Sometimes she surfaces something I'd been circling around but hadn't named. Sometimes I read it and think "no, that's off," which is also useful because it makes me articulate why.
This is the section of the workflow that made the biggest difference to the quality of my coaching, not the time savings. Seeing a client's arc through a different lens every few months keeps me from getting too locked into my own interpretation of who they are.
The 10 minutes after
Every piece of this system falls apart if the update habit is hard.
I update client files immediately after the session. Not the next morning. Not before the next session. Right after, while I'm on my walk and the conversation is still live in my body.
The walk is where I figure out what actually happened in the session, which is often different from what I thought was happening while I was in it. By the time I'm back at my desk, I know what to write. It takes about 10 minutes per file entry when I'm current. It takes 45 minutes and a lot of invented memory when I let it go cold.
I'm not saying you have to walk. I'm saying the window between session and notes matters. The longer it is, the more you lose and the more you'll just make up to fill the gaps.
The update workflow also connects directly to how I prepare for sessions. When a file is well-maintained, prep takes 15 minutes. When it's not, prep is a kind of archaeological excavation, and I often give up halfway through and walk in underprepared. I wrote about how the prep workflow uses the client file here.
Starting a file for a client you've had for a year
This is the question I get most often, and it has a simple answer: don't backfill the whole thing.
Start with what you know right now. What's the current working goal? What patterns have you noticed? What's in the open loops? What quotes can you remember?
Write that. It takes 20 minutes.
Then, every time you walk out of a session and add an entry to the log, if something surfaces that connects to something earlier, add it to the pattern tracker then. The file builds forward. You don't reconstruct the past, you capture the present and let it accumulate.
The temptation is to feel like the file is incomplete because it doesn't go back to session one. It is incomplete. So is your memory. Start from where you are.
---
The 47-page file I mentioned at the start: I didn't build it by being methodical about documentation. I built it one session entry at a time, across three years, because I knew this client deserved someone who showed up knowing what had happened before. The file made that possible.
That's what it's for. Not completeness. Not compliance. Showing up as someone who's been paying attention.