Field service management software only delivers real-time visibility when the field team runs a disciplined daily workflow: geofenced check-ins, tamper-resistant proof of work, real-time expense capture, and offline sync. The software captures the data. The workflow decides whether that data is trustworthy enough to act on.
Ask most sales or service directors how their field team is doing right now, and the honest answer is a shrug. The data exists. Reps took photos, wrote down expenses, visited stores. But it is sitting in a Viber group, on a paper form in someone’s bag, in an Excel file that gets consolidated on Friday. By the time the numbers reach head office, they describe a week that is already gone. Insights arrive as hindsights.
Software is supposed to close that gap. And it can. But buying the app is the easy part. The gap does not close because you installed something on 200 phones. It closes because the team runs a daily workflow where every step leaves proof, in real time, whether or not there is signal. That workflow is the actual product. The app just enforces it.
We have set this up across more than 200 field deployments since 2014, for sales agents, merchandisers, and service technicians. The teams that get visibility and the teams that get a prettier version of the same mess are not separated by which software they bought. They are separated by whether the daily journey is disciplined. Here is what that journey looks like on the ground, step by step, and how to run it with your own team this quarter.
The app is the easy part
A field team app that nobody uses correctly produces worse data than paper, because paper at least does not pretend to be real-time. The failure mode is familiar: the app goes out, adoption is patchy, reps log some things and skip others, and three months later the dashboard is full of holes that leadership stops trusting. Everyone quietly goes back to Viber.
The fix is not more features. It is a defined sequence that the whole team follows the same way every day, with the software checking each step instead of hoping the rep remembered. The rest of this article is that sequence.
Two clocks, not one
The single most common point of confusion we see in the first week of any rollout is the difference between attendance and visits. They are two separate clocks, and treating them as one wrecks both your timesheets and your coverage data.
The first clock is the working day. The rep clocks in at the start of the day and clocks out at the end. That is attendance, and it feeds payroll and DTR.
The second clock runs at each store or job site. The rep checks in on arrival, does the work, and checks out when the task is done, then moves to the next stop. That is the visit record, and it feeds coverage and productivity.
A rep who confuses the two either clocks in for the day and never checks into a single store, so their attendance looks fine but their coverage reads zero, or checks into a store without ever starting their day, so the visit floats with no attendance behind it. Neither is a software bug. It is a workflow that was never taught. Get the two-clock model into the first training session and most of the phantom problems disappear.
Planned visits versus the ones your team adds on the fly
Every field day starts from a plan. In the Philippines that plan usually arrives as a journey plan or PJP, the list of stores or accounts a rep is supposed to cover, uploaded by the office before the cut-off. Those are planned visits.
Then reality happens. A dealer calls a meeting, an urgent account needs a drop-in, a store closes early and the rep substitutes another. Any stop the rep adds themselves during the day is an unplanned visit, and good field software tags it as exactly that, separate from the plan.
That one distinction is what makes route adherence measurable. If planned and added visits look identical in the data, you can never answer the question a manager actually cares about: did the team cover the route we agreed on, or did they freelance? When the plan and the app disagree, that is a signal, not an error. A visit that was in the plan but never showed up on the rep’s phone means the upload was wrong and the office needs to fix it. A pile of self-added visits means the plan does not match the territory. Both are worth knowing before the month ends.
Proof of work, not a selfie
Here is a correction we make in almost every training. Ask a rep to attach proof that they were at a store, or proof that a schedule change was approved, and the reflex is to snap a selfie. A selfie proves a face was somewhere. It does not prove the work happened or that anyone signed off on it.
The proof the office actually needs is the artifact. For a store visit, it is the geotagged, timestamped, tamper-resistant photo of the shelf, the display, the completed job. For a change of route, it is the screenshot of the dealer’s Viber or Telegram message approving it, uploaded as the reason. The photo field is not there to collect faces. It is there to collect evidence that survives a question three weeks later.
Geofencing is what makes location proof honest. A rep can only check into a store when they are physically within a set radius of it, often around 100 to 200 meters. No more time-ins from the jeepney or the house. And the geofence has to cover every legitimate work location, not just customer stores. Warehouses, the regional office, an approved training venue, all of them need to be mapped, or your best reps get blocked for being exactly where they are supposed to be. Map the locations first, then turn on the restriction.
Capture the peso at the point of spend
Expenses are where field data quietly bleeds. The rep pays for a jeep, a per diem meal, a night in a provincial lodge, printouts for a store display, and by the time they sit down to file it days later, half the amounts are guesses and the receipts are gone.
The workflow that fixes this is boring and it works: file the expense at the moment of the spend, from the field, with the receipt photographed on the spot. Categories matter here, because the office reconciles against them. Transportation, per diem, accommodation, merchandising materials, communication load. When the category needs an official receipt, the software should ask for the OR number and refuse to let it pass empty. When it does not, it should not nag for one.
The reason to do this in real time is not tidiness. It is that the plan and the actual finally line up. The team submitted a budget for the month. Now every peso spent is tagged, timed, and located against that budget. A rep can still file a real expense that was never in the plan, and they should, because deviation is exactly what management wants to see. What you lose forever is the Friday-night reconstruction where honest people guess and the numbers stop meaning anything.
Sync is upload, update master file is download
Filipino field teams do not work in places with clean, constant connectivity. Provincial routes drop signal. So the software has to be offline-first, and the whole team needs one mental model to keep it straight.
Sync is upload. Everything the rep recorded on the phone, the time-ins, the visits, the photos, the expenses, gets pushed up to the server when there is signal. The system syncs when able, so a rep can work through a dead zone and the data catches up later. Update master file is download. It pulls the latest plan, the new store assignments, the current budget, the assigned forms down to the phone. Sync sends your work up. Update master file brings the office’s changes down.
One practical warning that saves more support tickets than anything else: set the app’s permissions to the highest level, especially camera, location, and photos. The most common call that starts with “the app crashed” is not a crash at all. It is a rep who reinstalled the app or switched phones and never re-granted permissions, so the camera silently fails. Set permissions to always-allow on day one and revisit them after any phone change.
How to run this with your team this quarter
You do not need to wait for a perfect rollout to fix the workflow. Start with these.
Teach the two-clock model in the first session. Have every rep clock in for the day, then check into a demo store, then check out, then clock out, so the sequence is muscle memory before real stores are involved.
Separate planned from unplanned visits in your reporting from day one, and review the gap weekly. Treat missing planned visits as an upload problem to fix and a pile of added visits as a plan that needs rewriting.
Ban the proof-of-work selfie explicitly. Tell reps what a valid photo is, a shelf, a job, an approval screenshot, and audit a sample each week until it sticks.
Map every work location before you switch on geofencing, warehouses and offices included, then set the radius tight enough to matter.
Require expenses to be filed in the field with a receipt photo, and reconcile actuals against the monthly plan, deviations included.
Set app permissions to always-allow on every device on day one, and re-check them after any phone swap.
How Tarkie implements this
This workflow is the reason Tarkie exists. It runs offline-first with sync-when-able, so provincial routes do not lose data. It separates the working-day clock from the per-store check-in and check-out, tags planned versus unplanned visits automatically, and enforces geofenced attendance so a check-in has to happen where the work is. Photos are geotagged and tamper-resistant, expenses are captured in the field against the monthly budget, and forms with approval steps route to the right person’s inbox by role. Supervisors watch all of it on a live national view of coverage versus plan, and for technician-led teams the same discipline drives smart job dispatch and proof-of-work fulfillment.
The payoff is coverage, not just cleaner reports. By digitizing 90% of their field reports, Chooks-to-Go doubled store coverage from 10 to 20 stores per day per field employee. Same reps, same day, twice the ground covered, because the workflow stopped leaking time into admin. That is what field service management software is supposed to buy you, and it only happens when the daily journey underneath it is disciplined. Tarkie’s field service automation is built around exactly this sequence.
If your field reports still arrive as end-of-day photos in a group chat, the workflow above is what we build for teams, and we are happy to walk you through how it runs on a real deployment.
Frequently asked questions
What does field service management software actually do day to day?
Day to day, field service management software enforces a repeatable field journey rather than just storing data. It handles working-day attendance and per-site check-ins, tags planned against unplanned visits, captures geotagged proof of work and receipts, and syncs everything to head office even over spotty connections. The value comes from the workflow it enforces, not from the number of features on the brochure.
What is the difference between time in and check in on a field app?
Time in and time out cover the whole working day and feed attendance and payroll. Check in and check out happen at each store or job site and feed coverage and productivity data. They are two separate clocks, and teams that treat them as one end up with attendance that looks fine but coverage that reads zero.
What is a planned visit versus an unplanned visit?
A planned visit comes from the journey plan the office uploads before the cut-off, the route a rep is supposed to cover. An unplanned or added visit is any stop the rep creates themselves during the day. Keeping the two separate is what lets a manager measure whether the agreed route was actually covered.
Why does a field app need geofencing?
Geofencing lets a rep check in only when they are physically within a set radius of the location, often around 100 to 200 meters. This stops attendance and visits from being logged remotely, which is the most common way field data gets faked. Every legitimate work site, including warehouses and offices, has to be mapped or reps get blocked where they belong.
What counts as valid proof of work for a field visit?
Valid proof is the artifact of the work, not a selfie. For a store visit it is a geotagged, timestamped, tamper-resistant photo of the shelf, display, or completed job. For an approved route change it is a screenshot of the message that authorized it, uploaded as the reason.