{
 "name": "The Handoff Checklist",
 "edition": "2026-11-10",
 "read_date": "2026-11-10",
 "source": "https://whichclientportal.com/datasets/",
 "license": "CC BY 4.0",
 "cite": "Which Client Portal, Handoff Checklist, edition 10 Nov 2026, https://whichclientportal.com/datasets/",
 "description": "Twelve items that must pass from sales to onboarding: owner, moment, what passes.",
 "rows": [
  {
   "n": 1,
   "key": "deal-goals",
   "title": "Deal goals",
   "owner": "Account executive",
   "when": "Within one working day of closed won, before the kickoff invite is sent",
   "what_passes": "The result the buyer wants, quoted from a call or email.; The measure and today's baseline, if the buyer gave one.; The date the buyer expects to see the result, and why that date.; The person on the buyer side who will judge the result.; Where the goal was said: call date, email or document.",
   "failure": "The customer success manager runs a generic onboarding and measures against features delivered, so the buyer's own test of success is never checked until the renewal call."
  },
  {
   "n": 2,
   "key": "stakeholders",
   "title": "Stakeholders",
   "owner": "Account executive",
   "when": "At handoff, before the kickoff call",
   "what_passes": "Each person's name, title and role: signer, user, blocker, payer, technical owner.; Who is the day-to-day contact.; Who was involved late or came from a forward.; Who has been quiet since the last meeting.; The source for each entry: call, email or room view.",
   "failure": "The onboarding team emails the wrong person, misses the technical owner until week three, and learns of a blocker from the blocker."
  },
  {
   "n": 3,
   "key": "commitments",
   "title": "Commitments",
   "owner": "Account executive and sales manager",
   "when": "Before kickoff, and again at the first plan review",
   "what_passes": "Each promise in one sentence, with the person who made it.; The date it was made and where (call, email, proposal).; Whether it is in the contract or only said.; The date the buyer expects it.; Who on the delivery side now owns it.",
   "failure": "A promise that exists only in a seller's memory becomes a dispute at the first quarterly review, and the customer success manager hears of it from the customer."
  },
  {
   "n": 4,
   "key": "plan-history",
   "title": "Plan history",
   "owner": "Account executive",
   "when": "At closed won, with the final version frozen",
   "what_passes": "The plan as signed, with owners and dates.; Steps that moved and the reason each moved.; Steps done by the buyer, with dates.; Open steps carried into the onboarding plan.; Link to the live plan, not a screenshot.",
   "failure": "The onboarding plan starts from a blank page, and the buyer is asked again for dates it already gave."
  },
  {
   "n": 5,
   "key": "documents",
   "title": "Documents",
   "owner": "Account executive or sales engineer",
   "when": "At handoff, in the customer's space and not in the seller's inbox",
   "what_passes": "The signed order form and any statement of work.; Security questionnaire answers and the reports shared.; The proposal as presented.; Files the buyer uploaded during the sale.; Who may see each file, and who has seen it.",
   "failure": "The onboarding team asks the customer for a document the customer already sent to the seller, and the customer notices."
  },
  {
   "n": 6,
   "key": "go-live-date",
   "title": "Go-live date",
   "owner": "Account executive",
   "when": "At closed won, confirmed on the kickoff call",
   "what_passes": "The date, and whether it is a hard deadline or a hope.; The event behind the date: a launch, a renewal of another tool, a board meeting.; The tasks that must finish before it.; Who on the buyer side is accountable for it.; What the seller said about feasibility.",
   "failure": "The customer success manager sets a plan date from the delivery team's capacity, the buyer learns it at kickoff, and the first call becomes a negotiation."
  },
  {
   "n": 7,
   "key": "technical-requirements",
   "title": "Technical requirements",
   "owner": "Sales engineer",
   "when": "Before kickoff, with the buyer's technical owner named",
   "what_passes": "The systems involved and their versions.; The data to be loaded and who owns it.; The access the delivery team needs, and by when.; Security or legal steps the buyer must complete.; The named technical owner on the buyer side.",
   "failure": "The kickoff call finds that no one has asked the buyer's IT team for access, and a task that takes two days waits three weeks."
  },
  {
   "n": 8,
   "key": "risks",
   "title": "Risks",
   "owner": "Account executive and sales manager",
   "when": "At handoff, in writing",
   "what_passes": "Each open concern in one sentence.; The evidence: a call, an email or a missing person.; What would reduce it.; Who on the customer side knows about it.; Whether the buyer has seen it written down.",
   "failure": "The onboarding team finds the risk when it becomes a delay, and the seller who knew has moved to the next deal."
  },
  {
   "n": 9,
   "key": "champion-sponsor",
   "title": "Champion and sponsor",
   "owner": "Account executive",
   "when": "At handoff, with an introduction call booked",
   "what_passes": "The champion's name, role and how they helped the deal.; The sponsor's name and what they want to see.; How each prefers to be contacted.; The last meeting with each and the date.; A planned introduction to the customer success manager.",
   "failure": "The customer success manager meets the sponsor for the first time at the renewal, and the champion has left without anyone noticing."
  },
  {
   "n": 10,
   "key": "package-purchased",
   "title": "Package purchased",
   "owner": "Account executive or deal desk",
   "when": "At closed won, taken from the order form",
   "what_passes": "The plan name and term.; The number of seats or accounts.; Modules and add-ons, with any limits.; Any price or discount agreed outside the list.; Features promised that sit on a higher plan, if any.",
   "failure": "The delivery team builds the wrong template, or promises a feature the customer did not buy, and the first invoice dispute reaches the sponsor."
  },
  {
   "n": 11,
   "key": "integrations",
   "title": "Integrations",
   "owner": "Sales engineer",
   "when": "Before kickoff, with the order of connection",
   "what_passes": "Each system, the product's connector or API, and the plan that includes it.; The order of connection and the reason.; The owner on the buyer side for each.; Any connector the vendor lists on a higher plan.; What happens if one cannot be connected by go-live.",
   "failure": "The customer learns at week three that a promised connector sits on a higher plan, and go-live moves by the time it takes to buy it."
  },
  {
   "n": 12,
   "key": "conversation-history",
   "title": "Conversation history",
   "owner": "Account executive",
   "when": "At handoff, summarized and linked",
   "what_passes": "Call summaries for each key meeting, with dates.; The objections raised and how each was answered.; Questions the buyer asked that the seller could not answer.; Emails that changed the scope or price.; Where the recording is, if one is kept.",
   "failure": "The customer success manager asks questions the buyer already answered three times, and the buyer concludes that no one on the vendor side talked to each other."
  }
 ]
}