The Handoff From Onboarding to Manager Is Where Most Ramp Plans Actually Break

Most ramp post-mortems are archaeology. Someone pulls the data six months after a rep missed quota, traces back through the onboarding calendar, and concludes the problem was week one product training or a certification gate that didn't stick. That diagnosis is almost always wrong, or at least incomplete. The failure point isn't usually in the formal programme. It's in the gap between when enablement stops owning the rep and when the manager starts, which is a structural seam that almost no organisation has actually designed. It just exists, like a load-bearing wall nobody put on the plans.

What the seam looks like in practice

Enablement runs a structured programme, typically six to ten weeks, with a curriculum, milestones, and some form of certification. It's deliberate work. The rep gets assessed on product knowledge, call structure, and objection handling. There's a graduation moment, sometimes literal. Then the rep moves to the floor, joins the team standup, gets added to the pipeline review, and the manager's mental model of them begins.

That mental model starts from almost nothing useful.

The manager gets a name, a start date, and maybe a Slack intro. What they don't get: a skill-state snapshot. Not a summary of "passed all modules", which is a compliance record, not a development picture. A real snapshot: where this person is strong, where they are brittle, what was observed in their practice calls, what the enablement team is genuinely worried about, and what the first sixty days of manager-led coaching should focus on. That document almost never exists, and if it does, it rarely gets read before the first one-to-one.

So the first manager one-to-one after onboarding is a pipeline check. Because that's what managers do in one-to-ones when they don't have a better frame. It's not laziness; it's the default filling a vacuum.

What gets lost at the seam

Three categories of information evaporate at handoff.

Observed skill gaps that weren't certification blockers. Certification gates are binary. The rep either passes or repeats the module. But plenty of meaningful signal sits below the gate: a rep who technically passed discovery call certification but consistently skips commercial qualification questions; a rep whose demo is strong but who collapses under pushback. Enablement saw it. It lived in a facilitator's notebook or a coach's memory. It doesn't travel.

Confidence and self-efficacy data. A rep can know the methodology and still be genuinely frightened of the phone. That shows up in role-play debrief notes, in the questions they asked, in where they stalled. The manager, seeing someone who certified, assumes readiness. The rep performs compliance and masks the anxiety. This is one of the cleanest predictors of a slow start, and it is almost never handed over.

The ramp plan itself. The 30-60-90 the rep signed off on during onboarding often becomes a historical document rather than a live tool. The manager has their own operating rhythm. They're not going to subordinate their pipeline cadence to a ramp plan they didn't build. So the plan becomes the onboarding team's artefact, the manager's instinct takes over, and any coherence between the two phases disappears.

A useful frame: think of it as two separate films with no connecting scene. The viewer is the new rep, and they're watching the edit wondering if the director changed halfway through.

Why the protocol doesn't exist

The honest answer is accountability design. Enablement is measured on time-to-productive and certification pass rates. Once the rep certifies, those metrics are largely set. The manager is measured on pipeline and revenue. The handoff happens at the exact moment both parties' incentive systems stop pointing at the same thing.

Nobody is being negligent. The system just doesn't require the handoff to be good. It only requires it to happen.

The second reason: skill-state documentation takes effort and shared language. If enablement is using a competency framework and the manager isn't, the snapshot has no receiver. You can hand over a beautiful map to someone who doesn't know the territory it describes. New Rep Skill Gap Diagnostic is a practical starting point here, specifically because it gives managers and enablement a common vocabulary before the handoff rather than after.

What a proper handoff protocol contains

A handoff protocol is not a meeting. A meeting is how you transmit a protocol. The protocol itself is a defined set of artefacts and commitments, produced by enablement and received by the manager, before the rep hits the floor.

It contains five things:

1. Skill-state snapshot. Competency-by-competency, not module-by-module. What the rep can do reliably, what they can do inconsistently, and what they haven't demonstrated yet. Two pages maximum; a manager will not read a ten-page assessment.
2. Coaching focus for days 60-90. The one or two areas enablement recommends the manager prioritise first, based on what they observed. Not a list of everything; a ranked priority.
3. Live ramp plan handover. The existing 30-60-90 needs to become a shared document with manager edit rights, not a PDF in a shared drive. Use something like Ramp Milestone Tracker (30/60/90 Days) to make this a live instrument both parties are actually referencing.
4. First one-to-one agenda. Enablement should provide a suggested agenda for the manager's first development conversation with the new rep, because leaving it blank guarantees a pipeline check. Manager's First 1:1 Guide for New Hires covers exactly this gap.
5. A 30-day check-in commitment. Enablement doesn't disappear at handoff. One structured check-in at day 30 post-handoff, between enablement and manager, to surface whether the skill gaps identified are showing up in real selling situations or resolving. Thirty minutes. Calendar it at the point of handoff, not retrospectively.

The conversation enablement leaders avoid

Implementing this protocol requires enablement to say something uncomfortable to the sales leadership team: "Our certification data is not a skill-state picture, and you shouldn't treat it as one." That's a hard conversation because it implicitly admits that current outputs are less informative than they appeared.

It also requires managers to show up to a handoff meeting prepared to engage with development data rather than skim it. Some won't want to. The ones who do are almost always the managers whose new hires ramp fastest, which is not a coincidence.

Ramp variance that nobody can explain is almost always ramp variance at the seam. The programme was fine. The manager is capable. The connection between them was never built.

That's a solvable problem, but only if you first admit it's a structural one, not a personnel one.

The tool for this: Enablement-to-Manager Handoff Protocol: Five-Artefact Template, free and no signup.