GHT: Glass House Technologies
GHT service / Physical security

Visitor and contractor entry

From the front door to signed out, accounted for

Pre-registration, arrival, identity checks, host approval, badges, temporary credentials, escort rules, emergency accounting, checkout, accessibility, and record retention, connected into one process.

What you should have at closeoutA tested arrival-to-departure process with named hosts, time-limited access, accessible alternatives, expiration evidence, and operating guides.
References3 reviewed
Last updated2026-08-20
Overview

What Visitor and contractor entry includes

Visitor and contractor entry spans people, policy, space, and technology. Kiosks, intercoms, badge printers, cameras, access credentials, notifications, and watchlists support the process but do not decide who may enter or what data should be collected.

The owner defines identity evidence, consent or notice, host responsibility, escort needs, retention, emergency accounting, accessibility, and exceptions. Contractor onboarding may also involve safety training or work authorization outside the visitor platform.

Question to answer before designWhat must be approved before entry, what temporary access is needed, and how will expiration or departure be confirmed?
Common situations

This service may fit when:

  • Paper logs are incomplete, exposed, or difficult to search
  • Hosts miss arrivals or temporary credentials outlive the visit
  • Contractors move among sites without consistent approval or checkout
  • Lobby congestion or inaccessible check-in blocks legitimate visitors
System components

What the system includes

A complete scope covers each part below and the connections between them.

01

Arrival

Pre-registration, signage, kiosk, desk, intercom, accessible alternative

02

Decision

Identity evidence, host approval, policy, watchlist or safety requirement

03

Temporary access

Badge, credential, zones, schedule, escort, expiration

04

Record

Arrival, host, access, checkout, emergency roster, retention and deletion

Project record

How site information becomes a tested project

A complete project record connects the conditions found on site, the design decisions made from them, and the tests and closeout documents delivered afterward.

Site information

What we confirm before design

  • Visitor and contractor types, entry points, hosts, and operating hours
  • Identity, approval, escort, safety, denial, and exception policies
  • Badge, credential, accessible check-in, and emergency-accounting needs
Design decisions

What those findings determine

  • Check-in: Preserve a staffed and accessible exception path.
  • Host approval: Define timeout, delegation, denial, and no-response behavior.
  • Access: Issue only what is needed and prove automatic expiration.
Closeout records

What you should receive

  • Visitor-type and decision matrix
  • Arrival-to-departure workflow and accessible fallback
  • Temporary credential, badge, host, and retention configuration

The exact inputs, decisions, and acceptance records depend on the site and signed scope.

Project stagesSurvey through closeoutView details
Project stages

How the work moves from survey to closeout

Each stage should produce the records and test results needed before the next stage begins.

  1. 01

    Map people and policy

    Document visitor types, hosts, entry points, identity checks, approvals, restricted areas, escorts, accessibility, emergency accounting, data, and retention.

    EvidenceVisitor-type matrix, journey map, policy decisions, data inventory, and exception list.
  2. 02

    Design the entry path

    Define pre-registration, arrival, accessible alternatives, host notification, badge and credential issuance, expiration, denial, checkout, and offline fallback.

    EvidenceFuture-state workflow, screen and station locations, credential rules, integration map, and fallback procedure.
  3. 03

    Configure and pilot

    Set roles, sites, messages, badge fields, integrations, retention, and temporary-access rules; then pilot with representative visitor types.

    EvidenceConfiguration record, pilot transactions, permission tests, printed badge samples, and issue log.
  4. 04

    Exercise exceptions

    Test walk-ins, pre-registered visits, no host response, denied access, accessibility path, expired credentials, evacuation list, checkout, and unavailable services.

    EvidenceScenario results, expired-credential event, emergency roster sample, operator guide, and accepted exceptions.
Design choicesCompare the available approachesView details
Options

How to choose the right approach

The right choice depends on the site, application, operating risk, and acceptance requirements. More equipment does not automatically improve the system.

FactorTypical approachMore demanding conditionsWhat determines the choice
Check-inTypical approach: Reception or paper logMore demanding conditions: Pre-registration with assisted or self-service arrivalWhat determines the choice: Preserve a staffed and accessible exception path.
Host approvalTypical approach: Phone or desk confirmationMore demanding conditions: Policy-based notification and approval trailWhat determines the choice: Define timeout, delegation, denial, and no-response behavior.
AccessTypical approach: Badge plus escortMore demanding conditions: Temporary credential limited by time and zoneWhat determines the choice: Issue only what is needed and prove automatic expiration.
RecordsTypical approach: Visit logMore demanding conditions: Purpose-limited workflow with defined retentionWhat determines the choice: Collect and retain only what policy, risk, and applicable rules justify.
Before design

What we need to know

  • Visitor and contractor types, entry points, hosts, and operating hours
  • Identity, approval, escort, safety, denial, and exception policies
  • Badge, credential, accessible check-in, and emergency-accounting needs
  • Access, directory, calendar, messaging, and identity integrations
  • Notice, consent, privacy, retention, deletion, and record-owner decisions
At closeout

What you should receive

  • Visitor-type and decision matrix
  • Arrival-to-departure workflow and accessible fallback
  • Temporary credential, badge, host, and retention configuration
  • Scenario-based acceptance and expiration evidence
  • Reception, host, security, and administrator operating guides
Equipment examplesSee relevant hardwareView details
Best fit

When this service makes sense

  • Facilities with defined hosts, restricted spaces, and temporary access
  • Organizations that need repeatable multi-site visitor policy
  • Sites coordinating reception, intercom, access, badges, and notifications
  • Operations prepared to establish data-minimization and retention rules
Before we commit

What we verify first

  • Visitor technology does not establish legal identity or authorization policy by itself
  • Identity documents, photos, watchlists, and visit history can create privacy, security, and retention obligations
  • Accessible entry and communication need physical and procedural alternatives, not only a touchscreen
  • Directory, calendar, messaging, and access integrations depend on supported interfaces and owner-managed permissions
Site contextSee where this work is usedView details
Where it is used

How site conditions change the design

Occupancy, operating hours, user activity, regulation, weather, construction, and access can change the design.

Common questions

What people usually ask

Should visitors scan an identity document?

Only after the organization defines the purpose, authority, fields needed, storage, access, retention, deletion, breach impact, and an alternative process. More data is not automatically better security.

Can a visitor receive a mobile credential?

Yes when the visitor’s device, identity and approval policy, access platform, connectivity, expiration behavior, and support path are suitable. A physical or assisted alternative may still be required.

How are contractor visits different?

Contractors may need recurring schedules, work orders, safety orientation, sponsor approval, tool or vehicle records, and area-specific access. Those responsibilities should be separated from basic visitor check-in.

Standards and referencesReview the source materialView details