A client emails to ask how things are going. You answer. Two days later they ask again. Nothing has gone wrong with the work — the problem is that they have no way of knowing that. Every unanswered question turns into an email you have to write, and writing it costs more than the answer is worth.
The usual advice is to buy a CRM. That is a large tool aimed at a different problem: managing a sales pipeline of people who are not yet customers. You have the opposite situation — a small number of active clients who have already paid or committed, and who simply want to know where their work stands. This guide covers the four gaps that actually cause status-chasing, and how to close each one without new software.
Why clients chase you
It is worth being precise about the cause, because the fix follows from it. Clients chase for one of four reasons, and each has a different remedy.
| What the client is missing | What they do | What fixes it |
|---|---|---|
| They cannot name where the work is | Ask "any update?" | Named stages |
| They do not know when they will hear next | Ask again a day later | A promised cadence |
| They cannot find your last message | Ask for a resend | One channel |
| They have to ask you to find out anything | Ask for everything | A status page |
Notice that none of these are solved by working faster. A client with no visibility will chase a fast job and a slow one at the same rate. Visibility is the product here, not speed.
1. Give the work named stages
A stage is a short, plain-language name for where a file currently is. Three to six is the right number. Fewer than three and the stages carry no information; more than six and you will stop updating them accurately, which is worse than not having them.
The test for a good stage name is whether the client can read it without you explaining it. "In review" passes. "QA2" does not. If your internal vocabulary is more precise than your clients need, keep both: an internal name for your team and a plain label for the client.
| Internal stage | What the client sees |
|---|---|
| Intake — docs pending | Waiting on your documents |
| In prep — first pass | In progress |
| Partner review | In review |
| Awaiting client sign-off | Waiting on your approval |
| Filed / delivered | Complete |
2. Promise a cadence and keep it
The single highest-leverage sentence in client work is a promise about when they will hear from you next. It converts an open-ended wait into a defined one. People wait patiently for a known duration and impatiently for an unknown one, regardless of the actual length.
A workable cadence has two triggers: send an update whenever the stage changes, and send one anyway if a fixed interval passes with no change. The second trigger matters more than the first — silence during a slow stretch is exactly when clients start chasing.
Pick the interval
Weekly suits most service work. Fortnightly is enough for long compliance or legal matters. Anything shorter than weekly becomes noise and you will abandon it.
Say it out loud at kickoff
One line in your onboarding message: "You will hear from us every Friday, and any time the file moves." This is the promise clients actually remember.
Send the boring ones
An update that says "no change, still with the reviewer, next update Friday" is not a wasted message. It is the message that stops the chase.
Subject Quick update on {{project}} — no change this week
Hi {{first_name}},
Short one this week: {{project}} is still at {{stage}}. Nothing is blocked and nothing is needed from you.
Next update Friday, or sooner if it moves.
{{your_name}}This message takes thirty seconds to send and prevents the two-email exchange that would otherwise happen on Monday.
3. Put updates in one place
Status information scattered across email, text messages, a shared drive comment and a phone call is information the client cannot retrieve. When they cannot retrieve it, they ask you — which is the behaviour you are trying to eliminate.
Pick one channel for status and use it exclusively. Email is usually right for service work: it is searchable, it needs no login, and clients already live there. What matters is not which channel you pick but that status never appears anywhere else.
- Status changes go in the status channel — always, even if you also mentioned it on a call.
- Questions and discussion can happen anywhere; they are not status.
- If a client asks for status in the wrong channel, answer briefly and point at the right one.
4. Give them somewhere to look
The first three fixes reduce chasing. The fourth removes the need to ask at all. If the client can look up the answer themselves at 9pm on a Sunday, the question never reaches you.
This does not mean building a client portal. A portal means accounts, passwords, permissions and support requests when people cannot log in — you have added a system to avoid writing emails. A read-only page at a private link does the same job with none of that: no account, nothing to remember, nothing for you to administer.
What belongs on a client-facing status view
- Current stage, in the plain-language label
- When it last changed
- What happens next, and who it is waiting on
- Anything outstanding from the client, stated explicitly
- Amount due and due date, if money is involved
- A way to reach you
How to tell whether it worked
Track one number for a month before you change anything: how many inbound messages you receive whose entire content is a request for status. Most small teams are surprised — it is usually between four and ten a week per person, each costing five to fifteen minutes once you include the context-switch.
Then put the four fixes in place and count again after a month. The number that matters is the reduction, not zero: some clients will always prefer to ask, and that is fine. If you have not moved the number at all, the usual cause is the second fix — a cadence that was promised but not kept teaches clients that the promise means nothing, and they go back to chasing.