Ask a sales manager how much time they spend reviewing calls each week and you will get an answer somewhere between "not enough" and "too much, with not enough to show for it." Those two answers describe the same problem from different directions. The real question is not hours spent. It is what those hours are producing.
We started paying close attention to this when we were designing Brevity's coaching workflow. One of the things we kept hearing from managers in early conversations was a version of: "I review a lot of calls, but I do not always know what to do with what I find." That disconnect between review volume and development output is worth examining in detail, because the fix is not simply reviewing fewer calls or more of them.
What "Reviewing a Call" Usually Means
When managers say they are reviewing calls, they are typically doing a mix of at least three different activities: listening for deal-specific information ("what did the prospect actually say about budget?"), general quality monitoring ("is this rep doing anything that could get us in trouble?"), and coaching-intent observation ("what should I talk to this rep about?"). These are different activities that have been bundled together under a single label.
The deal-specific listening often cannot wait and produces immediate action: a follow-up email, a deal strategy adjustment, a Slack message to the rep. It is reactive but justified.
The quality monitoring is lower urgency and often gets deprioritized. It ends up being retrospective when it happens at all, surfacing issues after they have been compounding rather than catching them early.
The coaching-intent review is the one where the time investment pays back in rep development. It is also the most cognitively demanding, because it requires the manager to hold a mental model of the rep's development arc while listening to the call. Most managers are not explicitly separating these modes when they sit down to review calls, which means they shift between them without being deliberate about which one they are doing at any given moment.
The Preparation Problem
One thing that reliably makes call review time less productive is reviewing calls without preparation. A manager who starts listening to a call without knowing what they are looking for will spend most of the call just following the conversation rather than evaluating it against specific criteria. That is a passive activity that produces impressions rather than observations.
The preparation that actually helps: before listening, answer three questions. What do I know about this rep's current development focus? What stage is this call from, and what should I see in this stage from a rep at this skill level? What specific behavior pattern has come up before with this rep that I might see again here?
Those three questions take two minutes. They change the entire character of the review from passive listening to active evaluation. A manager who reviews a call without that preparation will often finish and feel uncertain about what they learned. A manager who goes in with those three questions will usually finish with a clear observation they can use in coaching.
Where the Time Actually Goes
Based on what we see from managers using Brevity, the distribution of review time often looks roughly like this: a significant portion goes to replaying sections to understand what was actually said (transcript and automated segmentation significantly reduce this), another portion goes to note-taking and CRM updates (often triggered by deal-specific content that should be captured separately), and the remainder is available for genuine coaching-intent evaluation.
The problem is not that managers are lazy or uninterested in development. The problem is that the infrastructure they are working with turns review into a high-effort, low-yield activity. Listening to a full call to find two minutes of developmentally relevant content is a poor return on the time. Most managers know this, which is why they tend to review fewer calls than they think they should, or review calls and come away without a clear coaching anchor.
What Better Review Time Distribution Looks Like
The shift that produces better outcomes from the same or less review time looks like this: more time spent before the review preparing the evaluation frame, less time spent during the review on activities that technology can handle (transcription, segmentation, deal-specific summary), and more time spent after the review translating observations into specific coaching commitments.
The "after" part is the most commonly skipped. A manager who reviews a call and thinks "I should talk to Jordan about their discovery questions" but does not book a coaching session in that moment will frequently not follow through. The observation decays. The next time they review Jordan's calls, they might arrive at the same observation without knowing they had it before. That is a waste of the review time that was spent to get there.
A simple habit that closes this: at the end of every call review with coaching intent, make one concrete next-step commitment before closing the browser. Not a note-to-self. A calendar event or a Slack message to the rep scheduling time. The review is only complete when that commitment exists.
On the Question of Volume
There is a common assumption that managers who review more calls are doing more for their team's development. That is true only if the quality of the review and the follow-through on observations are held constant. A manager who reviews ten calls per week and follows up on zero observations is producing less development than a manager who reviews two calls per week and follows up on both.
We are not saying review volume does not matter. Systematic coverage of calls across all reps and call types is genuinely valuable, and it requires a certain volume commitment to achieve. The point is that volume is not the metric to optimize. The metric is: after reviewing a call, did the rep's next three calls go differently as a result? If the answer is yes, the review process is working. If the answer is consistently no, something in the review-to-coaching pathway needs to change.
