How to Hand Over a Sale to Delivery: A Practical Guide
A sales-to-delivery handover form is the document that transfers everything the sales team promised, and everything the customer expects, to the people who will actually deliver it. Most customer disappointment doesn’t come from bad delivery; it comes from delivery never hearing what sales agreed. This form closes that gap, in writing, before work starts.
When to Use This
Complete the handover for every won deal, as soon as the order or contract is confirmed, before delivery begins, not after problems appear. For simple product orders a short handover may be enough; for services, projects and anything custom, fill it in fully. No handover, no start: make it a rule that the delivery team doesn’t begin work until they’ve received and acknowledged the form.
How to Fill It Out
Customer and deal summary. Customer name, company, key contacts and their roles, plus what was sold and the total value. Example: “Copperline Foods, contract $28,800/year. Main contact: Hannah Reyes (Procurement Lead). Day-to-day contact: Jonah (assistant). Finance: Marcus Webb.”
What was promised. This is the heart of the form: every commitment sales made, written plainly. Scope, quantities, service levels, timelines, and any extras thrown in during negotiation. Example: “Weekly deep clean of 3 sites (schedule attached). 4-hour response guarantee on call-outs. Monthly hygiene report by the 5th. First clean: week of 1 Dec 2026. Free first-month reporting trial, agreed by Amara 26 Oct.” If it was promised, it goes here, including the verbal ones.
Key dates and milestones. Start date, delivery dates, review points, renewal date. Example: “Service starts 1 Dec 2026. First hygiene report 5 Jan 2027. Quarterly review meetings: Jan, Apr, Jul, Oct. Contract renews 1 Dec 2027 (90-day notice period).” Delivery can’t hit dates it doesn’t know about.
Pricing and billing details. What the customer pays, how they’re billed, and any special terms. Example: “$2,400/month, invoiced monthly in arrears, 14-day terms. Purchase order number: PO-8841. Invoices to marcus.webb@[example].com.” Billing surprises are relationship poison, get the details right now.
Customer quirks and context. Anything delivery should know that isn’t in the contract: site access rules, the customer’s pet peeves, internal politics, history. Example: “Site B: security gate, driver must call Jonah 30 min before arrival. Hannah is particular about the monthly report format, use the template she approved. Previous supplier lost the contract over slow response times; speed matters to them.”
Risks and watch-outs. Flag anything that could go wrong: tight timelines, dependencies on the customer, known concerns. Example: “December start is tight, equipment must be ordered by 10 Nov. Customer’s Site C has limited storage for our supplies; confirm arrangements before first clean.”
Handover meeting notes. Record that a handover conversation happened: date, who attended, questions raised and answers given. Example: “Handover meeting 30 Oct: Amara (sales) + Jonas (operations). Jonas confirmed schedule fits current crew capacity. Open question: Site C storage, Jonas to visit site 5 Nov.” The form plus a short conversation beats the form alone.
Acceptance. The delivery lead signs (or confirms in writing) that they’ve received the handover, understand the commitments, and accept responsibility from the agreed date. Example: “Received and understood, Jonas, Operations Lead, 30 Oct 2026.”
Common Mistakes
1. Handing over the contract but not the conversation. The contract says what’s legally agreed; it doesn’t say the customer is nervous after a bad experience with their last supplier, or that the finance director needs wooing. The context section is often more valuable than the paperwork.
2. Verbal promises that never make it onto the form. “Sales said we’d do the first month free”, where’s that written? If it’s not on the handover, delivery won’t know, the customer will expect it, and someone will have an ugly conversation. Every promise goes on the form, no matter how small.
3. No named owner on the delivery side. A handover addressed “to the team” is owned by nobody. Name the delivery lead who accepts it, and name the day-to-day contact the customer will deal with.
4. Skipping the handover meeting. Emailing the form and assuming it’s read is not a handover. A 20-minute conversation surfaces questions the form can’t, “wait, we can’t do Site B on Tuesdays”, while there’s still time to fix them.
Who Needs to Sign Off
The salesperson completes the form and the sales manager checks it’s complete and honest, particularly the promises section, which has a habit of being optimistic. The delivery or operations lead formally accepts it, confirming the commitments are deliverable as written. If anything in the handover looks undeliverable, it gets renegotiated with the customer now, not discovered mid-delivery. For large or complex deals, the business owner should see the handover before work starts.
How Often to Review and Update
Every won deal gets a handover, no exceptions, no matter how small. If the deal changes after handover (scope changes, new dates, added extras), update the form and re-confirm with the delivery lead; a handover that doesn’t reflect reality is worse than none. Quarterly, review a sample of handovers against delivery outcomes: where did surprises come from, and what should future handovers capture? That feedback loop is how handovers get sharper over time.
Download the free Sales-to-Delivery Handover Form.