Answer
How do you keep customers informed during a long job?
On a schedule they know about in advance, including the updates where nothing has changed.
Agree a schedule at the start and keep it, including when there is nothing to report. Most chasing calls are caused by uncertainty about whether anything is happening, not by dissatisfaction with the pace.
On any job that runs longer than a few days, the customer's experience is dominated by what they know rather than by what is happening. A job progressing well with no communication feels worse than a job progressing slowly with clear updates, and the difference generates the calls, the anxiety and the impression of disorganisation that businesses find surprising when the work itself was fine.
Agreeing a cadence at the start converts this from an ongoing judgement into a commitment. A short update every Friday, or at defined milestones, told to the customer before work begins. The specific frequency matters far less than that it exists and is known, because what the customer is managing is uncertainty about whether they will hear anything, and a known schedule removes that entirely.
The update where nothing has changed is the one that does the work and the one that gets skipped. A business with nothing to report feels there is no reason to write, and the customer experiences a missed update as a signal — something has gone wrong, or they have been forgotten. A single line saying the position is unchanged and the next step remains on schedule takes seconds and prevents the call that would have taken twenty minutes.
Content should be brief and specific: what has happened since the last update, what happens next, and whether the completion date has moved. The last item is the one customers are actually reading for, and it should be stated explicitly even when the answer is no. An update that describes activity without addressing the date leaves the question that prompted the reading unanswered.
Where something has gone wrong or a date has moved, the update is the right vehicle and it should not wait for the next scheduled one. The principle is the same as any deadline communication: the moment the belief changes rather than the moment the date arrives. A customer who learns of a delay in a routine update, before it affects them, treats it very differently from one who learns on the day.
There is a practical reason to keep the record beyond the customer relationship. A written trail of what was reported and when settles the disputes that arise on long jobs about what was known, what was agreed and when a change was raised. That trail is produced as a side effect of a scheduled update habit, which is one of the more useful things about having one.
The update where nothing has changed is the one that stops the phone ringing, and it is the only one businesses skip.
Answer Production Engine, Context Theory
Related questions
How often is too often?
Frequently enough that the customer never wonders, infrequently enough that the updates carry something. On most service work that is weekly, with milestone updates in between. Daily updates on a job with slow-moving stages become noise and are ignored, which costs the channel at the point where something actually needs to be read.
Who should send the updates?
Whoever knows what is happening, which is usually the person doing the work rather than an administrator relaying it. Relayed updates are vaguer, slower and prone to being missed when the relay is busy. Where the person doing the work will not reliably send them, a scheduled prompt is a better fix than moving the task to someone with less information.
METHOD
Every figure below carries its source and the date it was verified. Nothing on this page is asserted.
The numbers on this page.
| What | Value | Specific to |
|---|---|---|
| Firms that never responded to a web enquiry at all | 23% | Category-wide |
| Average B2B first-response time | 42 hrs | Category-wide |
| Agents who give up after one contact | 44% | Category-wide |
Oldroyd, McElheran & Elkington, "The Short Life of Online Sales Leads", Harvard Business Review (March 2011) · hours · 1.25M inbound leads across 2,241 US firms · verified
Multi-study aggregate · verified
What is specific to this page.
| Kind | Claim | Check it against |
|---|---|---|
| Buying behaviour | On jobs running longer than a few days the customer's experience is dominated by what they know rather than by progress, so well-run silent work feels worse than slower work with clear updates. | The business's own inbound calls on long jobs, classified by whether the caller sought information or raised a problem. |
| Workflow | An update stating that nothing has changed prevents the chasing call, and it is the update businesses skip because having nothing to report feels like having no reason to write. | Chasing call volume on jobs where no-change updates were sent against those where updates paused. |
| Workflow | Customers read updates primarily for whether the completion date has moved, so an update describing activity without addressing the date leaves the question that prompted the reading unanswered. | The content of customer replies to progress updates, checked for what they ask about. |
| Procurement | A scheduled update habit produces a written record of what was reported and when, which settles the disputes that arise on long jobs about what was known and when a change was raised. | The business's own disputed long jobs, checked for whether a contemporaneous update trail existed. |
Each row would be wrong on another industry's page. Where a sourced figure exists it is in the table above instead; these are the constraints that shape the work and do not happen to be numbers.
Start with the measurement.
Reading about a benchmark is not the same as knowing your own number. The audit produces yours, measured rather than estimated.
$497 · delivered in 5 business days · credited against month one