At 8:52 on a Monday there are eleven people in your lobby. Four are contractors who were told to ask for someone whose name they have spelled wrong. Three are candidates for an interview on nine. Two are couriers. One is a tenant who forgot their badge. One is a fire inspector, and nobody knows that yet.

The front desk handles all of it with a paper log, a phone and goodwill. That is the system in most multi-tenant buildings, and it holds up until the morning it does not. A tenant visitor management system is what replaces the goodwill with a record, without turning the lobby into an airport.

The front desk is doing three jobs at once

It is checking identity, granting access, and creating a record. Those jobs have different owners and different consequences.

Identity is the tenant's business. The host knows who they invited. Access is the building's business, because the building owns the turnstiles and the lifts. The record is everyone's business the day something goes wrong, and it is the one that gets written last, in the worst handwriting, on the page that later cannot be found.

Most lobby friction comes from asking one person at a desk to carry all three at the same time while a queue builds behind the courier.

What pre-registration changes

When a host registers a guest in advance, the building stops improvising. The name is spelled the way the host spelled it. The visit has a date, a window and a destination floor. The credential can be prepared before the guest arrives instead of negotiated at the desk.

It also changes who does the work. Pre-registration moves the data entry to the person who has the information, which is the tenant, and leaves the desk to do the thing only the desk can do: look at the human being in front of them.

Every minute the front desk spends typing a name into a log is a minute it is not spending looking at who just walked past the turnstile.

What good visitor management looks like

Hosts register their own guests. From the tenant portal, in under a minute, with a repeat option for the contractor who is here every Wednesday for the next two months.
The pass is digital and expires. A wallet credential or QR that works for the window of the visit and stops working after it, without anyone collecting a plastic card.
Approval exists where it is needed. Most visits need none. A rooftop, a data hall or an after-hours entry needs one, and the rule should live in the system instead of in a manager's head.
Vendors are checked against compliance. If a contractor's certificate of insurance has lapsed, the front desk should know that before the lift does, not after an incident.
Every entry is searchable. Name, host, company, floor, time in, time out. The record is the point. Pulling it up should be a simple export.

The evacuation question

There is one question that separates a visitor log from a visitor management system, and it gets asked on the worst day: who is in the building right now?

A paper log can answer who signed in. It cannot answer who signed in and has not left, across three entrances, in the four minutes you have while the alarm is sounding. A live record can, and it can do it on a phone in the assembly area.

Fire wardens and life-safety teams already run this drill. Most of them run it on a clipboard that is out of date the moment the last person walks through the door.

Where visitor management meets access control

Visitor management that does not talk to the door is a very organised waiting room. The value arrives when the registration and the credential are the same event: the host invites, the system issues, the turnstile accepts, the record closes itself when the guest leaves.

This is also where buildings should be careful about rip-and-replace. Most multi-tenant buildings already own an access control system that works, and the tenants already have credentials in it. The right integration adds a visitor layer on top of what is installed. It does not ask a building to re-badge two thousand people to fix a lobby problem.

The tenant experience nobody credits

Ask a tenant what they think of the building and they will tell you about the lift, the temperature, and how their guests were treated. That third one is unmeasured in almost every building and remembered in all of them.

A candidate who was greeted by name at 8:55 tells the hiring manager. A client who stood in a queue for eleven minutes tells the tenant's CEO. Neither of those conversations appears in an operating report, and both of them show up at renewal in a tone you can feel.

What to fix first

If you are starting from paper, the sequence that gets results fastest is unglamorous. Put pre-registration in the tenants' hands. Give the desk a live list for the day. Connect the credential so the turnstile stops being a manual override. Then, and only then, worry about kiosks and badge printers, which solve the part of the problem that was never really the problem.

Contractors are not guests

A visitor comes to see someone and leaves. A contractor comes to work on the building, often out of hours, sometimes with tools that can set off an alarm, and always with an insurance obligation attached.

Treating both as one category is how buildings end up with an uninsured technician on a roof at 7pm with nobody aware they are there. The distinctions worth building into the process are unglamorous and short: is the certificate current, does this trade need an escort, is the work order they are here for open, and does the access they receive expire when the job ends instead of when someone remembers.

None of that needs to slow anyone down at the desk. It needs to be decided before they arrive.

What to measure once you have a system

Before any of that, one habit is worth building: read the previous day's arrivals once a week. Not as an audit, as a sanity check. Patterns show up fast when a person looks at them, and the ones that matter are rarely the ones a report would flag. A vendor appearing daily on a job that was supposed to take an afternoon, an interview candidate logged at a floor with no vacancy, twelve deliveries to a tenant who has complained about the loading dock twice.

Three numbers tell you whether the change took.

The share of visits that were pre-registered, which is the adoption number. Time from arrival to access, which is the tenant experience number. And the share of vendor entries where compliance was verified, which is the number your insurer would ask about if they thought to ask.

None of the three needs a dashboard project. They come out of the visit records if the visit records exist, which is the entire argument for having them.

Where BuildingHub fits

Security Hub handles guest pre-registration from the tenant side, issues the pass to Apple Wallet for the window of the visit, and logs every entry against the host and their company. It works with the access control already in the building through integrations with Genea, LenelS2 and HID instead of replacing them, and vendor visits can be checked against the certificate tracking in Operations Hub before anyone reaches a lift.

The front desk problem: what a tenant visitor management system has to solve