Visitor management sounds like an administrative nicety right up until there is an evacuation. Then it becomes the most important list in the building, and the paper book at reception turns out to have three illegible names, four people who signed in and never signed out, and no record of who they came to see. Nexora Visitors replaces that book. A host pre registers the visitor, the visitor gets an emailed invitation with a QR code attached, and the gate checks them in and out against a real record. Visits are tied to a branch, so a company with several sites sees the right gate and the right list, and anyone who has not checked out gets chased automatically.
Reception has a book. People sign it with varying degrees of legibility. Nobody signs out, because signing out means walking back to the desk and there is a taxi waiting. The company photocopies identity documents and keeps them in a drawer, which is its own quiet problem in every jurisdiction that has a privacy law.
The host does not know their visitor has arrived until reception calls, and reception does not know the visitor is expected until they turn up. Everybody is doing something manual to fill in for the fact that the two halves were never connected.
Then there is the count. In a drill, or worse, in a real evacuation, the marshal needs to know how many non employees are on site. The book says forty seven people signed in today. It does not say how many are still here, because sign out is fiction. So the answer becomes a guess, and the guess is the thing the whole assembly point procedure depends on.
A visit starts with the person expecting it. They enter the visitor’s name, company, purpose and expected time. That single change removes most of the friction in visitor management, because the information now comes from the person who actually has it, rather than being reconstructed at a desk by someone who has never heard of the meeting. The visitor receives an invitation by email with a QR code attached, generated by the system. They arrive knowing where to go and with something to present. Reception is no longer the place where the whole process is invented from scratch at the moment of arrival.
At the gate the visitor is checked in against their record and checked out when they leave. Both movements are recorded against the branch. Check out is the half everyone skips and the half that matters. It is what converts a list of people who arrived into a list of people who are here, and those are entirely different pieces of information. One is an administrative record. The other is the thing a fire marshal is holding at the assembly point.
The system runs overstay reminders on its own. A visitor still showing as on site well past their expected departure triggers a reminder, so somebody looks into it. Most of the time the answer is dull. They left through a different gate, or their meeting overran, or somebody forgot to check them out. Dull is fine. The value is that the discrepancy surfaces the same day, while it can still be resolved, rather than being discovered during a drill when the numbers refuse to add up.
The visitor’s photograph and identity documents are held on the visit record. That is better than a photocopy in a drawer in every way that matters: it is attached to the visit it belongs to, it is searchable, it is subject to the same access control as everything else in the system, and it does not sit in a filing cabinet in a corridor for six years because nobody knew whose job it was to shred it.
