Title: Sales call review checklist: a 15-minute template | Spellit
Description: A copyable checklist for reviewing one sales call in 15 minutes: five moments to listen to, nine yes-or-no lines worth 100 points, and one coaching point.
Page: https://spellit.ai/blog/templates/sales-call-review-checklist/

---

[Blog](https://spellit.ai/blog/) [Templates](https://spellit.ai/blog/templates/)

# Sales call review checklist: a 15-minute template for one call

A sales call review takes 15 minutes when you check nine yes-or-no lines against five moments of the recording instead of listening to the whole call. Tag the call type and the outcome first, score the nine lines, then write one thing to keep and one thing to change. The checklist below is ready to copy, with points that add up to 100 and a rule for lines that do not apply.

Andrey Tikhomirov CRO, Spellit 16 November 2026 6 min read

On this page

- A 15-minute review listens to five moments and skips the rest
- The checklist is nine yes-or-no lines worth 100 points
- Tag the call type first, because a score means different things on different calls
- Finish with one thing to keep and one thing to change, written before you close the recording
- Four habits turn a checklist into paperwork
- What to do next

A review that takes an hour gets skipped in a busy week. The template fixes the time first and then chooses only the lines that can be checked inside that budget.

## A 15-minute review listens to five moments and skips the rest

The 15 minutes split into three minutes of preparation, ten minutes of listening and two minutes to write the coaching point. Folk's guide to sales call review, updated in October 2026, makes the same point about scope: a review "doesn't need to cover every sentence in equal detail", and the checks should fit the purpose of the call.

The five moments are chosen because each one can be found without hearing the rest of the recording:

- The first 90 seconds, found by the clock.
- The buyer's longest answer, found by speaker time in the transcript.
- The first objection and the reply to it, found by searching the transcript.
- The point where the product first comes up, found the same way.
- The last 90 seconds, found by the clock.

In Actions, every call quality score opens into the sentence it rests on and the minute it was said, so the same jump is one click inside a [call quality review](https://spellit.ai/use-cases/call-quality/). Without a tool, the transcript search and the timer do the same job.

## The checklist is nine yes-or-no lines worth 100 points

Copy the table, delete any line the call type makes irrelevant, and write the sentence the rep said next to every yes. A line with no sentence beside it stays blank. Folk's version scores six areas from 0 to 2; this one splits the same ground into single yes-or-no lines, so two reviewers can compare notes line by line.

Moment Yes-or-no line Counts as yes when Points First 90 seconds Did the rep state why the call exists and how long it would take? Both are said, in any words 10 First 90 seconds Did the buyer confirm or change the agenda? Buyer says yes, or adds or removes a topic 10 Buyer's longest answer Did the buyer describe how they handle the problem today, in their own words? Buyer speaks for more than one sentence about their own process 15 Buyer's longest answer Did the rep follow up on something the buyer just said before moving on? The next question refers to the buyer's last answer 15 First objection Did the rep ask a question before answering it? A question about the objection comes before any rebuttal 10 First objection Did the rep come back to it before the call ended? The objection is named again later, with a reply 10 Product first mentioned Did the rep tie the product to a problem the buyer had already named? The buyer's problem and the capability are in the same breath 10 Last 90 seconds Did the rep propose a specific next step with a date? The rep says a day or a date 15 Last 90 seconds Did the rep summarize what the buyer said? Two or more of the buyer's points are repeated back 5

Three things sit next to the score and never inside it, plus one stop rule:

- Call type: first call, discovery, demo, negotiation or renewal.
- Length against the plan for the call.
- Outcome: whether the buyer named or accepted a date. The rep proposing a date is a behavior and scores. The buyer accepting it is a result and is only recorded.
- Stop rule: if the rep promised a term they were not authorized to give, or made a false claim about the product, mark the call for escalation and skip the scoring.

The split between behaviors and results is argued in full in [the longer sales call scorecard](https://spellit.ai/blog/playbooks/sales-call-scorecard/), which also covers weights per section for teams that want more than nine lines.

## Tag the call type first, because a score means different things on different calls

Across 13 sales teams at seven companies in the 90 days to October 4, 2026, the share of scored calls with a next step recorded ran from 1.1% to 80.9%. The base is 6,819 calls scored yes or no in Spellit Actions. The spread tracks the kind of conversation, from first consultations at the top to an inbound contact centre queue at the bottom, more than it tracks any one rep. [The full breakdown is in the next step statistics piece](https://spellit.ai/blog/call-data/next-step-statistics-sales-calls/).

The consequence for a review is plain. A 70 on a renewal call and a 70 on a cold first call say different things about the rep, and a leaderboard that mixes the two ranks call types instead of people. Keep one copy of the checklist per call type, delete lines instead of rewording them, and compare scores only inside a copy. [See how that spread looks on your own recordings](https://spellit.ai/request-demo/).

## Finish with one thing to keep and one thing to change, written before you close the recording

The last two minutes decide whether the review changes anything. Write one line the rep should keep, with the quote, and one line to change, with the quote and the minute. Claap's guide to sales call coaching, from October 2026, reports Gong's advice to start with one scored call per rep each week and raise the frequency once coaching becomes a habit.

At that pace a manager with eight reps spends two hours a week on reviews. Alternate the calls you pick: one the rep is proud of, one that went badly, and a different call type each week. When every call is scored automatically, the coaching point can come from a ranked list instead of one recording, and in Spellit Actions a rule picks one to three tasks per week for each rep from that rep's own calls. [Sales coaching from recorded calls](https://spellit.ai/use-cases/sales-coaching/) describes that route.

The checklist here is the version one manager can run alone with a spreadsheet. [Bring your current review form to a demo](https://spellit.ai/request-demo/) and compare the two.

## Four habits turn a checklist into paperwork

A review form fails slowly. Nobody objects to it, and a quarter later nobody can say what it changed. Four habits are behind most of that:

- Scoring a line without the sentence behind it. A yes with no quote cannot be challenged, and a no with no quote cannot be coached.
- Editing lines in the middle of a quarter. Scores before and after the edit stop being comparable, so change the form at the start of a month and write the date on it.
- Reviewing only lost deals. Folk's guide advises including both successful and difficult calls, because a lost-only sample shows what failed and hides what works.
- Reviewing alone. Two reviewers scoring the same call will differ on some lines, and [calibration on a shared call](https://spellit.ai/blog/playbooks/sales-call-quality-calibration/) finds those lines before the first score reaches a rep.

## What to do next

Pick one recorded call from this week and run the clock: three minutes to tag the call type and the outcome, ten minutes on the five moments, two minutes for the two lines. If a single line took longer than a minute to check, it is worded as an impression. Rewrite it as something a second listener could find in the recording, then run the next review.

> Start with the form you already have. Spellit Actions builds the call quality rubric from the review form a team already uses, in the team's own wording. [Ask for a demo and watch one of your calls scored line by line](https://spellit.ai/request-demo/).

See the demo now. Then run it on yours.

A live demo of our products and a real conversation about the growth problem you need to solve.

[Book a demo](https://spellit.ai/request-demo/)

See it on your own calls

A live demo and a real conversation about your growth problem.

[Book a demo](https://spellit.ai/request-demo/)

45 minutes · nothing to prepare

## More in Templates

[All Templates](https://spellit.ai/blog/templates/)

- [Templates Call QA scorecard template for contact centres: three gates and eleven lines A call QA scorecard for a contact centre needs three parts: a few gates that fail a call outright, about ten yes-or-no lines grouped into customer, co… 16 November 2026 7 min read](https://spellit.ai/blog/templates/call-qa-scorecard-template/)

## FAQ

### How long should a sales call review take?

Fifteen minutes is a workable target for a call of about half an hour: three minutes to tag the call type and the outcome, ten to listen to the five marked moments, and two to write one thing to keep and one to change. In a busy week an hour-long review is the first thing to drop, so cut lines before you extend the time. Listening to the whole recording still makes sense when the call will be discussed in detail or used as a training example, but that should be a decision, not the default. If one line takes more than a minute to check, it is worded as an impression and needs rewriting.

### How many calls should I review per rep each week?

One scored call per rep is a sound start. Claap's October 2026 guide reports that Gong's coaching guidance recommends starting there and raising the frequency once coaching is routine. At 15 minutes a call, a manager with eight reps spends two hours a week, which fits in a calendar. Choose the call by a rule instead of by mood: alternate a call the rep is proud of with one that went badly, and change the call type from week to week. A team that scores every call automatically can keep the manual review for the calls a score flagged and skip hand-picking. Either way, write down which rule picked the call, so the sample can be explained to the rep and repeated next week.

### Should the rep review their own call first?

Yes, as a default worth starting from. Have the rep fill in the nine lines on their own call before the one-on-one, then compare. The lines where you both wrote yes are settled in seconds, and the lines where you disagree become the conversation, with the quote beside each line to settle most of them. This is our recommendation, not a measured result. It works best when the rep sees the checklist before the call is made, so the lines read as a description of the job and not as a test sprung afterwards. Keep the self-review short: the rep needs the same 15 minutes, and a rep who spends an hour on it is grading the form, not the call.

### Should a review cover wins as well as lost deals?

Yes, both. A sample made only of lost deals shows what failed and hides what works, and Folk's guide advises including successful and difficult calls alike. A simple split is to treat the first call you pick each week as a routine one, whatever happened to the deal, and the second as one the rep flagged as hard. Score both with the same copy of the checklist for that call type. If the winning calls score no higher than the lost ones, the lines are not describing what moves your deals, and the form needs rewriting before the scores are used. Run that comparison once a quarter on the calls you already reviewed, using the outcome you recorded beside each score.

### What if a line does not apply to the call?

Mark it not applicable and take its points out of the total. If the objection-return line is irrelevant because the buyer raised nothing, that is 10 points removed, and the rep is scored out of 90: 72 earned points read as 80, not 72. Do not give the points for free and do not count the line as a fail. Keep a tally of how often each line comes back not applicable. A line skipped on most calls was written for another call type and belongs in that type's copy of the checklist. The tally also protects the rep: a score built on fewer applicable lines is noisier, so say how many lines were scored beside the number.
