How to Check In Visitors: A Practical Guide
The visitor experience starts at reception and sets the tone for every meeting your office hosts. But visitor check-in is also a security control: it confirms who’s in the building, who they’re here to see, and when they leave. A written SOP means every visitor gets the same professional welcome and the same security treatment, whether it’s a client, a contractor, or a delivery driver, and it means reception never has to improvise.
When to Use This
Use this SOP in any office that receives visitors, clients, suppliers, contractors, interview candidates, delivery drivers. It’s most needed when reception is staffed by a rota or when visitors arrive before their host is ready: those are the moments when procedures get skipped and strangers end up wandering corridors. If your office has restricted areas (server rooms, finance offices, stock rooms), a visitor SOP isn’t optional, it’s how you prove access was controlled.
The visitor log also has a practical afterlife: it’s the record you reach for when someone asks who was in the building on a given day, whether for a security incident, a lost item, or a follow-up with a client who visited.
How to Fill It Out
The header box. Who prepared it, who owns it, the version, the date issued, and the review date. The owner is usually the office manager or reception supervisor.
Fields to complete before use. Replace every bracketed field: the host deputy contact (who to try when a host can’t be reached), the restricted areas visitors must never enter, and the reception phone number or extension. Then delete the example rows. Name your restricted areas specifically, “server room, finance office”, not “sensitive areas.” Vague restrictions don’t get enforced.
Arrival and identification. Greet the visitor by name where possible (the pre-registered visitor list for the day makes this easy), confirm the host’s name, and check photo identification for contractors and delivery drivers. The SOP is clear on the hard case: visitors who refuse identification are not admitted, and the host is informed. That’s an awkward conversation, but a written policy makes it a policy conversation instead of a personal one.
Sign-in and badge issue. Record the time in, visitor name, company, host, and badge number in the visitor register. Issue a visitor badge showing the visitor’s name and host, and the visitor wears it visibly at all times. Badges that stay in pockets are decorations; the point of a badge is that anyone in the office can see at a glance that a stranger is accounted for.
Host notification. Phone or message the host immediately with the visitor’s name and arrival time, don’t make the visitor wait in silence while reception does other things. If the host can’t be reached within 10 minutes, ask the visitor to wait in reception and try the host deputy from the reception phone. Never send a visitor to find a meeting room unescorted on their first visit. Getting lost in someone else’s office is a bad first impression and a security gap.
Escort and access rules. Collect the visitor from reception and stay with them in staff-only areas. Don’t admit visitors to the restricted areas you named above. And don’t give visitors door codes, alarm codes, or network passwords, this is the rule that gets broken casually (“the Wi-Fi password is on the whiteboard”) and should be stated explicitly. Set up a guest Wi-Fi network with a printed code if you need one.
Departure and sign-out. Collect the badge on departure, record the departure time, and confirm the visitor has left the building. If a visitor leaves without signing out, note the estimated departure time and inform the host. Unreturned badges should be chased, a stack of missing visitor badges is a small security hole that grows over time.
A note on visitor data. Visitor logs contain personal information, names, companies, sometimes ID details. Check your local data-protection rules about how long to keep them and who can access them, and keep the register somewhere visitors can’t browse each other’s entries.
Completion checklist. The per-visit confirmation: greeted, host confirmed, pre-registered list checked, ID verified where required, badge issued and returned, departure recorded.
Common Mistakes
1. Letting regulars bypass the process. The delivery driver who comes daily, the contractor who’s “basically staff”, these are exactly the people the process is for. Familiarity is not identification, and the day something goes missing, the log is only useful if it’s complete.
2. Badges issued but not worn or collected. A badge in a pocket helps nobody, and uncollected badges accumulate into an untracked set of building passes. Issue, wear visibly, collect, all three, every time.
3. No plan for an unreachable host. Without the deputy contact and the 10-minute rule, reception is stuck between an annoyed visitor and an absent host, improvising. Write the fallback into the SOP so nobody has to invent it.
4. Sharing codes and passwords casually. Door codes given to “just this once” visitors have a way of spreading. Keep visitor access physical and escorted; if visitors need network access, give them a guest network, not your internal credentials.
Who Needs to Sign Off
The office manager or reception supervisor prepares and owns this SOP; a senior manager approves it, since it governs building security. Facilities or IT should confirm the restricted areas and the access-code rules. Every receptionist and anyone who might cover reception reads it and practices the routine, including the awkward parts, like refusing entry without ID, before handling visitors solo.
How Often to Review and Update
Review every six months, and update immediately when the building changes: new restricted areas, new badge system, new reception phone setup, or changes to the host deputy arrangements. Review the visitor log retention period against your local data-protection requirements at each review. After any security incident involving a visitor, audit the SOP as part of the debrief and close whatever gap the incident found.
Download the free Visitor Check-In SOP template.