Sales Call Planning: A Pre-Call Checklist and Template

Marcus pulls into the lumber yard at 10:15 for his second visit with the purchasing manager. He knows the account. He doesn't reread his notes.

Ten minutes in, the buyer asks, "Did you bring the fastener samples you mentioned?" He didn't. The visit ends with "Let's catch up next month," and Marcus drives off with nothing new on the calendar. (Marcus is a composite, but most field reps have had that visit.)

The visit was lost in the parking lot, in the five minutes he didn't spend on sales call planning. Time is tight: Salesforce's State of Sales statistics for 2026 report that reps spend 60% of their time on non-selling tasks. Planning has to be short to happen at all.

Below: a copy-ready template, a checklist that sizes prep to the call, a filled-in example, and a 20-minute routine for planning a whole day the night before. If you'd rather talk than type, ParrotNotes records a spoken plan or debrief on the phone you already carry and turns it into a summary and action items.

What sales call planning is (and what it isn't)

Sales call planning is deciding, before a customer visit or call, what you want the call to produce and what you need to know, ask and bring to get it. It's written down, short, and done for every call, not only the big ones.

A useful plan has four components:

1. An objective: the commitment you want the customer to make by the end.
2. What you already know: the account, the people, and what each side promised last time.
3. What you need to learn: three or four questions you can't answer from your notes or the CRM.
4. What could get in the way: the likely objection, and the things to bring that answer it.

Sales route planning decides the order of your stops; the call plan covers each stop. Afterwards, the sales call report records what actually happened, and the follow-up email confirms it with the customer.

Start with the call objective: one advance, one fallback

Most pre-call planning goes wrong at the objective. "Build the relationship" and "check in" aren't objectives. You can't tell afterwards whether you hit them.

Neil Rackham's research for SPIN Selling (McGraw-Hill, 1988) sorted call outcomes into four types: an order, an advance, a continuation, and no sale. An advance is something the customer agrees to do that moves the sale forward. A continuation is the polite non-result Marcus got: the conversation goes on, but nobody has committed to anything. Huthwaite International, the firm Rackham founded, still runs training on the sales advance.

So write your objective as an advance the customer could agree to today. Then write a smaller fallback, in case the big one isn't there:

The fallback matters. It turns "they weren't ready" into a visit that still moved something.

The sales call planning template (copy this)

Copy this into your notes app or CRM. Fields 2 and 3 are the minimum for every call, even a drop-in. The checklist below tells you how many more each call needs.

SALES CALL PLAN
Account · Date/time · Location · Call type (first / repeat / review / joint / drop-in)

1. Who will be there: names, roles, who decides
2. Objective: the advance I'll ask for
   Fallback: the smaller advance if that's not on the table
3. Open loops from last visit
   - What I promised:
   - What they promised:
4. What changed since then: people, news, competitor, deadline
5. What I need to learn (3 questions I can't answer yet)
6. Likely objection and my answer
7. What I'll bring: samples, quote, spec sheet, references
8. My closing ask, word for word

What each field is for

Who will be there stops surprises. Also ask who has a say but won't be in the room.

Open loops is the field most plans skip and the one that cost Marcus his visit. Lead with what you owe them. If it isn't done, say so before they ask.

What I need to learn is capped at three questions so the rest of the conversation can follow the customer. For a first meeting, the discovery call guide has the questions to choose from.

Likely objection gets one line and one answer. For the ones you hear every week, see the objection handling guide.

My closing ask, word for word sounds fussy, but a written ask is far easier to say: "Can we put 30 minutes on the calendar with your plant manager next week?"

Pre-call planning checklist: how much prep each call deserves

The usual advice is "don't over-prepare", but it never says how much is enough. Let the call's value and newness decide:

And the checklist, in the order you'd do it:

• Reread your last note on this account (not the whole history)
• List open loops: what you promised, what they promised
• Write the objective as an advance, plus a fallback
• Confirm who'll be in the room
• Pick three questions you can't answer yet
• Note the likely objection and your answer
• Pack samples, quotes and spec sheets
• Write your closing ask

A sales call plan example, filled in

Priya and the account below are a composite. Priya sells flexible packaging. On Thursday she has a repeat visit with a snack co-packer that ran a trial of her new film on one line. A four-line deal is worth more than the usual five minutes, so she fills all eight fields the night before.

Notice that the open loops cut both ways: Priya has something to deliver and something to ask for. And the fallback is still a real step, because trial data in writing makes the next quote believable.

Plan tomorrow's sales calls in 20 minutes the night before

For a five-call day, batch the planning the night before, after your route is set:

1. Minutes 0 to 5: list the calls from your calendar or route, each with its call type from the prep table.
2. Minutes 5 to 15: fill fields 2 and 3 for every call. These are the two you can't make up on the spot. A high-stakes call still gets its own 45 minutes earlier in the week.
3. Minutes 15 to 18: pack. Samples, printed quotes, the spec sheet you promised. Put them in the car in stop order.
4. Minutes 18 to 20: confirm by text any stop where the time or attendees are uncertain.

In the morning, parked outside each stop with the engine off, reread that call's plan for a minute. That's the same parked moment the windshield time guide builds into the day.

Step 2 goes fastest in your notes app. In ParrotNotes, keyword search finds every past note for an account, and on Pro, AI semantic search finds notes by meaning ("the visit where they mentioned the night shift"). You can also open last visit's recording and ask its AI chat, "What did I promise to send them?" The answer comes from your own transcript.

Prefer talking? Record a 60-second plan (objective, fallback, open loops, closing ask) and read its summary in the parking lot. Download ParrotNotes free and plan your next day out loud.

After the call: check the plan against what happened

A plan you never look at again only helps once. Before you drive on, answer one question: did you get the advance, the fallback, or a continuation? Then the rest of the plan turns into your call report almost field for field:

The agreed next step then goes straight into your follow-up email after the sales call, ideally the same day.

Jordan, another composite, sells HVAC controls to building managers. A month of plans and debriefs showed him that 9 of his 22 repeat visits ended in continuations, and in 7 of those he never said his closing ask. The next month he read field 8 aloud in the car before each visit. His plans stayed the same. His asks didn't.

Make sales call planning a habit, not a homework task

Sales call planning doesn't need to be long. It needs to happen before every visit:

• Write the objective as an advance, with a fallback.
• Check open loops on both sides.
• Size your prep to the call: 2, 5, 20 or 45 minutes.
• After the call, compare plan and outcome, then write the report.

Copy the template and fill it in for your first call tomorrow. Rather say it than type it? Try ParrotNotes free: speak your plan tonight and your debrief in the parking lot, and get a summary and action items for both.