Contents
Subscribe to our newsletter
Subscribe to the elia newsletter for exclusive product updates and industry best practices. You can unsubscribe at any time.
Thank you! You're subscribed.
Oops! Something went wrong while submitting the form.

It's 9 AM. Four people hit reception at once: a contractor, two interview candidates, and a courier. Your receptionist is printing badges by hand and calling hosts one at a time. Two of those guests have already drifted toward the elevators with nothing clipped to their shirt.
That scene plays out way too many times. The badges printed just fine, but the trouble was everything else around them: no record of who those two guests were, and no one sure where they'd gone.
That's the job of a visitor badge system, and the badge itself is the smallest part of it. Any printer makes a badge. What you're paying for is the system behind it: how the visitor gets identified, what the badge lets them into, and whether there's a usable record when someone asks three months later.
So before you go and buy one, here's:

A visitor badge system is a combo of software and hardware that registers a visitor, checks who they are, and issues a credential tied to that record. The credential is usually a printed badge or a digital pass.
The badge is one bit of the system, but the rest of it is doing all the work you care about: keeping a record of the visit, alerting the host, and controlling where the visitor can go. When you’re comparing options, make sure to focus on what each system does with the visit.
Most systems follow a pretty standard visitor management process:
At the very least you need to show the word VISITOR big enough to read from across a room, plus the visitor's name, their company name, the host they're seeing, and an expiry time. Add a photo if your policy needs visual ID, and a QR code for check-out or door access. The company logo is optional.

Most systems let you customize this. You can color-code badges by visitor type, so a contractor's badge looks different from an interview candidate's. You can show different fields or messages depending on who's checking in.
Design the badge so that staff and security personnel can quickly identify visitors at a glance. A photo and the host's name do way more for easy identification than a logo does. If a staff member can look at a badge and know this person is with the facilities contractor on floor 3, the badge is doing its job.
Different visitors need different badges. A few common cases:
Escort-required is worth its own special mention. In regulated and manufacturing sites, some visitors can't roam the building on their own. A badge that visibly says "escort required" tells any staff member this person should have someone with them, which is far easier to enforce than a line in a policy document.
Not every workplace needs the same badge. The main options:

When I'm checking out a badge system, I tend to ignore the feature list at first. Almost every vendor prints badges, notifies hosts, and logs the visit. It's the way those pieces hold up in real world use that tells you where a system really stands. Here's what I'd check:

Every badge you print leaves a data trail, and that's useful for security, but it's also a responsibility under privacy rules like GDPR.
The principles are pretty simple: collect only what you need, tell visitors why you're collecting it, keep it only as long as it's useful, and then get rid of it. GDPR is the one most people mention, but the same rule runs through the laws your buyers answer to.
Canada's federal PIPEDA and Quebec's Law 25 both require you to keep personal information only as long as necessary and to destroy or anonymize it after. US privacy law is a patchwork of state rules like California's CCPA, with the same core idea. None of them sets a single fixed retention period. In practice, most organizations keep visitor records for 30 to 90 days, then bin them.
This is where digital beats paper on every count. A cloud-based log is encrypted and can delete records automatically on a schedule. A paper logbook can't do any of that. It sits on the front desk where anyone can read it, and enforcing a retention policy means someone has to remember to shred it.
If a badge system can't auto-delete records on a schedule, treat that as a compliance liability.
Where you end up depends on your site, so here's how I'd categorize it, roughly, in 3 tiers:
Setup time scales the same way. A single-site, self-service system can go live the same day. Guided onboarding with integrations takes 1 to 4 weeks. Enterprise rollouts across multiple sites, especially ones wired into access control, run 3 to 6 months.
The tipping point for most offices is somewhere around 40-50 visitors a week, or the first real compliance requirement, whichever comes first. Below that, you can probably keep things simple. Above it, the log and the access rules stop being extras.
For the full breakdown by plan, hardware, and hidden fees, see our visitor management system cost guide.
Most of these run the core flow well. Where they split is who they're built for: a polished lobby, a factory floor, or a school checking IDs at the door:
If you're looking for systems to demo, pick 2-3 that fit your needs and then have a real person come in and try them out. That's often a much better way to figure out what works than just looking at a spec sheet.
Whatever system you're looking at, the same test applies: can a badge hook into a record, notification and access controls that still work their magic on a mad morning?
That's what elia's all about. Visitors check in at a kiosk or tablet, or register ahead of time by scanning a QR code. The host is pinged with an email or a notification on Slack or Teams the moment they sign in, and every single visit winds up in a log that's ready to be exported whenever someone comes knocking. Because it's part of a bigger workplace platform, the badge sits comfy next to desk and room booking instead of off on its own in a separate app.
If you want to see how that looks in your own office, take the interactive tour or book a demo!
Make every guest feel expected before they even reach reception.
Answers to Your Common Queries
It's a combination of software and hardware that signs in visitors, verifies who they are and issues a credential tied to that record (usually a printed badge or digital pass). The badge lets staff quickly spot visitors while the system behind it keeps a record of the visit, notifies the host and often controls access to specific areas.
They can, and for higher-security sites they should. Expiring badge stock changes color overnight so a badge is visibly no longer valid the next day, which stops someone reusing it. Digital passes and access credentials can also be set to expire at the end of the visit if you need to be extra secure.
Most systems print visitor badges on a thermal printer at the check-in kiosk the moment a visitor finishes signing in. Printing takes a few seconds and you can stick them on an adhesive sticker or into a lanyard holder. There are also systems that skip printing and just hand out a digital pass on the visitor's phone instead.
You'll see the visitor's name, company, photo, the host they're visiting, and the date and time on most badges. Plus, your company logo, and sometimes a QR code for check-out or door access. A photo and host name are the most important bits for easy recognition.
Only as long as you need to. GDPR, Canada's PIPEDA, Quebec's Law 25, and US state laws all say you have to keep visitor info for as long as you need it, without setting a fixed time limit. Most companies keep records for 30 to 90 days, then auto-delete them.