Why clients keep asking "where are we on this?"
Clients keep asking where things stand because they were not told first. Many check-ins exist because an update was missing or a promise slipped. Answering faster does not stop them. Status sent before they ask, taken from the work itself, removes the reason.
The account inbox opens with "just checking in" and "any update on". You reply, then a teammate replies, and two days later the same client asks again.
What owners try
Owners answer faster, hire an account manager for client check-ins, or add a weekly status call. Each one makes the answer quicker or moves it to someone else, and each leaves the cause of the question in place.
Why the messages keep coming
Some client messages are real needs: a decision, a file, a question only they can answer. Many are not. They exist because something the client expected to hear never arrived. Work that a missing update or a slipped promise created comes back as a message.
This is demand your own business created, by something not done right earlier. Answering it faster does nothing about why it exists. Those messages tend to stop once the reason for them does.
Signs the messages are your own gaps
- Messages that begin "just checking in" or "any update on".
- The same client asking twice about the same project.
- Questions that your project tool already answers.
- A client chasing a date nobody told them had moved.
Which message is yours
| The message | What it usually means | What stops it |
|---|---|---|
| "Any update on...?" | No status went out after the last milestone | An update sent when the milestone is reached |
| "Just checking in" | The client does not know what happens next | The next step and its date in every update |
| "Did you get my file?" | Nobody confirmed receipt | A receipt note sent when the file arrives |
| "When will this be done?" | The date was never set, or it moved without notice | The date shown, and any change announced |
To size it, count one week of check-in messages and note the minutes each one takes. The coordination cost tool turns your own total into a yearly figure.
Status sent before they ask
The status comes from the work itself. When a task moves to its next stage in your project tool, a short update is drafted in plain words for the client's contact. A person reads it and approves it before it goes. The client hears first, so there is less to chase.
A typical update reads: "The homepage design is approved and moving to build. The next step is your review of the staging link on Thursday."
- 01Collect a month of check-in messagesSort them by what each client wanted to know.
- 02Pick the most common reasonThat is the first update to send.
- 03Find the moment that should have triggered itA milestone, a file arriving, a date moving.
- 04Send that update at that moment for a monthShort, with the next step and its date.
- 05Count the check-ins againThe gap tells you what to automate next.
Decisions you keep
- Decisions about what an update says about a delay. A person approves the wording before it goes.
- Which clients get a call instead of a message.
- What you promise about dates.
The system behind this: status drafted from the work itself and sent before the client asks, with every update approved by a person.
Questions
Why do my clients keep asking where things are?
Often because something they expected to hear never arrived. A missing update or a slipped date turns into a message, so the questions are partly caused by your own gaps.
Will answering faster or hiring someone for check-ins stop the messages?
It keeps them coming. A faster answer handles one message and does nothing about why it was sent.
How do I automate client project status updates?
Draft the update from the change in the work itself, such as a milestone reached or a date moved, and have a person approve it before it goes. Start with the one reason clients ask most often.
Does the client get messages that nobody checked?
No. Every update is drafted for a person to read and approve before it goes out. What the automation can see and change is set out on the access and data page.
Related
- The agency client lifecycle: five stages from first touch to renewalMap agency work across Acquire, Convert, Onboard, Deliver, and Retain and expand: who owns each handoff and where client work stalls.
- The owner-approval bottleneck: when every yes waits for youReplies, proposals and discounts all wait for the owner's yes. Written rules send the routine to a named person and bring the owner only the exceptions.
- What does coordination cost your business each year?Turn your leads, proposals and active projects into the hours your people spend coordinating each month, and what that time costs you in a year.
- A drafted reply to each lead, approved from your phone before it sendsAI drafts replies to lead emails that pass a junk screen, from your business facts. Risky asks get flagged. Nothing sends until a person approves it by phone.