PJP in Sales: What a Permanent Journey Plan Is and How to Build One

PJP Full Form and What It Actually Means

PJP stands for Permanent Journey Plan. In Indian FMCG and dairy distribution it refers to the fixed, repeating schedule that determines which retail outlets a sales representative visits on each working day of a cycle. The word permanent is doing real work in that phrase. The plan is not a suggestion or a route that gets rebuilt every morning. It is a committed cycle that repeats, so that a kirana store owner in a given lane knows their salesperson arrives every Tuesday, and the distributor knows roughly what that lane will order before the rep sets out.

Parameter	Indian Benchmark
Full form	Permanent Journey Plan
Cycle length	Weekly or fortnightly, repeating
Sales calls per rep per day, urban	30-45
Sales calls per rep per day, rural	18-25, travel-constrained
Delivery drops per day, dairy	60-150
Beat load target	~85% of theoretical capacity
Adherence, GPS-verified	85% acceptable, 90%+ well run
Productive call rate	60-75% established territory
Visit frequency A / B / C	Weekly / fortnightly / monthly
Review cadence	Quarterly beats, annual re-classification

You will also see the term written as Permanent Journey Cycle, or simply journey plan. Some organisations use PJP and beat plan interchangeably, which causes more confusion than it should. The distinction matters and we cover it below.

The reason PJP exists is economic rather than administrative. A field sales rep in Indian general trade is the single most expensive variable in the distribution cost structure once you account for salary, incentive, travel and supervision. Every hour that rep spends deciding where to go, backtracking across a territory, or calling on an outlet that had no reason to order is margin burned. A well-built PJP removes that decision from the rep entirely and replaces it with a route that has already been optimised for outlet value, travel distance and order frequency.

PJP vs Beat Plan: The Difference

This is the single most common point of confusion, so it is worth being precise.

A beat is one day of coverage. It is the specific cluster of outlets a rep visits on a single working day, usually geographically tight so that travel time between calls stays low. Monday's beat might be 38 outlets across two adjacent markets.

A PJP is the complete repeating cycle made up of all those beats. If a rep works six days a week and the cycle repeats weekly, the PJP is the full set of six beats plus the rules governing how often each outlet class gets visited.

Put simply: the beat is the day, the PJP is the calendar. You build beats first, then assemble them into a PJP. Our guide to what beat planning is in FMCG covers the day-level mechanics in more depth, and the beat planning software guide covers the tooling side, while our beat planning pillar sets out the whole discipline end to end.

The Coverage Maths Behind a Workable PJP

Most bad PJPs are bad because nobody did the arithmetic before drawing the routes. The maths is not complicated, but it constrains everything that follows.

Step 1: Establish Your Outlet Universe

Start with a verified count of every retail outlet in the territory that could stock your products, not just the ones you currently bill. This is your outlet universe. In most Indian territories the universe is 30-60% larger than the billed base, and the gap is where growth lives. If you skip this step you will build a PJP that perfectly services your existing customers and never finds new ones.

Step 2: Classify Outlets by Value

Classify each outlet into value bands, conventionally A, B and C, based on monthly offtake potential rather than current billing. A typical Indian general trade split lands near:

• A-class (roughly 15-20% of outlets): high-volume counters, often 50-60% of territory revenue. Visit weekly, sometimes twice weekly for perishables.
• B-class (roughly 30-35%): steady mid-volume outlets. Visit fortnightly.
• C-class (roughly 45-55%): low-volume or occasional counters. Visit monthly, or fold into a lower-cost channel.

Getting this classification wrong is expensive in both directions. Under-visiting an A-class outlet loses orders to whichever competitor shows up more often. Over-visiting C-class outlets consumes the working days you needed for the A-class ones.

Step 3: Calculate Required Call Capacity

Convert your frequency rules into monthly calls. For a territory of 1,000 outlets split 18/32/50 across A, B and C with weekly, fortnightly and monthly frequencies:

• A-class: 180 outlets x 4 visits = 720 calls
• B-class: 320 outlets x 2 visits = 640 calls
• C-class: 500 outlets x 1 visit = 500 calls
• Total: 1,860 calls per month

At a realistic 35 productive calls per rep per day across 25 working days, one rep delivers 875 calls a month. This territory therefore needs a little over two reps, not one. Most territories that feel chronically under-covered are simply carrying a PJP that was never reconciled against capacity.

Step 4: Build Geographically Tight Beats

Only now do you draw routes. Each day's beat should be compact enough that travel consumes well under a third of the working day. In dense urban markets a beat can be a few adjacent lanes. In rural and semi-urban territories the constraint flips and travel time, not outlet count, sets the ceiling, which is why rural beats often carry 20-25 outlets rather than 40.

What a Good PJP Looks Like in Practice

A usable PJP specifies, for every rep and every working day: the beat name, the ordered list of outlets, the planned call sequence, the expected time window, and the frequency class of each outlet. It is not a list of market names. If the plan does not name outlets in sequence, it is not a PJP, it is a territory sketch.

Three design rules separate plans that survive contact with the field from those that do not:

• Same day, same beat, every cycle. The value of a permanent plan is retailer predictability. Rotating beats week to week destroys the one benefit that justifies the word permanent.
• Sequence by geography, not by outlet importance. Reps should move in one direction through a beat. Zig-zagging to hit the biggest counters first adds travel time that costs more than the sequencing gains.
• Leave slack. A beat loaded to 100% of theoretical capacity fails on the first day a retailer wants a long conversation. Plan to about 85%.

Frequency Rules by Outlet Class

Classification drives frequency, and frequency drives the whole capacity calculation. The bands below are the common Indian general trade split.

Class	Share of Outlets	Share of Revenue	Visit Frequency	Calls / Month per 1,000 Outlets
A	15-20%	50-60%	Weekly	~700
B	30-35%	25-35%	Fortnightly	~650
C	45-55%	10-15%	Monthly	~500

Classification must rest on potential offtake rather than current billing, or the plan simply entrenches whatever coverage already exists. Our guide to effective coverage of outlets covers how to build the universe the classification sits on.

Measuring Whether Your PJP Is Working

Visit counts alone tell you almost nothing. Four metrics matter, and they should be read together.

PJP Adherence

The percentage of planned calls actually made, in the planned sequence, on the planned day. Below 80% adherence the plan has stopped describing reality and the reps are effectively self-routing. Adherence is only trustworthy when it is captured through GPS-stamped check-ins from a field sales mobile app rather than self-reported at day end.

Productive Call Rate

Also called strike rate: the share of visits that produce an order. Indian general trade benchmarks sit around 60-75% for established territories. A high adherence score paired with a low strike rate means the reps are going where you told them and the plan is sending them to the wrong outlets.

Lines Per Call

The average number of distinct SKUs sold per productive call, tracked as lines per call. This is the clearest indicator of whether reps are range selling or simply topping up the two fastest-moving lines. Improving lines per call is usually cheaper than adding outlets.

Coverage and ECO

Track unique outlets billed in the cycle against the universe, and watch effective coverage of outlets. Coverage that is flat while call counts rise means reps are revisiting the same comfortable counters.

Common PJP Mistakes

Building the plan once and never revising it. Outlet universes churn. New counters open, others close, and value classes shift with local demand. A PJP that has not been reviewed in a year is typically mis-routing 15-20% of its calls. Review quarterly at minimum.

Equal frequency for every outlet. Visiting every counter fortnightly is administratively simple and commercially wasteful. It under-serves the outlets that pay for the territory and over-serves the ones that do not.

Confusing PJP adherence with productivity. A rep can hit 98% adherence while selling nothing. Adherence is a hygiene metric, not a performance one.

Planning on paper or in spreadsheets. A spreadsheet PJP cannot be verified, cannot be updated centrally, and cannot tell you whether the rep was actually at the outlet. It also cannot re-sequence a beat when three outlets are shut. This is the point at which most distributors move to route optimisation software and GPS-backed attendance tracking.

Ignoring the delivery side. A sales PJP that is not aligned with the delivery route means orders taken on Tuesday arrive on Friday. For dairy and other perishables this gap is fatal.

Moving From Spreadsheet to System

Most distributors start with a PJP in Excel, and for a single rep with 200 outlets that is genuinely fine. The model breaks somewhere between three and five reps, because at that point the plan has to be maintained centrally, verified in the field, and reconciled against orders and deliveries every cycle.

What software changes is not the planning logic, which stays exactly as described above, but the feedback loop. GPS check-ins turn adherence from a claim into a measurement. Order data flowing back against the plan shows which beats are producing and which are not. Automatic re-sequencing handles the shut-outlet problem. And because the plan, the orders and the delivery routes sit in one place, the sales PJP and the delivery run stop drifting apart.

If you are evaluating whether that shift is worth it, the honest test is arithmetic: multiply your rep count by the hours per week currently spent maintaining and reconciling the plan, and compare it against the productive calls those hours could have generated. Our distributor ROI calculation guide walks through the same maths for the wider operation.

Building a PJP From Scratch: A Worked Example

Abstract rules are easy to agree with and hard to apply. Here is the whole sequence run against a real-shaped territory.

The territory. A dairy and FMCG distributor in a tier-2 city. Physical census finds 1,180 outlets that could stock the range. Current billing master holds 780, so 400 outlets have never been called on. Two salesmen, six working days a week, roughly 25 working days a month.

Step 1: Classify

Sorting the 1,180 by estimated monthly potential rather than current billing produces 190 A-class, 385 B-class and 605 C-class. Note the shape: the A-class list includes 40 outlets currently unbilled, which is where the fastest revenue in this territory sits.

Step 2: Convert to Calls

• A-class: 190 x 4 weekly visits = 760 calls
• B-class: 385 x 2 fortnightly visits = 770 calls
• C-class: 605 x 1 monthly visit = 605 calls
• Required: 2,135 calls per month

Step 3: Compare Against Capacity

Two reps at 35 productive calls a day across 25 days deliver 1,750 calls. The plan requires 2,135. The territory is short by 385 calls, roughly 22%.

This is the moment most PJPs go wrong, because the shortfall is usually resolved by pretending it does not exist: the plan is published anyway, reps silently drop the least rewarding calls, and six months later nobody can explain why C-class coverage collapsed. There are only three honest options.

• Add capacity. A third rep closes the gap with room to spare. Justified if the unbilled A-class outlets carry the volume the classification suggests.
• Reduce frequency on the tail. Moving C-class to a six-week cycle rather than monthly removes about 200 calls. Least damaging option if the tail genuinely is low-value.
• Remove outlets from the plan entirely. If 150 C-class outlets cannot be served at a positive contribution, say so explicitly and hand them to a wholesaler or a sub stockist rather than pretending they are covered.

Any of the three is defensible. Publishing a 2,135-call plan against 1,750 calls of capacity is not.

Step 4: Cut the Beats

With frequency settled, group outlets geographically into twelve beats per rep across a fortnightly cycle, keeping each beat inside a tight travel radius and loading to about 85% of theoretical capacity. A-class outlets appear in every cycle; B-class in alternate cycles; C-class slot into whichever beat covers their locality on their scheduled month.

PJP for Different Distribution Models

The planning logic is constant; the constraints are not.

Pre-Sales (Order Today, Deliver Tomorrow)

The standard general trade model. The rep carries no stock, so beats can be larger and travel lighter. The critical dependency is that the delivery route must follow the sales route by a fixed interval. Where sales and delivery beats drift apart, the retailer experiences unpredictable service even though the PJP is being followed perfectly.

Van Sales (Sell and Deliver in One Visit)

Here the constraint flips from time to vehicle capacity. A van carrying 120 cases cannot serve 45 outlets if average drop size is 4 cases. Beat size is set by load, not by hours, and the sequence matters more because a van that empties early wastes the rest of the route. Our comparison of van sales versus pre-sales models covers the trade-off.

Dairy and Daily Delivery

Daily cycles make the PJP almost trivial in structure and unforgiving in execution: the same route every single day, before dawn, with a fixed window. The planning question is not frequency but route efficiency and substitution, because a single absent delivery boy breaks the whole route.

Rural and Semi-Urban

Travel time dominates. A rural beat may carry 18 to 25 outlets against 40 in a dense urban market, and the cycle is often monthly rather than weekly. Market days matter enormously: calling on a village on its weekly haat day can double the order value, and a PJP that ignores local market calendars leaves that on the table.

Rebalancing an Existing PJP

Most distributors never build a PJP from scratch; they inherit one that has quietly decayed. A rebalance is cheaper than a rebuild and follows a different sequence.

Start with the exception list, not the plan. Pull every outlet billed in the last three months that is not in the current PJP, and every outlet in the PJP that has not billed in three months. Those two lists usually account for most of the drift, and fixing them alone recovers a surprising amount of coverage.

Check beat load against actual call times. Where GPS data exists, compare planned calls per beat against the number actually completed before the working day ended. Beats consistently finishing short are overloaded, and the outlets at the end of those beats are the ones silently dropping out.

Re-cut only the failing beats. Rebuilding every route at once destroys the retailer predictability that makes a permanent plan valuable. Fix the two or three worst beats, let them stabilise for a cycle, then move on.

Re-classify annually, not quarterly. Value classes should be reviewed once a year with real offtake data. Reclassifying too often produces frequency churn that confuses both reps and retailers.

Aligning the Sales PJP With Delivery

A sales journey plan that is not aligned to the delivery schedule creates problems no amount of field discipline can fix. If a rep books an order on Tuesday and the delivery vehicle covers that locality on Friday, the retailer waits three days regardless of how well the PJP was designed. In perishable categories that gap is fatal.

Alignment means three things in practice: the delivery route covers each sales beat at a fixed, known interval; the order cut-off is set so that orders booked on the beat make that delivery cycle, as covered in our guide to order cut-off discipline; and beat-level order volumes are predictable enough to plan vehicle loads against. When those hold, the retailer experiences a rhythm rather than a series of individual events, which is the entire point of the word permanent.

Where the Journey Plan Sits in the Wider System

A PJP is one input into a chain of dependent decisions, and it fails quietly when the pieces either side of it are wrong.

• Upstream: The plan is only as good as the outlet universe beneath it and the A/B/C classification built on it. Get those wrong and every route is wrong.
• Execution: Route adherence, productive call rate, lines per call and value per call are read together, never alone — the method is in our field sales KPI guide.
• Downstream: Orders booked on the beat have to make the order cut-off to ship that cycle, and the delivery route must follow the sales beat at a fixed interval or the retailer experiences unpredictability regardless of the plan.
• Coverage: Effective coverage of outlets is the outcome measure; weighted distribution tells you whether that coverage reaches the counters that carry category volume.
• Channel: In kirana-dominated general trade the plan is the whole operating system; in modern trade it barely applies.
• Scale: Where route economics stop working, the answer is usually a sub stockist rather than a longer beat.