People onsite
Checked-in visits without confirmed checkout
Reconcile with hosts when the list does not match reality.Visitor tracking system
Visitor tracking that answers who is onsite right now
Track active visits by person, host, destination, badge, escort, arrival, expected checkout, current status, exception, and confirmed departure.
Tracking is not a lifetime profile or website analytics. It is an accurate operational record of the current physical visit and the actions required to close it.
- Current onsite register
- Overdue-checkout and exception queues
- Searchable completed visit history
Keep the fields that make a visit actionable
The active record should answer what reception or the host needs to do next.
| Field | Question answered | Operational use |
|---|---|---|
| Visit status | Expected, waiting, onsite, overdue, checked out, or cancelled? | Determines the current queue. |
| Host and destination | Who owns the visit and where should the person be? | Supports handoff and follow-up. |
| Arrival and expected checkout | How long has the visit been active? | Identifies host delay and overdue departure. |
| Badge and escort | Which physical handoff is still open? | Supports return and escort accountability. |
| Current exception | What prevents the visit from moving or closing? | Routes a response to one owner. |
| Actual checkout | Has departure been confirmed? | Removes the person from the onsite list. |
Measure accuracy and response, not surveillance
Use the minimum operational data needed to keep the current list and exceptions reliable.
Waiting for host
Arrived visits without host handoff
Notify, escalate, or provide an alternate instruction.Checkout overdue
Open visits beyond expected departure
Contact the host or visitor and record closeout.Unresolved exceptions
Open visit exceptions by severity and owner
Work the oldest or highest-impact response first.Keep visitor tracking focused on the visit
Clarify what this system does and what belongs elsewhere.
Physical visit operations
Arrival, onsite status, host, destination, badge, escort, exception, checkout, and history belong here.
Website visitor analytics
Anonymous traffic, sessions, pages, campaigns, and conversion belong in analytics—not this page.
Employee location tracking
Continuous workforce location or attendance requires separate policy, purpose, and systems.
Door access events
Reader, credential, and controller events belong to physical access-control systems; link only the context needed by the visit.
Visitor tracking system questions
01What is visitor tracking?+
For physical-site operations, it means keeping the current visit status, host, destination, timing, badge or escort context, exception, checkout, and history accurate from arrival to departure.
02How do we know who is onsite?+
Use active-visit records with explicit check-in and checkout timestamps. Do not count approved invitations or unconfirmed appointments as onsite.
03What should happen when checkout is overdue?+
Create an exception with the host, visit, expected time, elapsed delay, response owner, next action, escalation, and final departure or closeout.
04Can the system show a visitor’s current location?+
You can store the approved or last reported destination and host handoff. Continuous real-time positioning requires specialist sensors or access systems and a separate privacy assessment.
05How long should visitor history be retained?+
Set retention according to the operational purpose, applicable policy, legal advice, and security needs. Collect and retain only the data that has a defined use.
Test the real visitor operation
Open the onsite visitor viewReconcile one day of real visits before trusting the dashboard
Compare expected, waiting, onsite, overdue, checked-out, and cancelled records with what reception and hosts actually observed.