Outbound resource

Sales appointment qualification checklist and handoff template

Agree what a useful meeting looks like before a campaign starts. This checklist helps SDRs and account executives record fit, the reason for meeting and the information still needed, without treating a calendar booking as an opportunity.

Editorial update:

Separate meeting stages
3
Handoff fields
6
Acceptance owner
Named

Use agreed definitions for each stage

For the reporting convention in this guide, booked means an appointment was scheduled; held means the conversation occurred; sales-qualified means the receiving sales owner accepted it against agreed criteria. These are separate fields. A prospect can attend and still be a poor fit, while a good-fit account may need more discovery before an opportunity is created.

Qualify enough to make the meeting useful

Confirm account fit, the participant's relationship to the workflow and the reason they want to talk. Ask about timing as a question, not a condition you silently assume. Some offers require budget confirmation before a meeting; others use discovery to establish the business case. Put that choice in the written acceptance criteria so the SDR does not invent an answer to satisfy a quota.

Let the receiving owner accept or return the handoff

Name the person responsible for reviewing meeting notes and give them a way to record an accepted, pending or rejected outcome with a reason. Rejection reasons such as wrong account, wrong participant and no relevant use case call for different fixes. Preserve the original notes when a status changes so the team can see what was known at booking time.

Copyable meeting handoff

Use this blank six-field template in your CRM. It is an operational convention you can adapt, not a universal qualification standard.

  1. 1. Account and fit

    Company: [name] Matched ICP criteria: [evidence] Unresolved prerequisite: [unknown or none]

  2. 2. Participant and role

    Attendee: [name and role] Relationship to workflow: [confirmed responsibility] Other stakeholders mentioned: [confirmed names/roles or unknown]

  3. 3. Reason for meeting

    Prospect's question or goal: [quote or faithful summary] Agreed agenda: [topic] Do not assume: [unconfirmed pain, budget or authority]

  4. 4. Timing and open questions

    Timing stated by prospect: [answer or unknown] Remaining discovery questions: [questions] Materials promised: [item and owner]

  5. 5. Meeting logistics

    Scheduled time and time zone: [details] Invite and conversation record: [internal links] Receiving owner: [name]

  6. 6. Post-meeting decision

    Held: [yes/no/rescheduled] Sales acceptance: [accepted/pending/rejected] Reason and next action: [details] Reviewed by and date: [owner/date]

Action checklist

Before marking a meeting ready

  • Account matches the written ICP

    Record which criteria match and any unresolved prerequisite. A correct title is insufficient.

  • Participant has a relevant role

    Ask how they relate to the process. Do not assume final authority from seniority.

  • Reason to meet is explicit

    Confirm the topic the prospect expects to discuss so the sales call does not start with a different pitch.

  • Logistics and next owner are clear

    Check the time zone, invite details and internal owner. Record reschedules separately from completed conversations.

  • Open questions remain visible

    Unknown budget or timing should be marked unknown, with the next discovery question attached.

Who this helps

  • SDR teams agreeing meeting standards with account executives
  • Founders reviewing outsourced appointment setting
  • Revenue teams separating activity from qualified pipeline

Work through the process

  1. 01

    Agree acceptance criteria

    Choose the required account, role and use-case conditions together with the sales owner. Define how unknowns will be handled.

  2. 02

    Capture the prospect's words

    Use a short quote or a faithful summary for the reason to meet. Mark your interpretation separately.

  3. 03

    Send the handoff

    Attach the conversation context, agenda, time zone and remaining questions to the meeting record.

  4. 04

    Close the feedback loop

    After the call, record held status and the sales owner's decision. Review rejected reasons by source and segment.

Questions and answers

Does a booked meeting count as an SQL?
Only if it independently meets your agreed SQL criteria and the owner accepts it. In this guide, booking status and sales qualification are recorded separately.
Must every prospect have a confirmed budget?
That depends on your offer and sales process. Specify whether budget is required before booking or is a discovery question. Never fill the field with a guess.
How should we count a rescheduled call?
Keep one meeting record or link the replacement to the original. Update its date and status so a reschedule does not appear as an additional unique meeting.

Sources and editorial notes

Original AI-assisted editorial templates and planning conventions prepared for LeadFlow. Examples are illustrative; they are not independently tested results, customer evidence or performance benchmarks. Check facts and adapt the material to your own workflow before use.

    Keep reading