Field workforce management software does more than catch time theft. Its geo-tagged attendance, mock-GPS detection, and photo validation build a timestamped evidence trail that lets Philippine employers discipline field staff proportionately and defensibly, while protecting honest workers from a wrongful dismissal complaint at the NLRC.
The report lands on a Monday. One of your field promoters opened a fake GPS app during his shift last week, and the system flagged it. A manager reads the flag, connects it to a rumor that the promoter has been lining up ride-hailing bookings on the side, and wants him gone by Friday. On the surface, it looks clean: he cheated the location, so he was not really working, so dismiss him.
That reflex is where good companies lose labor cases.
Field teams are the hardest part of any business to see. Promoters, merchandisers, and agency-deployed staff work in stores and routes you will never physically check on a given day, and the honest reply to “where’s the coverage report” is often “nasa field pa.” That gap is exactly why field workforce management software exists. What most managers miss is that the same system built to catch a dishonest worker is also the only thing that can protect an honest one, and protect the company from a dismissal it cannot defend.
Why “fire him” is the expensive reflex
In the Philippines, an employer cannot dismiss a field employee on a hunch, on a rumor, or on a single ambiguous flag. Termination for just cause under Article 297 of the Labor Code has to clear two separate bars. The first is substantive: the employer must prove, with substantial evidence, that the worker committed a listed offense such as serious misconduct or willful breach of trust. The second is procedural: the employer must follow the twin-notice rule, a written notice to explain the specific charge, a real chance for the employee to respond, and a written notice of decision.
Miss the first bar and the dismissal is illegal, which can mean reinstatement plus full back wages from the day the worker was let go. Miss only the second bar, even when the offense is real, and the dismissal is still procedurally defective and carries nominal damages. The Supreme Court set out this twin-requirement standard in King of Kings Transport v. Mamac, and DOLE Department Order 147-15 spells out the disciplinary procedure.
There is a further trap in the word “serious.” Philippine jurisprudence treats serious misconduct as conduct that is grave, work-related, and shows the employee is unfit to continue. An isolated minor infraction usually does not qualify. So a manager who fires a promoter for “using his phone” is betting the company on a charge that may not survive an illegal-dismissal complaint at the NLRC. The rumor about side gigs is not evidence. The GPS flag, read carelessly, is not evidence either. What you can prove is the only thing that counts.
Courts also look favorably on employers who apply progressive discipline against a written standard. A documented code of conduct that names the offense and its penalty, followed consistently, is far easier to defend than a one-off dismissal that looks like a manager acting on a grudge. This is where reflex firing quietly costs the most. Reinstatement with full back wages is not a slap on the wrist for a company running hundreds of field staff; it is a recurring liability that a single careless decision can trigger, and it lands months later when the manager who made the call has forgotten the details.
Separate the place from the act
Most bad field-discipline decisions come from collapsing two questions into one. Managers see “fake GPS” and conclude “he was not at his post and he was not working,” when those are two different claims that the data answers separately. A field workforce management system that logs geo-tagged attendance, validates photos, and flags mock-location apps lets you read the day in two distinct layers.
The first is the location layer. Was the worker physically where he was assigned during his shift? Geo-tagged time-in and time-out, mapped against the assigned store, answers this. In the real case behind this article, the promoter’s time-in and time-out placed him inside the assigned store for the whole shift. His location was clean. He was not faking his post at all.
The second is the conduct layer. What did the worker actually do while on duty? Here the same system told a different story. His scheduled shift ran until 8:00 in the evening. Shortly before eight, the activity log showed he had opened a mock-location app and begun setting up ride-hailing bookings for the area he was about to head to once he clocked out. The system detected the fake-GPS app the instant it ran and marked the associated capture invalid, on its own, with a timestamp. He was not trying to leave his post early and hide it; he was queueing up his evening side income on company time, minutes before the shift ended.
Read as one blurred accusation, this promoter looks like a fraud who should be fired. Read in two layers, the picture is precise and far more useful. He did not falsify his attendance, so the serious charge collapses. He did misuse duty time and run a prohibited app on a work device, which is a real, documented, memo-worthy infraction. The correct action was a notice to explain and a proportionate penalty, not a dismissal the company would have lost. The data did not just catch him. It stopped a manager from over-punishing him.
Field workforce management software as an evidence trail
The reason this two-layer read is possible is that the records are built to hold up, not to be argued over. A Viber photo and an end-of-day Excel consolidation cannot tell you when a photo was taken, where, on whose device, or whether the location was spoofed. A purpose-built field workforce management platform can, because every capture carries a timestamp, a geo-tag, a device identity, and a tamper signal when a mock-location app is running.
That changes what a flag is worth. When the system marks a capture invalid because it detected a fake GPS app, that invalidation is itself a clean fact you can put in a notice to explain. When geo-tagged attendance shows the worker inside the assigned store, that is a fact that defends the worker. The trail cuts in both directions, which is what makes it fair and what makes it defensible.
Field teams cannot use the controls that office teams take for granted. A biometric wall clock verifies presence for people who report to one building; it does nothing for a promoter assigned to a store in another province or a merchandiser covering a dozen outlets in a week. For field roles, the phone is the time clock, the camera, and the location sensor all at once, which is precisely why the phone becomes the point of attack. Spoofing location, borrowing a co-worker’s login, submitting a photo taken somewhere else on another day: these are the field equivalents of buddy punching, and a plain attendance sheet cannot see any of them.
Scale is where this stops being theoretical. One of Tarkie’s clients, Megasoft, uses the platform to keep secure attendance and coverage data across 1,500 merchandisers and coordinators. At that headcount, “trust the group-chat photos” is not a control; it is a hope. Immutable, geo-tagged, timestamped records are the only version of the truth that survives a dispute, whether the dispute is with a dishonest worker or with a labor tribunal reviewing how you treated an honest one. The same records also give head office a live, national view of field operations instead of a week-old spreadsheet.
How to act on a field-fraud flag without creating a bigger problem
When a flag comes in, slow the decision down and work through the evidence in order. The steps below apply whether or not you run a formal system, though they are far faster when you do.
- Pull the location layer first. Before anyone forms a view, check the geo-tagged attendance for the exact dates in question and confirm whether the worker was actually where he was assigned.
- Read the conduct layer separately. Ask what the activity and photo logs show the worker did on duty, and keep that question distinct from the location question.
- Match the penalty to what the records prove, not to what a manager suspects. If the evidence supports a memo, issue a memo; do not stretch it into a dismissal the facts will not carry.
- Issue a notice to explain that cites the specific timestamped records, and give the worker a genuine chance to respond before deciding anything.
- Preserve the raw records and keep them exportable. Do not rely on screenshots forwarded through a group chat, which prove nothing about when or where they were made.
- Write the rule down. If running a mock-location app on a work device is an offense, put it in the code of conduct so the penalty rests on a known, published standard.
None of these steps needs a lawyer in the room. They need records you can trust and the discipline to read them before reacting.
The point most monitoring pitches miss
Field monitoring is usually sold as a way to catch people. The more valuable use is quieter: it lets you be fair at scale and prove that you were. The company that reads its field data in two layers disciplines the right person for the right offense, keeps the workers it would otherwise have wrongly lost, and walks into any NLRC review with a timestamped trail instead of a rumor. The founding idea behind Tarkie came from exactly this kind of gap between where a field employee claimed to be and where he actually was. That is not surveillance for its own sake. It is the difference between a decision you can defend and one that costs you a reinstatement order.
Tarkie was built for this exact problem: field teams you cannot watch, and decisions you have to defend. Its geo-tagged attendance, photo validation, and mock-GPS detection give you the two-layer record described here.
Frequently asked questions
What is field workforce management software?
Field workforce management software is a platform for teams that work outside the office, such as sales agents, merchandisers, and field technicians. It handles geo-tagged attendance, photo validation, route and coverage tracking, and reporting, giving head office a real-time, verifiable record of what field staff did and where.
Can employers in the Philippines track field employees by GPS?
Yes. Employers may monitor the location of staff during working hours for legitimate business purposes such as attendance and coverage verification. Best practice is to disclose the monitoring in the employment contract or company policy, limit it to work hours, and handle the data under the Data Privacy Act.
Is GPS location data valid evidence for disciplining an employee?
It can be, when the records are timestamped, geo-tagged, and tamper-evident rather than screenshots forwarded through a group chat. Under Article 297 of the Labor Code the employer must prove the offense with substantial evidence, so a defensible system log carries far more weight than a manager’s recollection or a rumor.
Can you dismiss an employee for using a fake GPS app at work?
Not automatically. Running a mock-location app can be a documented offense worth a notice to explain and a proportionate penalty, but dismissal requires a serious, work-related just cause proven with evidence. If attendance records show the worker was actually at the assigned site, a jump straight to dismissal is likely to fail at the NLRC.
What is the twin-notice rule in Philippine dismissal?
The twin-notice rule is the procedural due-process requirement for a just-cause dismissal. The employer must issue a first written notice stating the specific charge, give the employee a real chance to respond, then issue a second written notice of the decision. Skipping it makes the dismissal procedurally defective even when the cause is valid.