A permanent journey plan (PJP) is a fixed, repeating schedule stating which outlets a salesperson visits on which day of a weekly or monthly cycle. It turns coverage from something decided each morning into something planned once and executed repeatedly.
Why a PJP matters
Without a standing plan, the day's route is chosen by the person driving it, and the choices are predictable: nearby outlets over distant ones, friendly buyers over difficult ones, and outlets that ordered last time over those that did not. The territory develops quiet gaps that nobody decided on.
A PJP also matters to the outlet. A shopkeeper who knows the rep comes every Tuesday can hold their order for that visit, plan working capital around it, and raise issues at a known time. Predictability is worth real money in a relationship business — it is why the plan is called permanent.
How a PJP is constructed
The plan is a grid of coverage against time, built from a small number of decisions:
- Cycle length — usually one week or four weeks. A monthly cycle allows frequencies finer than "weekly or not at all".
- Working days — days available per cycle, net of holidays and non-selling time.
- Visit frequency per outlet — derived from outlet value or potential, so effort follows contribution.
- Daily capacity — realistic calls per day, including travel, which is the constraint that makes the arithmetic honest.
- Assignment — which day, and which person.
The plan is feasible only if the total visits demanded per cycle fit within days × capacity. Most unrealistic plans fail this test at the design stage and are never checked.
An example
A four-week cycle with 24 working days and a capacity of 28 calls a day gives 672 visits per cycle. A universe of 480 outlets, where 90 are visited weekly (360 visits) and 390 monthly (390 visits), demands 750 — about 12% more than capacity. The plan will fail, and it will fail invisibly: reps will drop the outlets that are furthest away and least welcoming, which are frequently the ones with the most headroom.
Common variations
- Weekly PJP. A single week repeated. Simple, but frequencies below weekly are hard to express.
- Monthly cycle with week-of-month patterns. An outlet is visited in weeks one and three, say, which supports fortnightly coverage cleanly.
- Rolling PJP. Regenerated periodically from recent outlet performance, trading predictability for responsiveness.
Limitations worth stating
A PJP is a plan, and the territory keeps moving underneath it. Outlets open, close, change hands and change value; a plan not revisited for a year is quietly wrong in a hundred small ways. Rigidity is the other failure: a plan with no slack cannot absorb an urgent customer request or a market visit, so either it gets broken routinely — teaching everyone the plan is optional — or genuine opportunities are refused. Well-run teams leave deliberate slack rather than pretending days are fully bookable.
How xMatix supports permanent journey plans
In xMatix Field Sales, the journey plan lives on the visit route itself. A route carries its own schedule — day-of-week flags, a week-of-month pattern, or a cron expression — and visit plans are materialised from it automatically over a rolling lead-days window, so the coming days' lists exist in advance without anyone assembling them.
Because generation is continuous rather than a one-off import, changes to the plan take effect on the next generation rather than requiring a rebuild. Stops can be transferred between routes as territories change, plans can be assigned and accepted by the person who will execute them, and stale visits that were never executed are cleaned up rather than accumulating as false backlog.
Sequencing within the plan is versioned separately — planned, road-network optimized, and learned from the order reps actually drove — so the journey plan states which outlets and when, while route optimization answers in what order.
Related: beat planning · route optimization · territory planning