The first 30 days with inviol: what new customers experience

Every new technology comes with that slightly nervous question: what's this actually going to be like?

You've seen the demo. You've read the case studies. You've spoken to a reference customer. But there's still a gap between "this looks great" and "this is working in our facility." That gap is the first 30 days, and in my experience working with new inviol customers, it's where the platform stops being a concept and starts being part of how your team operates.

Here's what that first month actually looks like, from the day you sign through to the moment your safety manager pulls up a heatmap and says, "I didn't know that was happening."

Before day 1: the stuff that happens behind the scenes

Before anything gets plugged in, there's a short scoping conversation. Our team works with yours to understand your facility layout, your existing camera infrastructure, your highest-risk areas, and what you're hoping to learn first.

This isn't a months-long discovery process. It's typically a couple of calls and a site plan. We're figuring out which cameras to connect (you don't need all of them, just the ones covering your priority zones), confirming compatibility, and making sure your network can support the processing unit.

Most customers are surprised by how little they need to prepare. If you have modern IP cameras on a wired network, you're almost certainly ready. If your cameras are older or analogue, we'll work through the options with you, but in most cases, the existing setup is more than sufficient.

Week 1: getting connected

This is where the physical setup happens. An inviol processing unit arrives at your site. It's a compact device that connects to your existing network and starts receiving camera feeds from the zones you've chosen to monitor.

The setup is genuinely straightforward. One of our enterprise customers described it as plug-and-play: collect the device, connect it to the network, configure with the IT team, and go live. There's no major infrastructure project, no new cabling runs, no months of integration work.

During this first week, the system is calibrating. It's learning the layout of your facility through the camera views, understanding what normal activity looks like, and beginning to detect and classify safety events in real time: pedestrian-vehicle interactions, exclusion zone breaches, vehicle speed events, and more.

Your team doesn't need to do much during calibration other than confirm that the camera feeds look right and the detection zones are correctly defined. Our team handles the technical configuration and makes adjustments remotely as needed.

Most sites are fully live and detecting events within about two weeks of signing.

Week 2-3: first insights

This is the phase where things get interesting. The system has been running continuously, and your dashboard is starting to populate with real data from your facility.

The first reaction from most safety managers is some version of: "I had no idea that was happening." The volume of near misses, exclusion zone breaches, and pedestrian-vehicle interactions that occur outside of anyone's direct line of sight is consistently higher than people expect. That's not a failure of your current safety programme. It's the nature of the problem. Manual observation can only catch what someone happens to see, during the hours they happen to be watching.

During this phase, your safety team gets access to the reporting dashboard. The interface is designed to be intuitive. One operations manager at a large distribution centre described it as feeling similar to familiar consumer apps in its ease of use. After an initial walkthrough, she was able to train her managers on it herself. Daily event review typically takes around 5-10 minutes.

This is also when your team starts to see the heatmap take shape. As events accumulate across your facility, patterns emerge: which zones have the highest concentration of events, what time of day risk peaks, and whether certain areas are consistently hotter than others. These spatial and temporal patterns are almost impossible to identify through manual observation, but they become obvious when you can see weeks of data visualised on a single screen.

We'll also walk your team through the coaching platform during this phase. This is where detected safety events become short, reviewable video clips that supervisors can use in conversations with their teams. The clips are automatically face-blurred, so the focus is on the behaviour and the environment, not on identifying individuals. This privacy-first approach is critical for building trust with your workforce.

Week 4: coaching starts to land

By the end of the first month, the transition from "we have a new tool" to "we're using this tool" should be underway. Here's what that looks like in practice.

Supervisors are running coaching sessions. The platform packages detected events into short clips that a supervisor can pull up on a tablet or screen during a toolbox talk or shift briefing. Instead of talking about safety in abstract terms, the conversation is grounded in something specific and recent: "Here's a near miss that happened in our zone on Tuesday. Let's talk about what we can do differently." This is the shift from policing to coaching, and it changes the tone of safety conversations entirely.

The team knows the system isn't surveillance. By now, your workforce has seen the face-blurred clips. They understand that the platform detects interactions (person near vehicle, vehicle in exclusion zone), not individuals. For most teams, any initial scepticism fades quickly once they see how the system is being used: to improve conditions and start better conversations, not to catch people out. Our customers tell us this cultural shift is one of the most valuable outcomes of the first 30 days.

You have a baseline. Four weeks of continuous data gives you something you probably didn't have before: a quantified safety baseline. You now know how many near misses occur per day across your monitored zones, where they concentrate, when they peak, and what types of events are most common. That baseline is the foundation for everything that comes next, because every improvement you make from here can be measured against it.

You've identified your first quick wins. Almost every customer discovers something in the first month that they can act on immediately. A blind corner where forklifts and pedestrians regularly converge. A delivery window that creates a burst of vehicle-pedestrian interactions. A traffic flow pattern that could be improved by moving a single barrier. These aren't theoretical insights. They're specific, actionable, and backed by timestamped event data that makes the case for change straightforward.

What happens after day 30

The first month is the foundation. What comes next is where the compounding value kicks in.

Over the following weeks and months, customers typically see a measurable decline in safety events as coaching takes hold and operational adjustments are made. One major New Zealand retailer achieved a 63% reduction in health and safety incidents within two months of going live. Across our customer base, the average risk reduction is 67%.

The platform also starts delivering value beyond safety. Customers frequently discover that heatmap data reveals operational insights they didn't expect: traffic flow bottlenecks, inefficient vehicle routes, congestion points during shift changes. These findings often lead to improvements in throughput, reduced damage to goods and machinery, and more efficient use of space, benefits that extend well beyond the EHS team.

For organisations with multiple sites, the playbook from site one becomes the template for sites two, three, and beyond. Once your team knows the system, subsequent deployments are faster and smoother. Many of our customers operate across more sites than they're currently monitoring, and expansion typically accelerates once the first site proves the value.

The honest version

Not everything is perfect from day one. Calibration takes time. False positive rates are higher in the first few days before the system adjusts to your specific environment. Your team needs to build new habits around reviewing events and running coaching sessions. And there will be at least one person on the floor who asks, "Is this going to be used to watch us?" (The answer, supported by the face-blurred clips and the coaching-first approach, resolves that concern quickly.)

But the honest truth is that most of the hard work isn't technical. The technology is the easy part. The real work of the first 30 days is cultural: helping your team see that this is a tool designed to help them, not monitor them. Get that right, and the rest follows.

If you're curious about what the first 30 days would look like in your facility, book a demo and we'll walk you through it.

Frequently Asked Questions

How long does it take to deploy inviol?

Most sites are fully live within approximately two weeks of signing. The setup involves connecting a processing unit to your existing network, configuring camera feeds, and defining detection zones. There's no requirement for new cameras, new cabling, or lengthy IT projects. The system starts detecting safety events as soon as calibration is complete.

Do we need new cameras to use inviol?

In most cases, no. inviol works with existing IP CCTV cameras on a wired network. You don't need to connect every camera on site, just the ones covering your highest-risk zones. During the scoping phase, our team assesses your camera infrastructure and confirms compatibility before any hardware is shipped.

How much time does inviol take to manage day to day?

Daily event review typically takes around 5-10 minutes. The dashboard is designed to surface the most important events first, and coaching clips are pre-packaged so supervisors can use them directly in toolbox talks or shift briefings without any additional preparation.

What results can we expect in the first 30 days?

In the first month, you'll establish a quantified safety baseline across your monitored zones, identify your highest-risk areas through heatmap data, begin running coaching sessions using real video clips from your facility, and almost certainly discover quick-win improvements (such as traffic flow adjustments or barrier placements) that can be acted on immediately. Measurable risk reduction typically follows within the first two to three months.

How does inviol protect worker privacy?

All video footage is processed on-premise, meaning it doesn't leave your site. Detected safety events are automatically face-blurred, so coaching conversations focus on behaviour and environment rather than individual identification. The platform is SOC 2, ISO 27001, and GDPR compliant, and inviol's security certifications can be verified at trust.inviol.com.