Beat Plan

A beat plan is a fixed, repeating schedule that tells a field sales rep which outlets to visit, on which day and in what order.

In FMCG, pharma, consumer durables and distribution businesses, a "beat" is a cluster of retail outlets in one area that a sales rep can cover in a single working day. The beat plan maps every beat to a day of the week, so each outlet gets a visit at a regular frequency, such as once a week or once a fortnight.

For example, a rep in Pune may cover Kothrud on Monday, Karve Nagar on Tuesday and Warje on Wednesday, then repeat the cycle the next week. Retailers know when to expect the rep, which helps with order planning and stock rotation.

A beat plan answers three simple questions for every working day:

• Where will the rep go (area and outlets)?
• When will each outlet be visited (day and frequency)?
• What should happen at each visit (order, collection, display check, new outlet listing)?

Most companies now run beat plans on field force management software instead of Excel sheets, so managers can assign beats, see visits as they happen and spot missed outlets quickly.

The terms are often used together, but a beat is the group of outlets, the PJP is the calendar of beats, and the route plan is the travel path within a beat.

HR and sales teams in India use these words loosely, which can cause confusion when targets and allowances are set. The table below shows how they differ.

A static beat plan stays the same week after week. A dynamic beat plan changes visits based on stock levels, pending payments or new outlet leads. Many teams use a static PJP as the base and allow small daily changes with manager approval.

A useful beat plan balances outlet coverage, travel time and the rep's working hours, so targets are realistic and visits are not skipped.

When sales and HR teams design beats together, they usually check these elements:

• Outlet list: name, address, GPS location, category (A, B or C by sales value) and contact person.
• Visit frequency: high-value outlets may need a weekly visit, while smaller ones can be visited every two weeks.
• Outlets per day: usually 20–35 in dense city markets and fewer in rural or semi-urban areas where travel takes longer.
• Travel distance: beats should start close to the rep's home or the distributor point to cut travel cost.
• Visit tasks: order booking, payment collection, merchandising, scheme communication or competitor checks.
• Distributor mapping: each beat should link to one distributor so orders reach the right stockist.

A beat with too many outlets leads to rushed visits and fake check-ins. A beat with too few outlets wastes the rep's day. Review outlet counts every quarter as markets grow.

Creating a beat plan starts with clean outlet data, then groups outlets by area, assigns them to days and tracks actual visits against the plan.

1. Collect outlet data: build a master list of all active and potential outlets with addresses and map locations.
2. Classify outlets: tag them A, B or C based on monthly sales or potential.
3. Group by geography: cluster nearby outlets into beats that one rep can cover in a working day.
4. Assign days and reps: map each beat to a day of the week and a named rep to create the PJP.
5. Set visit goals: define the expected calls, productive calls and order value for each beat.
6. Track visits: use check-in and check-out with location so planned and actual visits can be compared.
7. Review and adjust: move outlets between beats when travel time is too high or coverage is poor.

Step 6 is where most plans fail without the right tools. Real-time location tracking shows whether the rep actually reached the outlet and how long each visit lasted, which makes beat compliance easy to measure.

A beat plan also controls travel spend, so HR and finance teams can estimate monthly allowances and compare them with the sales each rep brings in.

Take a sales rep in a Tier-2 city who works 26 days a month, covers 25 outlets per beat and travels about 40 km a day on a two-wheeler. Assume the company pays ₹4 per km as fuel reimbursement and ₹250 as daily allowance (DA). These rates are only examples; use your company's travel policy.

If GPS logs show the rep actually travelled 1,040 km, the claim matches the beat plan. Linking beats with employee expense management lets HR approve fuel and DA claims based on real distance, not manual entries.

Field sales reps on a beat plan are employees, so working hours, overtime, wages and leave rules under India's Labour Codes still apply to them.

The four Labour Codes, including the Code on Wages, 2019 and the Occupational Safety, Health and Working Conditions Code, 2020, have applied since 21 November 2025. Points HR should keep in mind when designing beats:

• Working hours: the OSH Code caps normal work at 8 hours a day and 48 hours a week. A beat that needs 11 hours of travel and visits every day may create overtime liability. HR should confirm the exact limits notified by the state government.
• Overtime: where overtime applies, it is payable at twice the ordinary wage rate. Sales staff who are classed as supervisory or managerial may fall outside some of these rules, depending on role and wage level.
• Wages definition: under the Code on Wages, allowances beyond 50% of total pay are added back to "wages". Very high travel or conveyance allowances can affect PF and gratuity calculations.
• Weekly off and leave: the PJP must leave room for the weekly rest day, holidays and approved leave.
• Location tracking consent: tell employees in writing that GPS is tracked during working hours only, in line with the Digital Personal Data Protection Act, 2023.

HR teams link beat plans with attendance, expenses, incentives and payroll, so field staff are paid correctly for the work they actually did.

In many companies, sales managers own the beat plan, but HR owns the data that comes out of it. Good practice includes:

• Beat-based attendance: mark attendance from the first outlet check-in instead of a manual register.
• Expense checks: approve travel claims only for beats that were actually covered.
• Incentive tracking: link beat compliance, productive calls and order value to monthly incentives. Sales performance reports help managers compare reps fairly across beats of different sizes.
• Fair workload: review beats that regularly push reps beyond normal working hours.
• Clear policy: write the beat plan, deviation approval and tracking rules into the field sales policy.

When beat data, approved expenses and incentives flow into payroll software, HR can process field staff salaries without chasing spreadsheets from every sales manager.