Care management teams are still measured by calls made. It's the wrong number.

Care management teams are still measured by how many calls they make. It's the wrong number, and everyone on the team knows it.

Calls made is easy to count. It fits on a dashboard. It goes up when people work harder. That is exactly the problem with it as one of the core care management metrics: it rewards effort instead of outcomes, and it quietly shapes how the work gets done.

Nobody designed it that way. It's what happens when you measure the thing that's easy to see.

What does a calls-made scoreboard actually reward?

If calls are the scoreboard, the rational move is to make quick ones. Work the list top to bottom. Leave a voicemail, mark it attempted, move on. Nobody on the team is cutting corners when they do this. They are reading the scoreboard correctly.

Picture a composite care manager, call her Dana, near the end of a long morning. Her list is sorted the way it always is. The next member is a woman who, it turns out when she picks up, stopped taking her heart medication a while ago. She isn't sure why it matters. She has questions about side effects, about cost, about whether her doctor even knows. That is a long conversation, and it is the conversation the whole program exists to have.

On a calls-made scoreboard, it is also a productivity problem. While Dana talks, the count stands still. The colleague who left a string of voicemails in the same stretch of time looks, on paper, like the stronger performer. Over enough weeks, people learn what the organization actually values, and it isn't the long conversation.

Measure the effort and you'll get plenty of it, pointed at the wrong things.

Why do care management programs keep counting calls?

Because activity is the only thing most teams can see in time. A call is logged the moment it ends. Outcomes take longer to show up. Whether a member saw a doctor after leaving the hospital, whether a screening happened, whether a medication was refilled: that evidence often arrives in claims, and claims usually arrive weeks after the care happened.

So leaders reach for the number that is current, even when they know it is the wrong one. Activity becomes a stand-in for results, not because anyone believes it is a good stand-in, but because the results usually lag well behind. We've written about the same pattern in care gap outreach, where most of a list is lost to reaching people, not to the members' decisions, and a dial count hides that entirely.

Better care management metrics: questions for the scoreboard

None of these are exotic. They are the questions a care management leader already asks in hallway conversations. The shift is making them the thing the team is measured on.

• How many members had a hospital stay, and how many heard from us within days of getting home? The days right after a discharge are often when a call about new prescriptions and follow-up visits does the most good. Our piece on discharge visibility goes deeper on that window.
• How many care gaps actually closed, not just "outreach attempted"? An attempt is an input. A completed screening that shows up in the record is the outcome.
• How many members on the high-risk list had a real conversation this month? Not a voicemail, not a mailed letter. A conversation where the care manager learned something.
• On average, how long passes between something happening to a member and our team knowing about it?

Why time-to-know is the metric that decides the others

That last question is the one almost nobody tracks. It's also the one that decides all the others. A team can't respond quickly to something it learns about late.

Follow it through. If the team hears about a discharge weeks afterward, the post-discharge call happens after the period when it mattered most, no matter how hard anyone works. If a care gap list is built from data that is weeks old, outreach goes to members who already got the screening while the ones still open wait. If the high-risk list is built on old data, the first real conversation comes months after the member's situation changed.

In each case, the care manager's effort is fine. The timing is what fails. And because timing doesn't appear on a calls-made dashboard, the usual response is to ask for more calls, which makes the dashboard look better and changes very little for the members.

Tracking time-to-know does something the other measures can't. It points at the system instead of the people. When that number is long, no amount of individual hustle closes it, and a leader can see that plainly instead of reading it as a performance issue.

What changes in a care team's week when the scoreboard changes

The list stops being worked top to bottom. A member home from the hospital moves to the front because that is where a call matters this week. A gap that already closed comes off the list instead of earning another dial. Dana's long conversation about the heart medication counts as the work, because it is the work.

Weekly huddles change too. Instead of comparing call totals, the team asks which members they learned about late and why. That question tends to surface the real bottlenecks: a feed that arrives on a slow cycle, a list built from an old extract, a roster that still shows members who have moved on to another doctor.

Measure the outcome and the effort sorts itself out.

Much of shortening time-to-know comes down to the data a team works from. ElevateCare 360's Quality Module tracks open quality measures the moment data lands, so care teams see what's open, what's closing, and what needs attention without waiting for a quarterly report. You can see how that works on our care gap closure page.