What it means
A salesperson promises a launch in six weeks, and delivery learns after signature that the customer also expects two complex integrations. A scope handoff should surface such facts before the project team begins promising dates.
Start with the accepted contract, order form and final proposal, not a sales summary alone, because earlier drafts can contain terms later removed while verbal expectations may still need clarification. Estii's services handover guidance stresses shared understanding among sales, delivery and customer, and recommends involving delivery before close where possible, since a late handoff may be too late to price a hidden requirement.
Map deliverables, exclusions, milestones, dependencies and acceptance criteria, so that each item points to the agreed source or is labelled an open question. Atlassian's implementation-plan guidance discusses translating goals into actions, roles and timelines, and the handoff supplies the verified inputs that such a plan requires.
An illustrative scope confirmation rate is signed engagements whose key deliverables and dependencies have delivery-owner acknowledgment before kickoff divided by all signed engagements due to start, so if 18 of 20 qualify the rate is 90%. Record customer responsibilities such as data access, approvals and staff availability, because these can determine whether a promised timeline is realistic and an internal assumption is not a customer commitment unless accepted.
Keep commercial limits visible, including hours, site count, usage caps and change-order terms, so a team does not discover a margin boundary only after doing extra work. List open risks with owners, since a missing API specification or uncertain permitting requirement may be manageable but hiding it under a "green" handoff is not.
Define the customer contacts, because project sponsor, operational lead, approver and billing contact may be different people and assigning the wrong decision-maker causes avoidable delay. Check differences between quote and contract, as a discount may have been granted in exchange for reduced support or a milestone moved, and the latest accepted document governs.
Preserve the sales relationship context appropriately, because a customer's reason for buying can help delivery focus, though confidential comments outside the project need not be circulated widely. Invite delivery challenge before kickoff so the receiving lead can question capacity and feasibility rather than sign off under pressure.
Document unresolved conflicts: if sales notes say "custom report included" while the contract excludes it, do not silently pick one, but clarify through the proper customer or commercial process. Separate handoff from amendment, since a handoff document cannot add new services to the agreed contract and new scope needs the authorised commercial change path.
Track readiness for the first milestone with owners and dates for equipment, access, training and customer inputs, restate the agreed scope and dependencies to the client in plain language at kickoff, and give the receiving team a named escalation path for decisions discovered afterwards. Measure rework, missed milestones and disputed invoices after delivery, keep one central link to authoritative documents rather than several conflicting spreadsheets, and remember that for an owner a good handoff is the moment a sale becomes a deliverable plan without losing the customer's actual agreement.
In practice
Real-world examples.
Example
A systems integrator signs 20 engagements in a quarter, and 18 have delivery-owner acknowledgment of scope and dependencies before kickoff. The two without acknowledgment are held for a review call, and kickoff dates are not promised to those customers until the gaps are closed.
Example
A software vendor's sales notes mention a custom integration, but the signed order form does not list it. The delivery lead flags it as an unconfirmed item, asks sales to clarify with the customer, and does not assume it is included.
Example
A delivery lead for a training business checks the final signed terms against a superseded sales draft. The draft offered ten sessions, the signed agreement says eight, and the project plan is built on eight.
Formula
Calculation
Scope confirmation rate = engagements with delivery acknowledgment before kickoff / engagements due to start x 100.
Worked example. In a quarter, 20 signed engagements are due to start and 18 have delivery-owner acknowledgment of key deliverables and dependencies before kickoff.
- Scope confirmation rate = 18 / 20 x 100 = 90%.
A value-weighted view can tell a different story. If the 20 engagements total $1,000,000 in contract value and the 2 unconfirmed ones total $150,000, the acknowledged engagements are worth $850,000, so the value-weighted rate is $850,000 / $1,000,000 x 100 = 85%. The lower figure shows the unconfirmed engagements are larger than average and deserve attention first.Case study
Seen in the real world.
In this entirely fictional example, Maple Services catches a customer expectation for an extra dashboard during the handoff. Sales and delivery compare the signed scope, clarify the request with the customer and use the agreed change route before building it. The internal handoff does not quietly rewrite the contract.
Maple then adds a short readiness check to every kickoff: named customer contacts, data access dates, open risks with owners and a list of exclusions restated in plain language. Within two quarters the delivery team reports fewer surprise requests in the first month, though the company treats that as an observation to keep testing. The company and events are invented.
Watch out
Common mistakes.
- Using an old proposal when the final agreement changed scope.
- Treating a receiving-team signature as proof customer assumptions were confirmed.
- Adding work in an internal handoff instead of using the authorised change process.
Questions
People also ask.
When should delivery join the process?
Early enough to test material scope and feasibility before kickoff, ideally before close for complex work.
Does a handoff change the contract?
No. It transfers the accepted agreement and flags changes for the proper process.
What if documents conflict?
Keep the gap open and clarify it rather than silently choosing one version.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%