How to build a pharmaceutical sales territory plan
A territory plan is a ranked list turned into a quarter you can drive. Tiers, weekday zones, cadence and the clock, with one territory worked through.
Adam DeLeon · Founder, Adelo CRM
9 min read
A pharmaceutical sales territory plan turns your target file into a quarter you can actually drive: who you see, how often, on which weekday, and how many calls each day can really hold. You build it in four steps (tier the list, carve the map into weekday zones, place the call cadence, size each day by the clock) and then check one number, the calls you have promised against the calls the quarter can hold. Most plans fail that check, and nobody notices until week five.
What follows is the method, a worked territory with every number stated so you can redo it with your own, and the questions people ask most. Nothing here needs data you do not already have.
What a territory plan has to answer
A target file is a ranking. It tells you who matters most in your geography. It does not tell you when you will see them, it does not know that two offices in adjacent rows are thirty miles apart, and it has no idea how long a day is. A plan has to supply all three.
So a useful plan answers four questions, in this order:
- Who gets a promise? Which providers are in a tier with a set frequency, and which are coverage you see when you are nearby.
- Which day is whose? Which part of the map you work on Monday, Tuesday and so on, every week.
- When exactly? Which weeks each provider is seen, so twice monthly means weeks one and three, not one and two.
- Does it fit? Whether each weekday's zone can hold the calls the cadence puts on it, given the drive.
Most templates you find online stop at a list of goals and a SWOT grid. That is a business plan, and you may need one too. But a district manager reading your plan wants to know whether the weekly tier will actually be seen weekly, and only the last two questions answer that.
Know what your target file can and cannot tell you
Before you tier anything, be clear about where the file came from, because its gaps become your plan's gaps.
Prescribing volume in most target files traces back, at least in part, to claims data. The public version is the CMS dataset of Medicare Part D prescribers by provider and drug, which gives prescription fills and drug cost for each prescribing NPI. Three things about it matter for planning:
- It is Medicare Part D only. The methodology says the dataset is based on beneficiaries enrolled in the Part D program. A prescriber with a young, commercially insured panel can look small in it and be large in real life.
- Small numbers are missing. The detail file does not include providers with fewer than 11 total claims, and values from 1 to 10 are suppressed. A prescriber who has just started writing your product can be invisible.
- It runs behind. CMS publishes each year after the claims settle. As of this writing, the newest year in the catalog is 2024.
Addresses usually come from the NPI registry. CMS says the NPPES downloadable file is replaced in full every month, with weekly files in between, and that a separate reference file holds every practice location other than the primary one. So a provider who splits the week between two offices may show up at only one address in your file. That is a routing problem, not a ranking problem, and it is worth fixing before you carve zones.
None of this means the ranking is wrong. Your data vendor did real work, and second guessing the decile with a homemade score usually makes it worse. It means local knowledge belongs in the plan as a stated adjustment, which is exactly what Zoltners and Lorimer argue in their paper on territory alignment: consistent, objective criteria first, then local management judgment on top.
The four steps
1. Tier the file
A score sorts. A tier makes a promise. Cut the ranked list into three tiers, each with a frequency: weekly, twice monthly and monthly. Everyone below the tiers is coverage, seen when you are already in the zone.
Two adjustments are worth making by hand. Move up any office that already uses your product, because losing it costs more than its decile suggests. And find the accounts your vendor encodes oddly, such as a practice name sitting where a surname should be, so your most valuable rows do not arrive blank.
2. Carve the map into weekday zones
Split the territory into five zones and pin each one to a weekday. Tuesday is always the same patch. This is what makes weekly possible: a weekly provider in the Tuesday zone is seen every Tuesday, and you never cross the metro twice in a week to keep a promise.
Geography decides which zone a ZIP code belongs to. Workload only breaks ties. A zone balanced on workload alone can end up spanning two towns on opposite sides of the map, and a day you cannot drive is not balanced. There is more on drawing zones on the territory management page.
3. Place the cadence
Weekly means every week. Twice monthly means weeks one and three, or two and four, never two weeks running followed by three weeks of nothing. Monthly means one of the four. Assign each provider whichever legal pattern is least loaded on their own weekday, rather than alternating down the list, and the weeks stay even.
4. Size every day by the clock
Calls a day is a result of the geography, not an input. Start with an eight hour field day, take out an hour for lunch, and you have 420 minutes. Take out about 45 minutes for the first leg out to the zone and the last leg home, which leaves 375. Each call costs about 22 minutes in the office plus the drive to the next one. Divide, and round down.
At an average of 26 miles an hour, a working figure for metro driving between offices, the drive between stops sets the day:
| Average miles between offices | Drive minutes per leg | Minutes per call | Calls the day holds |
|---|---|---|---|
| 2.5 | 5.8 | 27.8 | 13 |
| 3 | 6.9 | 28.9 | 12 |
| 3.5 | 8.1 | 30.1 | 12 |
| 4.5 | 10.4 | 32.4 | 11 |
| 6 | 13.8 | 35.8 | 10 |
Counting one leg per call slightly overstates the drive, which errs on the safe side. Swap in your own minutes per call and your own speed; the method is what matters. There is more on this arithmetic in ten to twelve calls a day is a consequence, not a target.
A worked territory for one quarter
Here is a made up territory, with every input stated.
The file. 480 targets. The first cut of tiers takes deciles straight down the list: 30 providers weekly, 50 twice monthly, 60 monthly. The other 340 are coverage.
The zones. Monday averages 2.5 miles between offices, Tuesday 3, Wednesday 6, Thursday 3.5 and Friday 4.5. From the table, that is 13, 12, 10, 12 and 11 calls, or 58 a week.
The calendar. A 13 week quarter has 65 weekdays. Take out two holidays, a three day national meeting and two days of training, and 58 field days are left. At an average of 11.6 calls a day, the quarter holds about 670 calls.
The promises. Count the cadence by month: weekly is 4 a month, twice monthly is 2, monthly is 1, and a quarter is three months.
| Tier | Providers | Calls a quarter each | Calls promised |
|---|---|---|---|
| Weekly | 30 | 12 | 360 |
| Twice monthly | 50 | 6 | 300 |
| Monthly | 60 | 3 | 180 |
| Total | 140 | 840 |
That is 840 calls promised against about 670 the quarter can hold, 125 percent, before a single coverage call or a new name. The same thing shows up weekly: the tiers put about 70 calls a week on days that hold 58. This plan looks fine in a spreadsheet and falls apart in the car.
The fix, in order of preference.
First, redraw the zone that is costing the most. Wednesday's six miles between offices comes from straddling two towns. Moving a handful of ZIP codes to Thursday, which has room, brings Wednesday to about four miles between offices, which holds 12 calls instead of 10. The week now holds 60 calls, and the quarter about 696 (12 a day for 58 days).
Second, shrink the tiers, not the frequencies. A top 30 is a habit, not a law. Cut the weekly tier to 20, twice monthly to 36 and monthly to 40. Those who drop out become coverage and still get seen when you are nearby.
| Tier | Providers | Calls a quarter each | Calls promised |
|---|---|---|---|
| Weekly | 20 | 12 | 240 |
| Twice monthly | 36 | 6 | 216 |
| Monthly | 40 | 3 | 120 |
| Total | 96 | 576 |
Now 576 calls are promised against 696, about 83 percent. The other 120 or so calls are for coverage, new prescribers who appear between data releases, and the days that go sideways.
Then check every weekday, not just the total. A quarter can balance while one day overflows. Spread the tiers by where the offices actually are, and count a typical week as weekly providers, plus half the twice monthly ones, plus a quarter of the monthly ones:
| Day | Holds | Weekly | Twice monthly | Monthly | Typical week |
|---|---|---|---|---|---|
| Monday | 13 | 5 | 8 | 8 | 11 |
| Tuesday | 12 | 4 | 8 | 8 | 10 |
| Wednesday | 12 | 4 | 6 | 8 | 9 |
| Thursday | 12 | 4 | 8 | 8 | 10 |
| Friday | 11 | 3 | 6 | 8 | 8 |
| Week | 60 | 20 | 36 | 40 | 48 |
On a full week the plan commits 48 of 60 calls, 80 percent. The quarter figure is tighter, 83 percent, because the meeting and the holidays take days away but do not take promises away. That gap is the reason to plan the quarter and not just a sample week.
Keeping the plan honest during the quarter
A plan is worth something only if you can compare it with what happened. Once a month, check three numbers for each tier: calls planned, calls made, and the names that were missed twice in a row. "We planned 48 a week, worked 41, and here are the seven and why" is a conversation a rep and a manager can solve. "Are you working hard enough" is not.
Watch for the same failure modes every quarter. The bottom tier slips first and quietly, which reads as a performance problem when it is a capacity problem. A zone that keeps running late usually needs redrawing, not a pep talk. And when new data lands, retier at the start of a quarter, not in the middle, so the promises you made still mean something.
If you would rather not do the arithmetic by hand, Adelo CRM takes the target file you already have, scores and tiers it, carves the territory into weekday zones, places weekly, twice monthly and monthly calls on the calendar, and counts drive time against the clock for every day, so the check above is done before the quarter starts. For more on fitting cadence to geography, read a call cadence only works if the map agrees with it.
Questions people ask
What should a pharmaceutical sales territory plan include?
At minimum: the tiers and their frequencies, the weekday each zone is worked, the weeks each tiered provider is seen, how many calls each day can hold, and the comparison of promised calls against capacity. Goals, competitor notes and account strategy can sit alongside it, but those four pieces are what make the plan drivable.
How many calls a day should a pharma rep make?
It depends on how far apart the offices are, not on a target. With about 375 working minutes after lunch and the first and last legs, 22 minutes per call, and 26 miles an hour, a compact zone at 2.5 miles between offices holds 13 calls and a spread out one at 6 miles holds 10. Work it out per zone with your own numbers.
How do you tier targets in pharmaceutical sales?
Start from the ranking your data vendor provides, cut it into weekly, twice monthly and monthly tiers, and leave everyone else as coverage. Then size the tiers so the promises fit the days you have. A tier that the calendar cannot honor is a list of people you will disappoint.
How often should a territory plan be updated?
Review it monthly against what was worked, and rebuild the tiers each quarter or when new data arrives. Redraw zones only when a day keeps overflowing or the target list moves, since your offices learn which day you come and changing it costs goodwill.
Where does the data in a target file come from?
It varies by vendor and most do not publish their methods. Two public sources sit underneath many files: CMS's Medicare Part D prescriber data for prescribing volume, and the NPI registry for names, specialties and practice addresses. Knowing their limits tells you where your own knowledge should adjust the list.
Sources
- Medicare Part D Prescribers by Provider and Drug, CMS, the prescriber dataset by NPI, brand and generic name, with years 2013 to 2024.
- Medicare Part D Prescribers methodology, CMS, Part D coverage only and the suppression of providers with fewer than 11 claims.
- NPPES data dissemination, CMS, the monthly NPI file, the weekly updates and the practice location reference file.
- Sales Territory Alignment: An Overlooked Productivity Tool, Andris Zoltners and Sally Lorimer, Journal of Personal Selling and Sales Management, 2000.
Written by Adam DeLeon, Founder, Adelo CRM. Where a figure appears it is either arithmetic you can redo from the inputs in the text or it is labeled as an assumption. None of it is a customer outcome.