Effective field sales KPIs measure what a rep can control: visits completed, coverage hit against the plan, orders captured, and verified on-site work. Metrics tied to factors outside the rep’s hands, like a client’s headcount or app login counts, punish the wrong people and erode trust in the entire scorecard.
Picture a sales manager building a performance scorecard for the field team. One line on it counts how many people at each client account actively use the system the rep manages. On a spreadsheet it looks reasonable. Then the client reorganizes, lets ten people go, and the number drops. The rep did nothing wrong. Their coaching was fine, their coverage was fine, their reports came in on time. The scorecard turns red anyway.
This exact argument plays out in operations reviews across the country, usually as some version of the same question: paano kung nag-resign yung tao? Hindi naman nila control yun. If a rep cannot move a number by doing their job well, why is that number on their scorecard?
The instinct to measure everything is understandable. Field work is hard to see. The team is scattered across routes, stores, and provinces, and the manager wants a dashboard that proves the day happened. But a scorecard packed with the wrong measures does not create accountability. It creates resentment, gamed numbers, and a report nobody trusts.
Why most field sales KPIs fail
Two failures show up again and again.
The first is measuring outcomes the rep does not control. Revenue booked at an account depends on the client’s budget, the category’s health, a competitor’s promo, and a dozen decisions made above the rep’s pay grade. The number of active users at a client depends on the client’s hiring. Tie a rep’s evaluation to any of these and you are grading them on the weather.
The second is measuring presence instead of work. The easiest metric to pull is often login activity: did the person open the app this month? Nag-login ba siya? It feels like usage data. It is not. A login proves someone tapped an icon. It says nothing about whether they ran their route, completed their store checks, or captured a single order. Presence is not performance, and a team quickly learns to produce whatever the dashboard counts.
British economist Charles Goodhart described the trap decades ago. Once a measure becomes a target, it stops being a good measure, because people optimize for the number rather than the work the number was meant to represent. If you reward logins, you get logins. You do not get coverage.
There is a simpler way to see the same problem. Revenue, retention, and account growth are lagging indicators. They are the results, and they arrive late, shaped by many hands. The work a rep does today is a leading indicator: the visit made, the order taken, the stockout caught. Evaluate people on lagging results alone and you are holding them responsible for outcomes that a good quarter of effort might not move for months. Evaluate them on the leading actions and you are measuring the part they own.
The control test for field sales KPIs
Before any metric goes on a field scorecard, run it through one question: can the rep move this number, up or down, purely by how well they do their job?
If yes, it belongs. If the number can swing because of a client’s decision, a market shift, or a colleague’s resignation, it fails the test. It might still be worth tracking as context for the manager, but it does not belong on the individual’s evaluation.
Apply it honestly and most bloated scorecards shrink fast. “Total revenue in territory” fails. “Planned visits completed” passes. “Client’s active headcount” fails. “Orders captured per covered store” passes. “System login” fails. “Store audits submitted with a valid photo and location” passes.
The passing metrics share a trait: they describe an action the rep personally takes, and they can be verified. That second half matters as much as the first.
Measure verified work, not self-reported activity
A controllable metric is only useful if you can trust the number behind it. This is where a lot of field measurement quietly falls apart.
If a rep marks a visit as done in a form, and nothing checks whether they were actually at the store, the metric measures typing, not visiting. If a store audit is a photo pasted into a Viber group at the end of the day, you have no way to know when or where it was taken. The manager ends up defending numbers they cannot actually stand behind, which is the worst position to be in when a client or a boss starts asking questions.
Trust breaks in a specific, damaging way. A report goes out, someone acts on it, and later the number turns out to be wrong. After that, the whole dashboard is suspect. A metric you cannot verify is not a weak metric. It is a liability, because it invites decisions built on data that may not hold.
The fix is to attach proof to the action. A visit counts when it carries a timestamp and a GPS location. A store check counts when it carries a photo taken on site, not uploaded later. Coverage counts when planned routes can be compared against where the rep’s device actually was. Verification is what turns a controllable metric into a trustworthy one.
What controllable field metrics look like in the Philippines
For a distributor or FMCG field team, the metrics that survive the control test are the ones tied to route-to-market execution. Coverage completed against the plan for the day. Stores visited with GPS confirmation. On-shelf availability checks submitted with photos. Orders captured per covered outlet. Stockouts flagged before the shelf goes empty. These are all things the rep does, and all things a system can verify. (A worked breakdown by field-team type lives in our guide to Tarkie use-cases for Philippine field teams.)
For a field service or technician team, the equivalents are work orders closed, service visits completed with on-site confirmation, and first-visit completion rate. For a merchandising team deployed into supermarkets, it is planogram compliance photos, promo execution checks, and audits filed from the store floor.
Manpower and staffing agencies face the sharpest version of this. When you deploy hundreds of people to a client’s sites, the client is paying for attendance and coverage they can verify, not for a timesheet someone filled in from home. Megasoft runs secure attendance and coverage data from 1,500 merchandisers and coordinators on Tarkie, which is the scale at which self-reported numbers stop being defensible and verified ones start protecting the contract.
None of these depend on the client’s headcount or the health of the category. They depend on whether the person did the field work, and they leave a verifiable trail. That is the entire point.
How Tarkie makes field metrics controllable and verified
This is the problem Tarkie was built to solve for Philippine field teams. Every field action in the system carries proof: attendance is geo-tagged, store visits are timestamped and location-confirmed, and audits are captured with photo validation from the site itself, so a completed visit means the rep was actually there. Managers see planned coverage against actual coverage in real time, which turns “did the route happen?” from an end-of-day guess into a live answer. For FMCG teams this rolls up into coaching views, scorecards, and leaderboards built on activity a supervisor can trust.
The clearest example is coverage. Chooks-to-Go digitized 90% of their field reports and doubled store coverage from 10 to 20 stores per day per field employee. That is the model controllable metric. Stores covered per rep per day sits entirely within the rep’s control, it is verified by the system, and it maps directly to how the business grows. It rewards the work, and only the work.
How to fix your field sales scorecard this quarter
Pull your current field scorecard and run every line through the control test. Mark each metric as “rep controls it” or “rep does not.” Delete or demote everything in the second column.
Replace outcome metrics with the activities that drive them. Swap “revenue in territory” for “planned visits completed” and “orders captured per covered store,” which the rep can move directly.
Kill login and presence metrics. Ask what work you actually want to see, then measure that work: completed visits, submitted store checks, orders taken.
Attach proof to every remaining metric. If a metric cannot be verified with a timestamp, a location, or a photo, decide how you will verify it before you grade anyone on it.
Separate context from evaluation. Keep client headcount, category trends, and market conditions on the manager’s view for coaching, but off the individual’s scorecard.
Rebuild trust in the numbers before you rebuild the dashboard. Confirm the data behind each metric is accurate, because one wrong report undoes a quarter of goodwill with a client.
You can do most of this without new software. The scorecard cleanup alone makes reviews fairer and less contentious. Verification is where a system earns its place, because proof at scale is hard to collect on paper.
Fair metrics start with data you can trust
If your field scorecard still counts logins and outcomes your reps cannot control, the fix starts with measuring verified work instead. Tarkie gives Philippine field teams geo-tagged, photo-verified activity data, so every metric on the board is one the rep can move and one you can stand behind. See it against your own coverage plan: book a demo at https://go.tarkie.com/inquire.
Which metric on your current scorecard would fail the control test first?
Frequently asked questions
What are the best KPIs for a field sales team?
The best field sales KPIs measure actions the rep controls and that can be verified, such as planned visits completed, coverage against the route plan, orders captured per covered store, and audits submitted with a valid photo and location. Avoid grading reps on total territory revenue or client headcount, which move for reasons outside their control.
Why should app login count not be used as a performance metric?
A login only proves someone opened the app, not that they did any field work. Teams graded on logins learn to log in and nothing more. Measure the work you actually want to see, like completed visits and submitted store checks, rather than mere presence.
How do you measure field team performance you cannot directly see?
Attach proof to each action. A visit counts when it carries a timestamp and GPS location, a store check counts when it includes a photo taken on site, and coverage is measured by comparing planned routes to where the device actually was. Verification replaces trust-based self-reporting.
What is the control test for a KPI?
The control test asks whether a rep can move a metric up or down purely by how well they do their job. If a client’s decision, a market shift, or a colleague’s resignation can swing the number, it fails the test and should not sit on that person’s individual scorecard.
What field sales metrics work best for FMCG and distribution teams in the Philippines?
Route-to-market execution metrics work best: coverage completed against the daily plan, stores visited with GPS confirmation, on-shelf availability checks with photos, orders captured per outlet, and stockouts flagged. Each is controlled by the rep and verifiable by the system.