When a client asks "any updates?" — end it for good

It lands on a Tuesday afternoon: "Hey — any updates?" Two words, no exclamation point, and somehow heavier than a complaint. Here's the direct answer to the situation: respond within the hour with outcomes-first specifics, then install a weekly rhythm so the question never gets asked again. The email isn't really about updates — it's the sound of a client deciding whether to worry.

What is the client actually asking?

Not for a task list. The subtext of "any updates?" is one of three worries: is my project moving, did my money disappear into silence, or have I been deprioritized for a bigger client? Notice that all three are trust questions, not information questions — which is why a defensive data dump ("here are the 34 things I did") answers the words and misses the point.

It's also why the question stings. You have been working. But work the client can't see doesn't exist for them, and the gap between effort and visibility is where engagements quietly rot — the same gap behind most of the communication mistakes that kill renewals.

How should you respond right now?

Fast and structured. Speed matters more than completeness — a good reply in an hour beats a perfect one tomorrow:

1. First line answers the real question. "Yes — everything's on track for the 15th." Anxiety handled; now they can actually read the rest.
2. Three outcome bullets. What's done and true, not what you did: "Checkout bug fixed and live" beats "worked on checkout issues."
3. One next step with a date. "Next: payment-provider integration, landing Thursday."
4. One ask, if you have one. Blocked on their API keys? Say so now — it reframes the conversation from "are you working?" to "we're working together."

No apology paragraph. If your rhythm slipped, the fix is structural, and the last line of your reply can say so: "I'm moving us to a fixed Friday update so you always know where things stand." That sentence converts an awkward moment into a professionalism upgrade.

Why does the question keep coming back?

Because ad-hoc communication decays under pressure. You answer thoroughly, two quiet weeks pass, the client asks again — and now it's a pattern, and patterns are what clients remember at renewal. The failure mode isn't laziness; it's that "send an update when there's something to say" is a rule that always loses to deadline pressure, and it puts the judgment call ("is this worth mentioning?") on every single day.

A fixed rhythm deletes the judgment call. Update goes out Friday, whether the week was dramatic or quiet. "Quiet week — deep in the data migration, on track" is a perfectly good update; what's not fine is the client inferring quiet weeks from silence. For picking the interval, see weekly vs monthly reporting — for anything active, weekly wins.

What does "never hear it again" actually take?

Two layers:

A weekly report they can set their watch by. Same day, same format — summary, done, next, needs-input. Steal a structure from the status report template collection and stop redesigning it weekly. The consistency is the feature: after three weeks, the client's Tuesday worry has nowhere to grow, because Friday's answer is already scheduled.

Visible progress between reports. The stretch goal: a place the client can glance mid-week without asking — a live feed of real activity, shared as it happens. This is what WorkedOn does for freelancers and agencies: your commits, board moves, and quick notes become a client-visible feed plus an AI-drafted weekly report you approve before it sends. The update stops being a chore you owe and becomes a byproduct of working. Clients with a window don't knock.

The payoff compounds. Clients who never have to ask refer more, renew more, and negotiate less — because the question under the question ("can I trust this person with more?") has been getting answered every Friday.

FAQ

Is a client asking for updates a bad sign?

Once, no. As a pattern, yes — it means their anxiety is arriving faster than your information. Clients who have to ask start wondering what else they'd have to ask about, and that doubt shows up at renewal time.

How do I respond to "any updates?" without sounding defensive?

Answer the real question — is my project okay? — in the first line, then outcomes, then next steps: "Yes — the integration is on track for Friday. This week: X and Y shipped. Next: Z." No apology needed; just add the structure that prevents the next one.

What if there's genuinely nothing to report?

There's never nothing. "Deep in the payment-provider integration this week — no visible output yet, on track for Thursday" is a real update. Silence during heads-down work is exactly when clients worry most.

How often should I send updates so clients never ask?

Weekly, same day, same shape, for any engagement longer than two weeks. Predictability does most of the work — clients stop asking when they know exactly when the next update lands.