The beat plan is signed off on a Friday afternoon. Forty-two outlets, four days, one rep, a neat loop across the eastern side of Nairobi. The spacing looks sensible and the distances add up. Nobody who approved it has driven it.
By ten on Tuesday the rep has covered four kilometres and made two calls. A stalled lorry has closed a lane. The duka at number seven is shut because the owner has gone to the wholesaler herself. The three outlets clustered near a matatu stage — the ones that move real volume — sit at the end of the sequence, and he will reach them long after the lunchtime rush.
None of that reaches the compliance report. It will show thirty-eight of forty-two visits completed, a respectable number, and a supervisor with no idea that the best shops on the route are being served at the worst hour of the day.
What a Beat Plan Is Meant to Do
A beat plan answers three questions at once: which outlets belong to whom, how often each is called on, and in what order. Get one wrong and the other two stop working. A rep with too many outlets rushes the ones that matter; a rep with the right number in the wrong sequence spends the day in traffic.
What makes this hard in Kenya is the shape of the trade. Most consumer volume moves through a long tail of small independent outlets — dukas, kiosks, roadside stalls, agrovets, stalls inside an open-air market — buying small quantities several times a week, often from a wholesaler rather than direct. Modern trade matters — chain supply into Naivas, Quickmart or Carrefour has its own rhythm — but it is the secondary motion. The beat plan is built for the long tail, which is dense, informal and constantly moving. It is not a map exercise but a claim about how a working week should be spent, and like any claim it has to be checked against what happened.
Territory Comes Before Route
Before anyone sequences a day, someone decides what belongs in the territory at all. A route can be re-sequenced in an afternoon; a badly cut territory takes a quarter to unwind, because credit has already been extended and reassigning a shop means telling an owner that the person she has dealt with for two years is no longer hers.
Territory design balances things that pull against each other — outlet count, travel time, expected value, and the effort each type demands. An agrovet placing a seasonal order needs a different call pattern from a kiosk buying sachets twice a week, and a wholesaler supplying forty dukas is one line on the plan and forty shops' worth of consequence if it goes wrong.
Two habits keep territories honest. Classify outlets by throughput rather than counting them, so a duka on a busy junction and a kiosk on a quiet lane are not treated as equivalent units. And deactivate dead outlets as routine — shops here open, close, change hands and reopen a hundred metres away under a new name. If nobody owns that job, every coverage number built on the territory is wrong.
Sequencing Outlets When the Road Decides
Distance is a poor proxy for time anywhere. In Nairobi it is close to useless. Two outlets four kilometres apart may be eight minutes apart at half past seven and fifty minutes apart an hour later, and that gap is most of a working morning across a week. A sequence optimised on distance looks efficient on a map and costs the rep an hour a day on the road.
Sequencing that survives contact with the city follows a few rules. Cluster tightly, so the rep works a pocket of outlets on foot rather than driving between them. Put high-value calls at the hour the owner can actually talk, which is usually early. Face the direction of traffic rather than fighting it, and accept a longer loop that runs with the flow over a shorter one that crosses it twice.
Matatu Stages and Where Trade Clusters
Kenyan retail is not spread evenly along a road. It clusters, and the strongest clustering force is where people get on and off matatus. A matatu stage concentrates footfall into a few predictable windows a day, and the outlets around it — kiosks, roadside stalls, a couple of dukas, sometimes a mini-mart — trade at a different intensity from shops two hundred metres away.
That matters three ways. Those outlets need calling before their peak, not during it, because an owner serving a queue will agree to anything to end the conversation. They usually justify a higher call frequency, since they sell through faster. And they sit close enough that the cluster should be one stop on the plan, worked on foot, rather than several entries implying travel between them.
Open-air market days do the same on a weekly cycle: a rep arriving the day before a market day and the day after is having two different conversations.
The Long Upcountry Leg
Away from the cities the problem inverts. Instead of many outlets and no time, there are few outlets and a great deal of road. A rep working out of Nakuru or Eldoret along the Northern Corridor may drive an hour between meaningful clusters, and the A104 sets the shape of the week whether the plan acknowledges it or not.
Upcountry beats need their own rules. Frequency has to be traded against travel honestly — a fortnightly call carrying an order of, say, KSh 40,000 beats a weekly call that cannot pay for the fuel to reach it. Trading centres along the corridor should be one day's work, not split across two visits. And the wholesaler in the nearest town is usually the anchor call: if the fast lines are not on that floor, everything downstream runs out regardless of what the rep sells.
A Wednesday Beat Out of Thika
Consider a Wednesday worked out of Thika. The rep starts before eight at a wholesaler on the edge of town, checking that the two fast lines are on the floor. Several of his larger duka accounts buy there later in the week, and if the stock is missing today, half his outlets are empty by Saturday whatever he sells them.
By nine he is at a cluster of six outlets around a matatu stage — four kiosks, a duka and a roadside stall — and works them on foot in forty minutes. One has taken a competitor's promotion and wants to halve the order; he records it, because otherwise nobody at head office learns of it before the month closes. One is shut, and he logs a bypass with a reason rather than leaving a gap. Mid-morning he drives twenty-five minutes to an agrovet that buys monthly and in size — the largest order of the day, which is why it sits at an hour when the owner can talk.
The afternoon is the long leg: four shops along a stretch of road, none worth the drive alone but which together fill the run home. The supervisor can see which outlets were served, which were bypassed and why, and where the competitor promotion appeared. What the numbers do not show, and the rep noted, is that two of those afternoon outlets should move to a fortnightly call.
GPS Check-In and What It Proves
A location-stamped check-in tied to a specific outlet at a specific time does a narrow job well. It confirms the rep was where the plan said, when the plan said — and that is all it does. It says nothing about whether he went inside, spoke to the owner or counted the shelf.
The value appears when the check-in is joined to something else. Next to a visit duration it shows whether the call was long enough to contain a conversation. Next to an order, a photo or a completed task list it becomes a record of a call rather than of a location. On its own it becomes the metric the programme drifts towards — and check-ins are easy to produce without selling anything.
Two constraints shape how this works in Kenya. Signal thins outside the main towns and disappears on parts of many routes, so check-ins, orders and photos must be captured locally and synchronised when a connection returns. Power is separate: Kenya had a nationwide blackout in 2026 and tariffs remain high, so neither the rep's phone nor the distributor's back office can be assumed continuously powered. Both are design conditions, not crises.
Geofences and the Awkward Cases
A geofence is a radius around an outlet's recorded location, inside which a check-in is accepted. The concept is simple; the awkwardness is the radius. Too tight and honest visits are rejected, because the coordinate was captured across the road or the fix is poor between buildings. Too loose and the rep can check in from the matatu without leaving his seat.
Most trouble traces back to the outlet master rather than the fence. If the coordinate was captured carelessly at onboarding — from a vehicle, or pinned approximately at the office afterwards — every later visit argues with a fence built on bad data. Geo-tagged capture at first contact, standing at the shop, is what makes geofencing work at all. Some outlet types then need their own treatment: stalls inside an open-air market sit within metres of each other, so a radius wide enough to accept one will accept its neighbours. There the honest answer is a wider fence plus a second form of evidence.
Missed Calls Are Data, Not Failure
Every beat produces calls that do not happen. The shop is shut. The owner has travelled. The road is closed. The outlet has been sold and the new owner buys elsewhere. If there is no way to record these, the rep has two options: leave a gap that looks like indiscipline, or produce a check-in that did not happen. Programmes that punish missed calls without capturing reasons reliably get the second.
A short, closed list of reason codes — closed, owner absent, refused, road inaccessible, outlet ceased trading — turns a gap into information, and the pattern across a month is where the value sits. One duka shut on a Tuesday means nothing. The same duka shut on four consecutive Tuesdays means the beat day is wrong. An outlet repeatedly logged as ceased trading should leave the territory rather than depress coverage forever.
Measuring Beat Compliance Without Rewarding the Wrong Thing
The standard measures are easy to define and easy to game: planned calls against actual calls, calls made in the planned sequence, productive calls and time in outlet. Each is reasonable on its own; the problem starts when one becomes the headline.
- Weight outlets by throughput. Near-perfect adherence achieved by skipping the three biggest shops is a worse week than a patchier one that covered them.
- Pair adherence with an outcome. Compliance read next to lines sold per call, or availability of the core range, is far harder to fake than compliance alone.
- Keep the denominator clean. Coverage is a fraction, and if closed outlets are never removed it ends up measuring record-keeping rather than field effort.
- Read the sequence, not just the count. Every call made in the wrong order is a different failure from most made in the right one.
- Give supervisors the view the same week. A monthly report cannot change a route; a Tuesday evening view can change Wednesday.
A beat plan is a hypothesis about how time should be spent. Compliance measurement exists to test it, not to prove that everyone did as they were told.
Where Beat Compliance Programmes Go Wrong
The most common failure is planning in the office and never revising. A route drawn once from a spreadsheet and defended for a year will be wrong in a market where shops open and close constantly, and the harder it is enforced, the more effort goes into satisfying a plan that no longer describes the territory. The second is treating the check-in as the deliverable: once adherence decides the rep's month, adherence is what gets produced, and sales stay flat while the dashboard improves.
- Geofences tightened to cover for a bad outlet master. The rejections land on honest reps, and the response is a workaround rather than better data.
- Frequency set by convention, not sell-through. Every outlet called weekly because that is how it has always been done, regardless of how fast each turns stock.
- No route for the rep's local knowledge. The person who drives the beat knows why the sequence is wrong, and has nowhere to say so.
- Territory changes made without handover. Reassigning outlets without account history, credit position and the owner relationship loses more than it tidies.
- Compliance measured, travel ignored. Two beats at the same adherence, one of them spending three hours a day on the road, are not the same beat.
Underneath most of these sits one assumption worth challenging: that the plan is the truth and the field is the variance. In this channel it is usually the other way round.
How 1Channel Supports Beat Planning and Compliance
1Channel provides the planning and field layer a programme like this runs on. Territories and beats are defined centrally, with outlets classified and assigned, call frequency set per outlet, and routes sequenced and revised by supervisors. Reps work the planned beat on a mobile app with attendance, outlet visits and location-stamped check-ins, capturing orders, task lists and photo proof.
Geofencing is configurable per outlet rather than applied as one global radius, and closed or inaccessible outlets are logged as bypasses with reason codes instead of leaving gaps. The outlet master holds geo-tagged capture at first contact, classification, norms and deactivation of shops that have stopped trading. The app works offline and synchronises when connectivity returns, and reporting rolls up from outlet to beat, supervisor, territory and national view.
On compliance, 1Channel is not a certifying body and makes no such claim: the product supports invoicing and record-keeping workflows aligned with eTIMS requirements, and is built to help organisations meet their own obligations under the Data Protection Act, 2019. More detail sits on the capability pages: route planning software, territory management, outlet and store management, field activity management and attendance.
Key Takeaways
A beat plan is not a map. It is a weekly argument about where a rep's hours should go, and in Kenya the road, the matatu stage and the market day have as much say in it as the planner does.
- Fix the territory before the sequence. Outlet classification, call frequency and routine deactivation of closed shops decide whether any downstream number means anything.
- Plan in minutes, not kilometres. Congestion in Nairobi and long legs on the A104 make travel time the real constraint, and a distance-optimised route hides it.
- Follow the clusters. Trade concentrates around matatu stages and open-air markets, and those outlets need calling before the peak, not during it.
- Treat the check-in as evidence, not achievement. Location proves presence; only an order, a task or a photo alongside it proves a call took place.
- Make missed calls loggable. Reason codes turn a gap into a signal about the plan, while punishing gaps without capturing reasons just produces cleaner-looking data.
The teams that hold a beat plan together rarely have the most elaborate routing. They let the field correct the plan, measure adherence next to something the rep cannot fake, and change the route the week they learn it is wrong.
