Field-Team KPIs: What to Measure and What to Report

Ask most brands how their field team is performing and you get a visit count. It is the worst available metric, because it is the one number that improves reliably without anything actually getting better: a merchandiser can visit more stores by spending less time in each, and the reported figure goes up while shelf execution goes down. Measure outputs, not attendance. Six KPIs cover it, and each needs a definition tight enough that it cannot be satisfied without the underlying work happening.

The six

Two of these are foundations rather than performance measures. Photo-proof rate is the integrity check: if it is low, every other figure on this list is unverified self-reporting. Visit compliance measured on the planned date matters because a visit that happened three weeks late is not the visit you planned — it is a different visit, and it did not prevent whatever it was scheduled to prevent.

Define them so they cannot be gamed

Every field KPI has a way to satisfy it without doing the work. Close those doors when you write the definition:

• Visit compliance without a date requirement becomes "we got there eventually". Require the planned date, and count late visits separately rather than counting them as compliant.
• OSA self-reported without a photo becomes an opinion. Require photo evidence of the shelf as found.
• Planogram compliance checked from memory is worthless. Require the current planogram to be accessible at the point of check — see shelf audits and planogram checks.
• OOS resolution time measured from escalation rather than discovery hides the delay you most want to see. Start the clock when the merchandiser saw it.
• Sales per visit without store-level data is a national average that hides everything. Compute it per store.

What to do when each one moves

A KPI that produces no action is a number you are paying to collect. Decide the response in advance:

Visit compliance falls → the route plan is unrealistic, or travel time was underestimated. Fix the plan before disciplining anyone; a plan nobody can complete produces dishonest reporting rather than more visits. Planning routes and store visit schedules covers rebuilding it.

OSA falls → separate the causes. Stock never delivered, stock in the back room, or stock genuinely sold out. These need three different fixes, and lumping them together produces none of them. See tracking out-of-stock, expiry and replenishment.

Photo-proof rate falls → either the requirement is impractical (too many photos, poor connectivity) or reporting has become box-ticking. Ask the team before assuming the second.

Planogram compliance falls → usually a store-side reset or a competitor taking space. Both need escalation to the retailer, and both need dated photo evidence to be taken seriously.

OOS resolution time rises → the bottleneck is almost never the merchandiser. It is the escalation path: who receives the report, who can act, and whether either was available.

Sales per visit falls → you may be over-visiting low-velocity stores. Reallocate frequency toward stores that reward it, rather than adding visits everywhere.

Report on one page, monthly

The reporting failure is as common as the measurement failure: a dashboard nobody opens, or a fifteen-page deck that hides the decision. One page:

1. The six numbers, current month against last month and against target.
2. Best and worst five stores by OSA, named. Averages hide the stores you can actually fix.
3. Exceptions — visits missed, OOS unresolved beyond target, compliance failures escalated to the retailer.
4. One decision requested. A report that asks for nothing gets read by nobody.

Distributors reporting to a brand principal need a slightly different pack, oriented to proving execution — see distributor reporting.

Three measurement anti-patterns

• Measuring people before measuring the system. If the route plan is impossible, individual scores measure the plan, not the person. Fix the system first, and say so to the team — it buys the honest reporting everything else depends on.
• Adding KPIs instead of acting on them. A team measured on twelve things is measured on nothing. Six is already generous; four would do.
• Reporting up without feeding back down. Field staff who never see the numbers they generate stop caring about their accuracy, which quietly destroys the data. Send the same one-pager to the team that goes to management.

Frequently asked questions

What is a good on-shelf availability figure?
There is no universal number — it depends on category, retailer and how tightly the supply chain is run. Measure your own baseline for a month, then set a target above it and move it as you improve. A benchmark from another brand in another category tells you nothing actionable about yours.

Should field staff be paid on KPIs?
Be careful. Incentivising visit count produces short visits; incentivising OSA can produce optimistic reporting unless photo proof is watertight. If you do incentivise, tie it to something the merchandiser genuinely controls and that is externally verifiable — photo-verified planogram compliance is a better candidate than sales.

How do I measure any of this without software?
A structured form and a shared sheet will run all six for a small team. What you cannot do on paper is verify photos at scale or compute resolution times reliably, which is where a field-ops tool starts earning its cost — usually somewhere around the point of several merchandisers across several states.

My team says the targets are unfair. What now?
Check the route plan first, with real travel times. In most disputes the plan is genuinely unachievable and the team is right, and discovering that is worth more than winning the argument. If the plan holds up, the conversation becomes about performance with the ground cleared.

How often should I review these?
Monthly for the numbers, weekly for exceptions. Anything reviewed quarterly is being reported rather than managed, and by the time a quarterly review surfaces a problem, a full review period of shelf performance has already been lost.

Sources: this guide is field-operations practice rather than a statement of any published standard. Retailer-specific measures such as on-shelf availability definitions and planogram compliance criteria vary by chain and by supplier agreement — align your definitions with what your retailer measures where possible, so your numbers and theirs can be discussed rather than reconciled.