← Back to Sales-to-Delivery Handoff

Handoff Protocol.

Run the handoff as one protocol in three phases: a readiness and gap check, a structured transfer, and a standardized gate.

Phase A: Readiness and gap check (Step 2)

Before delivery accepts the engagement, check the captured scope against reality. Where an answer is no, surface the gap now and record its resolution: renegotiate before starting, adjust the delivery plan, or escalate a mismatch to reconcile.

Can we deliver...	Yes / No	Gap and resolution
...this scope?
...on this timeline?
...at this price?
...with the team available?

Phase B: The transfer (Step 3)

Sales transferred the captured scope, context, client relationship notes, and commitments. The delivery owner can restate the scope and expectations back accurately. Delivery confirms it has what it needs to start.

The transfer is complete only when the delivery owner can restate it back. A handoff is a confirmation, not a forwarded email.

Phase C: The standard gate (Step 5)

No engagement starts delivery without the capture, the readiness check, the transfer, and the client kickoff complete. A named person is responsible for each phase. The gate is mandatory, even under deadline pressure.

Phase	Who is responsible	Required before delivery starts?
Capture
Readiness check
Transfer
Client kickoff

If mismatches keep surfacing mid-engagement, the readiness check is being skipped. Surfacing the gap at handoff, when it is cheap to fix, is the entire point. Save or print my copy

Your answers stay in your browser on this page and are never sent anywhere. Use Save or print to keep your copy.