If Your Client Has to Ask How It's Going, You're Already Late
When a client asks how it's going, answer the project question first and then repair the missing communication schedule.
A message saying "How's it going?" often means the client did not know when the next client update would arrive. It does not always signal distrust. A new risk, an internal meeting, or ordinary curiosity can produce the same question.
Why a client asks how it's going
Clients ask when the cost of not knowing becomes uncomfortable. They may need to brief a manager, protect a launch date, approve an invoice, or decide whether another team can begin. Your work can be progressing well while their planning has stalled.
The question can expose a cadence gap. Perhaps you send updates only after finishing a large item. Perhaps the promised Friday email has slipped to Monday twice. Perhaps your task tool shows activity but never explains outcomes in client language.
Do not diagnose the relationship from four words. One question is information. A pattern of chasing, surprise, and repeated requests for the same fact deserves more attention.
Answer without becoming defensive
Give the useful answer in the first sentence. Include completed work, the next step, any request, and any change. If you missed an agreed update, acknowledge it briefly.
A hypothetical reply could say:
The revised checkout is in testing, and the planned Tuesday release has not changed. I need your approval of the receipt text by 3pm Monday. I also missed the update due last Friday, which left you without a clear checkpoint. I will resume updates on Fridays this week and send the next one even if testing is still open.
Do not lead with a list of everything that made you busy. The client asked about their project. Your difficult week can explain a delay, but it should not make them extract the answer from your defence.
If the date is uncertain, say so. A quick confident answer that later collapses creates more work than an honest range with a named decision point.
Fix predictability rather than assigning blame
You do not need to tell the client they should have checked the project board. You also do not need to blame yourself for every new question. Agree what information should arrive and when.
Choose a fixed day for a weekly client update during active work. Include the next update date at the end. Send the update on quiet weeks, blocked weeks, and weeks when the main result is a decision rather than a delivery.
If weekly is too slow for the project's risk, use a shorter interval temporarily. A migration weekend may need several scheduled checks. Return to the normal cadence afterward, or the emergency routine will become your permanent job.
New questions can be healthy
A predictable update should reduce avoidable chasing, not eliminate conversation. Clients learn as work develops. A new stakeholder may ask about accessibility. Finance may request a different cost split. A user test may create a question nobody could have asked at the start.
Healthy questions add information or seek a decision. Cadence questions repeatedly ask for facts you should already provide, such as whether the deadline still stands. Treat the difference as guidance for the next update.
Do not punish engagement by replying, "As stated in my last email." Answer plainly and point to the history if context helps. A technically correct rebuke tends to produce less communication, not better communication.
Find what your update failed to show
Look at the exact question. "Are we still launching Thursday?" means the date was hard to find or no longer trusted. "What do you need from us?" means your requests lacked an owner or deadline. "What have we paid for?" calls for outcomes rather than tasks.
Change the format in response. Put a stable launch line near the top, use a clear requests section, or show the completed result in client terms. Do not add a page of detail when one clearer sentence would solve the problem.
Some clients prefer to ask in conversation even when the answer is available. Agreeing a schedule will not alter every personal habit. It still gives both sides a reliable baseline.
Keep a history people can use
When updates live across unrelated email threads, the client may ask because finding the last answer is harder than asking again. Keep an ordered history and make it easy to open.
Record decisions made on calls in the next written update. Add dates to changed commitments. When a new reader joins, send the history rather than forwarding a pile of messages and hoping chronology survives.
The history should not require unnecessary client accounts. If access uses a private link, be clear that any holder can read and reply. Convenience does not excuse careless forwarding.
Restore the schedule with the next message
The useful response to "How's it going?" is a clear answer followed by a dependable next date. Then keep the date. Reliability returns through repeated delivery rather than one unusually long report.
When a client asks how it's going, the question often identifies a preventable gap, but it is not proof of failure or distrust. Respond without blame and make future progress easier to predict. Friday can send the update by email and keep the project history at a private, no login link when that setup fits your work.