Visitor systems
What is a visitor management system?
Reviewed by Daniel Cluderay, director of ONDRAFT LTD · Published 2026-09-06
A visitor management system is the record of who is allowed in. Most products are a kiosk. The part people wear is still a sticker. We treat the system as the thing that compiles an e-ink face before the guest exists in the lobby — hire the hardware for a day, or keep it.
The record versus the object
Classic visitor management is a log: name, host, time in, time out. Paper sheets leak previous names to the next person in the queue. Thermal printers add a sticker that peels onto a coat. Digital kiosks move the log to a tablet and still often print the same sticker.
The object on the chest is what colleagues actually use. If that object is still paper, the software did half a job. We compile a 250×122 three-ink face so the record and the object agree before doors open — at least for the people you knew to invite.
Enterprise platforms wrap the log in NDA vaults, SSO, muster lists, and desk booking. Those are real products for facilities teams. They are not required to hand a named bezel to a guest on a Tuesday chapter morning.
How search stole the phrase
Type the phrase into a search engine and you will land on kiosk vendors, GDPR explainers, and workplace platforms that also sell desks. The head term no longer means “a list of guests.” It means a software category with a demo button. That capture is why a hardware company has to define the term before the kiosk copy defines it for us.
A system, in the original sense, is inputs, a process, and an output. Inputs: names, hosts, times, role. Process: consent, notify, identify. Output: a log and something on the chest. We insist the output on the chest is e-ink. If your system’s output is still a sticker, you bought a log with a printer tax.
Compliance teams hear “visitor management” and reach for retention policies and document signing. Those are adjacent systems. They can sit beside us. They should not swallow the badge. A signed NDA in a PDF and a named bezel can coexist without a single vendor owning both.
Event organisers hear the same phrase and think registration desks. Our visitor-days landing is the event flavour. This answer is the category flavour. The visitors hub is where those two stories share a compiler. Use the hub if you are still choosing office versus conference.
What we count as in-scope software
People. Events. Designer. Magic links. Checkout. Returns. That is the stack that writes a face. Account team invites exist so more than one person can operate the list. Billing exists because hire and buy are real money. None of that is a floor-plan product.
Out of scope, repeated so it cannot be missed: desk hotelling, parking, digital signage CMS, AI agents in Teams, occupancy cameras, auto-release of meeting rooms. Those pages on a competitor site are not a dare. They are a different company.
If a future calendar connector lands, it still only mints visitor rows. It does not become a meeting-room booking system because the word “calendar” appeared. Outlook already books rooms. We will print a room name as text if you give us the string. We will not fight Outlook for the resource.
Audit yourself with one question before you buy anyone’s VMS: does this purchase change the object on the chest this month? If the answer is only “we got a dashboard,” you purchased a report. Buy a report if you need a report. Do not call it a badge.
Paper log, thermal sticker, e-ink face
A paper log is a clipboard. It is cheap until it is lost, and it never sits on the chest. A thermal sticker is a printer tax at the glass: the guest types, the host gets an email, the chest gets a curling label. An e-ink face is a third output. Most “VMS” pages sell the second and mention the third as an accessory.
We invert the stack. The record can be a spreadsheet, People, or a future calendar row. The product is the third output. If your tender document scores kiosk UX at forty percent and badge hardware at five, you will buy a kiosk. That is a valid tender. It is not this shop.
Event mornings compress the system into a crate. Office weekdays stretch it into a tray. The head term “visitor management system” pretends those clocks are identical. They are not. Our visitors hub keeps both clocks on one pillar and refuses desk-booking as a third clock.
Joan’s visitor-management pages (getjoan.com, September 2026) describe pre-registration, host notification, reusable badges, and a wider workplace platform. We link them because they exist. We do not clone the desk and parking modules to look complete. Completeness that ships a product we do not sell is a different kind of emptiness.
Who owns the word inside a large firm
Security owns access control. Facilities owns the foyer. Marketing owns the visitor day. IT owns calendars. Procurement owns the PO. Each of those teams will try to buy “visitor management” and mean a different object. Put the 250×122 panel on the table in the first meeting. If they wanted a turnstile, they will say so. If they wanted a named chest, you are in the right room.
SMEs skip that meeting. One person books the kit. That is why hire exists. The same compiler still serves the two-hundred-badge buy when the SME grows a receptionist. We refuse a “starter SKU” that is a different film.
Coworking and multi-tenant buildings want tenant isolation. We do not sell that. If your building is a stack of companies sharing a glass door, you need a different vendor’s kiosk, or a human with a list. Our crate assumes one organiser accountable for the window.
Schools, hospitals, and sites with DBS or clinical rules have extra paper. We will not pretend a hire crate replaces that paper. We can still put a name on a chest for an open evening if the organiser is allowed to. Ask your own compliance team before you paste a pupil list into any cloud designer, including ours.