TL;DR:
Most visitor log templates are…basic.
They’re just a table with headers on top. You type a name, you type a time, and the file gives you nothing back.
This one calculates. Our free visitor log template in Excel shows who is still in the building right now, flags anyone who left without signing out, and tells you which records are old enough to delete. The same file works in Google Sheets.
Both versions are free, and there’s no sign-up.
Below: how to open it without losing your edits, what each tab does, what to record in a visitor log, and the point where a spreadsheet stops being the right tool.
For Google Sheets, you need to be signed in to a Google account. A personal Gmail address works, so does a Google Workspace account from your company. Once you’re signed in, go to File → Make a copy.
That step matters. The file we share is view-only, so anything you type into it won’t save and won’t be visible to anyone else. Your copy lands in your own Drive, under your control, and you can share it with reception from there.
If you see “View only” in the top right and the cells won’t accept typing, you either aren’t signed in or you haven’t made the copy yet.
For Excel – download the .xlsx file and open it. Excel usually opens files from the internet in Protected View, so click Enable Editing in the yellow bar at the top. The dropdowns and calculations stay switched off until you do.
There are no macros in either version, so nothing to trust or allow beyond that.
Five tabs you’ll use, plus one helper sheet you can ignore.
Setup. Your site name, your host list (up to 50 people), your visit types, and your floors or areas. Fill this in once. Everything you enter here becomes a dropdown on the log, so reception picks from a list instead of typing “J. Smith” one day and “Jane Smith” the next.
You also set 2 numbers here: how many hours counts as a long visit, and how many days you keep visitor records. Both feed the dashboard.
Visitor log. 300 rows. You fill in the visitor, the host, the badge number and the times. The template fills in the visit number, the length of the visit, and a status for every row:
There’s also a check that catches dates typed as text. If someone writes 16/09/2026 in a way the sheet reads as words instead of a date, a warning appears at the top of the log and tells you how many rows are affected. Those rows would otherwise vanish from every count without anyone noticing.
Dashboard. Pick any date and the tab shows who was on site, who was expected, the average visit length, and how many people across the whole log never signed out. Underneath that is a list of everyone currently in the building, with their host, badge number, and time in. Print it, and you have a roll call.
Visitor badge. Type a visit number and the printable pass fills itself in from the log: name, company, host, floor, date, time in, badge number. No handwriting, no retyping.
Lists. The helper sheet the dashboard reads from. Leave it alone.
The file is free to use and share, and the 3 sample rows are dummy data you can type straight over.
The fields below cover a normal office. Add or cut columns to suit your building, but be careful about adding fields you don’t have a reason to hold (more on that further down).
| Field | Why it’s there |
|---|---|
| Date | Anchors every count and every search of the log |
| Visitor name | The record itself |
| Company | Tells you whether this is a client, a supplier or a contractor at a glance |
| Email and phone | Reaching someone after they’ve left, and pre-registration |
| Visit type | Meeting, interview, delivery, contractor, audit. Useful for spotting patterns in traffic |
| Host | Who’s responsible for the guest while they’re in the building |
| Area or floor | Where to look during an evacuation |
| Badge number | Links the physical pass to the record |
| Time in and time out | The two fields that make a log a log |
| NDA or safety briefing | Proof the paperwork was done before they got past the lobby |
| Notes | Access needs, escort requirements, anything unusual |
Two fields do most of the work: time in and time out. Almost every problem with a paper or spreadsheet visitor sign-in sheet traces back to the second one.
Signing in has a prompt. Someone hands you a clipboard or points at a tablet. Signing out has nothing. The visitor is already thinking about their train.
People skip steps that happen at the door, and we have our own numbers on this. Over 12 months in our Sofia office, we recorded 13,024 desk bookings, and 9.1% of them were never checked into at all. The step was 1 tap on a phone. You can read the full year of data here.
Visitor check-out has no tap and no reminder, so the failure rate is worse. The result is a log that says 14 people are in your building when 3 actually are.
Our template can’t force anyone to sign out. What it does is make the gap visible: any row with a sign-in time, no sign-out time, and a date before today turns red and reads Not signed out. The dashboard counts them for you.
This is the question a visitor log exists to answer, and a flat spreadsheet answers it badly. You’d be scrolling and filtering while the alarm is going.
Under OSHA’s emergency action plan rule (29 CFR 1910.38), an employer’s written plan has to include procedures to account for everyone after an evacuation. The standard is written around employees, but any evacuation warden will tell you the people nobody can account for are usually the guests, because they’re the ones not on a team list.
The Dashboard tab handles this. Pick today’s date and you get a printed list of names, companies, hosts, badge numbers and sign-in times for everyone currently on site. Keep a copy at reception or print it at the start of each afternoon.
A visitor log holds names, phone numbers, email addresses and a record of someone’s movements through your building. That’s personal data, and most spreadsheet logs sit in a shared drive with 4 years of it and no deletion date.
The UK ICO’s guidance on the storage limitation principle is direct about this: GDPR sets no fixed retention periods, so you have to set your own, document them, and actually delete when they expire. Data held past the point you need it is data you probably have no lawful basis to hold.
So the template has a retention setting. Enter how many days you keep records on the Setup tab, and the Dashboard tells you how many rows are past that date and the exact cut-off to delete up to. Most offices land somewhere between 30 and 90 days unless a regulator says otherwise.
While you’re there, cut the columns you don’t have a reason to fill. A car registration field you use twice a year is personal data you’re storing for no purpose.
A spreadsheet is the right answer for a small office with a handful of guests a day. It costs nothing, everyone can already use it, and it works offline.
It stops being the right answer around the point any of these become true:
The last one catches people out. Excel can password-protect a file. It can’t give you role-based access, an audit trail of who opened the log, or a record of what changed.
| Excel or Google sheets | Visitor management software | |
|---|---|---|
| Cost | Free | Paid, usually offered as an add-on too |
| Setup time | Minutes | Hours, plus a tablet at reception |
| Works offline | Yes | Usually needs a connection |
| Check-in | Someone types it | The guest does it on a tablet or a QR code |
| Sign-out | Manual, and often skipped | Automatic or prompted |
| Host notification | Someone walks over | Instant, in Teams, Slack or email |
| Pre-registration | No | Yes, with an invite email and directions |
| Document signing | Printed and filed | Signed on screen before entry |
| Badge printing | Print the tab | Printed automatically at the desk |
| Who’s on site now | The Dashboard tab, if the log is current | Live, always |
| Access control | File permissions | Role-based, with an audit trail |
| Retention | You delete rows on schedule | Automated deletion policy |
| Export for compliance | Copy and paste | Any date range, on demand |
The honest summary: the spreadsheet wins on cost and speed of setup. Software wins on everything that depends on someone remembering to do something. And of course, easier and error-free automation, plus security.
Visitor Hub is the visitor management side of OfficeRnD Workplace. Guests pre-register before they arrive, sign your NDA on the way in, and check themselves in at a tablet. The host is notified in Microsoft Teams, Slack or email the moment it happens. Deliveries work the same way.
Every visit is logged without anyone typing it, so the on-site list is accurate by default and you can export any date range for an audit or a fire drill.
On enforcement, we can point at our own office again. Desk bookings at OfficeRnD auto-cancel if nobody checks in, and over the year that single rule returned about 4.5 desks a day to the pool, roughly 8% of the office. Rules that run by themselves collect data that people forget to enter.
Visitor Hub sits alongside desk booking, meeting rooms, parking, and helpdesk in the same platform, so you’re not running a separate system for the front desk.
See the main use cases of the visitor hub for modern workplaces here.
If the visitor log is useful, these are built the same way: