A customer says yes. Sales forwards the email thread to operations with the words "please process". Operations opens it and finds three versions of the quote, a delivery date mentioned in a phone call, and no idea whether the customer needs a separate invoice address. Two days of questions follow, and the customer, who thinks everything is settled, starts to wonder.
This is one of the cheapest problems to fix in a small company, because it needs no new software. It needs an agreed list of what must be passed on, and a person on each side who is responsible for it.
Where the handoff goes wrong
Sales and operations look at the same deal differently. Sales knows what was discussed and promised. Operations needs what can be executed: quantities, dates, addresses, conditions. The gap between the two is usually filled by memory and by forwarded messages.
Typical symptoms are:
- operations asks the customer questions the customer already answered,
- a special condition, such as a partial delivery or a fixed installation day, is discovered after the work has started,
- the price on the invoice differs from the price in the quote and nobody can say which one is right,
- the order waits because each side thinks the other has the next step.
Pass what was promised, not only what was priced
The quote is a document about price. The order is a document about commitments. Anything sales said that the customer may rely on belongs in the handoff, even if it is not in the quote: a delivery window, a substitute product, a free repair, a payment term that differs from the standard.
A simple test: if the customer called operations tomorrow and quoted a sentence from the sales conversation, could operations answer? If not, that sentence is missing from the handoff.
The required fields
Keep the list short enough that people really fill it in. For most small companies these are enough:
- Customer and contact: legal name, the person who confirms details, phone and email.
- Quote reference and final version: one number, one file, with older versions clearly marked as replaced.
- Items and quantities: exactly as agreed, including any variants.
- Price and payment terms: the agreed total, discounts and when payment is due.
- Delivery or start date: a date or a window, and whether it is firm or only a wish.
- Delivery and invoice addresses: they are often different.
- Special conditions: anything promised outside the standard terms.
- Customer's order number or purchase reference, if the customer requires it on the invoice.
- Sales owner: who answers questions about the deal.
If your business needs more, such as a site access note or a technical specification, add it, but write a reason next to each field. A field no one has ever used should be removed.
One person on each side
Name one person in sales who sends the handoff and one person in operations who receives it. In a very small team these may be the same people for every order; in a larger one, a rota is fine. The point is that the handoff has an addressee.
Agree on a fixed time for operations to answer, for example one working day. The answer is one of three: accepted, accepted with a question, or returned with a list of missing fields. Silence is not an answer.
What to do when something is missing
Operations should not guess, and should not start by writing to the customer. The order goes back to the sales owner with the missing fields listed, and the clock stops until they are filled in. This feels strict at first. In practice it takes a few days for sales to learn the list, and after that returns become rare.
If a deal is urgent, operations can accept it with an open question, but the question is written down, with a name and a date. An urgent exception that is not recorded becomes the normal way of working within a month.
Where to keep it
A shared form, a template in the folder of the deal, or a simple ticket is enough. What matters is that there is one place and one current version. If the handoff is an email, use a fixed subject line and the same fields in the same order every time, so it can be found later.
It also helps to link the handoff to the quote and, later, to the invoice, so that anyone can follow the order from start to end. This is the same idea as a lead handoff from marketing to sales, one step further along the customer's path.
Review it quarterly
Once a quarter, take the last ten orders and ask two questions. How many came back with missing fields? What questions did operations still have to ask the customer? If the same question appears three times, add a field. If a field was empty or ignored on all ten, remove it.
If you are also looking for the slowest steps between teams, a short exercise to find the three slowest handoffs shows where this one stands.
Common mistakes
- Forwarding the whole email thread instead of writing the facts down.
- Letting the quote be the only document, so verbal promises are lost.
- Having several versions of the quote in circulation.
- Making the list so long that it is filled in carelessly.
- Letting operations start before the delivery address and date are clear.
- Not naming who answers questions after the handoff.
Summary
A good quote-to-order handoff is a short, fixed list of fields, filled in by sales, checked by one person in operations within a day, and kept in one place. Include what was promised, not only what was priced. Start with the nine fields above, send the next won deal in this form, and adjust the list after a quarter of real orders.
Sources
- Our related articles linked above.
- The field list and time frames are a working practice for small companies, not a formal standard; adjust them to your size, sector and contract terms. No client results or market figures are claimed in this article.
