A customer accepts a quotation on Friday. The sales conversation has gone well. Everyone is pleased that another job has been won.
On Monday, the team responsible for delivering the work opens the file and starts asking questions. Which version of the proposal did the customer accept? Was installation included? Did someone promise delivery by Thursday? Who is arranging access to the premises?
The customer believes everything was agreed. The delivery team believes it has been given an incomplete brief. The owner gets pulled in to sort out the confusion.
This is a sales-to-delivery handover problem. The business may be winning work successfully while quietly creating delays, avoidable effort and customer frustration after every sale.
Before hiring another employee, introducing a new system or blaming either team, it is worth checking whether the handover itself is the constraint.
A completed sale is not necessarily a job that is ready to start
Salespeople are naturally focused on helping customers make decisions and reaching an agreement. The people responsible for delivery need something different: enough reliable information to fulfil that agreement.
Those two objectives should support each other, but they are not identical. A signed quotation may confirm that a sale happened without telling the delivery team everything it needs to know.
For example, a customer may have discussed a special fitting requirement on a call, agreed a revised deadline by email or asked for one component to be excluded. If those details remain in someone’s inbox or memory, the next person may begin with the wrong information.
The team then has two unattractive options. It can pause and ask for clarification, delaying the job, or proceed on assumptions and risk delivering the wrong result.
Neither outcome necessarily means someone is careless. It may mean the business lacks a clear point at which an agreed sale becomes an operationally ready job.
Five warning signs that the handover may be failing
1. The same questions keep coming back
Employees repeatedly ask what was agreed, which version of the quotation is correct, or whether a particular task is included. Individual questions are normal; a pattern of recurring questions may signal missing information at the point of transfer.
2. Customers are asked to repeat themselves
A customer explains their requirements during the sales process, then has to explain them again when delivery begins. This can make an otherwise capable business appear disorganised.
3. Deadlines become disputed
Someone mentions a possible completion date during a conversation, but the delivery team has not confirmed capacity or dependencies. The customer hears a promise; the team hears an aspiration.
4. Jobs need changes after they start
An installer discovers that an agreed feature is missing from the instructions. A marketing team starts work using an outdated brief. A service technician arrives without the correct materials. Some changes are unavoidable, but others begin with the handover.
5. The owner becomes the missing link
Whenever there is uncertainty, everyone returns to the business owner because only the owner knows the full story. The owner may appear to be solving problems while actually compensating for an unreliable transfer of information.
These signals can overlap with the causes explored in our guide to the hidden cost of rework. The important question is whether the missing information began before the work started.
Try a ten-job sales-to-delivery handover review
You do not need to map every process in the company to make a useful start. Choose ten recently accepted jobs or customer orders that have moved from selling into delivery.
Include a mixture of straightforward and troublesome jobs. Avoid choosing only the obvious failures; the comparison with jobs that went smoothly may be just as revealing.
For each job, ask both the person who won the work and the person who received it:
What was promised? Can the receiving team find the agreed scope, price, exclusions and any special conditions in one reliable location?
Was the next step clear? Did someone know who was responsible, what had to happen first and when the team could realistically begin?
Did anything need clarification? Count requests for missing information and note whether a customer had to be contacted again.
What was the consequence? Record delays, active staff time spent resolving the gap, extra visits, changes or customer confusion. Do not treat every hour of elapsed waiting as an hour of lost labour.
A basic review might look like this:
| Job | Missing or unclear detail | Effect on delivery | Potential improvement |
|---|---|---|---|
| Office installation | Access arrangements | Visit rescheduled | Confirm access before booking |
| Customer website | Approved scope version | Work paused for clarification | Attach final agreed brief |
| Maintenance visit | Special equipment required | Additional journey | Record equipment needs |
| Training project | Customer availability | Start date moved | Agree scheduling dependency |
Illustrative examples only. This is a sample recording format, not data from an actual business.
At the end of the review, look for repeated causes rather than treating all ten jobs as unrelated incidents. If five jobs stalled because nobody knew what had been promised, that is a different problem from one job delayed by an unexpected supplier shortage.
A small sample is a useful diagnostic starting point, not proof of a company-wide trend. Expand it if the results are mixed or the work varies greatly between teams.
What a useful handover should contain
A complicated new form is rarely the starting point. A one-page handover note, completed before scheduling, may be enough for many smaller businesses.
It should give the receiving team a dependable answer to these seven questions:
| Handover field | What to record |
|---|---|
| Customer and contact | Who can confirm requirements and access? |
| Agreed work | What is included, using the approved quotation or brief? |
| Exclusions and changes | What is not included, and what changed during discussions? |
| Important promises | Which dates, service levels or conditions were actually agreed? |
| Prerequisites | What information, materials, access or approvals are needed first? |
| Responsibility | Who owns the next step and who should be contacted if something is unclear? |
| Readiness check | Has the receiving team confirmed that the job can proceed as promised? |
The final question is especially important. A handover is not finished merely because someone sent the document. The person receiving the work should be able to confirm that it is ready to proceed or identify what is still missing.
That doesn’t mean creating another owner-approval queue. Give the receiving team a clear way to flag genuine exceptions, while letting routine, complete jobs move ahead.
Run a small experiment before buying more software
Suppose the ten-job review shows that incomplete customer requirements are a repeated cause of delay. The first step may be as simple as requiring the agreed brief and key promises to be attached before work is scheduled.
Try that change on the next ten comparable jobs. Ask the delivery team to confirm readiness at the handover point and record any missing information.
Compare a few practical measures:
- The proportion of new jobs that can start without a clarification request.
- The number of occasions when a customer must repeat information already provided.
- The time between an accepted sale and a delivery-ready job.
- The number of avoidable corrections or rescheduled visits linked to the original brief.
Measure like with like where possible. A complex project may legitimately need more discussion than a routine order. And a lower number of questions is not automatically better if essential safety, legal or quality checks are being skipped.
If the results improve, make the successful handover method part of normal practice. If nothing changes, reconsider the diagnosis. The real constraint may be staffing capacity, scheduling, suppliers or unrealistic promises rather than the transfer of information.
The point is to test the suspected cause, not introduce paperwork simply because a process sounds more professional.
A better handover starts with a better conversation
Sales and delivery teams sometimes develop unhelpful opinions about each other. Sales believes operations is too slow. Operations believes sales promises things that cannot be delivered.
Both groups may have legitimate concerns, but assigning blame won’t show what the business needs to change.
Bring the people involved together and discuss two or three recent jobs. Ask where the first uncertainty appeared, what information would have prevented it and who was best placed to provide that information.
Often, the most useful improvement is an earlier conversation. If a proposed delivery date depends on a specialist being available, the sales team should know that before committing to the customer. If a customer requires something unusual, operations should have a way to review it before the agreement is final.
The aim is not to slow down every sale. It is to protect the quality of the promise and make it easier for the team to fulfil.
A reliable handover also benefits the customer. They should not need to understand your internal departments or repeat their story every time another employee becomes involved.
When the handover is not the real problem
There are situations where the handover is complete and reliable, yet delivery still falls behind. The business may be accepting more work than the team can realistically manage, or the customer may request new work after the original agreement.
Those are different causes and call for different decisions. If demand has genuinely outgrown capacity, see our guide on whether to hire more staff or improve the process first.
Similarly, if the business is losing prospects before any sale takes place, the starting point may be lead quality or sales conversion, not delivery.
An assessment should not begin with the assumption that every delay is a handover problem. It should establish where the failure occurs and which issue is most limiting progress.
Make sure the work can move before you try to win more of it
Winning a new customer is an achievement. But the value of the sale is only realised when the business can deliver what was promised, on terms that work for both the customer and the company.
If jobs repeatedly stall just after the sale, do not assume the solution is another employee, another CRM or more management involvement.
Look at the point where responsibility passes from one person or team to another. Review ten jobs. Identify the missing information. Test one practical change.
Sometimes a business doesn’t need to work harder or sell more. It needs to make sure the work it has already won can move forward without unnecessary interruption.
If you’re unsure where your business is losing momentum, a business growth assessment can help distinguish the visible symptoms from the underlying issue that deserves attention first. If you’re considering whether the real constraint lies in sales, delivery or management, learn about the free Business Priority Check before choosing a bigger intervention.
Illustrative image created for this article; it does not depict an actual client or workplace.