If the rep requests it, start a new one-on-one document and share it with the rep and the future manager, according to GitLab.
Key takeaways
- Ask the rep whether they want a new shared one-on-one document before you change anything about the meeting routine.
- Keep at least two synchronous one-on-ones per month on the calendar, and treat an alternating format as an option rather than a requirement.
- Populate the agenda at least 24 hours ahead so both of you can add items before the conversation starts.
- Recover the rep's context from the CRM where it already lives: activity timelines, tags, and deal labels.
- Preserve the handover document as the shared record with the rep and the future manager.
Sales manager handover: prepare the rep's first conversation
Your first conversation with an existing rep after a manager change should recover what the rep already knows before you introduce a new routine. The rep's existing context lives in the meeting documents they used with the previous manager, the CRM activity they have logged, and the labels or tags already attached to their records. Your preparation is about locating that context, not rebuilding it.
Start with the document question: the rep's preference determines whether you open a fresh document at all.
Ask the rep directly whether they want a new document or want to keep working from the existing one. Some reps will have a running document with months of notes, goals, and action items. A new document can leave that earlier context behind unless you link to the old one or carry its items over. If they request a new one, share it immediately with both the rep and the future manager so everyone works from the same file.
The five steps that follow are the ones that matter most when you inherit a rep: choose the cadence, populate the agenda, recover development context, inspect the CRM, and keep the handover document with the rep. The document comes first, so the context you recover has a permanent home rather than living only in your notes or memory.
Choose synchronous meetings or an alternating format
Start by deciding how often you and the rep will actually meet face-to-face. According to GitLab, to avoid prolonged periods without face-to-face communication, it is preferable for the manager and their direct report to have a minimum of two regularly scheduled synchronous 1-1s every month, barring any PTO or leave from work. That is GitLab's recommended minimum, not a legal or universal requirement. It is the floor for your cadence, not a ceiling, and it explicitly accounts for the rep being out of the office.
You are not locked into the same format for every meeting. According to GitLab, for example, some managers schedule 1-1s on alternating weeks, with one week for synchronous meetings and the next week for asynchronous meetings. Treat that alternating pattern as one option among several, not as a requirement.
For your first conversation after a handover, the practical move is to put the two synchronous meetings on the calendar first, then decide whether an asynchronous week fits the rep's workflow. If the rep has PTO or leave coming up, the two-meeting minimum flexes around that absence rather than requiring you to reschedule around it.
Your next step: block the two synchronous 1-1s for the month, then ask the rep whether they prefer the alternating asynchronous week between them.
Populate the agenda and recover development aspirations
Before the meeting, consider populating the agenda to the 1-1 meeting at least 24 hours in advance of the meeting, according to GitLab. That window lets the rep add their own items rather than reacting to yours on the spot. For a fuller agenda structure, see Sales One-on-One Agenda for Coaching Software Sellers.
The agenda is not a static document you fill once and close. As items come up, they can add them in real time instead of waiting until 30 minutes before the meeting to scramble to fill in the agenda, according to GitLab. Encourage the rep to drop in topics the moment they surface — a customer concern after a call, a question about a deal, a request for help — so nothing waits for the next scheduled slot.
Your existing relationship is part of the context you are recovering. Since you are already having regular 1:1s with your team member you may have ideas regarding your team member's development aspirations, according to GitLab. If the previous manager kept notes on where the rep wants to grow, bring those into the agenda as discussion points. If no such notes exist, ask the rep directly what they are working toward and record it in the shared document.
A practical sequence: open the shared agenda, add the standing items you know belong there, then ask the rep to add anything they are carrying. Keep the document open during the meeting and add items as they arise.
Your next step: send the rep the agenda link at least 24 hours ahead and ask them to add anything missing before the meeting.
Inspect activity history and existing CRM labels
Before the first one-on-one, recover the rep's existing context from the CRM's documented locations rather than assuming the records contain what you need. For a wider view of activity tools, see Contact activity: 4 tools to check before coaching.
In HubSpot, when an activity is associated with a contact, company, deal, ticket, or custom object, the activity will appear in that record's activity timeline, according to HubSpot. You can also view the history of associated activities on a record or associate records with each other, according to HubSpot. Before relying on those timelines, check the association logic: in your activity settings, view the default association settings and customize the automatic association logic to better fit your business needs, according to HubSpot. Current settings only show the automatic logic going forward, so open the records' actual activity histories to establish which past calls and emails are associated.
For Freshsales, recover tag context from two documented spots. You can edit tags from the contact summary view, according to Freshsales. You can also edit tags and reorder them from the edit form, according to Freshsales. If you add or change tags while preparing, remember the save step: after adding the relevant tags, click the tick icon to save the tags to the record, according to Freshsales. An unsaved tag edit is not retained context.
For Pipedrive, find the rep's existing deal labels in two places. You can view your deal labels in list view under the label column, according to Pipedrive. In the deal detail view, you can view the assigned label in the Summary on the left-hand side of the screen, according to Pipedrive. Check both locations when you want to see which deals the rep has already categorized.
Pull the activity timeline, confirm the association settings, review the tags, and note the deal labels before the meeting.
Manager handover reference table by publisher
The table below collects the documented meeting practices and CRM context locations from each publisher, so you can see at a glance where to recover the rep's existing context.
| Publisher | Documented practice or location | Key action |
|---|---|---|
| GitLab (cadence) | Prefer a minimum of two regularly scheduled synchronous 1-1s every month, barring PTO or leave | Schedule the recurring synchronous meetings before changing anything else |
| GitLab (document) | If the rep requests it, start a new one-on-one document and share it with the rep and future manager | Ask the rep whether they want a new shared document before the first meeting |
| HubSpot | Activity appears in the record's activity timeline when associated with a contact, company, deal, ticket, or custom object | Check which activities are associated with the rep's records |
| Freshsales | Tags can be edited from the contact summary view | Open the contact summary to review existing tags |
| Pipedrive | Deal labels appear in list view under the label column | Open list view and read the label column for each deal |
Use this table as your starting checklist: confirm the meeting cadence with the rep first, then open each CRM location listed to see what context already exists before you populate the first agenda together.
Keep the requested handover document with the rep
A shared document preserves the context you are trying to recover: it becomes the record both of you can see, and it travels with the rep when the next manager takes over. Ask the rep directly whether they want a fresh document rather than assuming the old one carries over. Creating a new document does not itself discard existing notes, but link or copy the old items so nothing is left behind. If they say yes, create it before the first meeting so the agenda, notes, and development items land in one place the rep recognizes. Then confirm the future manager has access at the same time you share it with the rep, so the handover does not depend on a later permission change. Keep the document as the standing reference for every recurring one-on-one after that, and let the rep add to it between meetings.
Illustrative example: the first month after a handover
This example uses round, made-up numbers. A manager inherits a rep and asks whether the rep wants a new document. The rep says yes, so the manager creates it and shares it with the rep and the future manager. The manager puts 2 synchronous one-on-ones on the calendar for the month. At least 24 hours before the first one, the manager sends the agenda link and the rep adds 3 items: a stalled deal, a question about a customer, and a growth goal. The manager then opens the activity timeline and deal labels for those deals, so the conversation starts from what the rep has already logged. Afterward, both of them add notes to the shared document, and the next agenda starts from those notes rather than from a blank page.
Your next step today
Open the rep's current one-on-one document, or message the rep to ask if they want a new one, then list the CRM records you will check. For more on gathering this context, read Sales coaching prep: 5 steps to assemble rep context.
FAQ: first one-on-ones after a manager change
How do I prepare for a sales manager handover before the next rep one-on-one?
Ask the rep whether they want a new shared document, then share it with the future manager if they do. If the rep requests it, start a new one-on-one document and share it with the team member and the future manager, according to GitLab.
Does GitLab's suggested synchronous meeting minimum account for PTO or leave?
Yes. GitLab notes it is preferable for the manager and their direct report to have a minimum of two regularly scheduled synchronous 1-1s every month, barring any PTO or leave from work, according to GitLab.
When should the rep and manager populate the meeting agenda?
At least 24 hours before the meeting. Consider populating the agenda to the 1-1 meeting at least 24 hours in advance of the meeting, according to GitLab.
Which HubSpot settings should I inspect before relying on associated activity history?
The default association settings in your activity settings. In your activity settings, view the default association settings and customize the automatic association logic to better fit your business needs, according to HubSpot.
Where can I find the rep's existing Pipedrive deal labels?
In list view under the label column and in the deal detail view.