A deployment scenario, not a named customer. This describes how these rollouts run in practice and what to measure, drawn from how the software is built and how these operations work. It does not report one organisation's results. For customer references, ask our team — we will introduce you to someone running it.
The situation
The operator runs multiple manufacturing sites in several regions, employing around multiple people with a contractor population that changes daily. Each site had a security desk, a bound register and a pen. On a normal day the gate handled multiple visitors, contractors, drivers and vendor engineers.
The register worked, in the sense that entries were written down. What it could not do was answer a question. During a fire drill, the safety officer needed the number of people inside the boundary, and the only way to get it was to carry the book to the assembly point and count by hand — by which point several of those names had already gone home without signing out.
What was actually going wrong
- Exits went unrecorded. Visitors signed in reliably and signed out rarely, so the register overstated occupancy by an unknown margin.
- Contractor validity was unchecked. Whether a contractor's safety induction or insurance was current depended on the guard remembering to ask.
- Nothing was searchable. Answering "when did this vendor last visit?" meant turning pages.
- Sites could not see each other. Someone barred from one plant could present at another the same week.
What changed
The operator deployed BeyondBoxAI Visitor Management across multiple gates over multiple weeks, starting with the busiest site.
- Pre-registration. Hosts invite in advance; the visitor completes their details before arriving, so the gate is a check rather than a data-entry desk.
- Identity capture. Photograph and identity document recorded at entry.
- Host approval. The person being visited approves before entry is granted.
- Blocklist checked automatically on every attempt, across all sites.
- Exit closes the record, so occupancy is a live number rather than a guess.
What to measure
These are the measures worth baselining before a rollout and checking after. If a baseline does not exist because nothing was being recorded, say so — an honest "previously unmeasurable" is more credible than a reconstructed number.
| Measure | Why it matters | Where the figure comes from |
|---|---|---|
| Average time to check in a visitor | The number that tells you whether the rollout worked | Timed at the gate |
| Visitors with no recorded exit | The number that tells you whether the rollout worked | Register audit |
| Time to produce an occupancy list | The number that tells you whether the rollout worked | Drill record |
| Contractors admitted with lapsed induction | The number that tells you whether the rollout worked | Compliance audit |
Read more about visitor management systems or see the product.
BLOG · 3 MIN READ
BLOG · 4 MIN READ