A call cadence only works if the map agrees with it

Most field organisations set a call cadence and most of them set it the same way: rank the target list, cut it into tiers, and assign each tier a frequency. Top tier weekly, next tier twice a month, the tier below that monthly, everyone else opportunistically. It is a sensible structure and I have never seen it fail because the tiers were wrong.

It fails because nobody checks the cadence against the map. And the check is one multiplication.

The multiplication

Every tier creates a monthly commitment equal to its size times its frequency. Take a territory with 31 weekly providers, 50 twice-monthly, and 50 monthly. That is 31 × 4 = 124, plus 50 × 2 = 100, plus 50 × 1 = 50. Two hundred and seventy-four calls a month, committed, before a single opportunistic Coverage stop.

Now the supply side. Twenty working days a month. If the territory's zones support an average of eleven calls a day, that is 220 calls of capacity. You have committed 274.

You are 54 calls short a month and nobody in the organisation knows it, because the shortfall never appears as a decision. It appears as a rep who is quietly behind on the bottom tier, month after month, and a manager who reads that as a performance issue.

A cadence that exceeds the territory's capacity does not fail loudly. It fails as a rep who always seems to be slightly behind, for reasons nobody can name.

Where the capacity number comes from

The supply figure is the one that needs care, because it is not a policy. It is a consequence of how far apart the offices in a zone are.

A field day is roughly 420 usable minutes after lunch. A call costs about twenty-two of them. The rest is driving, and driving is set by the geography of the zone: a compact suburban cluster averaging two and a half miles between offices supports twelve or thirteen calls; a zone spanning two towns at nine miles between offices supports eight. Same rep, same effort, four calls of difference.

So capacity is not one number for a territory. It is five numbers, one per weekday, and they are usually not equal. This is the fact that makes the whole thing tractable — and it only becomes visible once you have carved the territory into weekday zones in the first place.

Why weekday zones are the precondition

You cannot see a weekly provider weekly if their patch comes round at random. You can, easily, if their patch is always Tuesday.

Pinning a zone to a weekday is the structural decision the rest depends on. It means a weekly-tier provider is seen on Tuesdays, full stop, and the rep is never asked to cross the metro twice in a week to honour a frequency. It also means capacity is computable: Tuesday's zone supports twelve calls, and Tuesday's cadence commitments are whatever the weekly, twice-monthly and monthly providers in that zone add up to. Now the multiplication above can be done per day rather than per territory, which is where it becomes actionable.

When a day's commitments alone overrun its clock, that is a fact about the zone. Record it. Do not trim names until the arithmetic looks comfortable, because trimming quietly is how the shortfall becomes invisible again.

Three ways to close a gap, in order of preference

1. Re-carve the zone

The cheapest fix, and almost always available. If Wednesday's zone spans two towns and Thursday's is compact, moving a handful of ZIPs across the boundary can raise Wednesday's capacity by two or three calls a day without changing anything else. Ten calls a week. Forty a month.

The rule when you do this: geography decides which zone a ZIP belongs to, and capacity only breaks ties. Balancing purely on workload produces a Friday running two towns twenty-four miles apart, which is not balanced — it is evenly bad.

2. Change the tier sizes, not the frequencies

"Top 50" is a metro-sized number, not a law. A territory with 90 targets wants a Top 25. Shrinking the middle tier from 50 to 35 removes 30 committed calls a month and, crucially, does not weaken the promise made to the providers who remain in it. Weakening the frequency instead — going from twice-monthly to monthly across the board — degrades every relationship a little, which is the worse trade.

3. Accept the gap, explicitly

Sometimes the territory genuinely needs another head and will not get one this year. Fine — but decide which tier absorbs the shortfall and say so in writing. An acknowledged decision that the monthly tier will be worked opportunistically is a plan. An unacknowledged 54-call gap is a rep who looks like they are failing.

A note on what "twice a month" means

Small thing, large effect. Twice a month means weeks one and three, or weeks two and four. It does not mean weeks one and two. Two visits in consecutive weeks followed by three weeks of silence is not twice a month to the person on the receiving end — it is a burst and then absence, and the practice manager will describe your coverage exactly that way.

The related mistake is balancing week-assignments by alternating down the list: first record gets one and three, second gets two and four, and so on. It looks even and it is not, because tiers do not interleave uniformly across weekdays. I have seen this produce nineteen commitments on one Tuesday against eight on another from a list that looked perfectly alternated. Assign each record whichever legal combination is currently least loaded for its own weekday instead.

The check, in full

Before the next quarter, for each territory:

1. Multiply each tier's size by its monthly frequency and sum. That is committed demand.
2. For each weekday zone, compute the mean distance between offices and derive the day's capacity. Sum across five days and multiply by four. That is supply.
3. If demand exceeds supply, re-carve first, resize tiers second, and if neither closes it, name the tier that absorbs the gap.
4. Publish the per-day capacity numbers to the rep and the manager. The number the rep is measured against should be the number the territory supports, not a national average.

It takes an afternoon per territory the first time and minutes thereafter. It is the highest-return afternoon available to most field organisations, and it requires no new data, no new headcount and no new software — only the willingness to find out that a number you have been managing against was never achievable.