Enablement-to-Manager Handoff Protocol: Five-Artefact Template

How to use this pack

Enablement completes Artefacts 1-5 before the handoff meeting. The manager reviews them before that meeting, not in it. The meeting itself is for questions and commitment, not for reading.

Print or share as a single document. Every grey instruction block is for enablement. Every "Manager obligation" box is for the manager. Delete the instruction blocks before filing.

---

Artefact 1: Competency-Level Skill-State Snapshot

Purpose: A granular picture of where the rep actually is across core selling competencies at point of handoff. Not pass/fail. Not a compliance record. A coaching-grade assessment.

Enablement instructions

Score each competency on the scale below. Base every score on observed evidence, not self-report. If you have no observed evidence for a competency, mark it NE (not evidenced) and note why. Do not leave blanks and do not guess.

Rating scale:

• 4 - Ready: Demonstrated consistently, under real or realistic pressure, without prompting.
• 3 - Capable: Demonstrated reliably in controlled conditions. Needs live repetition to consolidate.
• 2 - Developing: Partially demonstrated. Scaffolded support still required.
• 1 - Not yet: Not observed at required standard.
• NE - Not evidenced: No opportunity to assess. Flag for manager to assess in weeks 1-2.

Enablement sign-off: Completed by: [Name] Date of final assessment: [Date] Bootcamp / programme completed: [Name and dates]

---

Manager obligation, Artefact 1 Read this before the handoff meeting. Mark any NE rows where you plan to create an early observation opportunity. Do not assume NE means "fine, we'll see." It means the gap is unquantified and is your first diagnostic task.

---

Artefact 2: Ranked Coaching Focus for Days 60-90

Purpose: Tells the manager which competencies to prioritise after the rep has settled, based on what enablement observed during the programme. Prevents the manager defaulting to whichever issue is loudest in week one at the expense of the more important developmental gaps.

Enablement instructions

List no more than three coaching priorities for days 60-90. Rank them 1 (most important) to 3. For each one: name the competency, describe the observed failure mode in plain language, and suggest one or two coaching methods that fit the gap.

Failure mode naming guidance: Be specific. "Struggles with objection handling" is not useful. "Concedes on price immediately when the buyer goes quiet, before any attempt to re-anchor on value" is useful.

When NOT to include something here: Do not list a competency as a 60-90 priority if it is actually a blocker right now. Blockers belong in Artefact 1 as a week 1-4 priority, not here.

---

Manager obligation, Artefact 2 Incorporate these priorities into the rep's development plan by end of week two. If you disagree with a ranking, contact enablement before overriding it. Override without discussion is a common failure mode and erodes the point of the handoff entirely.

---

Artefact 3: Live Ramp Plan Handover

Purpose: Transfers ownership of the ramp plan from enablement to the manager in a way that preserves continuity and prevents the plan being quietly shelved.

Enablement instructions

Complete the header fields. Paste or link the current version of the ramp plan. Mark every milestone as either "Enablement-owned until [date]" or "Manager-owned from [date]." Where milestones are shared, name who holds the pen.

Header fields:

• Rep name: [Name]
• Start date: [Date]
• Handoff date: [Date]
• Ramp target (attainment milestone and date): [e.g. 80% of quota by end of month 4]
• Current milestone status: [On track / At risk / Behind, with one sentence of context]

Shared edit conventions:

• Changes to milestone dates must be agreed by both manager and enablement in writing (email is fine).
• If the rep is tracking more than two weeks behind plan, enablement must be notified within 48 hours.
• The plan is a live document. "We talked about it" is not an update.

Ramp milestones table (populate with your standard ramp milestones):

---

Manager obligation, Artefact 3 Accept formal ownership of the ramp plan at the handoff meeting. If a milestone is already at risk, say so in the meeting. Do not inherit a plan you have not read. If you have questions about how a milestone was set, ask enablement before the rep's first day on patch.

---

Artefact 4: Suggested First Development 1:1 Agenda

Purpose: Gives the manager a ready-to-run agenda for their first structured development conversation with the rep. The first 1:1 is usually admin-heavy. This keeps development on the table from day one.

Enablement instructions

Populate the bracketed fields. This agenda is a suggestion, not a mandate. The manager should adapt the questions to their style. What matters is that the structure exists.

---

First Development 1:1 Agenda Recommended: week two, after the rep has had at least three live customer interactions. Duration: 45 minutes.

Opening (5 min) "I want to use some of our 1:1 time to focus specifically on your development, separate from pipeline reviews. This is one of those conversations."

Section 1: Rep self-assessment (15 min)

• "What felt hardest in your first calls this week?"
• "Where did you feel you were working from instinct rather than a clear approach?"
• "What do you want to get better at first?"

Section 2: Manager observation share (15 min) Share one specific observation from Artefact 1 and one priority from Artefact 2. Frame it as: "Here's what I noticed during your onboarding programme, and here's what I want to focus on with you over the next 60 days. Does that land?"

Do not share all of Artefact 1 in one sitting. One competency per conversation.

Section 3: Commitment (10 min)

• Agree one specific development action for the next two weeks (observable, not aspirational).
• Book the next development 1:1 before leaving this one.

Close (5 min) "Anything you need from me that you haven't got yet?"

---

Manager obligation: Artefact 4 Run this agenda, or a version of it, in week two. Do not wait until the rep "settles in." The first development 1:1 sets the tone for whether the rep treats coaching as normal or as a reaction to underperformance.

---

Artefact 5: Pre-Calendared 30-Day Post-Handoff Check-In Commitment

Purpose: Creates a structural commitment between enablement and manager to review ramp progress at day 30. Pre-calendared means both parties have agreed the date before the handoff meeting ends.

Enablement instructions

Complete the fields below and confirm the calendar invite is sent before the handoff meeting closes.

Check-in details:

• Date: [To be agreed at handoff meeting, calendar invite sent same day]
• Attendees: [Enablement lead] + [Manager]
• Duration: 30 minutes
• Location / call link: [Fill in]

Agenda for the 30-day check-in (do not change this structure):

What triggers an earlier conversation:

• Rep misses a ramp milestone by more than two weeks.
• Manager identifies a competency gap not flagged in Artefact 1.
• Rep flags a concern about their own readiness.

Any of the above overrides the 30-day timeline. Contact enablement immediately, not at the scheduled check-in.

---

Manager obligation, Artefact 5 Accept the calendar invite before the handoff meeting ends. If you reschedule, you own rescheduling within five working days. Cancellation without rescheduling is a protocol breach and should be escalated to sales leadership.

---

Protocol sign-off

Both parties sign (or confirm by email) that the five artefacts have been reviewed and obligations are understood.

---

Common failure modes

The thinking behind this

The Handoff From Onboarding to Manager Is Where Most Ramp Plans Actually Break is the argument this resource puts to work.