Visitor check in software: what the front desk actually needs to record

Visitor check in software replaces the paper book at reception with a form on a tablet, a QR code or a pre-registration link. The speed is what gets it bought; the log is what makes it worth keeping. When something goes wrong — an evacuation, a security incident, a contractor injury — the question is never how fast people signed in, but whether you can say exactly who was on site, who they were visiting, and when they left.

What visitor check in software should capture

• Full name and organisation, typed by the visitor rather than guessed by reception.
• Who they are visiting, chosen from a list so the host can be notified automatically.
• Arrival time stamped by the system, not written by hand.
• Departure time — the field most systems collect badly and evacuations depend on.
• Vehicle registration where there is parking or a gate.
• Acceptance of site rules, confidentiality or safety briefing, recorded with the version they accepted.
• Visitor type — guest, contractor, delivery, interview — because each follows different rules.

Fields that slow the lobby for no benefit

Home address, date of birth, a photograph of everyone and a free-text reason for visit. Each adds time at the desk and personal data you now have to protect, retain and delete. Collect what you would actually use in an incident or a follow-up, and state on the form why you are collecting it — visitors are data subjects like anyone else.

Pre-registration halves queues. Hosts who send a check-in link the day before turn a two-minute form at the desk into a ten-second confirmation on arrival.

The sign-out problem

1. Make sign-out as easy as sign-in — the same device, the same QR code, one tap.
2. Send the host a reminder for visitors still on site at the end of the day.
3. Close open visits automatically at a fixed time, flagged as "not signed out", never silently.
4. Review unclosed visits weekly; a pattern usually points to one exit nobody passes reception through.
5. For contractors, tie sign-out to the return of badges, keys or permits.

Where a form is enough

For an office or a site with tens of visitors a day, a well-designed form does most of what visitor check in software does: Ettex Forms captures the sign-in with required fields and a timestamp, can be opened from a QR code at the desk, and delivers each submission into Ettex Records as a searchable visitor log where departures can be added. What it does not do is print badges, scan identity documents or screen visitors against a watchlist — if your site needs those, dedicated visitor management hardware and software are the right purchase.

Healthcare settings are the case where office-grade tools most often fall short. A hospital visitor management system has to handle ward-level visiting rules, protected units and infection contact tracing, so the sign-in log becomes one part of a stricter policy rather than the whole answer.

Using the log in an evacuation

• Anyone who can reach the log from a phone outside the building has a roll call.
• Filter to visitors with an arrival today and no departure — that is the list to account for.
• Include contractors signed in through a separate route, which is where most gaps appear.
• After the drill, record who was unaccounted for and why, and fix the sign-out step that failed.

Visitor records sit alongside other site records: a site induction for contractors who will work on the premises, and a permit to work where the job itself carries risk. The check-in log tells you they arrived; those records tell you they were entitled to do what they did.