Handover Checklist for Field Sales: What to Include

A field sales handover checklist is a written transfer document that should move six core areas from the outgoing representative to the incoming one: territory and route coverage, store and customer contacts, commercial commitments, open orders and stock questions, unresolved store issues, and next visit dates and tasks. It should also cover access and tools, and it should end with a manager sign-off that spot-checks a sample of outlets. Complete it before the outgoing representative’s final working day, confirm priority outlets through joint visits, and accept the handover against evidence rather than a verbal briefing.

The same logic applies whether the representative works for a distributor or directly for the manufacturer, and whether the team records visits on paper, in a spreadsheet or in sales force automation (SFA) software. SFA can hold part of the record, but the checklist remains a management process: system data supports the handover, it does not replace an acceptance check.

What a field sales handover must cover

A handover is more than a contact list. Six core areas decide whether the incoming representative can trade from the first week, with access and tools as a practical addition.

• Territory and route: the outlet list with store identifiers, channel type, route day, call frequency and coverage targets, plus any outlets that are currently unassigned.
• Contacts: outlet owner or manager names, phone numbers, buying contacts at chains, and the distributor or van-sales contacts the representative deals with weekly.
• Commercial commitments: agreed prices, trade terms, promotions in flight or scheduled, display or shelf agreements, and credit or returns arrangements. These are usually business-level commitments, not personal ones.
• Open orders and stock: orders submitted but not delivered, backorders, pending returns or exchanges, and stock questions the outlet has raised.
• Unresolved store issues: out-of-stock on core lines, planogram or fixture gaps, damaged or near-expiry stock, disputed invoices, and anything promised to the outlet that has not been delivered.
• Next visit dates: the planned visit date for each priority outlet, the task for that visit, and who is responsible for confirming it.

Field sales handover checklist

Use the table below as the master document. Give every row an owner and a due date, and attach the supporting file or system export. Rows that cannot be completed should be logged as exceptions rather than left blank.

For a store-level issue, record what the outlet was told and by whom. An illustrative entry might read: promotion agreed for the next cycle, material not yet delivered, outlet expecting confirmation before ordering. That level of detail is what lets the incoming representative continue the conversation without contradicting a commitment.

How to run the handover: sequence and responsibilities

The sequence matters more than the format. A short, evidence-based handover beats a long verbal briefing.

1. Prepare the data (outgoing representative, sales operations). Freeze the outlet list, export open orders, compile commitments and build the issue log with dates and aging.
2. Rank the outlets (field manager). Identify the outlets that carry most of the volume or the most unresolved risk, and schedule joint visits for those first.
3. Run joint visits (outgoing and incoming representative). Introduce the incoming representative at priority outlets and confirm contacts, commitments and open issues face to face.
4. Walk the exception list (field manager). Resolve or formally accept every outlet with no recent visit record, no named contact or an open dispute.
5. Set the forward plan (incoming representative). Publish next visit dates and tasks for priority outlets, with the manager reviewing coverage against the call frequency target.
6. Sign off (field manager). Accept the handover only after the sample check described below.

Manager acceptance questions

Acceptance should be a short, repeatable test rather than a general impression. Ask the incoming representative to answer these without looking at notes, then verify the answers against the record.

• Which five outlets generate the most volume in this territory, and when will you visit each one?
• Which outlets have an unresolved issue, and what is the next action and date for each?
• Which promotions or trade terms are currently agreed with outlets, and who approved them?
• Which orders are open, and what does the outlet expect to receive?
• Which outlets have not been visited recently enough, and what is your catch-up plan?
• Who are your daily contacts at the distributor, and who signs off stock or returns issues?
• Where does the record disagree with what the outlet told you, and how will you resolve it?
• What is missing from this handover that you still need, and who will provide it by when?

A practical sample check is to select five outlets, confirm the contact and next visit date for each, and reconcile open orders against the order list. Discrepancies become exception items with an owner, not reasons to delay the whole handover.

Common handover mistakes

• Transferring a contact list with no commitments, so the incoming representative unknowingly contradicts an agreed price or promotion.
• Leaving unresolved store issues undocumented, which pushes the same complaint to a new person without context.
• Handing over without next visit dates, which turns coverage into guesswork in the first weeks.
• Treating a check-in photo as proof that a task was completed, instead of asking for time, store, task and review status.
• No exception rule for outlets with a missing or stale visit record, so gaps stay invisible.
• Accepting the handover verbally, with no sample check and no named owner for each open item.

Distinguish generic practice from verified software support

Handover quality depends on two different things, and teams often blur them.

• Generic field practice: a written checklist, joint visits to priority outlets, an issue log, and a signed acceptance. These work with paper, spreadsheets or any system.
• Software support: whether the software can list outlets by owner, show the last completed visit, carry open orders and outstanding tasks, and move outlets to a new representative. Availability depends on the implementation, so ask for a demonstration with your own sample stores.

Airpalm publicly describes mobile visits, route planning, store audits, sales orders, inventory and promotion management (source: airpalm.com, checked 2026-10-09). Those capability areas can hold records that a handover needs, such as outlet lists, visit history and orders. That public description does not confirm a dedicated handover workflow, specific export formats, permission rules or offline behaviour, so treat those as items to verify rather than assume.

Questions to ask before relying on system records

• Can we produce an outlet list by representative, with last visit date, last order and any outstanding task?
• What happens to open tasks and orders when an outlet is reassigned to another representative?
• Which fields are mandatory when a visit is closed, and who can edit them afterwards?
• For each piece of visit evidence, does the record carry a time, a store, a task and a review status? A photo or check-in alone does not show that a task was done correctly.
• Can we define an exception rule for outlets with no recorded visit inside the expected call frequency?
• Which roles can see the outgoing representative’s records after the account is closed or transferred?

Where Airpalm fits

A handover works best when outlet lists, visit history, tasks and orders live in one place rather than in one person’s notebook. Airpalm publicly describes mobile visits, route planning, store audits, sales orders, inventory and promotion management — capability areas that can hold handover-relevant records such as which outlets belong to a territory and when each was last visited. See airpalm.com for the public description.

Before choosing software for this purpose, request a demonstration using sample outlets, visits and orders from your own territory, and ask the verification questions above about reassignment, required fields and evidence status. If handover record-keeping is part of your evaluation, contact Airpalm with the checklist items you need to support.

Frequently asked questions (FAQ)

How long should a field sales handover take?

There is no single correct duration; it depends on territory size, the number of priority outlets and how many unresolved issues exist. A practical approach is to start data preparation well before the outgoing representative’s final working day, run joint visits for priority outlets, then hold a short acceptance check with sample outlets. The acceptance test, not a fixed number of days, tells you whether the handover is complete.

Should the incoming representative inherit the previous representative’s commitments?

Commitments made to outlets and distributors are normally business-level rather than personal, so the incoming representative is expected to honour them. Confirm that expectation with the field manager and whoever approves trade terms or promotions, and record every commitment with its approval source so there is no dispute later.

What if system records conflict with the outgoing representative’s own spreadsheet?

Treat both as inputs, not as a verdict. Reconcile the outlet list, open orders and visit dates side by side, then log each difference with an owner and a resolution date. Where the outlet’s own account differs from both, verify with the outlet during a joint visit. Logging exceptions is more reliable than delaying the handover until everything matches.

Do you need SFA software to run a field sales handover?

No. The checklist, joint visits, issue log and manager acceptance work with paper or spreadsheets. Software helps when outlet ownership, visit history, tasks and orders need to be reassigned and reviewed at scale, but the accuracy of those records still depends on required fields, permissions and review status being defined and checked.