What workforce tracking is, and the line it should not cross
The word tracking makes people flinch, so it is worth being precise about what a good site system actually does. It records events at fixed points: a credential presented at a gate, a door opened into a zone, a sign-in at a kiosk. From those events it derives presence: this person entered at 07:14, was last seen entering Zone B, and has not yet left. That is the whole mechanism.
What it does not do matters just as much. It does not follow anyone's phone. It does not know where a person stands within a zone, only that they entered it. It knows nothing about anyone outside the site boundary, at lunch, at home, at the weekend. The honest framing is that a site tracks presence on the site, in the same way a hotel knows which rooms are occupied, and that framing survives scrutiny because it is true.
Sites that blur this line pay for it. A workforce that believes it is being surveilled will fight the system, lend credentials to make a point, and treat every report as ammunition. A workforce that understands the system exists so the fire muster is right, and so their hours are provable when a payment is disputed, tends to see it for what it is: protection that runs both ways.
The live picture: headcount, categories and zones
The first output of workforce tracking is a number you can trust: how many people are on site right now. Not this morning's expected figure, not yesterday's total, the live count, moving as people badge through gates and sign in at kiosks. On its own that number runs evacuations, deliveries and end-of-day lockups.
One number is rarely enough, though, because a site is not one population. A useful register breaks the count down by category, employees, contractors, visitors, drivers, because each category carries different obligations. Forty contractors and no visitors is a normal Tuesday. Forty visitors is an open day, and reception should probably know. Drivers still on site at seven in the evening is a question worth asking.
Zones add the second dimension: not just who is in, but where. Live occupancy per zone shows the population of each area of the site, and last-seen zone pins each individual to the area they most recently entered. On an interactive site map, that turns an abstract list into an operational picture: the plant room has two people in it, the far compound is empty, and the person you are trying to find was last seen entering the workshop.
Headcount by category. Employees, contractors, visitors and drivers counted separately and live, so the number matches the obligations: hosts for visitors, inductions for contractors, everyone on the muster list.
Zone occupancy. The live population of each area, which is how you know a restricted area is clear before work starts and a high-risk zone is empty at the end of a shift.
Last-seen zone. The single most useful field in an incident: not a guarantee of where someone is, but a truthful record of the last fixed point they passed, and the right place to start looking.
Where the data comes from
A live picture is only as good as its inputs, and the inputs are the physical edges of the site. Gates, turnstiles and doors read credentials as people pass, each read stamped with who, where and when. Kiosks capture the people who do not carry credentials, visitors, first-day arrivals, whole crews signing out together at day end. Every one of those events lands in the same register, which is why the picture holds together instead of splitting into an access system that knows one thing and a sign-in app that knows another.
The connection between the reader and the register has to be trustworthy, because the whole value of tracking is that the record reflects reality. Site Commander's controllers use cryptographic device identity and replay-protected signed messaging, and when a gate loses its connection it keeps scanning, queues events locally, and replays them as a signed batch once the link returns. The operational meaning is simple: a network wobble does not put a hole in your attendance history.
It is also why phone-based tracking is the wrong tool for this job. GPS is vague at exactly the scale a site cares about, drains batteries, stops at the door of a steel-framed building, and requires every person on site to install and permit something on a personal device. Fixed-point presence is more accurate where it counts, includes everyone, and asks nothing of anyone's phone.
From live picture to evidence: movement history
The live register answers today's questions. The movement history answers everyone else's: the commercial team disputing a subcontractor invoice, the HR investigation that needs to know who was in on a specific Saturday, the auditor asking who entered a restricted area in March. Tracking without history is a dashboard. Tracking with history is evidence.
The per-person view is where the depth lives. A movement report for one individual should show hours by date range, by week and by month, visit counts, first-in and last-out times for each day, and a session-by-session timeline recording how every entry and exit was captured. Site Commander exports that as a formal PDF, which is the difference between answering a dispute with a document and answering it with a screenshot.
History also has to be honest about its own imperfections. People tailgate, exits get missed, and a register that pretends otherwise is lying politely. The correct behaviour is a full attendance history with filters to find the anomalies, manual corrections restricted to permitted users, every correction marked as manual, and an audit log recording who changed what. A record that shows its own repairs is more credible than one that appears flawless.
The live picture runs the day. The movement history wins the argument. A workforce tracking system has to do both from the same data, or the two will eventually disagree in front of someone important.
The emergency case: where tracking earns its keep
Everything above is useful on an ordinary day. On the day the alarm sounds, it becomes the only thing that matters. An evacuation run from memory, or from a signing-in book fetched from the gatehouse, is a guess wearing a hi-vis. An evacuation run from a live register is a checklist: this many people were in, these are their names, these are the first aiders among them, and here is who is not yet accounted for.
The details of the register decide whether that checklist works under pressure. Last-seen zone tells sweep teams where to concentrate. Category breakdowns make sure visitors and drivers, the people most likely to be forgotten, are on the list alongside the workforce. Safety flags surface the first aiders and incident response staff who happen to be in right now, not the ones on a laminated poster from last year.
In Site Commander, one press on the desktop starts a roll call against the live register, the muster list updates as people are marked safe, and a stamped muster sheet can be printed for the record. It works offline from an encrypted local snapshot and is reachable without a login, because an emergency does not wait for the network or a password. That is the standard worth holding any tracking system to: the picture must survive the exact moment it exists for.
Being straight with your workforce
Rolling out workforce tracking goes better when you say plainly what it does. People are recorded entering and leaving the site and its zones. Their hours are recorded, which protects them in pay and invoice disputes as much as it protects the business. Nobody is followed off site, nothing runs on personal phones, and the muster list is the reason the whole thing exists. Most objections dissolve when the explanation is concrete, because the alternative being defended is usually a paper book that protects no one.
It helps that the system itself behaves accountably. Access to reports should be limited to the roles that need them, administrative actions should be individually logged, and the audit trail should read in plain English so that what happened is legible to a layperson, not just an administrator. A tracking system that is transparent about its own operation is far easier to defend, to a workforce, a union or a regulator, than one that is a black box with a dashboard on top.
