Bravabase · Practical guides

LinkedIn lead handoff template: keep the context with the next step

By Bravabase · Published 19 October 2026

When another person takes over a promising LinkedIn conversation, pass on the reason it matters, what the buyer actually said and the next action they agreed to. A name and profile link leave too much to reconstruct.

This guide is for a founder handing a conversation to a colleague, or a team changing who owns the follow-up. It includes a blank text template and two fictional decisions. It works with your existing notes or CRM and does not require Bravabase.

Qualify first, then hand over the work

A handoff is useful when there is a clear reason for another person to continue. Confirm the company fits the offer, identify the relevant responsibility and record the stated need. Keep budget, authority and timing unknown unless they have been established. Use the lead qualification guide for that earlier decision.

Agree who will make the next contact. Passing a note does not mean the recipient has accepted the task. Until they do, the current owner remains responsible for the promise already made.

A handoff you can fill in

Record only the details the recipient needs. Keep private conversation links inside your own authorized workspace. The downloadable template contains no customer data.

Person and company:
Relevant role / responsibility:
Offer this could fit:
Source link and date checked:
Observed fact that supports fit:
Buyer’s stated need or request:
What is still unknown:
Last contact and what was promised:
Agreed next action and due date / timezone:
Current owner:
Proposed next owner:
Owner acceptance and time:
Contact preferences or stop request:
Decision: ready / needs review / do not contact
Reason for the decision:
Review date and eventual outcome:

Download the blank handoff template

Plain text · Free · No signup

Worked example: an agreed review

Fictional example: a founder at Cedar Studio asks an operations consultant how to improve project handoffs. After a discussion, the founder asks for a 20-minute review of the current intake checklist and agrees that the consultant’s delivery colleague can join.

Evidence: The company delivers client projects. The founder says scope changes are missed before kickoff. A review of the intake checklist has been requested.
Unknowns: No budget or wider engagement has been discussed. The team’s existing tools have not been reviewed.
Promise: Send two possible review times by Thursday, with the timezone stated. Ask which checklist can be shared for that review.
Ownership: The delivery colleague accepts the scheduling task. The original consultant introduces them in the existing conversation and records the acceptance.
Next review: After the call, record whether there is an agreed next step. Do not mark the person as a customer before paid work is confirmed.

The handoff gives the colleague enough context to act without turning a small review request into an assumed sales opportunity.

A handoff that is not ready

A marketing director likes a post about onboarding. Their company seems relevant, but there is no stated problem or agreed conversation. A note that says “interested lead; send a proposal” invents both interest and permission.

Keep the record in review. The next task is to check context, not send a proposal. If the person has asked not to be contacted, record that decision clearly and stop the outreach task.

Before the next owner makes contact

Read the original context. Confirm the note matches what was said, including any limits on the request.
Accept one specific action. Record the owner, action and timing. If the handoff is incomplete, return it with the missing question.
Avoid two people following up. Confirm who is replying before either person sends a message.
Keep the introduction truthful. Say why your colleague is involved. Do not claim a referral, recommendation or purchase commitment that was not made.
Close the loop. Save the result and next review date so the original owner can see what happened.

The free follow-up planner can organize the next action you enter. It does not assign a task to a teammate or send the message.

What belongs in a handoff rather than a lead score?

A score compresses a judgment. A handoff needs the evidence behind that judgment and a task someone can accept. “High priority” is less useful than “requested two review times by Thursday; budget not discussed.” Keep the original facts available when the decision changes.

How do you know the handoff worked?

Check whether the new owner accepted it, completed the promised action and recorded the outcome. A delivered note, a reply and a paying client are different events. Use the measurement guide for consistent definitions and the cost calculator when you have a complete set of reviewed figures.