Most consultants have a proposal template and an invoice template. Almost nobody has a template for the three messages they actually send more often: the nothing-to-report update, the deliverable-is-late warning, and the no to a request that was never in scope. Winging those in the moment is where tone goes wrong.
The "still working on it" update
Clients don't need a status update every week to feel reassured — they need to know silence means progress, not neglect. The mistake is either over-explaining a non-event or skipping the message entirely and letting a client wonder. A short, dated line does the job.
Subject: Quick status on the [project name] work
Hi [name] — quick check-in, nothing urgent needed on your end. We're still heads-down on [specific task], on track for the [date] update we discussed. I'll flag anything that changes that timeline before it becomes a problem. No action needed from you right now.
The phrase "no action needed from you right now" is doing real work here — it tells the client explicitly that this isn't a message they need to respond to, which is often the thing that makes people ignore updates in the first place.
The late-deliverable warning
The version of this message that damages trust is the one sent the day something was due, after the client has already noticed it's missing. The version that preserves trust is sent before the deadline, with a specific new date attached — not "soon," a date.
Subject: Heads-up on the [deliverable] timeline
Hi [name] — wanted to flag this before it becomes a surprise. The [deliverable] won't be ready by [original date] as planned — [brief, honest reason, one sentence]. I'm targeting [new date] instead, and I'll confirm by [check-in date] if anything shifts again. Let me know if that timing causes a problem on your end.
One reason, one new date, one offer to hear if it's a problem. Longer explanations read as justification, and clients generally care less about why something slipped than about knowing exactly when it's now landing.
Declining an out-of-scope request
This isn't the conversation about renegotiating scope — that's a longer discussion. This is the fast, in-the-moment reply to a single ask that's clearly outside the engagement, where the goal is just to not say yes by accident because a no felt awkward to type.
Hi [name] — happy to take a look, but this falls outside what we scoped for [engagement name], which is focused on [original scope in a few words]. I can either add it as a separate quick-turn item at [rate/estimate], or we can hold it for the next phase if that works better. Which would you prefer?
It names the boundary, doesn't apologize for having one, and hands the client a choice instead of a flat rejection — which is what keeps the answer from reading as unhelpful.
Why having these ready matters
Each of these takes under a minute to send when it's a template you're adapting, and fifteen minutes of second-guessing when you're composing it from scratch under a deadline. The content is short by design — clients read past the third sentence of a status update far less often than consultants think they do.
These cover the message itself. For the document that sets the scope these templates end up defending, see the consulting proposal generator.