Permanent Journey Plan (PJP) India: Build Beats That Get Followed

A pharma MR in Nagpur covers 11 doctors every day. Ask him to show you his PJP and he'll pull up a printed table his area manager gave him eight months ago. Ask him if he follows it — genuinely follows it — and he'll give you the smile that says: sometimes.

That printed table is not a permanent journey plan. It's a document that was once a plan. The difference matters, because a real PJP is a live operating system. When it breaks down, it doesn't announce itself. It just slowly stops producing outcomes — missed outlets, declining secondary sales, distributor gaps, and a manager who can't explain why coverage numbers look fine on the dashboard but offtake is soft on the ground.

What is a permanent journey plan (PJP)?

A permanent journey plan is a pre-scheduled, repeating route plan that assigns a field executive to specific outlets or customers on specific days of the week or month, on a fixed cycle. Unlike an ad-hoc visit list, a PJP repeats on a defined rhythm — weekly, fortnightly or monthly — and covers an executive's full outlet universe, not just the accounts they prefer to visit.

The word "permanent" does not mean unchangeable. It means the schedule is the default. Deviations require a reason, not the other way around. In most Indian field operations — FMCG distribution, pharma detailing, BFSI lead collection, retail servicing — the PJP is the foundational document from which everything else flows: target-setting, cost-per-call calculation, secondary sales benchmarks, and manager oversight.

How does a PJP differ from a beat plan?

A beat plan is the route an executive follows on a given day — the sequence of outlets, the geography, the travel logic. A PJP is the calendar that determines which beat runs on which day.

Think of it this way: the beat plan answers "where do I go today and in what order?" The PJP answers "which days of the month am I in which territory, covering which outlets?" A well-run field operation needs both. The beat plan without a PJP produces efficient routes with no coverage discipline. The PJP without a thoughtful beat plan produces the right outlets on the right days but with an executive doubling back across town unnecessarily.

In India, the terms are often used interchangeably, which causes real problems. A sales manager who thinks he has a PJP because he has beat routes is missing the frequency layer entirely. That frequency layer — how often does outlet X actually get visited — is where most coverage leakage hides.

How to design a PJP by outlet grade and frequency

The starting point is the outlet universe, not the route. Before a single beat is drawn, every outlet in the territory needs two things assigned to it: a grade and a visit frequency.

Grade reflects commercial priority — typically A, B or C, but derived from actual order history and potential, not inherited assumptions. An A-grade general trade outlet in a Tier 2 town might place ₹8,000–12,000 per month. A C-grade outlet in the same town might place ₹800 — or it might be a C only because nobody re-audited the universe in two years.

Frequency follows from the outlet's replenishment cycle and the economics of a call. In FMCG general trade, A-grade outlets often genuinely warrant fortnightly visits, not weekly — calling a kirana owner every seven days when his order cycle is 14 days just irritates him. In pharma, a top-decile doctor might need weekly detailing; a specialist who writes five scripts a month needs fortnightly at best. In banking and BFSI field sales, loan or insurance collection agents use monthly PJPs built around repayment dates, not geography alone.

A practical framework:

• A outlets: visit every cycle (weekly or fortnightly, depending on industry)
• B outlets: visit every second cycle
• C outlets: visit once per month, reviewed quarterly for reclassification

Once grades and frequencies are set, the PJP builds itself: slot each outlet into the days and weeks where the executive is in that territory, keep travel time between consecutive calls under 10 minutes in urban beats and under 18 minutes in semi-urban or rural ones, and make sure no single day is overloaded to the point that the executive cannot realistically complete the plan.

That last point is where most PJPs fail at the design stage. A 28-call day in a spread-out rural territory is a fantasy. The executive will cherry-pick the easy calls, skip the distant ones, and report 28 anyway. Design for 18–22 calls in urban beats and 14–16 in rural, with a small buffer for unexpected situations.

The counterintuitive case for fewer, better visits

There is a persistent belief in Indian field sales that more coverage frequency is always better. It is not.

Over-visiting high-value outlets creates diminishing returns and real commercial costs — the executive's time, the cost per call, and the goodwill of a trade partner who has nothing new to discuss with a rep who shows up every four days. A pharma MR detailing the same product to the same doctor three times in a fortnight is not building relationships. He's burning them.

The better goal is visit quality, not visit volume. A fortnightly visit where the executive arrives with an updated order history, a targeted SKU focus, a competitor price observation, and a specific ask produces more than two weekly visits where the conversation is "sir, kuch chahiye?"

This means the PJP design conversation has to include what happens during each visit, not just how often it happens. The PJP schedule and the call objective are inseparable. In pharma field force management, this means detailing sequences planned in advance. In FMCG, it means the executive knows the outlet's last order, current shelf position, and the scheme running that fortnight before they walk through the door.

How to measure PJP compliance without a manual report

This is the practical problem that makes or breaks PJP discipline. If compliance is measured by the DSR — the daily sales report the executive fills in at the end of the day — you are measuring their memory and their incentives, not their actual behaviour.

Three signals make compliance measurable without any self-reporting:

Geo-fenced check-in. Was the executive physically within the outlet's recorded coordinates when the visit was logged? Not in the street outside, not at the adjacent shop. Inside the geofence. This single check eliminates a significant proportion of phantom visits in most networks.

Dwell time. A real sales call at a kirana counter takes at least 4–5 minutes. A pharma detail takes 3–8 minutes depending on doctor availability. Any logged visit under 90 seconds is almost certainly a check-the-box event.

Sequence adherence. Did the executive visit outlets in roughly the planned beat sequence, or did they skip to the end of the beat and work backwards? Significant sequence deviation usually signals cherry-picking — hitting easy or nearby outlets and skipping the awkward ones.

PJP software in India that captures these three signals — passively, without adding friction for the executive — gives managers a compliance picture they can act on. The right response to low compliance is almost never a WhatsApp message to the executive. It is usually a plan that was too aggressive, a territory that was misclassified, or an outlet list that hasn't been audited since the previous FY.

A PJP compliance rate below 70% (verified, not self-reported) is a signal to redesign the plan, not to escalate to the executive. Most organisations do it the other way around, which is why the same compliance problems recur every quarter.

Where Kinematic fits in this picture

Kinematic's field force management platform is built around the PJP as the central operating object — not as a PDF that gets emailed once a quarter, but as the live plan the executive sees on their phone each morning, with today's outlets, yesterday's order history at each stop, and a running compliance count that the manager can read from the same screen.

The Kini AI layer flags when a territory's verified compliance drops below threshold and surfaces whether the cause is behaviour or plan design — which are very different problems requiring very different responses.

If you run field teams in logistics, real estate, or any sector where a sales or service executive follows a repeating schedule, the PJP problem is the same, even if the vocabulary differs. The plan needs to be designed on real data, executed with visibility, and measured on signals that can't be gamed.

That's a solvable problem. Start with the plan, not the escalation.