Buyer guide
Visitor management system requirements: the 18-point checklist.
Every visitor management demo shows the same happy path: a visitor types their name, a badge prints, the host gets a message. The differences that matter live in the requirements nobody demos. This checklist covers all 18, grouped by who in your organization cares about each.
Security team requirements
1 to 5: what the security lead should demand
- 1. Watchlist and sanctions screening at sign-in. Names checked against the OFAC SDN List, the US Consolidated Screening List, the UN and EU consolidated lists and the UK Sanctions List, plus your internal ban list, before a badge prints, not in a nightly batch.
- 2. Silent alert on a screening hit. A match must alert security without tipping off the person standing at the kiosk.
- 3. Evacuation roll call from a phone. A live list of everyone on site, filtered by zone, with one-tap safe marking. If the vendor's answer is an emailed CSV, keep shopping.
- 4. No biometric collection by default. Face capture creates obligations under Illinois BIPA, Texas CUBI, and similar state laws. Prefer systems that work without storing biometrics at all.
- 5. Full audit trail. Every sign-in, sign-out, screening result, badge print, and record edit, timestamped and attributable, exportable for investigations.
Facilities and reception requirements
6 to 10: what makes the front desk actually faster
- 6. Pre-registration with QR fast lane. Hosts invite visitors ahead; the visitor scans a QR on arrival and the badge prints in seconds.
- 7. Badge printing that identifies at a glance. Name, photo, host, validity period, and a visual category (visitor, contractor, delivery) readable from across a room.
- 8. Multi-entrance, one record. A person signing in at Gate B must appear on the same site list as reception sign-ins. Per-entrance silos break mustering and screening.
- 9. Automatic sign-out. Auto sign-out at a set closing time or after a set duration, plus exit scanning, so the on-site list does not accumulate ghosts.
- 10. Works during an internet outage. The kiosk must keep signing people in locally and sync later. Ask the vendor what specifically happens when the connection drops.
Compliance requirements
11 to 14: what keeps the audit painless
- 11. Contractor document verification at the gate. Insurance certificates, inductions, and permits checked for validity at sign-in, with expired documents blocking entry.
- 12. Configurable data retention. Visitor records auto-purge on your schedule per data category, satisfying GDPR-style minimization and your legal team.
- 13. NDAs and site rules signed at the kiosk. Version-tracked documents with signature records retrievable per visitor per visit.
- 14. Per-tenant data isolation. For multi-tenant buildings and multi-site companies: one tenant's visitor data must be invisible to every other tenant, provably.
IT requirements
15 to 18: what gets the deployment approved
- 15. SSO against your identity provider. OpenID Connect for staff access, per tenant, with no shared logins at reception.
- 16. Directory sync and SCIM. Hosts provisioned and deprovisioned automatically from Entra or your IdP; leavers disappear as hosts the day they leave.
- 17. Standard hardware. Runs on off-the-shelf tablets and label printers you can buy anywhere, not proprietary kiosks with proprietary replacement cycles.
- 18. Export everything. Full data export in open formats at any time. The system you choose today should not hold your visitor history hostage in five years.
Where BeckonDesk falls short on this list
BeckonDesk covers points 1, 2, 4, 8 and 17 as written. On the rest, here is what it does today and where it stops short:
- 3. Roll call. Fire marshals open the live roll call on their own phones by scanning a QR code, with no app or login, and mark people safe, missing or unaccounted. The list is fixed when the evacuation starts, so people who leave stay on it, flagged, and each roll call downloads as a CSV. There is no filtering by zone or muster point.
- 5. Audit trail. Sign-ins, sign-outs, screening checks and changes to records are logged with who and when, and the audit trail exports as CSV. Badge prints are not logged.
- 6. Badge printing. Pre-registered visitors scan their QR pass to sign in. The badge prints through the browser's print dialog from a "Print badge" button; nothing prints automatically.
- 7. Badge content. Badges show name, host, site, company and visitor type, with colors set per type, and can print a "Valid until" time: the end of the check-in day at the site. There is no photo (BeckonDesk doesn't capture them).
- 9. Automatic sign-out. It runs after a set duration from sign-in (8 hours by default), not at a fixed end-of-day time. Visitors can also sign out by scanning their badge, and contractors by scanning their contractor pass again.
- 10. Internet outage. Sign-in needs a connection, because every sign-in is screened against the live lists. Only sign-outs queue offline, from the sign-out screen, and they are sent when the connection returns.
- 11. Contractor checks. Expired certificates, expired company insurance, and assigned inductions not passed or lapsed all block entry. Permits to work are shown at check-in but don't block, and there are no rules requiring particular certificate types.
- 12. Retention. One retention period per workspace (365 days by default), not one per data category.
- 13. Agreements. Each signature is stored with the visit and the agreement's version number, and you can make earlier signers sign again when the text changes. Earlier versions of the text aren't kept.
- 14. Tenant isolation. All workspaces share one database, and the application keeps each workspace's records separate. A kiosk belongs to one workspace, so one tablet can't serve several companies in a shared reception.
- 15. SSO. Staff sign in with BeckonDesk accounts (email or Microsoft account). Sign-in through your own identity provider isn't available yet.
- 16. Directory sync. Entra ID group sync fills hosts and roles and can remove people who leave every group, on a schedule you set (daily by default, as often as hourly). SCIM 2.0 provisioning creates users with the Viewer role.
- 18. Export. Exports are specific CSVs: the visitor log, contractor compliance, the screening log, each evacuation's roll call, the audit trail (up to 10,000 rows), staff timesheets and a 30-day evidence pack. There is no one-click export of everything.
Check BeckonDesk against all 18.
The gaps are listed above. Bring this checklist to a 30-minute demo and go through the rest point by point, or test it yourself on a 30-day free trial.