A client communication cadence that keeps projects from going sideways

The “what’s the status?” email almost never arrives because a client is difficult. It arrives because the client has not heard from you recently enough to feel confident that things are on track. The silence created the anxiety. The email is just the symptom. A consistent communication cadence eliminates most of them before they are written, because the client already knows the status before they think to ask.

Why projects go sideways before the work does

Most project failures are not technical. The design is late, the scope ballooned, the relationship soured, and by the time the invoicing conversation happens it is awkward for everyone. But the root cause, almost always, is a gap in communication that allowed expectations to drift. The client imagined one thing. The team was building another. Neither party surfaced the difference until it was expensive to fix.

A communication cadence is a pre-agreed rhythm of touchpoints: when the client hears from you, in what format, and what that communication covers. It is not about more communication. It is about predictable communication. A client who knows they will receive a short project update every Monday morning stops watching their inbox for signs of life on Tuesday afternoon. The cadence replaces anxiety with structure.

This article covers the four touchpoints that make up a complete cadence, what belongs in each one, and the templates and cadence rules that make the system repeatable across every account you manage.

The four touchpoints of a complete cadence

Every project relationship needs four categories of communication, each serving a different purpose. Some can be combined. None can be skipped entirely without creating a gap the client will eventually fill with an anxious email or a phone call at the worst time.

• The project kickoff. Sets expectations for the entire engagement. This is where the communication cadence itself is introduced, so the client knows exactly what to expect going forward.
• The weekly status update. A short, consistent pulse that keeps the client informed without requiring a meeting. Same format, same day, every week.
• The milestone check-in. A more substantive conversation at natural inflection points in the project. Approval gates, deliverable handoffs, scope changes, and budget reviews belong here.
• The project close and review. A structured end-of-project conversation that wraps the engagement professionally and sets the stage for the next one.

Touchpoint 1: the kickoff

The kickoff is where the communication cadence is established, not just the project plan. Most kickoffs cover scope, timeline, and deliverables, but skip the meta-layer: how will we communicate throughout this project? That omission is where most of the “what’s the status?” emails are born.

At the kickoff, cover these five points explicitly before you close the call:

1. Establish the weekly update day and format. Tell the client: “You will receive a short project update from us every Monday morning. It covers what was completed last week, what is coming this week, and anything we need from you. It will be short, maybe five bullet points, and you do not need to reply unless something needs your attention.” Then send the first one the following Monday without fail.
2. Identify the milestone gates. Name the two to four moments in the project where the client will need to actively review and approve work. These are the milestone check-in points. Put them on the shared calendar during the kickoff, not later.
3. Set the response-time expectation clearly. Tell the client what you need from them in order to keep the timeline intact. “When we send something for approval, we need a response within 48 hours to stay on schedule.” Say it out loud in the kickoff and document it in the kickoff summary.
4. Agree on a single communication channel. Pick one channel for project communication: email, a shared workspace, or a client portal. Not all three. Multiple channels mean things get lost and the client feels like they have to check several places. This is also where a tool like Studio Craft earns its place: one client record, one project thread, one place the client checks.
5. Send the kickoff summary within 24 hours. A one-page written summary of what was agreed: scope, timeline, milestone dates, communication cadence, and response-time expectations. This becomes the document you reference when scope creep or miscommunication surfaces later.

Touchpoint 2: the weekly status update

The weekly update is the workhorse of the cadence. It does not need to be long. It needs to be consistent. A client who receives a five-bullet-point update every Monday morning for eight weeks has a fundamentally different experience than a client who receives a long email when something goes wrong and nothing in between.

Use the same structure every time. Clients learn to scan it quickly when the format is predictable:

• What we completed last week. Two to four specific items, named, done. Not “we worked on the design”; say “we completed the homepage wireframe and the mobile navigation draft.”
• What is coming this week. Two to four items the team is actively working on. This sets the expectation for the next update.
• What we need from you. Zero to two items the client needs to act on. If there is nothing, say “nothing needed from you this week.” The explicit zero prevents the client from wondering.
• Flags or risks. One sentence if anything is at risk: “The third-party integration is taking longer than expected; we are still tracking to the delivery date but will update you by Wednesday if that changes.” Silence on risks is where trust breaks.
• Next milestone date. A single line reminding the client of the next approval gate. Keeps the milestone visible and prevents it from being a surprise when it arrives.

A five-bullet-point update sent every Monday is worth more to a client relationship than a detailed report sent occasionally. Consistency is the signal.

Touchpoint 3: the milestone check-in

Milestone check-ins are the moments when work is handed off for review, major decisions need to be made, or the scope or budget needs to be reassessed. They are more substantive than a weekly update and usually involve a conversation rather than just an email. The key is that they were planned at the kickoff, so neither party is surprised by them.

A milestone check-in typically covers:

• What is being handed off or presented. The specific deliverable, decision, or review that triggered the milestone. Framed clearly: “We are presenting the first round of design concepts today. We need your consolidated feedback by Friday to stay on schedule.”
• Current budget status. A short budget check: percentage of hours used versus percentage of project complete. If these are misaligned, the milestone check-in is where you surface it, not in the final invoice.
• Any scope adjustments. If the work required more than expected, or the client has requested changes that are outside the original scope, the milestone check-in is where that conversation happens formally. Not over email after the fact.
• Updated timeline. Confirm the remaining milestones and delivery date. If anything has changed, address it now while there is still time to adjust.
• Decision log. A written record of what was approved or decided at the milestone, sent within 24 hours of the conversation. This is the single most protective document in the entire engagement.

Touchpoint 4: the project close and review

Most agency and freelance relationships end with a delivery email and a final invoice. The close review is what distinguishes a professional service firm from a contractor. It is a structured end-of-project conversation that has two functions: it wraps the engagement with intention, and it sets the stage for the next one.

Keep the close review short. Thirty minutes on a call or a structured email works for most projects. Cover these four things:

1. Recap what was delivered. A short summary of everything that was completed. This sounds redundant, but clients often have a foggier memory of scope than you do. The recap reminds them of the full value of what they received, which matters both for the final invoice and for the next proposal.
2. Ask one feedback question. Not a long survey. One question: “What is the one thing we could have done better on this project?” The answer is almost always useful, and asking it signals that you are a professional who improves rather than a contractor who disappears after delivery.
3. Name what comes next. If there is a natural next phase, say it directly: “The next step we would recommend is X. Would you like us to put together a proposal?” Clients who have just had a good experience are more receptive to the next conversation than they will be three months later when the project memory has faded.
4. Send the close summary. A written record of everything delivered, any outstanding items the client is responsible for, and the next recommended step. This is also the natural place to request a referral or a testimonial if the relationship earned it.

Common failure modes and how to prevent them

• Skipping a week. One missed update is fine if you flag it in advance. Two missed updates and the client’s anxiety starts climbing. If you are in a heavy production week and the update will be late, send a one-line email on Monday that says “Light update this week, heads-down on delivery, full update next Monday.” That thirty seconds prevents a “what’s the status?” email on Wednesday.
• Burying bad news in a long email. If there is a risk or a problem, surface it in the flags section of the weekly update with one clear sentence. Do not wrap it in so much context that the client has to find it. The faster and cleaner you surface a problem, the less catastrophic it tends to feel.
• Multiple communication channels running simultaneously. When decisions get made in a Slack thread, confirmed in an email, and then referenced in a shared doc, nobody can find the authoritative record. Pick one channel for project communication and be explicit about it at kickoff.
• Approval gates without a decision log. Verbal approvals disappear. If the client approved a direction on a call and later insists they did not, the only protection is a written record sent within 24 hours: “Following our call today, here is what we agreed: [X]. Please let us know if this does not reflect the conversation.” Silence from the client is confirmation.
• Skipping the close review. The close review is the most skipped step in most agency workflows. It is also the most recoverable. Even a short email that covers what was delivered and what comes next is dramatically better than a delivery and an invoice and nothing else.

Common questions

What if a client does not want regular updates?

Some clients will tell you at kickoff that they prefer minimal contact. Respect that, but do not interpret it as permission to disappear. A shorter update cadence, say bi-weekly instead of weekly, still provides the structure that prevents anxiety from building. Even a client who says they do not need updates will send a “what’s the status?” email if they go three weeks without hearing from you. Adjust the frequency; do not eliminate the cadence.

How do we handle a client who communicates outside the agreed channel?

Acknowledge it where they sent it, then redirect: “Got it, texting you back, but I will add this to our project thread so it is in the right place.” Do this consistently and without making the client feel bad about it. The goal is to keep the record intact, not to police communication style. After two or three gentle redirects most clients adopt the agreed channel without being asked again.

Our projects are short, two to three weeks. Does the full cadence still apply?

Scale it down, but keep the bones. A kickoff summary is always worth sending. A weekly update still applies if the project runs longer than a week. The milestone check-in may be the only substantive touchpoint. The close review takes ten minutes but prevents the loose ending that makes the next proposal harder. Even in short projects, the same failure mode applies: silence creates anxiety.

What is the right way to surface a budget issue mid-project?

Bring it up at the next milestone check-in, or sooner if the overrun is significant. Never save a budget surprise for the final invoice. Frame it factually: “We are at 70% of the estimated hours with roughly 50% of the project remaining. We want to flag this now while we have options.” Then present two or three paths forward. Clients handle budget surprises well when they are surfaced early with options. They handle them badly when the invoice is the first signal.

Should the communication cadence be in the contract?

Reference it in the contract, document it in the kickoff summary, and then follow it. The contract is the wrong place to put all the mechanics: it is too formal and clients rarely re-read it. The kickoff summary is the living document the client actually references. One sentence in the contract that says “we will maintain the communication cadence outlined in the project kickoff” is enough to create a paper trail without burying the details in legal language.