Every field organisation has a version of the same conversation. A manager asks how many doctors were seen this quarter. A rep says "most of them". A spreadsheet appears, built on Sunday night, and nobody quite believes it. The problem is rarely effort: reps work hard. The problem is that the plan and the reality were never written in the same place, so nobody can compare them.
This guide explains how to build a visit cycle that a rep can actually keep, and how to read coverage honestly while the cycle is still running — not three weeks after it ended.
Start from the contact, not the institution
A visit cycle is a period — often a quarter — during which each contact who matters should be seen a given number of times. The first decision is therefore who deserves how many visits. A key prescriber in a teaching hospital may need four visits a cycle; a pharmacist in a secondary town, one.
That cadence belongs to the contact, through a rank (A, B, C, or whatever your organisation calls them). It should not belong to the institution. When cadence is set on the institution, every contact inside it inherits the same frequency: a hospital with seven doctors suddenly "needs" twenty-eight visits, the plan becomes impossible, and reps quietly stop trusting it. The institution tells you where to go; the contact's rank tells you how often.
The institution still matters, as a targeting filter. A rep carrying premium products may focus on A and B institutions, another on B and C. Choosing which institution ranks to cover is part of building the plan.
Plan the days before placing the visits
The most common reason a plan fails is that it was drawn on days that did not exist. Before any visit is placed, each day of the cycle should have a type: visit day, leave, absence, sick leave, office, travel, group activity. Only visit days — and travel days, at their reduced capacity — can receive visits. A plan built this way is shorter than the optimistic version, and much more likely to happen.
In FunnelRover's CONVERT module, the rep chooses a cycle, the territories and the institution ranks to cover, sets the type of each day, and then generates the plan. The generator groups the contacts of one institution into a single pass, sets the number of passes according to the most demanding contact there, spreads them across the cycle, and puts neighbouring establishments on the same day.
Read the capacity report before you commit
A good plan says what it cannot do. After generation, a capacity report compares what the cadences require with what the working days allow, and names the contacts who found no place. That list is the most useful output of the whole exercise: it turns an invisible shortfall into a conversation. The rep can add visit days, narrow the scope, or accept the gap openly — then regenerate.
Make the plan an agreement
Once the rep is satisfied, the plan goes to a reviewer — the direct manager, or Master Data if there is none — who approves it or sends it back with a comment. After approval the plan no longer changes. That is deliberate: an approved plan is a commitment, and it is only useful as a reference if nobody can rewrite it after the fact.
Life still happens. A confirmed absence does not rewrite the plan; it changes what is counted. A slot that falls on a confirmed day of leave drops out of the calculation, so a rep on holiday does not appear late.
Record the visit where it happens
Each day, the rep logs visits from the slots of the plan, or marks a slot as missed with its reason. An unplanned visit remains possible. A visit report carries the objective, the report itself, the products discussed, the questions raised, the next action and the duration. When the phone allows it, the position is captured at the moment of recording.
The point is not surveillance. It is that the visit is written down once, on the spot, instead of being reconstructed from memory at the end of the week.
Read coverage honestly
Most coverage figures lie in one of two ways. Either they count the whole cycle, so a cycle half over can never look better than 50%, or they count only what was done, so the missing visits disappear. A more honest reading has three parts:
- Coverage to date — the share of past slots that produced a visit. Future slots do not count yet, so a cycle half over does not display 100%.
- Backlog, split in two — past slots without a visit, separated into missed (a reason was given) and silent (nothing was said). The silent ones are named, so they can be caught up or explained.
- Coverage by rank — to check that the most important contacts are actually the ones being seen.
A manager sees, in the same place, the plans waiting for review, the closures to check with their waiting time, and the reps who are falling behind. At the end of the cycle, the rep declares the plan finished and the reviewer confirms the closure.
Look at the trend, not only the cycle
A cycle tells you where you stand. It does not tell you whether you are improving. For that, you need months side by side: each rep's visits month by month, and a trend verdict that only appears once there are at least six months of data. Below that, "not enough history yet" is the honest answer. FunnelRover's ANALYZE module holds that longer view for Admins and Master Data, with CSV exports split by territory.
Where to start
You do not need to transform the whole sales force at once. Start with one team and one cycle: define the contact ranks and their cadence, set the working days, generate, read the capacity report together, and approve. By the end of that first cycle, you will have something most field organisations never have — a plan and a reality in the same place, and a clear list of what fell between them.