The Sales Manager CRM Activity Audit: How to Check the Follow-Up Happened

Search for a sales manager CRM activity audit and you get CRM vendor documentation: where the activity report lives, how to export it, how to clean up duplicate records at the end of the year. Useful if your CRM is a mess. Useless if your question is the one every sales manager has on a Monday morning: did the follow-up my reps promised me last week happen, or did it not?

That question has a fifteen-minute answer, and it does not need a new dashboard. It needs three numbers, a standard to hold them against, and a routine you run every week whether the quarter is good or bad. Here is the one I run, and the conversation that follows when a number is short.

Your CRM already tells you whether the follow-up happened

Every CRM I have worked in logs three things that answer the question, and none of them is on the default dashboard. The dashboard shows pipeline value and stage counts, which are outputs. The audit needs the inputs, per rep, for the last five working days.

• Activities logged, by type and by owner. Calls, texts, emails, DMs, and the date on each. This is attempts.
• Activities with a logged outcome of a two-way exchange. A note, a disposition, a meeting booked. This is conversations.
• Deals moved to won. This is closes, and it is here for the ratio, not because you expect it to move in a week.

The fourth field, and the one most managers have never opened, is the activity history on the leads marked lost or stalled in the period. How many touches did each one get before the rep stopped? If the answer is two, you have found the leak, and no amount of pipeline review will fix it until a manager looks at it every week.

If your CRM cannot produce those four in an afternoon, fix that first. Call The Damn Leads has the rep-side guide to using a CRM so leads stop dying, and the three fields it tells reps to fill, name, last contact date and next action, are what keep this audit readable.

Audit against a standard, not against a feeling

A number on its own is not a finding. Forty attempts last Tuesday is either a strong day or a half day depending on what the role is supposed to produce, and if the standard lives in the manager's head, every gap becomes an argument.

So write the standard down before the first audit. The one I use is the 100/10/2 Standard, a daily standard: 100 outbound attempts, 10 meaningful conversations, 2 sales closed. Scale it for the role, agree it with the team, and put it at the top of the audit sheet. From then on the audit is arithmetic: the rep's number, the standard, the gap. Nobody has to feel anything about it.

Two rules for the standard that save a lot of grief later. First, define attempts the same way for everyone, in writing, and hold the definition for at least a quarter. Second, the standard is a floor, not a ceiling. A rep above it is not a problem to solve, and the audit should say so out loud. Gallup estimates that managers account for at least 70% of the variance in employee engagement, and the fastest way a manager spends that influence badly is to run an audit that only ever finds fault.

How do you run the fifteen-minute weekly pass?

Monday, before the pipeline review, with the door closed. Same time every week, because the audit works through repetition, not through one dramatic deep look in March.

1. Open the activity report filtered to last week, grouped by owner. Write each rep's attempts and conversations next to the daily standard times five. Two minutes.
2. Open the lost and stalled leads for the period. For each one, count the touches before the rep stopped. Write the number next to the rep. Five minutes, and it is the five minutes that matter most.
3. Pull up your own notes from last week's pipeline review. Every promise that was made, "I will call them Wednesday," "I am sending the proposal Thursday," gets checked against the log. Did the activity happen on or near the day it was promised? Three minutes.
4. Mark each rep green, amber or red on the three numbers, and write one sentence per red: what the gap is, in numbers. Three minutes.
5. Pick the one conversation you will have this week. Not five. One. Two minutes.

That is the whole routine. It does not grade the calls themselves. A sales process audit does that, with a scorecard, twice a year. This is the weekly version that checks the work existed at all, and the two are meant to run as a pair.

What does a gap in the log mean?

A missing activity has three possible readings, and they need three different conversations. Deciding which one you are looking at before you open your mouth is the difference between a manager reps trust and one they route around.

• The work was not done. Attempts are low, conversations are low, and the lost leads got two touches each. This is the common case, and it is a coaching conversation about the standard.
• The work was done and not logged. Conversations and closes are fine, attempts look thin, and the rep is on the phone all day. This is a logging conversation, and the fix is usually a fifteen-second log at the end of each call, not a lecture.
• The standard is wrong for the role. A rep working inbound enterprise deals will never post 100 attempts a day and should not try. This is a conversation with yourself first, then a revised floor for that seat.

The tell between the first two is the ratio. A rep who is working but not logging has conversations and closes that are too good for the attempts shown. A rep who is not working has every number low together. How many sales calls per day a rep should make covers what the ratios usually look like by role, so you can read your own.

The conversation that follows a gap

Lead with a question, not the number. The number comes second, and it comes as a fact rather than an accusation. The shape I use fits in four lines.

• "Walk me through how last week went with the Henderson lead." Open, specific, about one deal.
• "The log shows two touches and then it went to lost on Thursday. Is that right, or did something happen off the log?" The fact, then the chance to correct it.
• "Our floor is eight touches before we let one go. What got in the way of touches three to eight?" The standard, said out loud, and the real question.
• "What is one thing you will do differently on the next three, and I will check the log on Friday." One change, one check, one date.

That last line is the part most managers skip, and it is the part that makes the audit a management routine rather than a weekly complaint. You said you would check, so check. Why leads go cold explains the rep-side habit you are correcting here, and the follow-up system reps should be running is the cadence the "eight touches" line refers to, and its weekly review is the team-level view of this same audit. This post does not re-teach either. It checks that they happened.

The sales manager CRM activity audit, in one table

Print this, or build it as a saved view. Eight rows, run top to bottom every Monday.

What to check	Where it lives in the CRM	The number that says it is healthy	What to do when it is not
Attempts per rep, last five days	Activity report, grouped by owner	At or above five days of the agreed daily floor (100/10/2 scaled to the role)	Read the ratio first: not done, or not logged?
Conversations per rep	Activities with a two-way outcome or disposition	Roughly 1 in 10 attempts	If attempts are fine and this is low, the opener or the list is the problem
Touches before a lead was marked lost	Activity history on lost and stalled leads	At or above the written cadence floor	The follow-up conversation above, on one named lead
Promises from last week's pipeline review	Your own notes against the activity log	Every promise has a logged activity within a day of the date	Ask about the one that is missing, before the next review
Next steps on open deals	Open opportunities with a dated task or meeting	Every open deal has one	Deals with no next step get asked about first in the review
Activities with no note	Activity report, note field empty	Under one in five	A logging habit, not a work problem
Closes	Opportunities moved to won	Tracks the ratio over a month, not a week	Do nothing weekly; read it at 30 days
Your own check-backs	Your calendar	Every "I will check Friday" was checked	If you skipped it, the audit is theater

When the audit will not fix it

That is what follow-up system training with Drewbie installs: the cadence, the scripts, and the accountability layer that this audit reads from, built with your team so the standard is theirs and not a number handed down. And if the gap is on the manager's side, if the Monday pass keeps getting skipped because nobody taught your managers to run one, sales leadership training is the version of this post delivered to the people who have to do it. Either way, the sales manager CRM activity audit is the fifteen minutes a week that make everything else you bought stick.

If the standard needs a trainer to install it, the sales training vendor evaluation checklist sorts the questions to ask by what you can verify later.

Sources: Gallup, Why Great Managers Are So Rare · Call The Damn Leads, How to Use a CRM for Sales · Call The Damn Leads, the 100/10/2 outbound sales standard