Why your visitor log is a security document
What auditors actually look for in visit records — and the five fields most lobbies forget to capture.
When most teams think about their visitor log, they picture a courtesy — a way to know who to expect and when to release the badge printer. But the first time an auditor, an insurer, or an incident-response team asks for it, the log changes character. It stops being hospitality paperwork and becomes evidence.
The difference between a log that helps you and one that embarrasses you comes down to what was captured at the door, in the moment — because none of it can be reconstructed afterwards.
The five fields most lobbies forget
Paper cannot do this. That is the point.
None of these fields are hard to capture — they are hard to capture consistently, on a busy morning, by a receptionist doing four other things. A guided check-in flow captures them every time, because the visitor cannot proceed without them, and the record files itself.
When your log is complete, timestamped and exportable, the audit conversation gets short. When it is not, the finding writes itself.
Where to start
Pull last month’s visitor records and check them against the five fields above. If two or more are missing, your lobby is collecting greetings, not records — and that is fixable in an afternoon.