Prioritizing a named-account list when reps can't call everyone every week

A rep with 150 named accounts and four selling days a week does the math fast: that's roughly 30 live touches if nothing else happens, no inbound, no proposal cleanup, no internal meetings eating the morning. In practice it's fewer. So the list gets worked in whatever order it's sorted, usually alphabetical or by last-touch date, and the rep ends up calling the easy ten accounts over and over while forty others go quiet for a quarter.
This is a triage problem, the same shape as any beat too big to patrol block by block. You weight the accounts where something is actually changing and let the quiet ones wait.
Calculate the coverage ratio before you argue about the list
Before any debate about which accounts matter more, pull the number that tells you whether this is a capacity problem or a routing problem. Account coverage ratio is touched accounts divided by total named accounts, over a rolling window, usually 30 or 90 days. A rep at 60% coverage on a list of 120 means 48 accounts got zero contact in a quarter. Run this by rep and by tier before you build any new priority scheme. Sometimes the list is just too big for the headcount, and no triage rule on earth fixes that.
Tier by what's changing, not by what the account is worth
Most named-account lists get tiered once, at list-build time, by revenue potential or logo size, and then never revisited. That ranking tells a rep nothing about this week. A $2M account that hasn't moved in six months and a $400K account that just broke ground on a second facility don't deserve the same spot on Tuesday's call sheet, but a static tier list treats them identically.
The fix is a second layer on top of the static tier: a change signal. A new hire posted on LinkedIn, a permit filed, a building expansion, a second location opening. Any of these is a reason to call this account now instead of whenever it comes up in rotation. Without a system that surfaces these, reps either miss them or stumble on them by accident weeks after the window to be first in the door has closed.
A lot of ops teams try to patch this with a shared spreadsheet where someone logs news they find. It works for about three weeks, until the person who kept it up moves roles and the tab goes stale. A standing watch on the physical sites in a territory, the kind Territory Watchlist runs against satellite imagery on a weekly cadence, catches the ground-level version of these signals: new construction, a site expansion, activity at an address that had none last month, and turns each one into a dated alert instead of a line nobody owns.
Build the weekly call list from triggers, not the whole roster
Once you have a coverage number and a trigger feed, the weekly list writes itself. Pull every account with a dated event from the last seven days first. That's the must-call tier regardless of account size, because the window on a trigger closes fast and someone else's rep is reading the same filing. Fill remaining capacity with the top of the static tier that's gone longest without a touch. Everyone else waits, and that's fine, because now it's a decision instead of an accident.
The reps who complain least about account count usually aren't working smaller lists. They're working lists where call order is decided by something other than habit. A 200-account book is manageable when 15 accounts are flagged as active this week and the other 185 are known-quiet. It's unmanageable when all 200 look identical on paper and the rep is guessing.
Coverage ratio tells you the size of the gap. Trigger-based tiering tells you which accounts close it first.
Put a watch on your own named-account territory and see which accounts move first.