Sales call scorecard
Most call scorecards ask managers to rate things like 'rapport' or 'confidence' from 1 to 5, and two managers watching the same call give different scores. Scores that depend on the scorer are no use for coaching or for comparing reps. This scorecard anchors every rating to observable behavior, so a 3 means the same thing no matter who is listening.
- Category:
- Enablement & Process
- Formats:
- PDF + CSV + web view
- Sections:
- 6
- Updated:
What you get
- Six scoring categories for discovery calls, each with anchors for 1, 3, and 5
- A per-call scoring sheet with evidence timestamps
- A calibration exercise so managers agree before scores are used
- A trend table to track each rep's scores across a month
Who it's for
- Frontline sales managers reviewing recorded calls
- Enablement leads running certifications
- Teams rolling out conversation intelligence who need a rubric
What's inside
- 1
Discovery call rubric
4 columns, 6 worked example rows
- 2
Call scoring sheet
5 columns, 6 worked example rows
- 3
Call details
6 fields to complete
- 4
Monthly trend
8 columns, blank working sheet
- 5
Calibration session
6-point checklist
- 6
Why behavior anchors matter
Guidance notes
Preview of section 1
Discovery call rubric
Score 1, 3, or 5 against the anchor. Use 2 or 4 when the call falls between them.
| Category | 1: Missing | 3: Adequate | 5: Strong |
|---|---|---|---|
| Agenda and purpose | No agenda stated; rep starts pitching | Agenda stated but not confirmed with the buyer | Agenda stated, buyer asked to add to it, time checked |
| Problem discovery | Asks about features or current vendor only | Identifies a problem but does not ask about impact | Buyer describes problem, its cost or impact, and who else it affects |
The preview shows part of section 1. The full template has all 6 sections (5 not previewed here), with blank rows ready to fill in. Download the full template
How to use it
- 1
Score one call type at a time
Discovery, demo, and negotiation calls need different rubrics. This one is for discovery. Scoring a demo against it will produce low scores that mean nothing.
- 2
Calibrate before you score reps
Have every manager score the same three recordings independently, then compare. Where scores differ by more than one point, rewrite the anchor until they would agree.
- 3
Cite a timestamp for every score
A score without evidence cannot be coached. Write the timestamp and a short quote for each rating.
- 4
Coach one category at a time
Pick the lowest-scoring category and work on that for two weeks. Feedback on six things at once gets you no change in any of them.
Frequently asked questions
What should a sales call scorecard measure?
Observable behaviors tied to outcomes for that call type. For discovery: agenda setting, depth of problem discovery, listening, understanding of the decision process, relevance of any product discussion, and a dated next step.
How many calls should a manager score per rep?
Enough to see a pattern. Two to four scored calls per rep per month is a common starting point for frontline managers; adjust to what your managers can do consistently.
Can conversation intelligence tools score calls automatically?
They can flag talk ratios, questions asked, and whether topics like pricing or next steps came up. Those signals help pick which calls to review, but judgment on discovery depth and relevance still needs a person using a rubric like this.
Related templates
All sales ops templatesSales coaching 1:1 template
Enablement & Process
A sales coaching template for weekly 1:1s that keeps pipeline review, skill coaching, and career development in separate, timed blocks. Free PDF.
Discovery call question bank
Enablement & Process
Discovery call questions grouped by what you need to learn: pain, impact, decision process, timing, alternatives, plus weak versions to avoid. Free PDF.
Sales onboarding plan template
Enablement & Process
A sales onboarding plan template with a week-by-week program, certifications, and ramp checkpoints that show whether a hire is on track. Free PDF and CSV.