Follow-Up
The Consultant's Guide to Post-Call Follow-Up Emails
A consulting follow-up email carries more weight than a coaching one. It's often the closest thing to a written record of what was agreed, which means it doubles as informal scope documentation — useful when a client later asks "wait, did we agree to that?" and you have a dated email that answers the question.
What a consulting follow-up needs that a coaching one doesn't
A clear separation between decisions and open items
Coaching follow-ups can be a bit more fluid. Consulting follow-ups benefit from explicitly separating "here's what we decided" from "here's what's still open," because scope and budget conversations often hinge on which category something falls into.
Attribution of who owns each next step
In consulting, action items split between your team and the client's team far more often than in one-on-one coaching. Every item needs an owner named, not just implied. "We'll send the revised proposal by Thursday; you'll confirm budget approval by end of next week" is unambiguous. "Next steps: revised proposal, budget approval" is not, and ambiguity here is where consulting relationships quietly break down.
Dates that double as a paper trail
If a deadline was discussed — a go-live date, a board presentation, a contract renewal — restate it in the email. This isn't just a courtesy; it's often the only place that date gets written down anywhere both parties can find it later. See tracking client deadlines for how to catch these during the call itself so they don't get missed in the follow-up.
A structure that holds up under scrutiny
- Subject line: specific, not generic — "Recap: Q3 Roadmap Call, Sept 15" beats "Follow-up" every time, especially once a client has a dozen of your emails in their inbox.
- One-paragraph recap: what the call covered, in plain language.
- Decisions made: bulleted, unambiguous.
- Open items: what's still being figured out, and by when it needs resolving.
- Next steps: owner and date for each, on both sides.
- Next touchpoint: when you're talking again, or what triggers the next contact.
Why this email protects you, not just the client
Scope creep rarely announces itself. It arrives as a small, reasonable-sounding addition mentioned in passing on a call, and if it's not written down anywhere, it quietly becomes an expectation. A follow-up email that clearly separates "decided" from "open" gives you a natural, non-confrontational place to note "we discussed X as a possible addition — happy to scope that separately" rather than letting it slide into assumed scope. This is one of the more overlooked consultant call notes best practices: the notes and the follow-up email work together as a light paper trail.
Send it the same day. A consulting follow-up sent 48 hours later has lost most of its value as a record — by then, if there's a disagreement about what was said, both sides are working from memory instead of from a document.
Tone: professional, not stiff
It's easy to over-formalize a consulting follow-up into something that reads like a contract amendment. Keep the tone conversational and direct — the goal is clarity, not legal weight. If something genuinely needs to be a formal scope change, that belongs in a proposal or contract addendum, not buried in a follow-up email's tone.
The mechanics are close enough to a coaching follow-up that it's worth reading how to write a follow-up email after a coaching call as well — the greeting-recap-next steps-close structure holds across both, even though the content and stakes differ.
Handling multi-stakeholder calls
When a call includes several people from the client side, cc everyone who attended, and consider explicitly noting who owns each item by name rather than relying on people to infer it from context. "Sarah to confirm budget by Friday; Tom to loop in procurement" is unambiguous even to someone skimming quickly on their phone. Leaving ownership implicit in a group email is one of the most common ways a commitment quietly falls through — everyone assumes someone else is handling it.
A short version for lower-stakes calls
Not every consulting call needs the full six-part structure. A quick weekly sync with no major decisions might only need three lines: what was covered, anything new due, and the next touchpoint. Save the fuller structure for calls where decisions, scope, or budget were actually discussed — using it for every single call, including routine syncs, tends to produce email fatigue that makes the important ones less likely to get read carefully.
What to do when the client doesn't reply
Silence after a follow-up email doesn't necessarily mean disagreement — often it just means the recap looked accurate enough that no response was needed. Still, for anything involving a decision with real budget or scope implications, it's worth adding a single line inviting correction: "Flag anything here that doesn't match your understanding." That sentence turns silence into implicit confirmation rather than an open question about whether everyone's on the same page.
Keeping a copy for your own records
Beyond serving the client, your sent follow-up emails are worth being able to search later — a client asking six months into a project "when did we agree to that scope change?" is much easier to answer by searching your sent folder for the relevant recap than by trying to reconstruct it from memory or scattered notes.
Templates worth having ready
Rather than starting from a blank page for every follow-up, it's worth keeping two or three loose templates on hand — one for a routine sync, one for a decision-heavy call, one for a kickoff or scoping session — adjusted each time for the specific content but consistent in structure. This cuts the actual writing time significantly without making the emails feel canned, since the substance still comes directly from that day's conversation.
Consulting follow-ups are more time-sensitive than most people treat them. SessionScribe drafts the recap and next-steps email straight from your call transcript, so it can go out the same day without eating into billable time.