Something like four in five of the world's workers do not sit at a desk, and essentially none of the employee monitoring industry is built for them. The tools in this category measure applications, windows and keyboards — all of which assume a computer the person works at.
So when a retail or logistics or care operator asks which monitoring tool to use, the honest first answer is that the category they are looking at is the wrong one.
What the actual categories are
Three distinct products get conflated here, and they are not interchangeable.
Time, attendance and scheduling is the one most deskless operations genuinely need. Who is rostered, who turned up, who swapped, hours against overtime thresholds, coverage against forecast demand, payroll-grade hour records. Vendors built for this — Jibble, Deputy, Connecteam, Homebase and the larger workforce management platforms — do it properly. Our attendance tracking guide covers the distinction from analytics, and workforce management versus analytics covers why these are separate categories rather than tiers of one.
Location and task tracking applies to a narrower set: field service, delivery, mobile maintenance. Where the work is inherently distributed and dispatch depends on knowing where people are, location data earns its place operationally. It is also the most legally sensitive data in this whole area.
Desktop activity analytics — the category this site mostly writes about — applies to the people who support a deskless operation rather than the operation itself. The schedulers, the dispatchers, the back-office and billing teams, the managers. These are desk workers inside a deskless business, and they are a legitimate but much smaller population than the headcount suggests.
A retail chain with 4,000 store staff and 60 head-office employees needs workforce management for 4,000 and might want analytics for 60. Vendors in both categories will quote you for 4,060.
The measurement that actually matters
Here is the thing most deskless operators have backwards. The controllable driver of cost in frontline work is usually not individual productivity. It is scheduling.
Frontline attrition is high and expensive, and the research on its causes points consistently at rota instability: shifts posted with little notice, hours that vary week to week so income is unpredictable, clopening patterns, split shifts. Those are management decisions, they are fully visible in scheduling data, and they produce turnover that dwarfs whatever individual variation in effort exists.
An operator who improves schedule predictability and reduces last-minute changes will typically see more financial benefit than one who tracks individual task rates — and the first intervention is cheaper, because the data is already in the scheduling system.
Measuring individuals harder is the intuitive move and the low-yield one. It is also, in a high-turnover sector where people have alternatives, actively counterproductive: the staff most willing to tolerate close monitoring are the ones with the fewest options, which is not a selection effect any operator wants.
The legal position on location
Location data is the sharpest issue in deskless monitoring and the one most often got wrong.
Tracking a work vehicle during working hours, with clear advance notice, is lawful in most places. The problems arise at the edges, and the edges are where real deployments live.
Tracking that continues outside working hours is very hard to justify anywhere. If the vehicle goes home with the driver, the tracker is recording their evenings and weekends, which is location data about their private life. The fix is technical — geofenced or shift-bounded collection — not a policy promise.
Tracking a personal vehicle or personal phone is a further step again and runs into the same problems as BYOD monitoring with added sensitivity.
Notice requirements are specific in several jurisdictions. Some US states require written notice or consent for vehicle tracking; Australia's surveillance Acts cover tracking devices explicitly with notice periods attached; the EU and UK treat location as requiring a proper necessity assessment, and continuous tracking of workers has been found disproportionate in several regulator decisions.
Unions and works councils are also more present in deskless sectors than in software, and in Germany or the Netherlands that means a formal process before deployment.
A sensible stack
For a deskless operation, the arrangement that works is usually:
Workforce management as the core system — scheduling, attendance, hours to payroll, labour rule compliance. This is where the money is and where the measurement should concentrate.
Biometric or geofenced clock-in if buddy punching is a genuine problem, which it sometimes is. This removes the mechanism rather than watching people, and our time theft piece covers why that distinction matters.
Location tracking only for roles where dispatch requires it, shift-bounded, with notice.
Desktop analytics for the back-office population only, if you want it at all.
And deliberately not: activity rates for physical work, continuous location, or anything that ends up as an individual pace score.
Where ProdView fits
Narrowly, and we would rather be clear about it. ProdView measures desktop activity and application metadata, so it is useful for the scheduling, dispatch, billing, support and management population inside a deskless business. It is of no use for the frontline workforce itself, and we have no attendance clock, no rota, no GPS and no payroll integration.
When not to pick us: for your deskless staff. That is a workforce management purchase — Jibble for simple attendance with a genuinely free unlimited tier, Deputy or Connecteam for scheduling-heavy operations, a full WFM platform if you forecast demand against labour. We will not pretend otherwise to win a seat count.
Try before you commit
If you have a head-office team worth measuring, three seats are free forever. For the frontline, the higher-yield exercise costs nothing: pull the last three months of schedule changes and measure how much notice staff actually got. That number usually explains more about your turnover than any tracking project would.
General information as of October 2026, not legal advice. Location and biometric data carry jurisdiction-specific requirements; take local advice before deploying either.