5/10/2026

How to Write a Sales Handover Checklist for Departing Reps

Why the Deal Dies Even After the Contact List Changes Hands

A contact list only records who the person is. Deals close on what was already agreed, what was promised, and how the client likes to be treated. In short, how to write a sales handover checklist for departing reps is about giving reps leverage, not replacing them.

A departing rep hands over a spreadsheet. The successor opens client A and reads: "high intent, in follow-up." What the sheet doesn't say is that during the last negotiation round, the rep verbally promised a 10% discount plus a free one-year warranty extension if the order landed by month-end. The successor sends the standard quote at full price. The client screenshots the old chat and asks: "So what you told me last time doesn't count?" Three days later, that client shows up in a competitor's comparison table.

The hidden-information gap clusters into four categories: promises (free warranty extension, waived shipping, priority production slots), quote history (floor price, special discounts, competitor benchmark pricing), client preferences (only takes calls Wednesday afternoons, hates phone calls, must receive voice notes), and relationship maps (who actually signs off, who quietly blocks). Most of this lives in the departing rep's head or scattered across their personal WhatsApp threads. It doesn't travel with a handover, and it can't be explained in a five-minute walkthrough.

The cost is visible. The successor spends the first two weeks digging through chat history, guessing at context, and asking colleagues for background. The client, meanwhile, experiences slower responses and promises nobody honors. The 30 days after a handover is the highest-risk window for churn.

Beyond Contacts: The Four Categories That Must Be Written Down

A usable sales handover checklist isn't built around contact fields. It's built around four categories of hidden information. Every item needs a concrete field. "Good relationship" is not a field.

Category one: promises. List every verbal or written commitment, and each one needs four elements: what was promised, the validity window, the trigger condition, and who approved it. Example: "Order by March 31, 2025 for 10% off, approved by supervisor Zhang." If the promise was fulfilled, mark it "fulfilled." If it's still waiting on a trigger, mark it "pending." If it expired, mark it "expired" and note why.

Category two: quote history. Record every quote sent to the client, the final agreed price, and the reason for any discount. The reason matters most. "Competitor came in 5% lower, special approval to match" tells the successor how much room exists in the next round. For quotes that never closed, note the validity date and current status: client read but didn't reply, in internal approval, verbally declined.

Category three: client preferences. Communication channel (WhatsApp, email, or phone), response-time expectations (within two hours, or next day is fine), decision-maker personality (data-driven buyers want the spec sheet first; relationship-driven buyers want two minutes of small talk first), and topics to avoid (don't mention the competitor's former employee). Use short tags: "voice notes only," "no weekends," "send PDF before calling."

Category four: relationship map. Who plays which role inside the client's organization: decision-maker, influencer, potential blocker. Also note how close the departing rep was to each person. "Played golf with Mr. Wang twice, friendly" tells the successor what tone to strike on first contact.

How to Write It: A Reusable Handover Checklist Structure

The template doesn't need to be complicated. A shared spreadsheet handles it. Suggested columns:

Three rules for filling it in. First, every promise must be tagged "fulfilled / pending / expired" — no blanks allowed. Second, quote history must include currency and validity date, e.g. "USD 12,500, valid through April 15, 2025," so the successor doesn't negotiate off an expired number. Third, preference tags stay under six words for fast scanning.

The handover confirmation needs three signatures: the departing rep, the successor, and the direct supervisor. The signature means the rep owns the completeness of the list, the successor owns execution, and the supervisor owns oversight. The successor should reach out to every client within 24 hours with a handover note. Template: "Hi Mr. Wang, this is Li. I'll be handling your account going forward. The free training that Manager Zhang confirmed is already scheduled for Wednesday afternoon — does that time still work for you?"

The Three Moments Where Handovers Break Down

One week before departure: keyword sweep. Have the departing rep export chat history and search for commitment keywords: "guarantee," "free," "by month-end," "special approval," "requested." Cross-check each hit against the checklist for missed promises. Do this with the supervisor present — departing reps consistently underestimate which verbal promises mattered.

Last working day: consolidate pending follow-ups. Pull every open item into one list: "client said they'd reply Friday," "waiting on client to confirm sample address." Set a reminder for each. The successor should identify which clients need proactive contact within 48 hours so nothing stalls on a client's silence.

30 days after departure: weekly feedback review. The successor logs client feedback once a week and flags misunderstandings caused by an incomplete handover. When a client says "you promised free shipping, why am I being charged," that goes back into the template as a mandatory field for next time.

Turn Hidden Information Into a Team Asset, Not a Personal Memory

The practical problem: reps talk to clients on personal WhatsApp. When they leave, the chat history doesn't come along. Promises and quotes sit in private threads. Handover depends on memory and screenshots. Supervisors can't audit any of it because it lives on a personal device.

Sellenca runs as a Chrome extension layered directly on WhatsApp Web. Reps keep their numbers and their chat habits, but key conversations get captured automatically. It mines Q&A and messaging patterns from real closed deals into a company knowledge base that sharpens with use. Client profiles are built automatically with six-dimension segmentation — region, intent, client type, value, relationship, stage — so a successor opens a profile and sees the whole picture instead of starting from zero.

Reference numbers: the 365nails team recorded a 97% AI suggestion adoption rate, roughly 1,973 AI calls per month, 960+ client profiles, and 907 knowledge base Q&A entries. The point isn't the volume — it's that hidden information can be carried by a system instead of one person's recall.

Week One for the Successor: Three Non-Negotiables

First: verify every promise, one by one. Send each client a confirmation message. Template: "Mr. Wang, regarding the free training we committed to, I've confirmed Wednesday afternoon this week — does that still work?" The message isn't just a notification. It gets the client to confirm the promise still stands and gives the successor a natural opening.

Second: update quote history. Fill in validity dates for all open quotes in the shared sheet or in Sellenca profiles. If a quote has expired, reach out proactively to refresh it rather than waiting for the client to wave the old number in your face.

Third: match the existing communication rhythm. Adjust outreach to client preferences, and for the first three interactions, follow the departing rep's habits exactly. If the previous rep sent voice notes, the successor sends voice notes for the first three touches. Introduce a personal style only after the client has adjusted. Force a new rhythm too early and the client reads it as "everything changed when the rep did."

If you want to see how profiles and the knowledge base look in an actual handover scenario, book a demo and walk through the flow.

FAQ

What's the difference between a sales handover checklist and a regular contact list?

A contact list has phone numbers and deal stages. A handover checklist adds promises, quote history, and client preferences. The list answers "who is this client." The checklist answers "what was agreed, what was promised, and how do I pick this up." Without the second part, the successor starts from guesswork.

What if the departing rep won't cooperate with the checklist?

Run two tracks at once. On process: tie handover quality to the departure letter and the final month's performance review, and require all three signatures before the exit is complete. On tooling: use something like Sellenca to capture key information from chat history automatically, reducing dependence on individual cooperation. Even if the rep writes nothing, the knowledge base and client profiles already hold the baseline data.

How does a small team without a CRM handle handovers cheaply?

Use a shared spreadsheet with the template above, paired with a lightweight tool that builds profiles automatically. Sellenca costs $19 per seat per month, or $190 per seat annually — less than most CRMs, and it doesn't change how reps use WhatsApp. Run your team size through the pricing page to see the math.

If the client churns after the handover, who's responsible?

The checklist is signed by three parties, and the successor executes against it. If churn traces to a gap in the checklist, the departing rep and supervisor own it. If the successor didn't follow the checklist, the successor owns it. The key is judging "was the checklist complete" and "was it followed" as separate questions, so the discussion stays factual.

The point of a handover checklist is converting personal memory into a team asset. If you're managing a rep's departure right now, fill in one version of the template above first, then use a tool to backfill the promises and quotes buried in chat history. To see how Sellenca handles this in practice, start with pricing or book a demo.