Session Notes 101

Why Every Coaching Session Needs a One-Line Summary

Published 2026-09-15 · SessionScribe Blog · For coaches & consultants

Of everything in a session note, the one-line summary is the part most coaches either skip or write badly — and it's arguably the most useful single line in the whole file. Six months from now, you're not going to reread the full note for most sessions. You're going to scan a list of one-line summaries looking for the session where a particular topic came up, and the quality of that line determines whether you find it in five seconds or five minutes.

What makes a one-line summary actually useful

A good summary is specific enough to distinguish this session from every other session with the same client. "Talked about work stuff" could describe forty different sessions. "Decided to delay the promotion ask until after the Q4 reorg" describes exactly one.

Three things a strong summary line includes:

• The specific topic, not a category. Not "career," but "whether to take the internal transfer or wait for external offers."
• The outcome, if there was one. A decision, a shift in framing, a plan. If nothing was decided, that's worth noting too: "explored options for the internal transfer, no decision yet" tells you something a bare topic line doesn't.
• Enough context to stand alone. If you read only this line with no other context, would you know roughly what happened? That's the bar.

Examples: weak vs. strong

Where it fits in your note template

The one-line summary should sit at the very top of the note, above the fuller discussion points — it's the header, not a footnote. See coaching session note templates for where it fits in a full note layout, and how to take coaching session notes for the broader five-part structure it belongs to.

It doubles as your follow-up email opener

A well-written one-line summary very often becomes, with light rewording, the opening line of your follow-up email to the client. "Decided to gather more info before deciding whether to push for the promotion now or wait for the reorg" becomes "Good session today — sounds like the plan is to gather a bit more information before deciding on timing for the promotion conversation." See how to write a follow-up email after a coaching call for the rest of that structure.

Why this is worth the extra ten seconds

Writing a sharp one-line summary takes maybe ten to twenty extra seconds compared to a lazy one. Multiplied across dozens of sessions per client over a year, that's the difference between a note history you can actually navigate and one that's just a pile of similar-looking entries. It's a small habit with a disproportionate payoff.

Using summaries to see a client's arc

Line up a client's one-line summaries in order, and you get something close to a table of contents for the whole relationship. Scanning ten or fifteen of them in sequence often reveals a trajectory that isn't obvious session to session — a client who spent months circling the same underlying concern before finally naming it directly, for instance. This kind of pattern is genuinely useful to reflect back to a client at a milestone review: "here's what we've actually worked through together" lands differently when you can point to a concrete sequence rather than describing it from memory.

Common summary-writing habits to avoid

• Writing the summary before the session ends. It's tempting to draft it early if the session seems to be heading somewhere predictable, but sessions often shift direction in the last ten minutes. Write it after, not during.
• Copying the client's opening statement verbatim. What a client says they want to discuss at the start of a session and what actually mattered by the end are often different. The summary should reflect where the session landed, not just where it began.
• Making it too short to be specific. "Career stuff" is a category, not a summary. A summary can be a full sentence — brevity matters less than specificity.

A format that works well

A reliable pattern: [what the session was actually about] + [what happened as a result]. "Explored the tension with a direct report" (topic) + "and landed on trying a direct conversation before escalating to HR" (outcome). This two-part structure almost automatically produces a summary specific enough to be useful later.

When a session genuinely resists a clean summary

Occasionally a session is scattered enough that no single sentence captures it cleanly — that's fine, and it's still worth writing something specific rather than defaulting to vague. "Wide-ranging session touching on the job search, a family issue, and general stress; no single clear focus this time" is honest and still more useful six weeks later than "general check-in."

Reading summaries back to a client at a milestone

At a quarterly or milestone review, reading a handful of past one-line summaries back to a client, in order, can be a genuinely powerful moment — it's often the first time they've seen their own progress laid out as a sequence rather than remembered in fragments. This works only if the summaries were specific enough in the first place; a string of vague one-liners doesn't produce the same effect.