Editorial desk
Guide
From the invitation to the follow-up, a visit is a chain of small handovers between host, visitor, reception and system. How to map each step, find the friction and fix the weak link most sites ignore: signing out.
How-to
Parcels arrive at the same desk as visitors and usually get less care. A step-by-step process for logging, notifying, storing and handing over deliveries, with a clear trail and a plan for the ones nobody collects.
Guide
What each kind of visitor badge is good for, how to show expiry and visitor type at a glance, when to reuse and when to bin, and the uncomfortable truth about how little a badge actually proves.
How-to
Five practical measures, from time to badge to roll-call accuracy in a drill, with how to collect each one using records you already have and a stopwatch. Set your own baseline; ignore anyone else's benchmark.
Guide
A practical plan for taking a visitor system from one building to many: choosing a pilot, deciding what is standard and what is local, setting up central reporting, training each role and phasing the go-lives.
Analysis
Desk-booking suites now ship visitor modules, and dedicated visitor systems keep adding workplace features. The right choice depends less on the feature list than on who in your organisation carries the risk at the front door.
Guide
How to connect a visitor system to the doors: issuing time-bound visitor credentials, deciding what data flows each way, and the questions to put to both vendors before anyone writes a line of configuration.
Analysis
Scanning a driving licence and checking visitors against a list feels like good security. Often it is more data than the risk justifies. A case for starting with the decision the check will change, and working back from there.
Guide
A practical guide to managing contractors through the front desk: checking documents before arrival, running inductions, linking sign-in to permits to work, tracking expiry dates and keeping on-site rules enforceable.
Analysis
Reception was designed for a stable building: staff who were always there and visitors who were the exception. Where attendance varies by the day, staff start to look like visitors, desk booking overlaps sign-in, and some front desks go unstaffed.
Guide
Tablet kiosk, dedicated kiosk, staffed desk or the visitor's own phone? How to match sign-in hardware and badge printers to your reception, and the power, network and accessibility details that decide whether it works.
Analysis
Most visitor management products in our directory list a cloud option, and most of those offer nothing else. The on-premises minority is concentrated in one category, and the reasons it survives tell you when you might need it.
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.