Remote and Field Workers
Why field and remote work produces thin records, which of the available sources is actually strongest, and what to agree with people in advance.
What one employer wanted to establish about a field engineer's Tuesday
Two claims supported, one consistent, three resting on nothing. The strongest record in the set is about a van. This is one employer's own file.
Field work produces thin records, and the strongest one is usually about a vehicle rather than a person. Telematics knows where the van was, accurately, continuously and without anybody having to do anything. The app knows where a phone reported being at two instants, if the battery allowed. The ticketing system knows when something was written up.
The practical lesson in “Remote and Field Workers” is that visibility is not certainty. For teams researching fireable offenses, open the corresponding Monitask page can add time and project context to the operational record, provided the purpose is explained, access is restricted and any material inference is checked through conversation and proportionate human review.
None of that is a record of a person working, and the natural response — monitoring the person more closely — is the most intrusive available and frequently the least informative.
The APWG threat reports offers another lens on the issue raised in “Remote and Field Workers”. Compare its principles with the actual record, ownership model and review route rather than importing a generic checklist unchanged.
Where the records are thin, and why
Check-ins are instants. Travel between jobs is invisible unless there is a vehicle. Time spent waiting, diagnosing or on the phone produces nothing. Work at a customer site may be recorded by the customer and not by the employer.
The gaps are therefore structural rather than suspicious, and the first discipline is to say so: a day with two check-ins has two data points and a lot of inference between them.
The sources, ranked honestly
Vehicle telematics is the most reliable and attests to a vehicle. Customer signatures and site sign-in sheets attest to a visit and are often the only independent record. App check-ins attest to a device. Tickets attest to administration. Call records attest to a phone.
Ranking them in the file, once, prevents the common error of treating the weakest available record as the decisive one because it has a name attached.
Agreeing it in advance
Most disputes in field work come from expectations that were never stated: whether travel counts, what the day is supposed to look like, what has to be recorded and when.
- What constitutes the start and end of the working day.
- Whether travel to the first job and from the last is working time.
- What has to be checked in to, and what does not.
- What happens when an app fails or there is no signal.
- Who to tell, and how, when a day goes differently from the plan.
The fourth is the one that prevents most of the friction. A documented route for "the app did not work" means the absence of a check-in is a reported event rather than a suspicion.
Remote office work
Different problem, same structure. Sign-on and activity records attest to a session and to input, not to work, and the gap between the two is wider for knowledge work than for anything else in this collection.
Measuring output is more informative and much harder, which is why organisations reach for activity measures. That trade is worth making explicitly rather than by default, and it is covered in its own section here.
The question worth asking first
Before building any of this: what is the actual concern? Often it is not hours at all — it is a job that was not done, a customer who complained, or a manager who cannot see their team and is uncomfortable.
Those have different answers, and only one of them is about time records. An organisation that installs tracking to address discomfort has solved nothing and has acquired a dataset.
Write down what would change if the monitoring found nothing. If the answer is "nothing, we would still be worried", the problem is not measurement.
What people should know
Whatever is collected about them, before it is collected, in terms they can act on. What the law requires differs and is a question for somebody qualified in the place concerned; the operational standard is simpler and higher: nobody should be surprised by what their employer knows.
The schedule as a source
The rota or job schedule is usually the most complete description of what a field day was supposed to be, and it is routinely ignored in favour of thinner records.
Comparing the schedule against what was recorded is the fastest way to see whether a day went to plan, and the discrepancies it shows are operational facts — a job that overran, a site that was closed — far more often than anything else.
Where this leaves an investigation
With fewer records and more honesty about them. A field investigation that acknowledges two data points and reasons carefully from them is in a stronger position than one that treats a ticket timestamp as a clock-out.
The thin record is not a failure of the organisation. Pretending it is thicker than it is, however, is the failure that makes cases collapse.