Explaining a long lead time to a waiting customer honestly

Aug 29
3 min read

Updated: 2 days ago

Introduction

A customer signs in February expecting installation in April. Equipment availability slips, scaffolding is unavailable, and an engineer is off sick. In June they have had two vague updates and no date, and they are asking for their deposit back.

The delay itself was largely unavoidable and it is not what lost the job. The customer accepted a timescale that was optimistic, then received silence, and concluded the business either did not know or was not saying. Lead times in this trade are genuinely long, and customers accept them when they are told the truth.

1. Explaining a long lead time to a waiting customer starts with an honest first estimate

The optimistic quote is the root of it.

A timescale given to win the work, rather than one you can meet, creates the problem months later. Customers compare on price and availability and then judge you on whether the date was kept, which is the harder test.

2. Say what determines the date

Understanding replaces frustration.

Equipment supply, scaffolding availability, electrical connection approvals, and weather for external work. A customer who knows which of these is outstanding experiences a wait rather than being ignored.

3. Give a range and a review date

Better than a single date you may miss.

A window, with a stated point at which you will confirm, is honest and manageable. It commits you to communicating on a date even when there is no progress, which is exactly when customers assume the worst.

4. Update them even when nothing has changed

The counterintuitive rule.

A message saying there is no news and the position will be reviewed in two weeks is far better than silence. Most complaints about delays are complaints about not being told, and the update costs a minute.

5. Do not let the customer chase you

Who initiates contact is the whole signal.

A customer who has to telephone for an update concludes they have been forgotten. Scheduled proactive contact, even brief, keeps the relationship intact through a delay of several months.

6. Be honest about your own capacity

Distinguish supply from workload.

Sometimes the delay is equipment and sometimes it is that your diary is full. Customers respect a business that says it is booked until September and resent one that blames a supplier for its own scheduling.

7. Offer something useful during the wait

Reduces the sense of nothing happening.

Preparatory work that can proceed, advice on what they can do meanwhile, or an earlier date for part of the job. Movement of any kind changes the experience of waiting considerably.

8. Protect deposits properly

Both a legal and a trust matter.

How deposits are held, what happens if the customer cancels during a delay, and what protection applies. Long lead times make this question live, and a clear answer prevents it becoming a dispute.

9. Learn where your estimates are wrong

Improve the first number.

Recording quoted lead times against actual completion dates, across many jobs, shows the size of your optimism. Most installers underestimate consistently in the same direction and by a fairly stable amount.

Tell customers who are still deciding what your lead time actually is. Some will go elsewhere, which is a genuine cost, and the ones who proceed have accepted the timescale in advance rather than discovering it afterwards, which is the difference between a delay and a broken promise.

Conclusion

Give an honest estimate at the outset, because the optimistic one causes the problem months later.

Explain which factors determine the date, provide a range with a stated review point, update customers even when nothing has changed, initiate contact rather than letting them chase, be honest about whether the constraint is supply or your own diary, offer preparatory work during the wait, be clear about how deposits are protected, record quoted against actual timescales to correct your estimating, and tell prospective customers the real lead time before they commit.