How beat planning works

Beat planning fails quietly. Nobody rejects the plan; the team simply cannot execute it, and the outlets that get dropped are the ones furthest away and least welcoming — often the ones with the most headroom.

This guide covers how to build a plan that fits, and the checks that catch an unworkable one before it reaches a field team. For the definition, see what is beat planning.

1. Establish the universe before the routes

List the outlets worth calling on, and classify them by value or potential. Every later decision depends on this, and the common error is planning coverage for outlets nobody has confirmed still trade.

Two hygiene items pay for themselves immediately: remove duplicates, because a duplicated outlet fragments the history that trend analysis depends on, and capture geolocation, because without coordinates no sequencing or territory work is possible later.

2. Set frequency from value, not habit

Frequency should follow contribution. A common starting structure:

Top tier — weekly. Usually a small fraction of outlets and a large share of volume.
Middle — fortnightly.
Tail — monthly, or served through a digital channel rather than a visit.

The instinct to promise everyone a weekly visit is the single most common cause of unworkable plans. It feels equitable and it guarantees the promise is broken somewhere — invisibly, and not where you would choose.

3. Do the capacity arithmetic honestly

This is the step that separates plans that work from plans that do not.

Capacity per cycle = working days × realistic calls per day.

Demand per cycle = Σ (outlets in tier × visits per cycle for that tier).

If demand exceeds capacity, the plan will fail. Not "will be challenging" — will fail, and the failure will be distributed by convenience rather than by value.

Be honest about calls per day. It is not the number of visits a rep can theoretically make; it is what they achieve including travel, waiting, a shop shut for lunch, and the two calls that overrun. If your data says 28 and your plan assumes 35, the plan is already 20% over.

Leave deliberate slack — five to ten per cent — for urgent customer requests and market visits. A plan with no slack gets broken routinely, which teaches everyone the plan is optional.

4. Group for geography, then sequence

Cluster outlets into beats that are geographically coherent; a beat that zigzags across a city spends the day in transit. Then decide the order of stops, which is a separate decision — see route optimization.

Where you have several people and a shared universe, the split across them is a territory planning problem and benefits from being solved as one rather than drawn by hand.

5. Express the plan as a repeating schedule

Convert the beats and frequencies into a permanent journey plan: which beat runs on which day, in a weekly or four-weekly cycle. A monthly cycle is worth the extra complexity because it expresses fortnightly coverage cleanly, which a weekly cycle cannot.

Five checks before you publish

Capacity check. Demand per cycle ≤ capacity per cycle, including slack.
Frequency-value check. Do high-value outlets actually get higher frequency? Sort by value and look at the frequency column — misalignment is obvious and common.
Geographic check. Plot each beat. If a day's stops are not visually clustered, the grouping is wrong regardless of what the counts say.
Ownership check. Every outlet belongs to exactly one beat. Outlets in two beats get visited twice or not at all; outlets in none disappear.
Day-balance check. No day should be significantly heavier than the others, or that day will be the one that fails every week.

Then measure the gap between plan and execution

A beat plan is a hypothesis. The value comes from comparing it to what happened: which planned visits were made, which were missed, and whether the misses cluster. They almost always do — the same outlets at the end of the same two beats — and that pattern is a planning fix, not a performance conversation.

Revisit quarterly. Territories move: outlets open, close, change hands and change value. A plan untouched for a year is quietly wrong in a hundred small ways.

How this works in xMatix

In xMatix Field Sales, a beat is a visit route: a named collection of outlet stops with per-stop geofence tolerance and its own schedule — day-of-week flags, a week-of-month pattern, or a cron expression. Visit plans generate from that schedule automatically over a rolling lead-days window, so the day's list exists in advance and coverage has a denominator.

Sequencing is versioned separately as planned, road-network optimized, and learned from what reps actually drove. Territory splits across people use a capacitated solver with service minutes, shift windows, balance tolerance and capacity as settings. Stops can be transferred between beats as territories change, plans that were never executed are cancelled rather than accumulating, and execution — visits, orders, activities, attendance — is captured offline and reconciled through a durable outbox.