Multi-Gate Visitor Management for Indian Factories

Most Indian plants don't have one gate. They have a main gate for staff and visitors, a separate gate for trucks and material, sometimes a third for contractors bussed in for a shift, and occasionally a back gate that everyone swears is locked but somehow has a guard chair next to it. Each gate has its own guard, its own register, and its own idea of who is "inside." The problem isn't that any single gate is dishonest. The problem is that three honest registers, kept separately, add up to one dishonest picture of the plant.

This matters more than it sounds. If a fire drill or an actual emergency requires a headcount, the answer has to come from somewhere real — not from three guards flipping through three notebooks while someone waits at the assembly point. If an auditor under the Factories Act 1948 or the state Factories Rules asks who was on the premises on a given shift, "we'll check with the other gate" is not an answer that holds up. And if a contractor's supervisor claims his labourer left at 6 PM but the labourer was actually still inside two hours later, the gate that can prove it is the one that matters — provided the two gates agree with each other.

This article is about what it actually takes to keep a multi-gate site honest: one on-site list, one number for who's in, and records that reconcile across every entry and exit point instead of contradicting each other.

The problem with parallel registers

A paper register, or even a digital one that isn't shared, is only honest about the gate it sits at. It has no way of knowing what happened at the other end of the plant.

Where the mismatch shows up

A visitor enters through the main gate, walks to a workshop near the material gate, and leaves from there. The main gate register shows him "in" forever.
A contractor's shift ends at the labour gate, but his exit is logged an hour late because the guard was busy with a truck queue, so the on-site count is wrong for that hour.
A vehicle enters loaded, exits empty from a different gate for a return trip, and nobody reconciles the two movements against each other.

None of these are dramatic failures. They're small, ordinary gaps that build up over a week until nobody — not security, not HR, not the plant head — can say with confidence who is actually on site right now. That's a question worth taking seriously on its own; we've written about it in Real-Time Gate Management: The Question Your Gate Must Answer.

What "one plant, one truth" requires

Keeping a multi-gate site honest doesn't mean forcing everyone through a single gate — that's rarely practical for a factory with separate material and staff flows. It means every gate writes to the same record, and every record has one open-close lifecycle regardless of which gate touches it.

The minimum conditions

A single searchable register that every gate feeds into, not a notebook per gate that gets reconciled at month-end.
An on-site list that is derived automatically from open records — anyone whose exit hasn't been logged is still counted "in," no matter which gate they entered from.
The ability to close a record from any authorised gate, since a person entering from Gate 1 might reasonably exit from Gate 2 during a shift change or a material handover.

This is the core idea behind a proper gate pass management software setup: it isn't about the gate, it's about the record. With VizPass, a tablet at each gate captures the visitor's photo and reads the ID document automatically, the host approves on WhatsApp, and a pass prints with a QR code. Scanning that QR at whichever gate the person exits from closes the record — so the system doesn't care which physical gate did the closing, only that it happened.

Material and vehicle gates: a different kind of honesty

Material gates carry a different risk than people gates. The question isn't just "is this person inside," it's "did what left match what came in."

What a material gate register needs to show

Items and quantity, whether the movement is inward or outward.
Whether the material is returnable — a tool sent out for repair is a very different record than a scrap sale.
The vehicle number tied to that specific movement, and approval before anything goes outward.

A returnable delivery that comes back three weeks later needs to be tied to the original outward entry, not logged as a fresh, unrelated inward movement — otherwise the register looks fine but tells you nothing about whether your own asset actually came back. This is exactly the gap covered under material gate pass tracking, and it's worth pairing with a proper vehicle gate pass system so a truck's entry and exit are both accounted for, even if it uses a different gate each time. It's worth being clear here that this only extends to logging vehicle numbers as part of a pass record — VizPass doesn't read number plates automatically, open barriers, or weigh vehicles; those remain manual or separately equipped processes.

Contractors and staff crossing gates mid-shift

Contract labour rarely enters and exits through one fixed point in practice. A crew might come in through the labour gate in the morning, but a supervisor might walk a few of them out through the main gate for a site visit or a material pickup. If the register only trusts the gate it was written at, that crew becomes untraceable the moment they cross.

Where this bites

Under the Contract Labour (Regulation and Abolition) Act 1970, a principal employer is expected to know who is on their premises and under what engagement — a register split across three untalking gates makes that harder to demonstrate, not easier.
Induction and validity expiry for contractors needs to be checked at whichever gate they present themselves at, not just the one they were first registered at.
A staff out-pass approved by a manager needs to be honoured — and stamped out and in — regardless of which gate the employee eventually returns through.

A gate register that keeps contractor validity and induction expiry checks live at every gate, not just the point of first entry, closes this gap. We've covered the broader accountability question in Contractor Access Control Gate Management: Who Vouches?, and the day-to-day mechanics are in contractor and labour entry.

Couriers, small movements, and the ones nobody tracks

Couriers and delivery riders are the traffic that everyone waves through and nobody logs properly — until a package goes missing or a rider is found wandering near a restricted area an hour after his delivery was supposedly made. A courier entry at one gate, unlogged and unclosed, is exactly the kind of small gap that erodes trust in the whole register, because it suggests other small things are being waved through too. Logging couriers with the same discipline as any other visitor — in, purpose, out — keeps the register consistent rather than selectively rigorous.

When a gate makes a mistake

Guards work under pressure — shift changes, truck queues, a line of contractors waiting in the heat — and mistakes happen: a wrong entry, a duplicate record, a person logged at the wrong gate entirely. The instinct is to delete and move on. That instinct is the enemy of an honest register.

Why correction beats deletion

A deleted entry leaves no trace that anything happened, which is indistinguishable from covering something up if it's ever questioned later.
A reversed entry, with a reason attached, shows exactly what went wrong and when it was caught — which is what actually holds up under an audit or an internal review.
Consistency across gates depends on every correction being visible, not silently erased.

This is why a mistaken entry should be reversed with a reason recorded, never deleted outright — the register stays complete even when a guard gets something wrong in the moment.

Roles: who sees what, at which gate

An honest multi-gate register also depends on the right people seeing the right slice of it. A guard at the material gate doesn't need visibility into every visitor pass issued at the main gate that day, and giving him that visibility creates more risk than it solves. A Security Guard role should see only the gate they're posted at — enough to do their job, not enough to become a liability if their tablet or device is compromised. Broader visibility — the full register, searchable and exportable — belongs with admins and security heads who need it for audits, DGFASLI-related safety reviews, or a plant head's monthly review, not with every gate individually. This kind of role separation, and how it fits into a wider access setup, is covered in how it works and in the full list of features.

It's also worth noting that any system handling photos and ID documents at the gate sits within the broader expectations set by the Ministry of Electronics & IT around personal data handling — worth keeping in mind when deciding who can export what, and for how long.

Conclusion

A plant with two gates doesn't need two registers — it needs one register that both gates are honest to. That means a shared on-site list built from open records, material and vehicle movements tied together across entry and exit points, contractor validity checked wherever they present themselves, and corrections made visibly instead of quietly erased. Get the underlying record right, and it stops mattering how many physical gates a site has.

If your plant runs more than one gate and you're not fully confident the two registers would agree with each other right now, it's worth seeing how this works in practice. VizPass runs on a tablet at each gate, feeds one shared register, and is priced at ₹4,999/month with a 7-day trial — you can see it applied across different industries and use-cases, or book a walkthrough at our Sector 62, Noida office to check it against your own site's gates before deciding anything.

Frequently Asked Questions

How do we get one accurate headcount when the main gate, truck gate and contractor gate all keep separate records?

You get one headcount by having every gate write to the same shared register instead of its own notebook or standalone device. Each gate — main, truck yard, contractor entry, back gate — runs on the same account, so when a guard checks someone in or out, that entry appears immediately in the central log rather than staying trapped at that one post. There's no end-of-day exercise of collecting four registers and adding them up; the system already holds one running list of who is inside, built from every gate at once. This is the core mechanic behind multi-gate visitor and contractor tracking: the gates don't need to talk to each other directly, because they're all writing to and reading from the same source. If someone enters through the contractor gate and is still on-site, that status shows up the same way whether you check from the main gate's tablet or from an office screen. The register stays one register with many entry points, not many registers that someone has to reconcile by hand later, which is what makes a single, trustworthy headcount possible during a drill, an audit, or an ordinary shift handover.

If a contractor enters through the labour gate but leaves through the main gate, does the exit still get logged correctly?

Yes, because the exit is tied to the person's record, not to the gate they happen to walk through. Each visitor or contractor is checked in once, against one record — typically via ID, photo, or a QR/pass generated at entry — and that same record is what any gate looks up at exit, regardless of which gate that is. So a labourer who enters through the contractor gate and exits through the main gate closes out the same record rather than creating a fresh, unmatched one. This is what stops "entry at Gate A, no matching exit anywhere" situations, which is exactly the kind of gap that makes a supervisor's claim about someone leaving at a given time unverifiable. It's also why gate-crossing movement, common on sites where contractors get escorted out through whichever gate is nearest, doesn't break the record the way it would with separate paper books at each post. This mechanic is described in more detail under use cases for multi-gate sites, since it's less about the software having extra features and more about how entries and exits are matched to one identity rather than one location.

What happens to the contractor gate's records if its internet or power goes down mid-shift?

The gate keeps logging entries and exits locally, and those records sync to the central register once connectivity is back, so nothing is lost in the gap. A guard at that post can continue checking people in and out during the outage; the system holds those entries on the device and pushes them through as soon as the connection returns, rather than requiring the guard to fall back to a paper notebook that then has to be typed up separately later. This matters specifically for gates that are physically remote from the main building — truck yards, back gates, temporary contractor entries — where network drops are more likely than at a reception desk. Once synced, those entries reconcile into the same single list as every other gate's activity, timestamped as they actually happened rather than backdated when someone remembers to update a register. If you want to see how this offline handling fits with the rest of the gate setup, it's covered under features for gate and access management. The point isn't that outages never happen — it's that an outage at one gate doesn't mean that gate's data quietly disappears from the plant's overall picture.

Can a security head monitor all the gates from one screen instead of calling each guard post for status?

Yes, a security head can view live entry and exit activity from every gate on one dashboard, because all gates feed the same central register rather than keeping status only at the guard post. Instead of phoning the truck gate, then the contractor gate, then the main gate to piece together who's currently inside, the dashboard shows checked-in status pulled from whichever gate last recorded that person's movement. This is useful less for day-to-day convenience and more for the moments when it actually matters — an emergency assembly point headcount, an unexpected auditor visit, or simply confirming a contractor supervisor's claim about when someone left. Access to this view is role-based, so a security head or admin can see the full picture across gates while individual guards still only manage their own post's check-ins. This central visibility is part of what's listed under VizPass features, and it's worth seeing in a live setup rather than reading about it — a walkthrough will show how the same dashboard looks across a site with more than one entry point, whether that's a factory, warehouse, or campus.

How do we produce a shift-wise on-site list if a Factories Act inspector asks who was present?

You pull it directly from the consolidated register, filtered by date and shift, rather than assembling it from separate gate notebooks after the fact. Because every gate's entries and exits write to the same log, a shift-wise list isn't a separate report someone builds manually — it's the same underlying data, filtered to the time window the inspector is asking about. This is the difference between saying "we'll check with the other gate" and being able to show a single list, drawn from all entry points, of who was recorded on the premises during that shift. It doesn't change what the Factories Act 1948 or state Factories Rules require of a site — those obligations exist independently — but it changes whether the answer is retrievable on demand or has to be reconstructed from memory and paper. For sites tracking safety and compliance obligations more broadly, the DGFASLI site is a reference point for what factory inspections typically look for. The register's job here is narrower and more mechanical: keep entries and exits from every gate in one place, time-stamped, so a shift-wise pull is a filter, not a reconstruction.

Tags: visitor management gate pass software factory security material gate pass vehicle gate pass contractor management Factories Act compliance

← Back to blog

Two gates, one plant: how a multi-gate register stays honest