Pilot programme

Pilots are how Overguard onboards enterprise customers.

An 8–12 week engagement on one live site: full hardware deployment, all four platform layers, a named executive sponsor, and success criteria you set. You measure it like any other piece of operational kit, and it earns the next site or it doesn’t.

Construction · Utilities · Infrastructure · UK & Australia

The journey

Six stages, from scope call to decision.

Every pilot follows the same structured programme. Dates are set at the scope call; nothing below depends on heroics.

Scope call

Stage 01
Your safety and operations leadership meet ours. We agree the site, the workforce population, the questions the pilot should answer, and the success criteria you will judge it against. Nothing ships until the scope is signed.
OutcomeSigned deployment plan and agreed success criteria.

Site survey

Stage 02
We map the site with your team: zones and exclusion areas, cellular coverage, indoor spaces that need BLE anchor beacons, and whether the deployment kit needs a LoRaWAN gateway. The platform is configured before a single pod arrives.
OutcomeSite configured on the platform: zones, roles, muster points.

Deployment kit arrives

Stage 03
Pods, charging docks, and gateway hardware arrive pre-configured for your site. Provisioning takes under four minutes per worker: clip, scan, assign. Site managers learn the platform in two short sessions.
OutcomeHardware on site; managers trained.

Pods go live

Stage 04
Workers wear the S1 from the first shift. Alerts route to your safety team in real time, the register builds itself, and Risk Signal starts learning the shape of your site. We watch the first days with you.
OutcomeWorkforce live on the platform.

Weekly reviews

Stage 05
A standing weekly working session with your named champion: what the platform caught, what it filtered, what Overguard AI is surfacing, and what to tune. Muster drills are run and timed as part of the programme.
OutcomeDocumented safety events, drills, and platform calibration.

Decision

Stage 06
You assess the pilot against the criteria you set at the scope call. Your assessment, not ours. If it earned the next site, we plan the rollout together. Either way, your data is yours, exportable in full.
OutcomeGo / no-go on rollout, on your evidence.
What a pilot includes

Six things every pilot ships with.

Hardware included
Every worker in the pilot population gets an S1, with docks and a LoRaWAN gateway where the site needs one. No capital purchase.
Full platform access
All four layers from day one: Alerts, Risk Signal, Insights with Overguard AI, and Reports. Nothing held back for a higher tier.
Emergency Muster drills
Whereabouts and Emergency Muster configured for your site, with timed drills run during the pilot so the capability is proven, not promised.
RIDDOR-compatible Reports
Notifiable-event reporting, muster records, and the audit trail, assembled from live telemetry and exportable throughout.
Named sponsor and champion
A named executive sponsor at Overguard and an operational champion dedicated to your pilot for the full engagement.
Weekly working sessions
Review, calibration, and tuning every week, by video or on site, against the success criteria you set.
Commercials

An operational expense, approvable at site level.

A pilot is priced as a per-worker operational fee for the engagement. There is no hardware purchase, no capital approval, and no minimum term beyond the pilot itself. Hardware remains Overguard property and is returned at pilot end.

That means a safety director or site lead can approve a pilot on the same authority they approve any other operational tool, without a capex cycle. We made that deliberate. Pilots that take six months to approve don’t run.

Request pilot access

Tell us about the site.

We respond within one working day, and the first conversation is a scope call, not a sales pitch.

Prefer email? Write to pilots@overguard.app directly.

Questions

What safety leaders ask first.