Headquarters
7150 Columbia Gateway Drive, Suite L, Columbia, MD 21046
New York Location
112 West 34th Street, 18th Floor, Room 18025, New York, NY 10001
Proud Member
A visitor check-in system records that someone arrived. Visitor management covers the arrival as a whole: what the visitor has to agree to or disclose before they come in, what access they are granted once they are in, and what the building can still answer about the visit weeks later. Check-in is one component inside that, which is why the two terms get used as though they mean the same thing. They do not, and the gap between them is the part that decides what a building should actually be shopping for.
Check-in is the moment of record. A visitor arrives, identifies themselves, and the system writes that down in a form someone can search later.
In practice that means a visitor scans a state-issued ID or enters their name, the system can capture a photo and a digital signature, a badge is printed or issued digitally, and the host is notified by text or email. Entry and exit timestamps attach to the same entry. The log lives in a web-based console instead of a book on the counter.
That is a real improvement over paper, and for a lot of buildings it is the whole job. A legible, searchable, time-stamped record of who was in the building is worth having on its own, and it is the one part of this category a building can adopt without changing anything else about how the lobby runs.
What it does not do is anything before the arrival or after it. The visitor is recorded, not screened, and nothing about the record decides where they are allowed to go next.
Three things, and they sit on either side of the check-in moment rather than inside it.
| Visitor check-in | Visitor management |
|---|---|---|
Before arrival | Nothing. The visitor is recorded when they show up | Conditions of entry: what has to be signed, disclosed or confirmed first |
At arrival | ID scan or name entry, photo, signature, badge, host notified | The same check-in, run through the workflow set for that visitor type |
Access | A badge that identifies the visitor to a person | A credential a turnstile or elevator recognizes, for a set window |
After the visit | A searchable record that the visit happened | What the building can report, prove and delete about it |
Fits a building with | One tenant, a staffed desk, no barrier, nothing to sign | Several tenants, turnstiles, paperwork, or hours with nobody at the desk |
A system that does all three and a system that does check-in alone will both be described as visitor management in a brochure. What a visitor management system does in an office building sets out the full scope in detail. This post is only about telling the two apart when you are looking at them side by side.
Because nothing makes anyone use them precisely. There is no standards body that defines either term, no certification that separates them, and no agreed feature line that a product has to cross before it can be called visitor management. Every vendor in the category, including the ones selling the narrower product, uses the broader word.
That is not usually bad faith. The categories genuinely overlap, and a check-in product that adds a document-signing step has arguably moved into the wider one. But it does mean the words on a product page are not a reliable guide to scope.
The reliable guide is a question, and it works on any vendor: what does your system do before the visitor arrives, and what does it do after they leave? A check-in product will answer the second and have little to say about the first. Anything broader will have a real answer to both. Asking it that way also tells you what you are being quoted for, because the before and after pieces are usually where the scope and the integration work live.
The honest answer is that it depends on four things, and none of them is building size.
A single-tenant building with a staffed desk, no turnstiles and no paperwork requirement is well served by check-in alone, and specifying more than that is money spent on capability nobody will configure. A multi-tenant building with turnstiles and several tenants running different visitor rules is the opposite case, and trying to cover it with a sign-in tablet puts the difference back on whoever is standing at the desk.
Evacuation is the clearest example, and it is worth being precise about what the rules actually say, because this gets overstated.
Under 29 CFR 1910.38, an employer must have an emergency action plan whenever another OSHA standard in that part requires one. Where that applies, the plan's minimum elements include procedures to account for all employees after evacuation. The standard says employees. It does not set a requirement to account for visitors.
So the roll call question for visitors is not answered by regulation. It is answered by whatever record the building happens to be keeping at the moment the alarm goes off, and by whether the employer wrote visitors into its own plan. A searchable check-in log is genuinely useful here, which is a point in favor of even the narrow version of this system. What it cannot tell anyone is where in the building a visitor was cleared to be, because a check-in record holds an arrival, not an access profile. In a building with floors a visitor could not have reached, that distinction is the difference between a list of names and a place to start looking.
Yes, and that is usually the sensible order. The three jobs sit at different levels of commitment, and the record is the one that stands up on its own.
On the Navigo side, pre-screening is built as a layer that can be switched on for one group and left off for others, so a building can require a disclosure from vendors and contractors without putting every guest through it. It runs two ways: a token link sent to a group on a schedule, so the screening is done before anyone arrives, or at the kiosk, where a visitor completes it at check-in before being approved for entry. Surveys, acknowledgements, NDA acceptance and digital signatures are configured per workflow rather than fixed.
Credentialing is the piece most often left for a later phase, because it depends on which access platform the building runs. Connecting visitor management to Lenel, Genetec, C-CURE, AMAG and Kastle covers how that part works and what to confirm before anyone quotes it.
The one thing worth getting right in the first phase is the record itself. Expanding what a system captures later is straightforward. Reconstructing visits it never captured is not.
Tell us what has to be signed before someone enters your building, whether there is a barrier between the lobby and the elevator, and whether the desk is staffed all day. Those three answers decide which version of this you need.
No. Check-in records an arrival. Visitor management also covers what is required before entry, what access the visitor is granted, and what the building can report on afterward. Both are commonly marketed as visitor management, because no standard defines either term.
Not by itself. Where 29 CFR 1910.38 applies, its minimum elements require procedures to account for all employees after evacuation and do not set a requirement covering visitors. A visitor log helps a roll call, but accounting for visitors depends on what the employer writes into its own plan.
Not usually. In an office building it more often means an NDA signed at arrival, a site-specific safety or medical disclosure, or confirmation of an authorized pickup. Navigo pre-screening is configured per visitor type, so a requirement can apply to contractors and not to guests.
Yes. Navigo supports self check-in and guard or receptionist-administered check-in on the same system, which matters for buildings where the desk is staffed during business hours and the lobby runs unattended early or late.
Ask what the system does before the visitor arrives and what it does after they leave. A check-in product answers the second and has little for the first. That question also exposes where the integration scope sits, which is usually what a quote turns on.
Toll-Free
Phone
© Copyright 2025 ITS, Inc. All rights reserved.
Stay in touch with the latest news and updates from ITS, Inc.
7150 Columbia Gateway Drive, Suite L
Columbia, MD 21046
112 West 34th Street, 18th Floor, Room 18025
New York, NY 10001