Writing a client communication plan that survives a busy week

You have a client who emails at 11pm, a client who only answers in a text thread that started during a launch two years ago, and a client whose approval you have been waiting on for nine days. That is not a discipline problem, and no amount of trying harder fixes it. It is a missing agreement about who says what, where, and how fast.

What a client communication plan actually is

A client communication plan is a one page agreement that names every recurring message between you and a client, the channel it travels on, how often it goes out, who sends it, and what happens when a reply does not come. It is not a values statement and it is not a section of your proposal that nobody reads twice. It is an operating document, and the test of a good one is simple: if your project manager got the flu on Monday, could someone else open the plan and run the account for a week without asking you anything?

Plans fail when they only describe the good week. They cover the kickoff call and the weekly update and stop there. The plan you need is the one that still works when two people are behind, a build slipped, and the client stopped answering.

The five questions your plan has to answer

Every line of a working plan answers the same five questions: what gets communicated, on which channel, how often, who owns it, and what happens if it does not get a response. Anything that does not answer all five is a preference, not a plan.

• What. The specific item. Not "updates" but "status of the three open build tasks and anything blocking them."
• Channel. One channel per message type. Not two. The moment approvals can arrive by email or text, they will arrive by both, and you will lose one.
• How often. A day and a time, not "regularly." Friday by 3pm beats "end of week" because Friday at 3pm can be missed and noticed.
• Owner. A person, not a role. Roles do not send messages.
• If quiet. The fallback. This is the part everyone skips and the only part that saves a timeline.

A fill-in-the-blank communication plan you can copy today

Copy this, fill it in for one client, and send it to them before your next meeting. It takes one sitting the first time and a few minutes after that.

Communication plan: [Client name] and [Your agency]
Effective [date]. Revisit on [date, 90 days out].

1. Where work lives. All project messages, files, and approvals live in [channel]. Anything sent outside it may be missed. If you send something elsewhere, we will move it in and reply there.

2. Who talks to whom. Your main contact at [agency] is [name, email]. Our main contact at [client] is [name, email]. Backup on our side is [name]. Backup on your side is [name].

3. Recurring messages.
Weekly status: what shipped, what is next, what we need from you. Sent by [name] every [day] by [time] via [channel].
Approvals: sent by [name] as they come up via [channel]. We need a yes, a no, or a question. Silence is not approval.
Monthly summary: hours or scope used, budget position, upcoming decisions. Sent by [name] on the [nth] of the month.
Invoices and billing questions: [channel], handled by [name].
Urgent issues (site down, payment failing, legal): [phone or channel], answered by [name].

4. Response times. We reply to anything you send within [X business hours] during [your hours, timezone]. We ask for the same from you on approvals and questions that block work: [Y business days]. Urgent issues get a response within [Z hours].

5. If it goes quiet. If we have not heard back on a blocking item, we send a reminder at 48 hours, a second at day five, and at day ten [name] calls. At day fifteen the work moves to the parked list and the timeline shifts by the number of days lost. We will always tell you before that happens.

6. When we go quiet. If you do not hear from us on a promised day, email [escalation name and address] directly. That is not an escalation with consequences for anyone. It is the release valve.

How to set response-time expectations in both directions

Set response times as a promise you can keep on your worst week, not your best one. If you answer in two hours when things are calm and two days when they are not, promise one business day and look reliable in both states. It is easy to get in trouble by quoting your fastest week and then living down to a slower average.

The half people forget is the client's side. You are allowed to ask for a response time, and the way to make it stick is to attach it to consequence rather than to guilt. "We need approvals within two business days, and if they run longer the timeline moves by the same number of days" is a clean sentence that no reasonable client argues with. It also gives your team a rule instead of a judgment call at 4pm on a Thursday.

Write both numbers on the same line of the plan so nobody can read one without the other. That symmetry is what makes it feel like an agreement instead of a policy.

What to do when a client goes quiet

The answer to a quiet client is a fixed sequence you run every time without deciding whether to run it. Deciding is the expensive part. If the stalled item is a sign-off, how to stop chasing clients for approvals goes deeper on that one case, and the sequence below works on anything. Run it on the approval that has sat for nine days, and on the launch date that moved once and reached three people on the account at three different times.

1. 48 hours. One reminder in the same thread. Short, no apology, restate the single decision you need and the date it affects. "Still need your yes on the homepage copy. Every day this waits moves launch by a day."
2. Day five. Different channel, different person. If the PM emailed, the owner texts or calls. Say what happens if it keeps waiting.
3. Day ten. A phone call, and if there is no answer, a message to the second contact at the client. This is why the plan names a backup on their side. Treat the silence as a scheduling problem before you treat it as a relationship problem, and assume someone is out of the office until you learn otherwise.
4. Day fifteen. Move the item to a parked list, put the timeline change in writing, and stop holding the slot. Send a short note that says exactly what is parked and what will restart it.

Two things make this sequence work. Every message names one decision and one consequence. And every message goes in the same thread as the original request, so a client returning after two weeks reads the whole history in one place instead of reconstructing it from four inboxes.

Where the plan should live so people follow it

A plan buried in a signed proposal does not change behavior, because signed proposals rarely get opened again. Put it where the work happens: pinned at the top of the client's channel, restated in the first line of the kickoff recap, and repeated verbatim in the onboarding sequence you send in the first week. Say it out loud on the kickoff call too. "Everything goes here. If you email me directly I will move it here and answer there." Clients tend to follow the channel you actually use, not the one you named once.

Cutting the number of channels is most of the work. If messages, files, and approvals live in three tools plus email, the plan will lose to convenience every time. A shared folder plus one email thread per project is a completely acceptable answer for a small book of clients. Some clients will never log in to anything you send them, and the email versus portal comparison is the place to work out whether that changes your answer. If you want one place per client with an audit trail, our product Client Atrium does this: a branded workspace per client where messages, files, approvals, and signatures sit together, with email notifications so a client who lives in their inbox still sees what is waiting. It is one option among several, and the plan matters more than the tool holding it.

If you do nothing else this week

Pick your three highest-revenue clients and write one sentence for each: the channel where their work lives, the day their status update goes out, and who sends it. Send that sentence to each of them. Expect at least one reply asking a question you had not thought about, and that question is the rest of your plan. Then start the 48 hour, day five, day ten, day fifteen sequence on every item you are currently waiting on. Some will close by Friday, and the ones that do not will tell you something true about the account that you would otherwise find out much later.