No two worksites are the same. A rail yard in the Northeast operates differently from a port terminal on the Gulf Coast. A construction corridor in a dense urban project has different risk geometry than an open-air mining operation. A warehouse running three forklift shifts faces different proximity challenges than a utility crew working wide-area field maintenance.
This is why proximity safety technology cannot be deployed the same way you'd roll out a software subscription or install a new camera system. The hardware lives on people's bodies and on moving equipment. The alerts fire in real environments with real noise, real obstacles, and real operational pressure. Getting it right requires a structured process of testing, learning, and calibrating before you scale.
That's the purpose of a 90-day pilot.
What a Pilot Actually Tests
A well-structured proximity safety pilot isn't just a product trial — it's a systematic evaluation of how the technology performs in your specific environment. The variables that matter most can't be simulated in a lab or predicted from a product spec sheet. They have to be measured in the field, with your workers, your equipment, and your operational rhythms.
The core questions a 90-day pilot answers:
- Are alert ranges calibrated correctly for your equipment speeds and site geometry?
- Does LTE connectivity hold across your full site — including low-signal areas, underground sections, or dense equipment staging zones?
- Are worker-worn devices comfortable enough that workers will actually keep them clipped on throughout a full shift?
- Are static beacon placements catching the right blind spots, or do some locations need repositioning?
- Is the alert acknowledgment feature reducing fatigue in high-traffic areas without creating gaps in coverage?
- What does equipment utilization data reveal about idle time and bottlenecks that your team didn't previously have visibility into?
"The pilot isn't about proving the technology works in general. It's about proving it works specifically for your site — and configuring it to work even better before you commit to full deployment."
A Progressive Structure That Reduces Risk
The 90-day structure is deliberately staged. Starting with a focused deployment on the highest-risk areas and equipment — rather than activating every device across the full site simultaneously — serves a critical purpose: it isolates variables.
When you start focused, you can evaluate alert performance without the complexity of hundreds of simultaneous device interactions. You can work out beacon placement issues, connectivity gaps, and calibration adjustments before they affect a large worker population. You can gather early worker and supervisor feedback while the deployment is still small enough to iterate quickly.
Baseline Deployment
Deploy to highest-risk equipment and worker groups. Establish alert baselines, map site-specific blind spots, validate LTE connectivity, and gather initial device performance data. Identify any beacon placement or configuration adjustments needed.
Expand & Stress-Test
Expand to additional equipment groups, worker roles, and site sections. Test alert performance under full operational load — peak traffic hours, shift changes, night operations, and adverse weather conditions. Refine acknowledgment settings to reduce fatigue in expected high-proximity zones.
Full Coverage & Analysis
Full device deployment across the site. Capture complete safety and operational data — close-call heatmaps, equipment run-times, idle patterns, bottleneck locations, and shift risk correlations. Compile the Safety & Operations Report for management and safety leadership review.
The Data You Walk Away With
Regardless of what happens next — whether you expand to full deployment, adjust the configuration, or simply bank the learning — the 90-day pilot generates a body of worksite intelligence that has value independent of any future technology decision.
The Safety & Operations Report delivered at pilot conclusion documents exactly where close-contact events clustered, which equipment paths created the most frequent worker-vehicle interactions, which shift windows correlated with elevated risk, and where physical layout changes could reduce hazard exposure permanently.
On the operational side: where equipment sat idle when it should have been moving, where crews and assets created congestion, and which maintenance windows could be better timed based on actual usage data rather than scheduled intervals.
That information has value whether you deploy 50 devices or 500. It's a map of your worksite risk and operational efficiency that didn't exist before — built from real data, during real operations, with your actual workforce.
What Workers and Supervisors Learn
There's another dimension of the pilot that doesn't show up in the data report but matters just as much: organizational readiness. Workers learn how to interpret alert tiers — the difference between a first-stage awareness nudge and an urgent alarm. Supervisors learn which zones generate the most alerts and how to respond. Safety teams develop the muscle memory of reviewing proximity data and acting on patterns rather than waiting for incidents.
By the end of 90 days, the technology isn't new anymore. It's part of the site's safety vocabulary. That organizational familiarity dramatically improves the effectiveness of any expanded deployment that follows.
A 90-day pilot isn't a trial period. It's the first chapter of a deployment — done right, so everything that comes next is built on validated ground.
Start With a Pilot Conversation
Tell us about your site and we'll walk through what a 90-day pilot would look like for your environment.
Request a Demo →