How to Build a Beat Plan Your FMCG Reps Will Actually Follow

Most beat plans I've seen were built in Excel by someone who hasn't ridden with a rep in five years.

And it shows. Reps skip outlets. Managers chase compliance numbers. The plan looks great on paper and falls apart by Wednesday.

I've spent the last few years building Zivni with FMCG distributors across Dubai, Karachi, Riyadh, and now a few in Manchester. So I've watched hundreds of beat plans get built, broken, and rebuilt. Here's what actually works when you sit down to design one from scratch.

Start with the outlet, not the rep

Honestly, this is where most people get it wrong. They start by asking "how many reps do I have?" and divide the city into that many chunks. Backwards.

Start with your universe of outlets. Every single one. If you don't have a clean master list with GPS coordinates, category, channel type, and average monthly offtake — stop and build that first. I know it's boring. Do it anyway.

One distributor we work with in Sharjah had 2,847 outlets on their books. When they actually mapped them, 611 had shut down or moved. That's 21% of their beat plan chasing ghosts.

So step one: clean the outlet master. Category A, B, C classification based on monthly sales value or volume. Don't overthink the buckets — top 20% by revenue is A, next 30% is B, rest is C. Move on.

Decide visit frequency before you decide routes

Here's the thing — a beat plan is really just a frequency plan with geography attached.

A-class outlets usually get visited weekly. Some FMCG categories (dairy, bakery, fresh) need twice a week or daily. B-class outlets typically fortnightly. C-class monthly, sometimes only for order-taking calls rather than full merchandising.

Write this down for each category and channel. Modern trade in Jeddah behaves nothing like traditional trade in Multan. Don't copy-paste frequency logic across markets.

Once you have frequency locked, you can calculate the total workload:

• 400 A outlets × 4 visits/month = 1,600 calls
• 700 B outlets × 2 visits/month = 1,400 calls
• 1,200 C outlets × 1 visit/month = 1,200 calls
• Total: 4,200 calls per month

Divide by working days (say 24) and you get 175 calls per day. If a rep can realistically do 35 productive calls, you need 5 reps. Not 4. Not 7. Five.

This simple math saves people from either overstaffing or burning their team out. Both happen a lot.

Cluster geographically, then sequence smartly

Now you draw territories. And this is where field sales route planning gets interesting.

Don't just draw circles on a map. Cluster outlets by natural boundaries — a main road, a market area, a residential zone. Reps understand "Al Quoz industrial" or "Saddar wholesale market" better than "Zone 4-B."

Within each territory, split into 6 daily beats (Monday to Saturday). Every beat should be a tight geographic cluster the rep can cover in one working day without zigzagging across the city. If your rep is doing 40 km between two consecutive outlets, something's wrong.

For sequencing inside a beat, I've seen two schools of thought:

1. Start from the farthest point and work back — good for reps who live centrally, less fuel wasted at end of day
2. Nearest-neighbor from the depot — better if reps carry stock and need to reload

Either works. What doesn't work is letting reps decide the sequence themselves every morning. That's how you end up with outlets getting visited at 4:47 PM when the shopkeeper is closing shutters.

Good beat planning software (yes, including Zivni) will auto-sequence based on GPS and travel time. But even a manual sequence, locked in and followed, beats improvisation.

The bit everyone forgets: buffer time

A rep's day is not 8 hours of pure calling. It's calling minus travel, minus lunch, minus that one customer who wants to argue about a damaged case from three weeks ago.

Assume 60-70% of the workday is actually productive selling time. If you plan for 100%, your beat plan will fail by Tuesday and your reps will lie on their reports by Friday. I've seen both.

Build in a weekly buffer day too. Reps use it for makeup calls, collections, or catching up with A outlets that need extra attention. Don't schedule it as "admin day" — schedule it as "flex day" and track what actually happens on it. You'll learn a lot about where your plan is leaking.

Publish it, measure it, tune it monthly

A beat plan isn't a document. It's a living thing.

Once your beats are live, watch three numbers religiously:

• Beat adherence — did the rep visit the outlets scheduled for today?
• Productive call rate — of visits made, how many resulted in an order or a merchandising action?
• Outlet coverage — over 30 days, what % of your universe got visited as planned?

If adherence drops below 85%, your plan is probably unrealistic (or your reps aren't bought in — different problem, different fix). If productive calls drop below 60%, your frequency or targeting is off.

Review the whole thing monthly. Outlets open, close, change hands. New malls come up. Roads get blocked for construction (looking at you, half of Riyadh right now). A beat plan from January is stale by April.

One last thing — involve your reps in the review. They know which outlets are dead, which ones are secretly buying from three distributors, and which routes have a traffic nightmare between 2 and 4 PM. Ignoring that intelligence is expensive.

And if you're still doing all this in Excel with color-coded tabs, we should probably talk.