Productive sales visit rate is the share of eligible planned store calls that achieved the objective set for each planned line in a period. Calculate it as productive visits ÷ eligible scheduled visits, score order-taking and service work separately, and publish the denominator, exclusions and raw counts so anyone can recompute it. A blended rate across mixed visit types is the most common source of misleading results.
Take a hypothetical distributor where a sales manager reports an 87% success rate built from GPS check-ins and photo uploads. Re-score the same month against the objectives the calls were planned to achieve and the number drops close to 42%. Nothing was hidden: the first metric counted presence, the second counted outcomes.
Define four states before calculating anything
Most disputes about the rate are really disputes about vocabulary. Agree on four states, write them into the reporting dictionary, and keep them stable for at least a quarter. The definitions below are a working template, not a universal standard.
| State | Definition for this metric | Appears in |
|---|---|---|
| Scheduled (eligible) | A planned line for a named store, rep and date, after exclusions such as permanently closed stores, duplicate route lines and approved leave | Denominator |
| Attempted | The rep reached or contacted the store on the planned day, whatever the result | Coverage rate only |
| Completed | Store entry inside the planned window plus all required fields for that objective | Completion rate only |
| Productive | The objective was met, for example an accepted order at or above the minimum drop size, or the assigned service issue closed and confirmed | Productive rate numerator |
Why the denominator is the harder half
Exclusions decide whether the rate is honest. A permanently closed store should leave the store master and future plans, not stay in the denominator as a permanent miss. A rep on approved leave should reduce the planned count. A duplicate route line where two reps were sent to the same store on the same day should be removed, not counted twice. Everything else stays in, including no-shows, because the metric asks whether planned coverage converted into productive outcomes.
Worked example: one month, one distributor
The figures below are hypothetical and illustrative only. Period: 1–28 February, one distributor territory, 10 field reps, 20 selling days, 10 planned stores per rep per day. The plan produced 2,000 planned lines. Before counting, 25 duplicate route lines and 15 permanently closed stores were removed, leaving 1,960 eligible scheduled visits.
| Step | Order-taking visits | Service visits | Total |
|---|---|---|---|
| Eligible scheduled visits | 1,200 | 760 | 1,960 |
| Completed visits | 1,000 | 620 | 1,620 |
| Productive visits | 520 | 300 | 820 |
| Productive rate | 43.3% | 39.5% | 41.8% |
The same month produces three different stories. Arrival records give 1,720 ÷ 2,000, or 86.0%, if the pre-cleaning plan is used. Completion gives 1,620 ÷ 1,960, or 82.7%. Productive outcome gives 820 ÷ 1,960, or 41.8%. Only the third answers the question a commercial director usually cares about: how much of the planned coverage produced something the business can bank.
Note also that 1,000 order-taking calls were completed but only 520 produced an accepted order at the agreed threshold. Completion without conversion is a coaching and assortment question; conversion measured on the wrong denominator is a reporting problem. Keep the two visible side by side rather than collapsing them.
Score order-taking and service work against different objectives
An order-taking call is productive when the store accepts an order that meets the agreed condition — for example the minimum drop size, a specified range, or a documented substitution the store accepted. A service call has no order to accept, so its productive condition must be a closed task: planogram corrected and photographed to standard, near-expiry stock rotated and the quantity recorded, a delivery discrepancy logged with a resolution, or a promotion set up and confirmed against the agreed conditions.
Two rules keep the split clean. First, do not let one type borrow the other’s definition; a service call with an incidental order is still a service call if that was how it was planned. Second, if a call legitimately carries both objectives, split it into two planned lines or assign a primary objective, and score only the primary one. Mixing objectives inside a single numerator is how a rate starts drifting upward without performance changing.
How to calculate productive visit rate: a defensible checklist
Use the same sequence each period. The steps below make the calculation auditable and keep the productive definition separate from activity evidence.
- Publish the productive definition for each type, including thresholds, before the period opens.
- Freeze the exclusion list: closed stores, duplicate lines, approved leave, reassignments, and how each is evidenced.
- Fix one period and one time zone, and count a call in the period in which it was scheduled, not when it was submitted.
- Treat check-ins, GPS pings and photos as evidence of activity, never as proof of a productive outcome.
- Report numerator, denominator, rate and raw counts together, with the formula shown.
- Allow documented outcome updates for a short, stated window, then lock the period.
- Name an owner for weekly exception review, so no-shows and non-productive outcomes are explained while memory is fresh.
Where field software fits, and what to verify
Airpalm publicly describes mobile visits, route planning, store audits, sales orders, inventory and promotion management (airpalm.com, checked 9 October 2026). If you want the productive definition captured at the moment of work, the objective needs to sit on the planned line, with required fields and a reason code for non-productive outcomes. Those are evaluation questions, not assumptions — ask for a demonstration using your own stores, types and thresholds, and confirm how an outcome is recorded, changed and locked.
Two related reads if you are tightening this area: guidance on measuring store visit quality in FMCG field sales, and on using reason codes for failed store visits so that misses become analysable rather than just low scores.
A restrained next step: re-score one closed month on paper against the four definitions above, without changing any targets. If the gap between completion and productive outcome is large, the reporting definition, the plan or the objectives need attention before anyone is measured against the new number. Airpalm’s platform overview is at airpalm.com if you want to see how objectives and outcomes are captured in a field workflow.
Frequently asked questions (FAQ)
Should a rep no-show stay in the denominator of productive visit rate?
Yes, unless the plan line was formally excluded before counting — for example approved leave, a reassignment, or a store removed from the master list. The rate measures whether planned coverage converted into productive outcomes, so removing no-shows turns a conversion metric into a completion metric. Keep no-shows visible as a separate count so you can distinguish a coverage failure from a conversion failure.
The store was closed when the rep arrived. Is that an attempted visit or an exclusion?
Split the case by what was knowable in advance. A permanently closed store should be removed from the store master and from future denominators, and the removal dated. A temporary closure on the day stays in as an attempted but non-productive visit with a reason code, so repeated closures at the same store become a pattern you can act on rather than a silent adjustment.
Can productive visit rate be compared across territories or distributors?
Only when the productive definitions, thresholds, exclusion rules, mix and period all match. A territory with a higher share of service calls or a different minimum drop size will show a different rate for reasons unrelated to performance. Compare movement within the same territory over time first, then normalise mix before any cross-territory comparison.
Put this guide into practice
This general-purpose worksheet is a starting point. Adapt its fields, responsibilities and rules to your business process.
