Wearables and worker tracking on a small site: the business and privacy case

Wearable technology in construction covers a wide field, from a simple tag that logs who entered a zone to a device that reports a worker’s movement or vital signs. On a large project, the case for them is often made at the top of the organisation, where a safety team has the resources to run a pilot and a legal team to look at the data. On a small site, the decision usually lands on the builder or the site supervisor, who has to weigh the same questions without that support.

The reason this is not a simple equipment purchase is that most tracking devices generate personal information. A tag that records a worker’s location over a shift is telling you where an identifiable person was, and often when. A device that measures heart rate or fatigue is collecting health information, which is a more sensitive category again. Once that data exists, it brings obligations about how it is collected, stored, used, and eventually destroyed.

So the practical question is not whether the technology works. It usually does. The question is whether the specific problem on your site justifies the cost, the disruption, and the ongoing duty that comes with holding personal information about your crew.

What small-site wearables actually do

It helps to separate the categories, because they carry different risks and different privacy weight. The most common deployments on small residential and light commercial sites fall into a few groups.

• Zone and access tags. A tag or fob that registers when a worker enters a defined area, such as an excavation, a roof, or a plant operating zone. The output is essentially a location log.
• Lone worker and emergency alert devices. A pendant or wristband with a manual alert and sometimes a fall or inactivity trigger. The purpose is to summon help, and the data is usually limited to an alert event and a location.
• Fatigue and physiological monitors. Devices that estimate fatigue, heat strain, or alertness from movement, heart rate, or skin temperature. These collect health-related information.
• Proximity and exclusion systems. Tags that warn when a worker is close to moving plant, or that shut down plant when a tag enters a zone. These are often paired with the plant rather than the person.
• General activity tracking. Step counts, hours on feet, or time on task, usually marketed as a productivity tool rather than a safety one.

Each of these answers a different question. A lone worker alert answers “if something happens to this person, how do we know?” A proximity system answers “how do we keep people out of the swing radius?” A fatigue monitor answers “is this person fit to keep working?” Those are genuinely different problems, and buying a device that answers one will not answer the others.

The safety case is usually the strongest one

If you are looking for a justification that stands up to scrutiny, it is usually found in a hazard you already know about. SafeWork Australia’s guidance on electrical safety, for example, is built around the idea that the risk is managed by controlling exposure to the hazard rather than by relying on the person to be careful. The same logic applies to plant, falls, and lone work. A control that keeps a person out of a zone, or that raises an alert when they are working alone, is doing something a briefing cannot.

That is the strongest version of the case: the device is a control on a risk you have already identified, and you can point to the risk in your own documentation. If you cannot name the hazard, the device is a gadget, and it will end up in a drawer.

The weaker version is productivity tracking dressed up as safety. A step counter or an activity log that is really about monitoring how much time a worker spends on a task does not have the same justification, and it is more likely to create friction with the crew. Workers are generally quick to work out which of the two they are being issued.

What the privacy regime does to the equation

This is the part that most small builders have not worked through, and it is the part that changes the ongoing cost of the decision.

The Office of the Australian Information Commissioner publishes guidance on privacy for small businesses, and the short version is that the small business exemptions in the Privacy Act are narrower than the common assumption. Some small businesses are covered, and some are not, depending on what they do and how they trade. A builder who assumes they are outside the regime because the crew is small may be wrong, and the cost of being wrong is not a fine at the low end — it is a complaint, a dispute with a worker, or an incident where the data has to be produced and it has not been managed.

Where the regime applies, the obligations are familiar in shape even if you have never read them. You need a lawful basis for collecting the information, you need to tell people what you are collecting and why, you should not collect more than you need, you have to keep it secure, and you have to dispose of it when it is no longer needed. Each of those has a practical implication on site.

“Not more than you need” is the one that bites hardest. If a proximity system only needs to know whether a tag is inside a zone, it does not need to keep a full shift-by-shift location history for every worker. If you can configure the system to discard the history and keep only the exceptions, that is a materially different privacy position from storing everything because the dashboard makes it easy.

Consent, consultation, and the crew conversation

On a small site, the privacy question and the industrial question arrive together. Workers will want to know what the device records, who looks at it, and whether it can be used against them. If you cannot answer those questions clearly, the rollout will not go well regardless of what the law requires.

The practical approach is to have the conversation before the devices are ordered, not after they arrive. Explain the hazard the device is addressing, show what the dashboard actually displays, and be honest about what is retained. If a worker asks whether the data can be used in a disciplinary process, the honest answer is that it might be, and that is exactly why the retention and access rules need to be settled in advance.

Consultation obligations under work health and safety law generally require you to talk to workers about matters that affect them, and a monitoring system is squarely in that territory. Treating the conversation as a formality is the mistake that turns a safety control into a dispute.

Data security is now part of your site setup

A tracking system produces a dataset that is unusual: it is commercially sensitive and personal at the same time. It tells you where your people were, which means it also tells anyone who obtains it where your site was active, when crews were on site, and how the programme was running. That combination makes it a more attractive target than a simple contact list.

The Australian Signals Directorate publishes guidance for small business on cyber security, and the themes apply directly here. Limit who can access the dashboard or portal. Use strong authentication rather than a shared login. Keep the device management platform updated. Know where the data is stored and who the supplier shares it with. Have a plan for what happens if the account is compromised, including how you would tell affected workers.

The supplier question matters more than most builders expect. A wearable system usually involves a cloud platform, and the data may be held offshore or shared with third parties for analytics. If you cannot get a straight answer about where the data lives and who can see it, that is a reason to look at a different product rather than a detail to sort out later.

The commercial reality on a small crew

On a small site, the maths is unforgiving. The hardware is the cheap part. The ongoing cost is in the subscription, the time to configure and manage the system, the conversation with the crew, the privacy work, and the review. Those costs do not scale down just because the crew is small.

What a tracking system can do is avoid a single bad outcome. A lone worker who collapses on a remote part of a site and is found quickly is a different incident from one found at the end of the day. A proximity alert that stops a near miss with an excavator is a different incident from a serious injury. If the risk is real on your site, the cost of the system is trivial next to the cost of the incident.

What it will not do is fix a disorganised site. If the real problem is that nobody knows who is on site or what is programmed for the day, a tracking device is an expensive way to find out. Site management software and a disciplined sign-in process will often answer the same question more cheaply. The related article on getting your team to use the software you paid for covers that decision, and it is worth reading before you look at hardware.

There is also a dispute dimension that builders often only discover later. If there is an incident, the tracking data may become evidence. That cuts both ways: it can show that a worker was in a controlled area, or it can show that a control was not working. If you are going to collect the data, you need to be comfortable with it being read back to you in a formal process.

A worked example

A builder in western Sydney runs a crew of five on residential renovations, with regular work on roofs and in roof spaces. A near miss the previous summer — a worker who became unwell in a roof space on a hot day and was not found for some time — is the specific hazard driving the decision.

The builder looks at three options. The first is a lone worker alert pendant with a manual trigger and an inactivity alert, which addresses the actual hazard. The second is a full location tracking platform with a dashboard showing every worker’s position across the day, which does more but collects far more personal information. The third is a change to the site process: a sign-in board, a check-in radio call at set intervals, and a rule that nobody works alone in a roof space.

The third option is the cheapest and addresses most of the risk, but it depends on the crew remembering to check in, which is exactly what failed last time. The first option provides an automatic alert if the worker does not move, which covers the failure mode. The second option provides the alert plus a lot of data the builder does not need and would have to manage, secure, and eventually delete.

The sensible outcome is the first option, with the process change kept as a backstop, and a decision recorded about what data is retained and for how long. The builder writes down the hazard, the control, and the review date, and tells the crew what the device does and does not record. That is a defensible position if anything goes wrong, and it does not require the builder to become a data manager for information they never needed.

Where this fits in your CPD and your documentation

If you are a licensed builder in NSW, the way you manage safety and technology decisions is part of the broader picture of how you run a compliant business. The guide to how NSW builder CPD works sets out the framework, and the course catalogue covers the areas where these decisions usually sit, including work health and safety and business practice.

The documentation point is the one to take away. Whatever you decide about wearables, write it down: the hazard, the control you chose, the alternatives you rejected, what data you collect, who can see it, and when it gets deleted. That record is what turns a technology purchase into a managed risk, and it is what you will want if a worker, a regulator, or an insurer ever asks why you did it that way.

Making the call

Wearables and worker tracking are not automatically worth it on a small site, and they are not automatically a bad idea either. The deciding factor is whether you can name a specific hazard or a specific question that the data answers, and whether you are prepared to manage the personal information that comes with it.

If you can do both, the case is usually sound, and the cost is small against the incident you are trying to avoid. If you cannot name the hazard, or you cannot say who will look at the data and when it will be deleted, the honest answer is to fix the process first. The technology will still be there when you have a question for it to answer.

Questions builders ask

• Technology
• Wearables
• Work Health Safety

Published 28 August 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.