Go Live in a Week: How a VizPass Implementation Runs
A step-by-step look at visitor management implementation with VizPass, taking a plant or office from paper gate registers to a fully configured tablet-based system in about a week, covering setup, roles, notifications and go-live. It walks through Day 1 sign-up and plan selection, Day 1–2 site, gate and host configuration, and the OTP and rollout steps that follow.
The gate register at most Indian plants runs on the same paper book it did a decade ago — a guard scribbling names half-legibly while a contractor crew waits, a host who never finds out a visitor arrived until security calls up, and a safety officer who cannot say who is inside the plant right now if there's an incident. None of that needs a new server room or a six-month IT project to fix. It needs a tablet at the gate and about a week of setup, done in the order below.
Day 1: The Workspace Opens, Nothing Is Installed
Someone signs up with a work email and a WhatsApp number, both get verified, and you pick a plan — ₹4,999, ₹9,999 or ₹14,999 a month per company, with a 7-day free trial to test it before paying. You name the company and the workspace opens with whichever modules that plan includes. There is no kiosk to procure, no local server, and nothing installed on a PC — the whole thing runs on any Android tablet you already have or can buy cheaply. If you run a multi-site group, each site and its gates get added under the same account, so a plant in Ghaziabad and a warehouse in Gurugram sit under one policy with separate gate screens.
Day 1–2: Sites, Gates, Hosts and Who Sees What
This is the structural work, and it's worth doing carefully because it doesn't change often. You add your sites and gates, then add hosts — name, email and mobile for each, because that mobile number is how a host actually finds out a visitor has arrived, by WhatsApp or SMS rather than a phone call to reception. Roles get assigned next:
- Company Admin — sets policy, adds sites and hosts, sees everything
- Receptionist — checks visitors in and out at a front desk
- Security Guard — sees only the gate screen, nothing else
- Host — gets notified, approves or declines their own visitors
You also set the visitor privacy notice at this stage, or keep the default one. This matters more than it sounds — under India's evolving personal data rules (the Ministry of Electronics & IT is the reference point here), a visitor's name, phone number and photograph are personal data the moment you collect them, and a plant that has never thought about consent language is exposed in a way a ₹5,000-a-month subscription fee is not.
Day 2–3: How a Visitor Actually Gets a Pass
This is where you decide the shape of the check-in experience, and it's genuinely a few configuration screens, not a project:
- OTP channel for visitor verification — WhatsApp, SMS/email, or switched off entirely if your gate process doesn't need it
- Approval mode per visitor type — a vendor might need host approval, a scheduled auditor might not
- Pass size — six sizes are available, so a small windshield sticker and a full A6 printed pass are both options depending on what your guard actually checks
- The QR poster for phone self-check-in, printed and put up at the gate so visitors can start their own entry from a phone camera
If you want mail to go out from your own domain rather than a generic sender, you can connect your own SMTP; if you'd rather run WhatsApp notifications through your own gateway instead of the default one, that's optional too. Neither is required to go live — both exist for the plant that already has an IT policy about outbound mail and messaging.
Day 3–4: The Gate Itself
An Android tablet with a camera goes on the gate, on Wi-Fi or 4G — 4G matters more than it sounds like it should, because a plant that loses power for twenty minutes during a load-shedding window shouldn't lose its gate register with it. If you print physical passes, a label or A6 printer sits alongside it. The guard walkthrough — how to scan an out-gate exit, how to search the on-site list, how to raise an overstay flag — takes about half an hour, and it's short because the Security Guard role is deliberately narrow: it shows the gate screen and nothing else, so a contract guard who rotates out next month isn't a training liability. For plants in Noida, Greater Noida, Ghaziabad, Delhi, Gurugram or Faridabad, this walkthrough happens on site, in person. Elsewhere in India, it's a video call with the gate tablet live in front of the camera, which works just as well for confirming the workflow.
Day 4–5: A Trial Afternoon, Register Still Running
Before you switch anything off, you run one afternoon with real visitors while the paper register is still in use alongside it. This is the point to actually check the things that matter on a plant floor rather than in a demo: does an overstay alert fire when a visitor who should have left two hours ago hasn't scanned out, does the out-gate scan work cleanly when a guard is dealing with three trucks and a visitor at once, and does the on-site list — the thing you'd hand a fire marshal — actually match who's inside. If something's wrong with a pass size or an approval rule, this is when you fix it, not after go-live.
Day 5–7: Switch Off, and What Doesn't Carry Over
The register switches off, contractors already on site get entered with their actual validity dates rather than a fresh clock, and whoever approves material moving out through the gate is named formally in the system rather than left to whoever happens to be at the desk. Hosts get shown what the WhatsApp notification actually looks like on their phone, so the first live visitor isn't also the first surprise.
One thing worth saying plainly: VizPass does not import your old paper register. The digital register starts on go-live day, and the old book is archived for whatever retention period your policy requires — it isn't something we can retroactively populate, and any tool that claims otherwise is describing a manual data-entry job, not a migration. For a plant that's been running the same book for years, this is usually a relief rather than a loss.
What We Need From You Before Day 1
The whole week runs faster if this is ready before the call starts:
- A list of hosts — name, email, mobile — for everyone who'll receive visitor notifications
- Your sites and gates, especially if you're a multi-site group
- Who approves material going out through the gate
- Your logo, for the printed or digital pass
- One person who owns the gate — not a committee, one name
That last point matters more than the others. A gate rollout that reports to three departments moves slower than one where a single plant head or maintenance manager owns the decision.
Getting You There
If you're in Delhi NCR, go-live support happens on site, in person, gate tablet in hand. Outside that radius, it's a video call with the gate live on camera — which, for a straightforward Android tablet setup, works about as well as being there. You can see the full module list on /features, check which plan fits your gate volume on /pricing, or look at how plants in your specific line of work have set this up on /industries. If you'd rather talk it through first, /contact books a walkthrough — including, if you're within reach, one at your own gate.
Go Live in a Week: How a VizPass Implementation Runs FAQs
Does the host need to install an app to get notified when a visitor arrives?
No — the notification goes out as a WhatsApp message or SMS to the host's registered mobile number, so there is nothing to download or log into. This works because during setup you add each host with a name, email and mobile number, and that mobile number becomes the address the system messages the moment a guard checks a visitor in at the gate tablet. Because it rides on WhatsApp or plain SMS rather than a dedicated app, it reaches whatever phone the host is actually carrying, including older handsets, and doesn't depend on the host having signed up for anything themselves. This also means a host who is on the shop floor or in a meeting room gets the same alert as one sitting at a desk, without security having to physically track them down or make a phone call to check. The structural setup — sites, gates and hosts — is done once during the first couple of days of implementation and doesn't need redoing unless a host changes their number or a new host joins. It's a small piece of configuration, but it's the piece that actually replaces the guard's phone call to the front desk.
Can a safety officer pull a list of everyone currently inside the plant during an emergency?
Yes — because every visitor and contractor is checked in through the gate tablet against a specific site and gate, the workspace holds a live record of who has entered and not yet exited at any given moment. That record is what a safety officer would use during a fire drill, gas leak, or any incident where DGFASLI-aligned safety practice requires knowing who is on site, since it removes the guesswork of relying on a paper register that may be incomplete or illegible. The mechanism is straightforward: each gate feeds its check-in and check-out entries into the same workspace, and because multi-site groups sit under one account, a plant with several gates shows a combined picture rather than separate paper books per entrance. This is one of the reasons the setup work on sites and gates in the first couple of days matters — every gate needs to be represented in the system for the "who's inside right now" picture to be complete. You can see how this fits alongside other plant-specific needs on the industries page.
Are contractor and vendor entries handled differently from regular visitor passes?
Yes — contractors, vendors and regular visitors can be set up as separate categories within the same workspace, because the modules included in your plan determine which entry types are available at each gate. A contractor crew checking in daily doesn't need the same host-notification flow as a one-time visitor waiting for someone to receive a WhatsApp alert; instead, the gate tablet can be configured to log contractor entries against a site or project rather than against an individual host. This distinction is set up during the same Day 1–2 structural work where you define sites, gates and access rules, so it doesn't require a separate system or a second tablet at the gate. Because everything sits in one workspace, a security head can still see contractor and visitor entries side by side when reviewing gate activity, even though the two flows behave differently at the point of check-in. Specific configurations for contractor-heavy sites, factories and warehouses are described on the use-cases page, which is worth checking against your own gate before you finalize the module selection for your plan.
How many gates or sites can we run under one VizPass plan?
That depends on which of the three plans you pick, since sites and gates are added under a single account regardless of plan, but the modules available at each gate — and how many you can run — are tied to the ₹4,999, ₹9,999 or ₹14,999 monthly tiers. A single-site office and a multi-site group with a plant in one city and a warehouse in another both sit under the same account structure; the difference is which modules are switched on and how much gate activity the plan supports. Because there's no server or per-gate hardware to install, adding another gate is a configuration step, not a procurement one — you're adding a tablet and pointing it at the workspace, not standing up new infrastructure. This is also why the 7-day free trial is useful before committing: it lets you test the actual number of gates and sites you plan to run, rather than guessing from a spec sheet. Full details on what each tier includes are on the pricing page, and if you're not sure which tier covers a multi-site rollout, a walkthrough is the faster way to check than working it out from the plan names alone.
Is visitor and employee data collected at the gate stored in compliance with Indian data protection rules?
The workspace is built around the kind of personal data — names, phone numbers, host details — that Indian data protection guidance under MeitY expects organizations to handle deliberately rather than leave in an open paper register at the gate. Because everything runs inside a single company workspace rather than being written on paper that anyone walking past can read, access to visitor and host records is controlled by who is set up as an admin, HR or security user during the Day 1–2 setup, rather than being visible to whoever is standing at the gate. There's no local server or PC install involved, so the data isn't sitting on a machine at the site itself; it lives in the workspace tied to the verified work email and WhatsApp number used to sign up. This is a meaningfully different starting point than a paper register, which has no access control at all and no way to know who has looked at it. If your compliance team wants specifics on how this maps to your organization's own data handling policy, that's a good question to bring to a walkthrough rather than assume from the software alone.
How much training do security guards need before they can run the gate tablet on their own?
Not much, because the gate tablet interface is built to replace a paper register with the same basic action — recording who's coming in — rather than asking guards to learn a new system of screens and settings. The structural setup (sites, gates, hosts, module selection) is done by an admin during the first couple of days, so by the time a guard is handed the tablet, the choices they need to make at the gate are limited to entering or scanning visitor details and selecting the host or category, not configuring anything. Because it runs on an Android tablet rather than requiring installed software, there's also no local IT dependency at the site — no PC to image, no server to maintain, so the same tablet a guard used yesterday keeps working today without needing an IT visit. If you're rolling this out across a plant with several gates or a multi-site group, it's worth confirming gate-level workflow with a walkthrough before go-live day, since that's the fastest way to see the actual screens a guard will use rather than describing them secondhand.
Where the Week Actually Slips
The five-to-seven-day timeline holds when someone owns the gate end to end. It stretches when that ownership is fuzzy. The three places we see plants lose a day or two:
- The host list arrives late or incomplete. If HR or admin sends names without mobile numbers, the WhatsApp notification — the entire point of the system for a host — doesn't work until someone chases the missing numbers down.
- No one is named to approve material out. Gate staff default to calling a supervisor anyway, which is exactly the delay you were trying to remove.
- The trial afternoon gets skipped. Running real visitors alongside the paper register for even one shift is what surfaces a gate with patchy Wi-Fi or a guard who needs a second walkthrough — better to find that on day 4 than on the day you switch the book off for good.
None of these need a project manager. They need one person at your end — the "gate owner" mentioned earlier — who has the host list, the site list, and the logo file ready before day 1.
Contract Labour, Shift Changes and Power Cuts
A plant floor is not an office lobby, and the rollout should account for that honestly. Contractor crews rotate weekly or even daily on many sites, so passes for them carry validity dates rather than being issued once and forgotten — a contractor whose work order ends Friday shouldn't still be walking in Monday. Guards change shift, often across three languages on the same floor, which is why the guard-facing screen is deliberately narrow: the Security Guard role shows only the gate, not the full admin console, so a new guard can be walked through it in about half an hour regardless of which language they're most comfortable in. And because the tablet runs on Wi-Fi or 4G rather than a wired server connection, a power cut that takes down the plant LAN doesn't necessarily take down the gate — worth confirming with your own network during the trial rather than assuming it.
What to Check Before You Call It Done
Once the paper register is switched off, the things worth watching for the first couple of weeks aren't dashboards — they're basic operational checks:
- Are overstay alerts actually reaching the right person, or disappearing into an inbox no one checks?
- Does the on-site list match who a walk-through headcount finds at the gate?
- Are hosts getting the WhatsApp message, and do they recognise it as an action item rather than spam?
If any of these are off, it's almost always a role or notification setting from day 2, not a system limitation.
Where This Doesn't Fit
Two honest limits worth stating up front rather than discovering later. VizPass does not import your old paper register — the digital record starts on go-live day, and the old book stays archived for its own retention period rather than being merged in. And this is gate and visitor management, not a broader safety or compliance system — for statutory factory safety obligations, DGFASLI remains the reference, and for how personal visitor data should be handled, MeitY is the authority, not us. Where VizPass fits your specific site type is easier to check against industries or use-cases than to guess — or book a walkthrough and bring your actual gate to the call.