What goes in a sales handover document when a tech rep leaves?

This method covers the technical history of each customer account: site conditions, documents sent and promises made. It does not cover contract assignment, commission, non-compete terms or the data protection rules for a leaver's personal data, which your HR and legal teams decide under your own jurisdiction.

What do you need before a technical sales rep's customer accounts are handed over?

Before a technical sales rep's customer accounts are handed over, you need a confirmed last working day, a named successor for every account, and access to every place the rep kept customer records. Agree the last working day first, because every later step has to finish while the rep can still explain what a note or an attachment means.

List the record places for this rep. A typical list covers the CRM, the rep's mailbox and sent mail, personal and shared drive folders, the phone used for site photos and messages, paper notebooks, and any spreadsheets of readings kept outside a shared system (illustrative list). Ask the rep to add places you did not think of.

Secure access before the account is closed. In Microsoft 365, a removed employee's mailbox data is retained for 30 days after the account is removed, and after 30 days the data is permanently removed, unless a hold was applied to the mailbox before the account was deleted (Microsoft, 2026). In Google Workspace, an administrator can transfer the files a leaver owns to someone else in the organization so they are saved before the account is deleted (Google, 2026). Ask your IT team which of these applies to you and set it up before the last working day.

Handing over customer accounts, step by step

Handing over a technical rep's customer accounts takes five steps, and each step produces one record per customer account that the successor keeps.

1. List the accounts. Pull every customer the rep served from the CRM and from the sent mail of the last 12 months (illustrative window), and give each one row with its successor's name.

2. Collect the site history. For each account, write down the sites, the equipment and process each product serves, the products in use, the last measured values with date and unit, and any open problem.

3. List the documents already sent. Record each quotation, technical data sheet, safety data sheet, certificate, trial plan and report sent to the customer, with its version or date and where the copy now lives.

4. List the open commitments. Record every promised action with its date, the customer contact it was promised to, and the evidence: an email, a visit report or a meeting note.

5. Introduce the successor. Hold one joint call or visit per key account before the last working day, walk the customer through the open commitments, and confirm the contact list with them.

Store all five records where the successor's team can open them, not in the departing rep's personal folders.

Why does a customer's site history disappear when a technical sales rep leaves?

A customer's site history disappears when a technical sales rep leaves because most of it was never written into a shared record: it sits in the rep's mailbox, personal folders, phone and memory. The CRM holds the contact, the deal and the order, while the reasons behind them stay with the person.

Site history is the technical context that explains each account. It includes why the customer moved to the current product, which concentration or dosing rate the plant settled on, which machine gave trouble, and which trial failed and why (illustrative examples). A rep collects this over years of visits and calls, and much of it lives in email threads with attachments, photos on a phone, and notes that only the author can read.

When the rep's account is removed, the mailbox and files follow the company's retention settings, not the customer's needs. Microsoft 365 permanently removes a deleted user's mailbox data after 30 days unless a hold was applied first (Microsoft, 2026). Even when the files survive, a successor who does not know which thread holds the agreed dosing rate cannot find it quickly. The wider cost of a technical person leaving is covered in when your best technical person leaves; the steps here limit that loss for customer accounts.

Which technical history does a sales handover document template miss?

A sales handover document template usually misses the site conditions per customer, the documents already sent with their versions, the promises made with dates, and where each record lives once the rep's mailbox closes. Published templates are written for a sales-to-service handover at the start of a customer relationship, not for a technical rep leaving an account they have served for years.

The difference shows in what each handover has to carry. A new customer has little history, so a template that records goals, contacts and contract terms covers most of it. An established technical account has a history of conditions, trials, complaints and agreed settings, and the successor needs that history to give the same advice the rep gave. A template built for the first case leaves those rows empty, and nobody notices until the customer asks about a past trial.

The table below compares what published handover templates list with what a technical account needs.

The site conditions row matters most: without it the successor learns the plant from scratch, and the customer repeats the history the rep already knew. Add the three missing rows to whatever handover template your team already uses rather than starting a new form, so the commercial fields and the technical history sit in one document per account.

How do you record the documents and commitments a departing rep made to each customer?

Record the documents and commitments a departing rep made to each customer as two lists per account: one row per document sent and one row per open commitment, each pointing to a copy the company holds. A list that only names a document is not enough if the copy stays in the rep's mailbox.

For documents, search the rep's sent mail by customer domain and attachment, and record the document type, title, version or date, the date sent and the contact it went to. Move each copy into the customer's shared folder or account record. Where two versions of a technical data sheet went to the same customer, note which one the customer is working from.

For commitments, read the last visit reports, meeting notes and sent mail for promised actions: a trial, a sample, a report, a price review or a follow-up visit (illustrative examples). Write each one as an action with a date, the contact it was made to and its evidence, then ask the rep to confirm the list and add promises made by phone or in person.

ISO 15489-1:2016, which remains current, applies to the creation, capture and management of records regardless of structure or form (ISO, 2016). Treat these two lists as records of that kind: they belong to the company and need an owner after the rep leaves.

How do you check that a customer account handover is complete?

A customer account handover is complete when the successor can find each customer's site history, sent documents and open commitments without asking the departing rep. Run the check table below per account, ideally with the rep still available to fix any failed row.

Check the records as the successor will use them, not as the rep describes them. Ask the successor, or a colleague who never served the account, to open each record and answer three questions from it: what the customer runs, what was last sent, and what is owed next. A record that only the rep can interpret fails the check, even if every field is filled.

The documents sent row fails most often, because the copy that matters is an attachment in a sent mail thread that disappears with the mailbox. Fix failed rows in order of risk: open commitments with a near date first, then documents the customer may ask about, then site conditions for accounts with no visit planned soon. Record the date the check passed for each account.

When should you bring in a manager or specialist about a customer account handover?

Bring in a manager or specialist about a customer account handover when the rep leaves without a notice period, when a key account has open technical problems, or when a commitment touches price, warranty or product performance. Each case needs a decision the successor should not make alone.

A departure without notice turns the handover into a search of the mailbox and files, so ask IT to apply a hold or transfer the files before the account is deleted. An open technical problem needs a technical specialist at the first successor visit, because the customer will judge the change of rep by how that problem is handled. A promise on price, warranty or performance can bind the company, so the commercial or technical manager should confirm it before the successor repeats it to the customer.

Long-term, the cheaper fix is to keep customer records under the customer rather than under the person. In Lubinpla, the customer account screen keeps contacts, notes, outputs, projects and work logs together under one customer, so they stay with the company when a rep leaves. Whatever system you use, the test is the same: a new rep should be able to read one account's history in one place.