Field visit planning: comparing what was planned with what happened
What is field staff tracking software? A weekly visit plan, per-action location verification, visit evidence and the plan-versus-actual gap in an XLSX report.
Tracking a field team does not have to mean watching every minute of an employee. What the manager really wants to know is whether the planned visit took place and, if it did, whether there is evidence of it. Field staff tracking software is software that plans field teams’ visits and records every visit that takes place in the field with location and evidence.
In this article we explain how the weekly field plan can be compared with what actually happened, how location can be verified without monitoring the employee continuously and how to read the report, using the Field Tracking & Planning module inside YazSis KurumsalPortal.
Continuous monitoring or per-action verification?
There are two different approaches to field tracking:
- Continuous location tracking: the employee’s location is recorded throughout the day. It gives the manager a lot of data, but it also gives the employee the feeling of being watched constantly; and most of this data does not answer the manager’s real question, “was the visit made?”.
- Per-action verification: location is taken only when the employee starts an action in the field, for example checking in to a visit, and is matched with the planned visit. Less data is collected, but the data collected is direct evidence of the visit.
The Field Tracking & Planning module uses the second approach. Location is not tracked continuously; the aim is to verify that the visit really took place at that point. The user starts the action from their phone browser, and no separate app needs to be installed.
The weekly field cycle in five steps
- Create the plan. Field visits are prepared as a weekly plan.
- Assign the task. Visits are assigned to team members as tasks; the regional manager sees beforehand who will go where.
- Check in in the field. The employee starts the action at the visit point; the location is taken at that moment and matched with the planned visit.
- Add the evidence. The employee adds evidence and a note to the visit; the evidence is stored in the visit record together with the location match.
- Report the outcome. The gap between plan and actual is exported as an XLSX report.
Let us imagine a fictional week. On Monday morning the regional manager publishes the weekly plan and assigns the visits to team members as tasks. On Tuesday an employee arrives at their first visit and starts the action from their phone; the location matches the planned point, and the employee adds a short note and evidence. On Wednesday the report shows a visit that was not in the plan; the note says there was an urgent customer request. At the end of the week the manager reads from the XLSX report how many visits happened as planned and how many fell outside the plan, and adjusts next week’s plan accordingly.
How is the gap between plan and actual read?
The visits in the weekly plan are compared with the check-ins made in the field and the location matches. The report produces three groups of results:
- Happened as planned: the visit was made, the location matched the plan, the evidence is on record.
- Planned but not made: visits that are in the weekly plan but have no check-in record in the field. They may have been postponed, cancelled or forgotten; the note field says which.
- Happened outside the plan: actions started at a point that was not in the plan. Sometimes this means an urgent customer request, and sometimes that the plan was prepared incompletely.
A gap in the report is not a verdict, it is a question: why did it not go as planned?
That is why the note the employee adds to the visit matters. A customer may have postponed the appointment or an urgent job may have come up; read together with the note, the gap is for the manager not a complaint but an opportunity to correct the plan.
What to watch for when preparing the weekly plan
- Make a realistic plan. Writing more visits than fit into a day fills the plan with “not made” results from the first day and weakens the meaning of the report.
- Write the purpose of each visit. If the employee knows why they are going, the evidence and note they add in the field will also be more to the point.
- Decide in advance what the evidence will be. Telling the team up front what kind of evidence is expected keeps the records orderly and comparable.
- Hold a weekly review meeting. Reading the gap report together is the most natural way to improve the plan for the following week.
Who uses it, and how?
- Field teams: start the action in the field, add evidence and a note.
- Regional managers: see the weekly plan, review the evidence, look at the gap report.
- Operations: prepares the plan and assigns the tasks, reports the outcome; by evaluating the weekly plan side by side with what happened, it helps the next plan to be prepared more accurately.
The gains the module aims for are visibility of out-of-plan movements, field efficiency and evidenced visit records. You can look into them on the Field Tracking & Planning page, and see the platform’s other modules on the KurumsalPortal page.
Frequently asked questions
Is field staff’s location tracked continuously?
No. Location is taken only when the user starts an action in the field, for example checking in to a visit, and is matched with the planned visit. This approach focuses on verifying that the visit took place, without continuous location tracking.
How is visit evidence added?
The field employee checks in at the visit point from their phone browser and adds evidence and a note to the visit; no separate app needs to be installed. The evidence is stored in the visit record together with the location match and can be seen by the regional manager.
How is the gap between plan and actual reported?
The visits in the weekly plan are compared with the check-ins made in the field and the location matches. Visits that were planned but not made, or that happened outside the plan, appear in the report, and the report can be exported as XLSX.
How are field visits planned?
Visits are created as a weekly plan and assigned to team members as tasks; the regional manager sees beforehand who will go where.
More articles
What is XML integration? How to import supplier product and stock feeds into your store
Your supplier publishes a new XML file every morning, and you are still typing prices in by hand. XML integration reads that file, applies your rules, passes the data to your online store and stops faulty data.
November 23, 2026 · 8 min readMaintenance tracking software vs Excel: when to switch for preventive maintenance
Tracking maintenance in Excel works for a while, but it breaks down at reminders, assignments, history and parts costs. We compare maintenance software with Excel, give seven criteria for switching and explain how to move your spreadsheet.
November 23, 2026 · 8 min readDocument and policy management: making sure the current version is read
The returns procedure was updated, but the field team is still working from the old PDF. Publishing policies with version control and tracking read status turns that uncertainty into a record.
November 23, 2026 · 5 min read