Industry Playbooks
Note-Taking Templates for Coaches — a practical, example-driven guide with honest tool comparisons and a clear place for WebSnips. Written for Coaches.
A blank note field after a coaching session produces one of two things: nothing, because you're tired and the next call is in ten minutes, or a vague summary — "explored leadership challenges" — that tells you nothing useful in session five. Note-taking templates for coaches solve the blank-field problem by giving you a structure to fill in rather than a page to compose from scratch, which is the difference between a two-minute note and a fifteen-minute one that still doesn't get written most weeks.
Templates aren't a shortcut that produces worse notes — they're what makes consistent, specific notes realistic given how little time exists between sessions. Below are five templates built for the specific documentation needs of a coaching practice, adapted from note-taking templates for coaches used across the profession, plus the reasoning behind each field.
Medicine solved this problem decades ago. The SOAP note format — Subjective, Objective, Assessment, Plan — was developed in the 1960s by physician Lawrence Weed specifically because unstructured clinical notes were inconsistent and hard to build on session to session. The format works as what researchers call a cognitive aid: it doesn't just record information, it prompts the clinician to think through a case systematically each time. A coaching note-taking template does the same job — the fields aren't paperwork, they're a prompt to notice the four or five things that actually matter about a session, every time, instead of whatever happens to come to mind first.
Client: [initials or code, not full name if stored outside secure practice system]
Session #: [n] | Date:
What happened: [main topic/theme; what emerged]
What was significant: [the pivotal moment; what landed or opened]
Client commitment: [exact words of what they agreed to try/explore]
Coach observation: [pattern noticed across sessions; what you chose to
follow or not follow, and why]
Quote worth keeping: [verbatim, if something said was particularly
revealing]
The "coach observation" and "quote" fields are the two most commonly skipped under time pressure — and the two most valuable eighteen months into an engagement, when a pattern across many sessions becomes visible only because it was written down each time it appeared. Writing the "coach observation" field in your own words, rather than leaving it blank or copying a phrase from the session, is also the kind of active retrieval that research on the testing effect associates with stronger long-term recall — the act of stating what you noticed, not just what happened, is what makes the note something you'll actually remember using.
Client: [name/code] | Engagement start:
Stated goals: [in the client's own words]
Context (from public research only): [industry, role, organizational
situation — see compliance note below]
Initial hypotheses (held loosely): [what might be below the surface —
to be tested, not assumed]
Contract check-in dates: [when to revisit whether the coaching contract
still fits the emerging work]
Client: [name/code] | Engagement: [start–end dates]
What was worked on: [themes across the engagement]
What shifted: [as the client experienced it / as you observed it]
What remains open: [for the client's own continued reflection]
What I learned as a coach: [your own professional development note]
Date: | Supervisor:
Case brought: [anonymized; what you were trying to work through]
What the supervisor observed: [that you hadn't seen yourself]
Question that opened something: [the specific question, verbatim if
possible]
What I'm taking forward: [concrete adjustment to your approach]
Pattern name: [short, memorable label]
Who shows up: [client type — anonymized, generalized]
Presenting issue: [what the client brings]
What it often masks: [the underlying dynamic]
What doesn't work: [interventions that miss the actual issue]
What works: [interventions with a track record for this pattern]
This last template is the one that converts individual client work into professional wisdom — a coach who fills it in after every third or fourth client who fits a recognizable pattern builds, over years, a reference no textbook can give them: their own evidence base.
The five templates above are a starting structure, not a rigid script — the specific fields worth adding depend on how you coach.
Group and team coaches benefit from adding a "group dynamic" field to the session note: what happened between participants, not just what any one person said, since the coaching unit is the group rather than an individual.
Health and wellness coaches often need an additional "referral/scope note" field — flagging when a client's disclosure falls outside coaching scope and into territory that needs a referral to a licensed clinician, which the ICF Code of Ethics requires coaches to recognize and act on appropriately.
Career and transition coaches frequently add a "external deadline" field to the session note — job application dates, decision deadlines — since the coaching arc is often tied tightly to a calendar the client doesn't control.
The underlying structure (what happened, what was significant, what was committed to, what the coach noticed) stays constant. The modality-specific field is the one addition worth making deliberately, rather than letting the template balloon with every possible field that might someday be relevant.
Capture using the template immediately after (or within a few hours of) the session — the specificity of "coach observation" and "quote worth keeping" decays fast, and a template filled in same-day is categorically more useful than one reconstructed a week later.
Connect pattern-library entries and framework notes into your broader knowledge base, tagged by domain and client type, separate from the confidential per-client session notes.
Create engagement summaries and supervision-ready case notes directly from the templates — because the fields you filled in during the engagement are already structured, writing the close summary is assembly, not a fresh writing task.
| Template | Where it lives | Why |
|---|---|---|
| Session note, intake, engagement close | Practice management (CoachAccountable / SimplePractice) | Confidential client record; access-controlled |
| Supervision note | Same secured system or a dedicated practice-development notebook | Sensitive but not strictly client-identifying if anonymized |
| Pattern-library entry | Notion, Obsidian, or a tagged WebSnips collection | Anonymized; searchable across your whole practice, not one client |
| Research supporting a pattern entry | WebSnips | Dated captures of the studies or articles that inform the pattern |
Where WebSnips fits: the pattern-library template above is strongest when each entry can point to the research that supports it — and that's usually where a coach's evidence trail is weakest, because the article that originally informed an intervention was read once, on a phone, and never saved. WebSnips lets you capture that source with its date and URL at the time you read it, then link it into the pattern-library entry later, so "what works" in your template isn't just intuition — it has a traceable source behind it when you want to revisit or share it in supervision.
Ben, a leadership coach, adopted Template 1 after realizing his session notes had become one-line summaries he couldn't reconstruct anything from. Three months in, reviewing his notes for a client before session eight, the "coach observation" field across sessions three through seven showed the same line repeated in different words: client deflects with humor exactly when a direct question gets close to a real vulnerability. He'd noticed it each time in the moment but never explicitly named the pattern until the template's structure forced him to write it down every single session — at which point it became visible as a pattern rather than a series of separate, forgotten observations.
That pattern became a new entry in his Template 5 pattern library — "deflection through humor at the vulnerability edge" — supported by two WebSnips-captured articles on humor as an emotional defense mechanism that he'd read months earlier and had almost not bothered to save.
Ben also started using Template 4 consistently after his monthly supervision sessions, which surfaced something he hadn't expected: his supervisor had noticed the same deflection dynamic from a different angle two months before Ben's own session notes made it explicit. Cross-referencing the two templates — supervision notes and session notes — showed him that the signal had been available earlier than he'd registered it, a gap he now checks for deliberately by rereading recent supervision notes before writing up a session.
Whether these templates live in a paper notebook, a practice-management text field, or a Notion database matters less than whether the fields get filled in every time. The temptation with digital templates is to let AI or auto-summarization fill them in from a session recording — which can work as a starting draft, but the "coach observation" field specifically has to be the coach's own reflection, not a machine's inference about what happened. A summarization tool can describe what was said; it can't tell you what you, as the coach, chose to follow or leave, which is the whole point of that field.
Session notes, intake notes, and engagement summaries are confidential client records under the ICF Code of Ethics, which requires that such records — in any format or tool — be stored, secured, and disposed of in ways that protect client confidentiality. Keep these templates inside your secured practice-management system, not a general notes app. Pattern-library entries and framework notes must be anonymized thoroughly before they leave the client-specific record — not just names removed, but any detail specific enough that the client could recognize themselves.
Filling in the template days later. The specificity that makes "coach observation" and "quote worth keeping" valuable decays within days; same-day notes capture what a reconstructed note from memory cannot.
Skipping fields that feel like extra work. The "coach observation" field is the one most often left blank under time pressure — and the one that makes patterns visible across sessions months later.
Using one template for every purpose. A session note and a pattern-library entry serve different functions and need different fields; forcing both into one generic template loses the specificity each is designed to capture.
Never converting session-note observations into pattern-library entries. The whole point of noticing a repeated theme across sessions is that it eventually gets distilled into Template 5 — skip that step and the same insight has to be rediscovered with the next client who shows the same pattern.
Adding every conceivable field "just in case." A session-note template with fifteen fields takes long enough to fill in that it gets skipped entirely on a busy week. Five to six fields, filled in consistently, beat fifteen fields filled in sporadically.
Note-taking templates for coaches turn a blank field and good intentions into a consistent, buildable record — one that makes session five sharper than session one instead of a fresh start every time. Five templates, filled in same-day, kept in the right system for their sensitivity level, and periodically distilled into a pattern library: that's a complete note-taking practice, and none of the individual pieces take more than a few minutes. For the fuller system these templates plug into, see our note-taking system for coaches and our guide to building a searchable knowledge base for coaches.
For more on this, see Best Web Clipper Extensions.
More WebSnips articles that pair well with this topic.
A Second-Brain Setup for Coaches — a practical, example-driven guide with honest tool comparisons and a clear place for WebSnips. Written for Coaches.
AI-Assisted Research for Coaches — a practical, example-driven guide with honest tool comparisons and a clear place for WebSnips. Written for Coaches.
From Research to Output — A Workflow for Coaches — a practical, example-driven guide with honest tool comparisons and a clear place for WebSnips. Written for Coaches.
The Reading and Research Workflow for Coaches — a practical, example-driven guide with honest tool comparisons and a clear place for WebSnips. Written for Coaches.
Beating Information Overload: A Guide for Coaches — a practical, example-driven guide with honest tool comparisons and a clear place for WebSnips. Written for Coaches.
Building a Searchable Knowledge Base for Coaches — a practical, example-driven guide with honest tool comparisons and a clear place for WebSnips. Written for Coaches.