Sales to Implementation Handoff Template
Three documents and two sheets that capture what got promised on the sales calls, not just what got written into the contract.
Free download · No account needed
Commitments Made · review of 14 closed-won deals, one vendor
13 commitments never made it into the contract. 3 of 5 affected deals still escalated.
| Read | Count |
|---|---|
| Statements across the calls that read as commitments | 27 |
| Beyond standard behavior | 18 |
| Already in the signed contract | 5 |
| Spoken only, never written anywhere | 13 |
What happened next
| Deals | Escalated within 30 days of kickoff |
|---|---|
| 5 deals with an unwritten commitment | 3 of 5 |
| 9 deals with none | 0 of 9 |
Checked individually, 9 of the 13 were fine. Only 4 were not, and none sounded worse on the call than the ones that were.
Every reachable result for this query already lists the same six things: an account summary, a stakeholder map, the promised scope, open risks, action items with owners, and links back to the call recordings and the signed contract. Several point out that promised scope should come from the SOW. None of them separately reads the calls themselves for what got said beyond what got written, because a signed contract legally supersedes spoken terms and nothing about closing a deal forces anyone to reconcile the two.
Checked against a review of fourteen closed-won deals for one vendor, the gap is real. Twenty-seven statements across those calls read as commitments; eighteen went beyond standard behavior, and thirteen never made it into the contract. Deals carrying at least one of the thirteen escalated within thirty days of kickoff, citing an unmet promise, in three cases of five; deals with none escalated for that reason in zero of nine. Contract law treats this as settled: a complete written agreement supersedes prior spoken terms, so nothing in the paperwork was ever going to catch it.
Built for whoever runs implementation once the mutual action plan has closed and the signature chain has cleared. It reads the calls that plan never touches. A buyer's own vendor setup, handled separately in the onboarding-forms register, and a deal that closes and is never reopened for review, covered in the post-mortem, sit on either side of this one. This space starts the day the contract is signed and finishes when the kickoff package is ready to send, nothing earlier and nothing later.
What's in the pack
Check Every Promise Before Kickoff
The method itself: sort every call statement as already true, already written, or neither, and route every "neither" to a named owner.
Commitments Made doc
The full record for one deal: every promise-shaped statement, its source call, and how it resolved once a real owner checked it.
Requirement to Delivery Map sheet
Contracted scope and confirmed commitments in one place, with an owner and a target date on every row.
Stakeholder Register sheet
Who is who on both sides, and which specific commitment or deliverable each person actually cares about.
Handoff Brief doc
The one document the implementation team reads before their first call, pointing to the rest rather than repeating them.
Risk Note doc
Anything confirmed undeliverable or delayed, with a specific recommendation for how to raise it before kickoff, not during it.
How it works
- 1
Send the call record
Discovery, demo and negotiation transcripts or notes, plus the signed contract or SOW.
- 2
River sorts every statement
Already true, already written, or neither, checked against the contract rather than assumed.
- 3
Route what's left to a named owner
Product, engineering, delivery or finance confirms each one, on the record, before kickoff.
- 4
Get the kickoff package
Brief, delivery map, risk note and stakeholder register, ready before the first implementation call.
Frequently asked questions
Is this template free?
Yes. Three Word documents and two CSV sheets, downloaded as a zip, no signup. River is the optional half: it reads your own call record, sorts every commitment, and routes what needs a decision to whichever internal owner can actually confirm it.
Why would an experienced rep promise something that was never in the contract?
Because the rep already knows what is standard, roadmapped or true of a competitor, and that private knowledge makes it hard to guess what an uninformed delivery team actually needs spelled out, a pattern documented as the "curse of knowledge". Checking with a named owner closes the gap; assuming the rep would have flagged a real problem does not.
Isn't this the same as tracking scope creep?
No. Scope creep is a new ask that surfaces during delivery and has to be negotiated. This is the opposite: a promise already made before the contract was signed, that nobody wrote down. The fix is reading the record that already exists, not negotiating anything new.
How is this different from the mutual action plan?
They run in sequence. The mutual action plan plans and tracks the path to signature, and treats the buyer's own process as the steps to decompose. This starts the day the contract is signed and reads the same calls for the opposite thing: promises made about delivery, not steps taken toward it.
What if the call transcripts are incomplete or messy?
Send whatever exists, notes, a partial transcript, an email recap. River flags any stakeholder or call referenced but never provided rather than guessing at what was said. A commitment nobody can actually source stays marked unreviewed instead of being sorted as though the record were complete.
Does this replace a formal handoff meeting?
No, it prepares one. A meeting where the delivery team is hearing a commitment for the first time from the customer's own mouth is the failure this space exists to prevent. Bring the Handoff Brief to the meeting instead, and the meeting becomes confirmation rather than discovery.
Find out which of your own promises never made it into the contract
Send the call record and the signed agreement. Every commitment gets sorted and routed before your next kickoff call.
Edit with AI