Beat Planning
Journey plans that never let a shop fall off the round.
Divide each van rep’s customers into beats served on a rotating cycle, let the system propose beats from real buying history, see the drive on a map, and give every rep an automatic day plan that pulls in overdue and skipped customers. Skips need a reason, and coverage gaps are reported.
- A/B/C classification
- Propose from history
- Route map
- Auto day plan
- Skip with reason
How it runs, start to finish
Built for
- Van-sales operations with fixed routes or rotating cycles
- Managers who need to prove coverage, not just sales
- Teams reassigning territories when reps join, leave or go on leave
- 1
Classify customers
A, B or C from eight weeks of invoices: A every two days, B at their revisit interval, C weekly.
- 2
Propose beats from history
Rotating beats built from when, and in what order, the rep actually serves each customer.
- 3
Set the route
On the map, with drive times, “usual order vs shortest drive”, expected arrival per stop and the return time.
- 4
Assign the rep
The customer book moves with the beat. Adding a BD-created customer to a beat is the hand-over to the van.
- 5
Work the day plan
Today’s beats plus overdue, never-served and yesterday’s skipped stops. An invoice completes a stop; a skip needs a reason.
- 6
Watch the exceptions
“Not served in N days”, a “no van rep” bucket and team-leader coverage views.
What you get
Everything below is live in the product today.
Beat rhythm
A cycle length (7 for weekday routes, or a rolling 1-, 2- or 3-day rotation) and a serving day per beat.
A/B/C classification
From real invoices, with cadence per class.
Propose from history
Builds rotating beats from the rep’s actual serving pattern.
Route map
Google drive times, stop order comparison, ETA per stop and return time.
Automatic day plan
Today’s beats plus overdue, never-served and yesterday’s skipped customers, on the rep’s phone.
Skip with reason
Reasons the Super Admin configures; a skipped stop carries to tomorrow.
Reassignment cascade with preview
Move a whole beat to a new rep in one step. Past sales stay with whoever held the customer on the day; BD ownership is untouched.
Stand-ins for absences
Cover a beat for up to 31 days with quick picks from the absence register.
Coverage exceptions
“Not served in N days” with a “no van rep” bucket, plus team-leader coverage views.
Roles and seats
Your Super Admin switches the module on and decides who holds each duty. Only the roles marked “seat” count against what you buy — back-office duties are free.
Beat planner
FreeA grant to managers and team leaders — the sales side designs territories. Not a seat.
Van Sales rep
FreeGets the day plan automatically; no extra seat.
Web for the office, mobile for the field
The module lands inside the same OrbisField apps your team already signs in to — no second product, no second login.
Web dashboard
- Operations ▸ Beats: beats, route map, assignments, exceptions
Mobile app
- Van Sales ▸ Day Plan for reps
- Beats for managers with the planner grant
How Beat Planning connects
Every module shares the same customers, products and stock ledger, so switching one on never means re-entering data in another.
Requires
Beat Planning questions
No. An invoice completes the stop. Only a skip needs the rep to pick a reason.
No. Sales stay with whoever held the customer on the invoice date.
Yes, once the Super Admin grants them the planner hat.
Run Beat Planning on OrbisField
Pick it in the sign-up wizard, or switch it on later from your dashboard. The wizard adds any prerequisites for you.