Keeping a client in the loop during a project

The client who asks "where are we with this?" is not a difficult client. They are a client who has not heard from you long enough for silence to become a question. And that question, once asked, shifts the dynamic: you are suddenly the one explaining yourself instead of the one getting on with it.

Here is how to keep the silence on your side and the trust on theirs, with the minimum of messages and the maximum of effect.

Why the client worries

Your client cannot see your screen. They do not know whether you have started, whether you are waiting on a file, whether you are on another job or whether you have forgotten entirely. What they know is that they have paid, or are about to, and nobody has said anything since.

Silence is never read as work in progress. It is read as delay, disorganisation, or indifference. Three interpretations, and none of them helps you.

The rhythm that works

No rigid calendar. Three moments are enough for almost any job:

• At the start. A short message saying what you will do, what you have received, and what is still missing. This message closes the door on the first wave of worry.
• In the middle. A milestone reached, a glimpse of what is done. Not a final render, not a mock-up demanding approval: a checkpoint that says "this is moving".
• Before delivery. A message announcing what is coming, when, and in what form. The client who knows when they will receive does not chase.

If the job takes less than a week, the middle one can go. If it takes a month, a message a week is a minimum. The principle does not change: the client gets news before they have time to go looking for it.

What replaces a message

Some updates do not need to be written. A preview of the work in progress, a partial file, a milestone marker: all of these show without you having to narrate them.

That is where a shared space changes everything. The client sees the status of their order without opening an email, without writing to you, without waiting. You are no longer the messenger: the status reads itself.

And that is also where you save time. The client who sees "in progress" does not ask "where are we?". And the one who sees the questions they still need to answer gets to them without a reminder.

The updates that waste your time

Not everything is worth saying. Three habits exhaust you without reassuring the client:

The daily message. You spend twenty minutes writing what you did, for a client who skims it and retains only that you are not done. A message a day turns the job into a report, and the report is never the work.

The open-ended question. "Any news?" does not say what news you are waiting for. The client does not know whether to reply, review, approve, or wait. Every message should say what you need from them, or say explicitly that you need nothing.

Announcing a problem without a solution. "There is an issue with the files" triggers panic that "I received the files, one is missing, I am sending you the details" does not. The problem is the same. How you say it changes everything.

When the client goes quiet

Silence comes from the other side too. You asked a question, sent a preview, requested approval, and nothing. The client is not responding.

Before following up, look at the calendar. A client who has not replied in a few days is not forgetting: they are at their own job, not yours. The follow-up then is done with context, not with a "so?", and it is the kind of message an automatic reminder writes better than you do, because it does not wait until it feels like it.

Give them what they need to reply in five minutes: the link, the question, and why it is blocking. A message that asks for a decision without giving the context to make it gets silence back.

Frequently asked questions

How often should you update a client during a project?

Three times for a short job: at the start, in the middle, before delivery. For a longer job, a message a week is a minimum. The principle stays the same: the client gets news before having to go looking for it.

What do you say when there is nothing to show?

Say where things stand and what is missing. A message saying "I am waiting on your copy for the About page" is more useful than a premature render. Silence is never read as work in progress.

How do you follow up with a client who is not responding?

With context, not with a "so?". Give the link, the question, and why it is blocking. A message that asks for a decision without giving the context to make it gets silence back.

Should you have a shared space with the client?

A space where the client sees the status of their order without writing to you replaces half your messages. You are no longer the messenger: the status reads itself.