Field supervision runs on phone calls. A branch manager with fourteen people on the road calls each one to ask where they are, hears fourteen different answers, and has no way to check any of them. At month end, a travel claim or an attendance dispute is settled by whoever argues longest.
The supervision problem nobody solves with a tracking app
The usual response is to install an app that follows everyone all day. That creates new problems without solving the old ones:
- The team resists it. People feel watched, and the app is switched off, forgotten or worked around.
- A dot on a map is not a visit. Being near a customer does not mean the customer was met.
- There is no plan to compare with. Movement is recorded, but nobody agreed where the person was supposed to go.
- Attendance and field records disagree. HR marks one thing, the field report says another.
- Data piles up. Location history is kept for ever, with no clear reason.
The gap is not a lack of data. It is that tracking is set up to watch people, not to answer a question.
What changes when tracking is built on the visit
The policy comes first
Before anyone is tracked, working hours, the retention period and the trigger are set in a policy, per zone, and shown to the employee. Consent is recorded against each employee, with the date it was given.
The day starts with a plan
A visit plan lists the customers to be seen and the order to see them in, drawn from deals and companies in CRM. The day is measured against what was agreed, not against a general impression.
The check-in happens at the customer
The field person checks in and checks out from the mobile app. A check-in is accepted only within about 100 metres of the customer location. An unplanned stop is marked as unplanned.
What is recorded, and what is not
Location is captured around the check-in and check-out of visits, and the location log shows those points for the day on a map. It is a record of visits, not a continuous trace of a person — and saying that clearly is what makes a team accept it.
The supervisor verifies the day
The supervisor compares the plan with the log and verifies the day. An exception is either explained or it stands, on the record.
What this looks like in practice
Consider a pharma distributor with fourteen medical representatives in one branch.
Each rep's visit plan for the day comes from CRM. The branch manager opens the tracking dashboard at noon and sees every planned visit and its state:
- Checked in — the rep is at the doctor or chemist now.
- Completed — checked in and checked out.
- Pending — not reached yet.
- Missed — the planned time has passed with no check-in.
One rep's check-in is refused because they are 400 metres from the chemist's shop. They move to the shop and check in again. Another rep visits a chemist who was not on the plan, and the visit is marked as unplanned.
At day end, the manager verifies each rep's day in a few minutes. The noon phone calls stop, and when a travel claim is questioned later, planned and actual visits are on the record with their times.
Nothing here makes the team sell more. What it does is settle "where were you" with a record instead of an argument — which is where most field disputes quietly waste time.
Reports the review meeting can use
A field review needs three numbers: visit compliance, coverage of the assigned territory, and the gap between plan and actual. Reports run by person, branch, customer or date range. Because they use the same records as the CRM pipeline, the conversation about effort and the conversation about results use one set of facts.
Where this meets the rest of the business
Tracking reads what other modules write, so nothing is entered twice.
- CRM and Sales: visit plans and check-ins come from these modules, and a verified visit counts as activity against the deal.
- HRMS: supervisor verification is shared with HRMS, so the muster agrees with the field record before the month closes.
- Payroll: how field attendance is treated for pay is your policy; Unnati makes sure the records agree.
That is the practical argument for tracking inside the same system as CRM and HRMS rather than as a separate app.
A note on trust
Field tracking works when it answers a question and then stops. Tell your team exactly what is recorded — check-ins and check-outs of planned visits, during working hours, kept for the retention period in the policy. A check-in made with no network is stored on the phone and sent when the connection returns, with its original time and location. A check-in from outside the geofence is not accepted, because that is the control the whole record depends on.
Unnati's Tracking module covers the field team dashboard, visit plans, geofenced check-ins, the location log, attendance verification and reports. The field tracking feature page shows the screens, and the CRM and field sales page covers visit plans and follow-ups.
Key takeaways
- Tracking set up to watch people fails; tracking set up to answer a question works.
- A visit plan gives the day something to be measured against.
- A geofenced check-in proves a visit in a way a dot on a map cannot.
- Tell the team exactly what is recorded, when, and for how long.
- Supervisor verification settles exceptions on the record, not in an argument.
- Field attendance and the HR muster should agree before the month closes.