Guide
How school offices can handle identity checks, lanyards, pupil sign-out, contractors, volunteers and visiting professionals, and how visitor records support lockdown and evacuation procedures.
How-to
A visitor system holds names, photos, host details and sometimes ID scans, and it runs on a tablet in a public lobby. These are the questions that separate a sound supplier from a slick demo, and how to read the answers.
Guide
How to turn sign-in records into a roll-call that works when the alarm sounds: who holds the list, how wardens reconcile it at the assembly point, what to do when the network or the tablet is unavailable, and how to drill it.
Analysis
The reception tablet was bought as a convenience. Once security, facilities and data protection start relying on its records, it is infrastructure, and it needs an owner, a failure plan and change control to match.
Guide
What to collect at sign-in, which lawful basis fits, how to show a privacy notice on a kiosk, how long to keep records, and how to handle photos, ID scans and subject access requests.
Analysis
The visitor book on the reception desk looks free. In practice it shows every visitor's details to the next one, cannot run a roll-call, and quietly keeps personal data for as long as nobody throws it away.
Guide
A practical guide to specifying a visitor management system: writing requirements as real scenarios, separating must-haves from nice-to-haves, scripting demos and comparing a shortlist on evidence rather than points.
Analysis
Our directory sorts visitor management into four categories of roughly equal size. They overlap on the sign-in screen and diverge almost everywhere else, which is why a shortlist should start with the category, not the feature list.
Guide
Sign-in is the visible part. The reason organisations buy a VMS is usually evacuation lists, contractor compliance and knowing who was in the building on a given afternoon.