A workforce that changes weekly, evidence that expires, and an obligation to know who was where. What differs is which of those hurts most.
Each one lists the capabilities that tend to matter first. None of this is a claim about who uses the product. It is a claim about what the product does.
Many sites, most of them staffed by somebody else’s people.
Contractor compliance is the whole problem: a workforce that changes weekly, licences that expire, and an obligation to know who was where. Site-scoped access keeps each depot’s data to that depot.
A gate, an induction, and a roll that has to be right in ninety seconds.
Inductions before access, geofenced check-in at the boundary, and a muster that starts from the live on-site list rather than from a sign-in book somebody has to find.
High-consequence work by people who do not work for you.
Controls of the kind a permit system needs: approvals before a pass is issued, policy acknowledgement that can hold access, and credentials that are revoked the moment somebody is archived.
A reception desk that should not need a paper book.
Hosts invite the people they are expecting, visitors arrive to a pass that already exists, and the front desk sees the day ahead instead of transcribing names.
Controlled areas, contractors, and records that must survive scrutiny.
Screening before entry, an append-only record of every decision, and retention rules that dispose of personal information on the schedule you set rather than on the one nobody set.
Campuses where the visitor and the contractor arrive at the same door.
One check-in surface for both, different questions for each, and a live roster per campus that the emergency plan can actually use.
VCMS is multi-tenant by construction, and a tenant can look quite different from its neighbour without a separate build.
A walkthrough with your site list, your contractor mix and the compliance evidence you actually have to collect. No obligation, and no access to anybody’s live data.
