The durable asset isn’t the wearable. It’s the ledger.
Every hazard module Exposia ships (UVDose, NoiseDose, and what comes after) writes into the same append-only exposure ledger, mapped against Australian standards. The wearable is the wedge; the record is what your business keeps building on.
Where Exposia fits your due-diligence obligations
Officer due diligence under section 27 of the model WHS Act asks for reasonable steps across six elements. It’s a non-exhaustive list; no single record ticks every box. But three of those elements are exactly what a continuous exposure record speaks to.
Resources and processes are available, and used
Continuous monitoring is the resource and process the standard asks for. Unlike a policy sitting in a drawer, usage is inherent: it runs on watches your workers already wear, every shift.
Verify those resources and processes are being used and are effective
Widely regarded as the most overlooked element of due diligence. A continuous exposure record is itself a form of verification, not just a claim of one.
Receive hazard information and respond in a timely way
Exceedance triage and a logged response are this element, in practice: when Exposia flags a crew, your dashboard shows whether and how you responded.
The pattern is consistent
Heat-related harm tends to show up in court. Noise and UV harm typically doesn’t: the financial consequence arrives later, as workers-comp claims, premium loadings, and regulator improvement notices, rather than a prosecution. Either way, the cases share a pattern: a safety system existed on paper, and monitoring conditions or planning work around exposure were the simple, available steps that weren’t actually taken.
Exposia is that monitoring and that planning evidence. It doesn’t replace supervision or emergency response, and it doesn’t guarantee an outcome: due diligence is a non-exhaustive list of reasonable steps, not a checklist that clears itself.
A dose ledger, not a dashboard skin
Sensor data comes in from each worker’s watch, gets fused with Australian environmental data (the ARPANSA UV index, BOM solar and heat data), and is written against the relevant exposure standard for that hazard. The ledger is append-only: nothing is silently overwritten or recalculated away. Every entry is timestamped and stays timestamped, for as long as your record-keeping duty requires.
We tell you what we didn’t measure
Honest-gap logging is a platform primitive, not a feature toggle. If a watch is off-wrist, out of battery, or out of range, Exposia records that period as missing, visibly, on the record, instead of interpolating a plausible-looking number to fill the hole.
It reads like a limitation. It’s actually the feature that makes the record worth having: an audit pack that shows exactly what was measured, and admits what wasn’t, is one that survives scrutiny after an incident. A record that quietly fills its own gaps doesn’t.
coverage 94% this shift · 06:00–06:40 no data, watch off-wrist
Audit packs, generated, not assembled by hand
Every organisation on Exposia can export an audit pack straight from the ledger: exposure records, coverage figures, exceedance history, and the actions taken against them, by crew or by site, for whatever window your officer or your insurer needs to see. No screenshots, no re-keying a spreadsheet the week before an audit.
The worker owns the data
Workers consent individually and can see everything about themselves, on their own device, at any time. Employers see aggregates, exceedance flags, and compliance records, never continuous location, raw sensor streams, or anything captured off-shift. That boundary is enforced in the architecture, at the policy-engine level, not asserted in a privacy policy nobody reads.
It’s also, deliberately, ahead of where Australian workplace surveillance regulation is heading, built this way from the start, rather than retrofitted once a state mandates it.
One worker app. Modules are entitlements, not installs.
Your workforce installs one app, once, with one consent flow and one HealthKit permission set. Every hazard module you license (UVDose today, NoiseDose alongside it, HeatDose later) shows up inside that same app as a licensed tab, switched on server-side. Adding a module to an existing account installs nothing new on a single device.
For your IT and MDM team, that means one rollout covers every module you’ll ever add. For your budget, it means the second module is an entitlement flip, not a deployment project.