What your client cannot see, and why they keep asking where things stand

You know exactly where the job stands. You started the layout yesterday, you are waiting on their logo as a vector, and you deliver Thursday if it arrives.

They know none of that. They sent their brief eight days ago, nothing has come back since, and they have no way of telling "this is progressing normally" apart from "they took another job and forgot". So they write. Not to nag you: to find out.

It is the most expensive asymmetry in commissioned work, and it has nothing to do with how good your work is.

For a client, no news is bad news

In salaried work, hearing nothing is neutral: things are moving, you will see it eventually. A client who has paid a deposit does not read silence that way, for a simple reason: they have handed over money and hold nothing. From that position silence never reads as calm. It reads as risk.

Which explains something usually taken the wrong way round: half the messages a client sends are not requests, they are checks. "Where are we at?" does not mean "hurry up". It means "tell me this is normal".

The practical consequence matters more than the observation. A message asking for information costs you the time to give it. A message asking to be reassured costs the same, except it comes back next week, because nothing has changed in what the client can see.

The three moments a client always worries

These are not three moods. They are three specific questions, and they land in the same places on nearly every job.

Right after sending the brief. Their question is not "when will it be ready", it is "did that arrive and was it complete". They filled in twenty fields and uploaded four files from a phone, and they have no idea whether the third one made it. This is the cheapest moment to handle and the one most often missed, because on your side nothing has happened yet.

In the middle, after a week of seeing nothing. Now the question is "are you waiting on me". Nine times out of ten the answer is yes and they do not know it. A job asleep for ten days over one question, asked once, in an email read while walking, is the most ordinary story in this trade.

Just before delivery. The question becomes "is this going to be what I asked for". It is legitimate and it is late: this is the point at which disagreement costs the most, because the work is done. A preview, even partial, even low resolution, defuses it entirely.

None of the three asks for a report. They ask for one sentence, at the right moment.

"I'll keep you posted" works against you

It is the most natural sentence in the world, and it creates exactly the problem it means to avoid.

It sets an expectation without naming a frequency. The client hears "you will get news", they do not know whether that means tomorrow or in three weeks, so they count the days from a marker you never gave them. And on the day they write to you, they are right: you promised something and did not do it.

The version that holds is shorter and more committing: name the next date. "I'll show you a first version on Thursday" is a checkable promise. It costs you one reminder in your calendar and buys a week of quiet. And if Thursday comes and it is not ready, two lines on Thursday beat finished work on Monday with nothing said in between.

The shape of an update that fits in three lines

When you do write one, it needs three things, in this order.

1. What is done. One sentence, without describing your method. The client is not buying your process.
2. The one thing you need from them. One at a time, named precisely. "Your copy" is a request that gets postponed; "the text for the Contact page, rough is fine" is a request handled in two minutes.
3. What happens next, with a date.

What has no business in there: apologies, technical detail, and the state of your other jobs. An update that apologises teaches the client there was something to worry about.

What a client should be able to check without writing to you

This is the version that scales, because it asks nothing extra of you per job. There are four things, and not one more, that a client wants to look at on their own.

• Did what I sent actually arrive, files included.
• What did I answer, exactly, because they do not remember and they are right to want to check before arguing.
• Is the ball in my court. This is the one that unblocks the most jobs.
• What is left to pay, and when.

This is not a weekly report. A weekly report is a third job, on top of yours and on top of the chasing, and it is the one that stops after three weeks. It is a page that says those four things by itself, with nobody keeping it up to date.

What Kalepio does about it

Your client keeps one link, from the first brief to the delivery, with no account to create. What they see there is not a summary you write: it is the job itself.

And above all, the page narrates itself. When you open a new request, when a delivery is published, when a payment is asked for or received, a line appears in the conversation without you writing anything. That is what replaces the status update in most cases: the client sees movement because something moved, not because you remembered to mention it.

Messages stay messages, both ways, with attachments. What they answered no longer moves: a submitted answer is frozen, so they can go back to it and you cannot rewrite it. And they are not emailed about what they are currently reading, because a message is only notified once it has gone unread for a few minutes.

For the other half of this subject, the half on your side: where every job stands, without a spreadsheet. And when the client goes quiet anyway, how to chase without apologising.

Frequently asked questions

Why does my client keep asking where things stand?

Because they have no way of telling a job that is progressing from a job that was forgotten. In their position they have paid and hold nothing, so silence does not read as calm, it reads as risk.

How often should you update a client?

Less often than people think, as long as you name the next date. "I'll show you a first version on Thursday" buys a week of quiet, whereas "I'll keep you posted" sets an expectation whose rhythm the client then decides for themselves.

What goes into a client status update?

Three things: what is done, the single thing you need from them, and what happens next with a date. No apologies and no technical detail: an update that apologises teaches the client there was something to worry about.

How do you stop a client worrying before delivery?

By showing them the result before handing it over. A low-resolution preview, a watermarked mock-up or a staging address defuses the question entirely, and at a point where disagreement still costs little.

Should you give a client access so they can follow their job?

Access yes, an account no. Creating a password is where half of all clients drop out, especially on a small job. A link they open that shows where things stand is enough, and there is nothing for them to dig out of their inbox.