Data

Every visit becomes a record.

Structured. Searchable. Yours to export.

VISITOR.RECORD · #00482 VERIFIED
visitor: "Emily Davis"
company: "Tech Solutions"
verified_by: "POC"
check_in: "15:02"
check_out: "16:34"
status: "CHECKED_OUT"
What every visit becomes

One structured record. Annotated.

Every visit produces the same shape of record. Same fields. Same types. Same timestamp format. Predictable enough to query, export, and audit without translation work.

visit_id String, unique
A stable identifier for the visit. Persists across check-in, check-out, and audit.
visitor Object
Name, company, contact, and visit purpose, captured at request time.
host Object, attributed
The employee who submitted the request. Tied to their authenticated account.
verified_by Enum, POC | SOC
How the visit was verified at the gate. Point of Contact or Security Operations Center.
check_in / check_out Timestamp, UTC
Recorded at the moment the guard taps the action. Tied to the guard's identity.
status Enum
SCHEDULED, EXPECTED, CHECKED_IN, CHECKED_OUT, NO_SHOW. One value at a time. State machine validated.
site String
Which facility the visit took place at. Used for filtering and per-site permissions.
What it lets you measure

Real questions, not estimates.

Once every visit has the same shape, the questions a security or operations team typically asks become straightforward queries against the data.

Average dwell time
Per site, per visitor type
Derived from check_out - check_in, grouped by site and visitor.company.
No-show rate
Per host, per period
Count of status = NO_SHOW divided by all scheduled visits, grouped by host.
Verification path mix
POC vs SOC, daily
Distribution of verified_by over a window. Useful for staffing reviews.
Active on site, now
Live, real-time
Count of records where status = CHECKED_IN. Visible on the admin dashboard.
What it replaces

Fragmented sources. Unified record.

Most facilities already have the data, but it lives in different places, captured by different people, often by hand. GuardView consolidates the capture into one structured record per visit.

Before
Scattered capture across people and systems.
  • Paper sign-in sheets at the gate
  • Emails between hosts and security
  • Calendar invites without verification
  • Shift logs that vary by guard
  • Manual reports compiled from memory
After
One structured record per visit.
  • Same fields every time
  • Same timestamp format every time
  • Every action attributed to a real user
  • Searchable and exportable on demand
  • Audit response in minutes, not days

Get the data, not the guesses.

Run a 30-day pilot. We export your full record at day thirty. You decide.

Request a 30-day pilot →