Visitor and Vendor Management for Commercial Buildings and Hotels
VizPass brings commercial building visitor management together with hotel back-of-house vendor control, tying each visitor's host approval to the correct tenant company via WhatsApp while security runs a single, searchable check-in register at the gate. Photo and ID capture, QR passes, contractor validity checks, and material-out approvals give every tenant and hotel department a verifiable record of who entered and why.
A commercial building lobby sees more strangers in a day than most factories — except here nobody owns the problem. The building's security desk isn't sure which of the fifteen tenant companies a visitor is calling on, tenants don't know who signed their guest in, and a hotel's service gate has vendors, banquet decorators and delivery trucks moving all day with no record anyone can pull up when something goes missing. The result is a logbook nobody trusts and a "who let this person in" conversation nobody can answer with facts.
One lobby, many tenants — one register
In a multi-tenant building, the building's own security staff runs check-in, but the person being visited works for a company that isn't the building owner. That mismatch is where most gate registers fall apart — the guard writes down a name and a floor number, and three months later nobody can say which tenant's staff actually approved that visit.
VizPass fixes this by keeping the host tied to the tenant company, not just to the building. When a visitor arrives, security captures a photo and reads an ID at the gate, picks the tenant company and host from the list, and sends the approval request straight to that host's WhatsApp. The host — sitting in a tenant office on the eighth floor — approves or declines from their phone, and only then does the gate print a pass. Every entry in the register carries the tenant name against it, so if a tenant's compliance team ever asks "who visited us in March," the answer is a search, not a memory exercise.
- Security runs the check-in desk; approval sits with the tenant's own staff, not the building
- The register is searchable and exportable by tenant, by date, by host — useful when a tenant asks for its own visitor history separately from the building's
- Passes print in six sizes, so a building running a single-lane lobby and one running a wider commercial entrance can both use a format that fits their printer and their pace of footfall
The gate itself: photo, approval, pass, exit
The mechanics are the same whether it's a 200-tenant commercial tower or a boutique building with six floors. A visitor's photo and ID are captured at the point of entry. The system pushes a WhatsApp approval to the host before anyone is waved through. Once approved, a QR-coded pass prints, and the visitor carries that pass until they leave — at which point scanning it at the out-gate closes the record. If a pass is scanned out at the wrong gate, or a visitor exits without being scanned, that gap shows up in the register rather than disappearing quietly.
This matters more in commercial buildings than it sounds, because these lobbies rarely have a single entry point — deliveries come through a side gate, tenant staff use a different lift bank, and a visitor who entered through the front desk might leave through a loading bay. VizPass doesn't manage lifts, turnstiles or barriers themselves — those stay under the building's existing systems — but it gives you a clean, closed record of every pass issued and every pass returned, regardless of which physical gate it moved through, as long as that gate has a scan point.
Contractors, AMC vendors and material leaving the building
A commercial building runs on AMC contracts — HVAC servicing, fire system checks, pantry maintenance, lift AMC, housekeeping contract staff — each with their own validity window and, often, their own induction requirement before they're allowed past the lobby. VizPass checks a contractor's validity and induction expiry at the gate itself, so a contractor whose AMC ran out last month, or whose safety induction has lapsed, gets flagged before they're on the floor, not after.
Material movement is the other half of this. Furniture going out for repair, e-waste being cleared, IT equipment being replaced — none of it should leave without someone signing off first. VizPass requires an approval before the gate releases a material pass, and the register keeps a record of what left, when, and who approved it. For a building housing dozens of tenants who each have their own asset movement, this is the difference between a security desk that can answer "what went out on Tuesday" and one that can't.
- Contractor and AMC vendor validity and induction expiry are checked at entry, not assumed
- Material out — equipment, furniture, e-waste — needs approval before the gate lets it go
- Vehicle numbers are logged for delivery and service vehicles using the same gate
- A courier log keeps parcel and courier traffic separate from visitor traffic, so the register isn't cluttered with deliveries when you're searching for a person
Hotels: what happens behind the service gate
This is worth being precise about, because a hotel's front-of-house and back-of-house are entirely different problems. VizPass has nothing to do with your guests — it doesn't replace your property-management system, it doesn't touch guest check-in, key cards or CCTV, and it isn't meant to. What it manages is everyone who comes through the service gate who isn't a guest: banquet decorators setting up for a wedding, event crews running lights and sound for a conference, AMC vendors servicing kitchen equipment, contractors doing repair work, and delivery vehicles bringing in supplies.
Each of these carries a validity period, the same way a commercial building's contractors do, and where the property requires an escort — through a kitchen, a back corridor, near a guest floor — that's noted against the entry. A decorator's crew for a Saturday banquet doesn't need standing access for the following month, and the validity window makes sure they don't get it by default. The service-gate register works the same as any other VizPass register: searchable, exportable, and closed out properly when a vehicle or crew member leaves.
- Vendors, contractors, event crews and decorators are logged with a validity period, not open-ended access
- Escort requirements are recorded where the property needs them
- Delivery vehicles through the service gate are logged by vehicle number
- Guest-facing systems — PMS, check-in, key cards, CCTV — stay exactly as they are; this only covers who else is on the property
Roll call and watchlist, without guesswork
Both a commercial tower and a hotel back-of-house have the same evacuation problem: at the moment an alarm goes off, security needs to know who's on site who isn't staff — which contractors, which vendors, which decorators — and that list has to come from the gate register, live, not from someone's memory of who they waved in that morning. VizPass generates that roll call from the same list the gate has been building all day, and a watchlist flags anyone who shouldn't be issued a pass at all, before they get anywhere near the lobby.
The register, and what it doesn't pretend to be
Every pass carries a visitor privacy notice, and consent is recorded against it — worth having in place given how personal data handling is increasingly scrutinised; the Ministry of Electronics & IT publishes guidance worth being familiar with if you're the one deciding what a gate register collects and how long it's kept. When an entry needs correcting — a wrong tenant selected, a mistaken approval — VizPass reverses it with a reason rather than deleting it, so the register stays an honest record of what actually happened at the gate, corrections included.
What VizPass will not do is control your lifts, turnstiles or barriers, and for a hotel, it will not touch anything guest-facing. It's built for the register, the approval, and the pass — the part of gate management that a spreadsheet or a paper book handles badly once a building has more than a handful of tenants or a hotel has more than one event running at a time. If you want to see how it maps onto a lobby or service gate the size of yours, the features list covers the full set, pricing is straightforward per gate, and a walkthrough is the fastest way to see the WhatsApp approval and pass printing on an actual phone rather than in a description. Other property types we work with are on the industries page, alongside the use-cases that go into specific scenarios like contractor induction or material gate-pass approval in more depth.
Visitor and Vendor Management for Commercial Buildings and Hotels FAQs
How does VizPass handle vendor and delivery entries at a hotel's service gate, separate from guest check-in?
Vendors and delivery staff at a hotel's service gate go through the same check-in mechanics as guests — photo capture and ID scan — but the approval routes to the department they're calling on, such as housekeeping, banquets, or F&B, instead of a guest host. Security picks the department and the specific staff member from a list at the gate, and that person approves the entry from their phone, the same way a tenant host approves a building visitor. This keeps a banquet decorator setting up for an event, a laundry contractor's van, and a food delivery rider on a distinct log from hotel guests staying in rooms, so if a security head needs to check who came in through the back gate on a given day, they're not sifting through guest arrival records to find it. Because every entry still carries a photo, an ID reference, and the approving department against it, departments can look back at their own vendor traffic without needing security to pull the full register. The same setup extends across industries beyond hotels, including factories that route contractor entries to a specific supervisor rather than a general security log.
Can each tenant in a shared commercial building see only their own visitor records, not other tenants' data?
Yes — access to visitor records in VizPass follows the tenant a visitor is checked in against, so a tenant's own team only sees entries logged under their company name, not the full building register. This works because the tenant field is captured at the point of check-in, alongside the host who receives the approval request, and that tenant tag stays attached to the entry permanently. When a tenant's HR or admin team reviews their visitor history, the system filters to records where their company was selected as the host organisation, so a visitor who came to see a different tenant on another floor won't show up in their pull. This matters in a multi-tenant lobby because several companies sharing one entrance otherwise means everyone's guest traffic sits in one undifferentiated logbook. The tenant separation is set at the point of data entry rather than applied afterward, so there's no manual filtering step for security staff to get wrong. Building management retains its own full view across all tenants for lobby oversight, while each tenant's access stays scoped to their own name. Details on how access permissions are structured are covered under features.
How do I blacklist a visitor so no tenant in the building can approve their entry again?
A visitor can be flagged at the point of ID and photo capture, and that flag stays attached to their record so it surfaces the next time the same ID or photo is presented at any gate in the building, regardless of which tenant they claim to be visiting. Because check-in always starts with reading an ID and taking a photo before a tenant and host are selected, the match happens before the approval request is even sent, so security sees the flag before a pass can be printed. This differs from a paper logbook, where a note written against one tenant's page doesn't help the guard handling a different floor's entry weeks later — the flag here is tied to the person, not to a single tenant's records. A building's security head can raise a flag based on an incident reported by any tenant, and it applies building-wide from that point on. Tenants aren't required to coordinate with each other for this to work; the flag sits at the building-level register that security manages. If a walkthrough would help show how this is configured for a specific site, it can be arranged through contact.
Can a host pre-register an expected visitor or vendor before they arrive at the gate?
Yes, a host can add an expected visitor or vendor to the system ahead of time, so the tenant, host, and purpose of visit are already on record before the person reaches the gate. This works through the same fields used at walk-in check-in — the host fills in the visitor's name and reason for visit in advance instead of security capturing it fresh at arrival. When the person shows up, security still takes a photo and reads their ID as usual, but the tenant and host are already matched from the pre-registered entry rather than being selected manually from a list. The approval step still goes to the host's phone, since pre-registration records intent to visit but doesn't skip the check-in or approval steps at the gate — it just means the details are already filled in when the visitor arrives. This is useful for scheduled vendor visits, like a contractor coming for planned maintenance, where the department already knows who's expected and can register them without waiting for the visitor to appear at the gate. More on how visitor pre-registration fits alongside walk-in check-in is covered on the features page.
Is the visitor and vendor ID data captured at the gate handled in line with India's data protection expectations?
Visitor and vendor data captured at the gate — a photo and an ID reference — is stored against the specific entry, tenant, and host, and access to it is limited to the security desk and the tenant or department that entry belongs to, rather than being open to every tenant sharing the building. This scoped access is the main control at the point of data handling: nobody outside the approving tenant or the building's security administration can pull a record just because they also operate out of the same lobby. For guidance on how personal data like ID details and photographs should be handled in India, the Ministry of Electronics & IT publishes rules and advisories that building administrators can refer to when setting their own data retention and access policies. VizPass doesn't set retention periods on a client's behalf — how long records are kept, and who beyond the security desk can access them, is a policy decision each building or company sets for itself. What the system does control is that access always follows the tenant/host structure captured at check-in, not the building as a whole.
Does the contractor entry log at a factory gate hold up for safety audits and compliance checks?
A factory's contractor and visitor log holds up for safety audits because each entry carries a photo, an ID reference, the host or supervisor who approved it, and a timestamp — the same core record an auditor would ask a paper register to produce, except it doesn't rely on legible handwriting or a logbook physically being on-site. Contractors are checked in the same way as any other visitor: ID scan, photo, and a supervisor selected from a list who approves entry from their phone rather than signing a paper register at the gate. For the specific safety record-keeping expectations that apply to factories in India, DGFASLI sets out requirements around visitor and contractor documentation that a factory's EHS team can check its own register against. VizPass doesn't certify compliance on a factory's behalf — it produces the entry-level record that a safety officer would need to demonstrate who was on-site and who approved them, which is the part a manual register often can't reliably provide once entries stretch back several months. Whether that record satisfies a specific audit depends on the factory's own documented safety procedures alongside it.
Rolling it out without freezing the lobby
A multi-tenant building can't afford a week where the front desk is confused and tenants are complaining about slow entry. The practical way in is to run the gate live for one or two tenant floors first — usually the ones with the most walk-in traffic — while the rest of the building still uses the paper register. Print the QR pass in a size that suits your counter (VizPass supports six), keep a laminated card at the desk showing security which tenant list to search first, and only switch every floor over once the host-approval flow on WhatsApp is something the guards do without thinking. Trying to onboard fifteen tenants on day one is the most common way these rollouts stall.
Mistakes that make tenants stop trusting the register
- Letting security guess the host's company instead of picking it from a list — this is how a visitor for Tenant A ends up logged against Tenant B
- Treating contractor and AMC vendor entries the same as one-time guests, so nobody notices a validity period has quietly lapsed
- Deleting or overwriting a wrong entry instead of using a reversal with a reason — the moment a register can be edited silently, it stops being evidence for anyone, including your own compliance team
- Skipping the privacy notice at the gate because "it's just a delivery boy" — consent should be recorded per pass, not selectively
What to actually track once it's live
Don't measure this by how many passes get printed — measure whether the register answers questions under pressure. After thirty days, check: can the front desk pull every visitor logged against a specific tenant for a given week in under a minute? Does the contractor list correctly flag whoever's induction or validity has expired before the gate releases them again? When you run a mock evacuation, does the live list actually match who's on the premises, including vendors and event crews who came in through the service gate? These three checks tell you more than a usage count ever will.
Where this does not reach
VizPass runs the gate and the register — it is not a replacement for a hotel's property-management system, guest check-in, key cards or CCTV, and it does not control lifts, turnstiles or barriers. A hotel's guests are never in this system; it's built for the back of house — vendors, contractors, banquet decorators, event crews and delivery vehicles moving through the service entrance. If your building already runs turnstiles or lift access control, VizPass sits alongside that hardware and keeps the paper trail; it doesn't replace the access decision those systems make. Knowing that boundary before you sign off on a rollout saves an awkward conversation with your IT or security integrator later.
Before you commit
Read through /features against your building's actual gate count and tenant list, look at /use-cases for how other campuses split check-in responsibility, and check /pricing against the number of gates you'll actually run this on — a single-lobby commercial building prices very differently from a hotel with a busy service entrance. If your visitor data handling needs to be reviewed against India's evolving personal-data rules, the Ministry of Electronics & IT is the primary reference point. A short call before rollout, booked through /contact, usually surfaces which floors or gates need special handling before you find out the hard way.