Call Observation Notes Template
A structured note-taking sheet for live or recorded call observation that forces a specific behavior, a verbatim quote, and a named coaching point per call — instead of a vague post-call impression.
What's inside
- Call context fields (rep, date, call type, stage)
- Repeatable behavior-quote-coaching-point row structure
- Skill/competency tag field per observation
- Strength-to-reinforce field
- Growth-edge-to-address field
- One-thing-for-next-call commitment field
- Manager overall rating field
- Fully filled-in worked example
A post-call impression ("that went pretty well") is not coaching data. This template forces three things for every observation: the specific behavior, the rep's actual words, and a named coaching point tied to a skill — filled in during the call, not reconstructed from memory an hour later.
Call Context
| Field | Entry |
|---|---|
| Rep | |
| Observer | |
| Date | |
| Call type (discovery / demo / negotiation / renewal / other) | |
| Deal stage | |
| Live observation or recorded review |
Observation Log
Fill in one row per notable moment. Aim for 2-3 rows minimum per call — don't try to capture everything.
| Timestamp | Specific behavior observed | Verbatim quote (rep or buyer) | Skill/competency tag | Coaching point (reinforce or adjust) |
|---|---|---|---|---|
Summary Fields
Strength to reinforce (one specific behavior, not a general compliment):
_______________________________________________
Growth edge to address (the single highest-leverage gap from this call):
_______________________________________________
One thing for next call (the specific commitment this becomes in the next 1:1 — should be small enough to actually change by the next call):
_______________________________________________
Manager overall rating (1-4, using your team's call-quality rubric): _______
Worked Example
| Field | Entry |
|---|---|
| Rep | J. Alvarez |
| Observer | Manager |
| Date | 2026-07-22 |
| Call type | Discovery |
| Deal stage | Stage 2 |
| Live or recorded | Recorded review |
| Timestamp | Specific behavior observed | Verbatim quote | Skill/competency tag | Coaching point |
|---|---|---|---|---|
| 04:12 | Asked an open discovery question, then interrupted the buyer's answer after 8 seconds to add detail | Buyer: "Well, the main issue is really—" Rep: "Right, and a lot of teams find that—" | Active listening / discovery | Adjust: let the buyer finish even through a pause; the interruption cut off what might have been the real pain point |
| 11:40 | Buyer raised a price concern; rep acknowledged and isolated it well before responding | Rep: "So if I'm hearing you right, it's less about the number and more about proving it out first — is that fair, or is there something else too?" | Objection handling — Isolate | Reinforce: this is exactly the isolating question we drilled last month — call it out explicitly in the 1:1 |
| 19:05 | Rep secured a specific next step with a date | Rep: "Let's put the technical call on the calendar for Thursday at 2, does that work?" | Closing / next steps | Reinforce: specific date and time, not "I'll follow up soon" |
Strength to reinforce: The isolating question at 11:40 — textbook execution, use as a peer example.
Growth edge to address: Interrupting buyer answers before they finish, especially through natural pauses (seen 3 times this call).
One thing for next call: Let any pause run 3 full seconds before responding, even if it feels like the buyer is done.
Manager overall rating: 3/4
How to use it
Keep this open while observing a live call or scrubbing through a recording, fill in at least 2-3 behavior rows during the call itself rather than reconstructing from memory afterward, and use the one-thing-for-next-call field as the entire agenda for the follow-up 1:1.