Visitors
Invitations, pre-registration, QR passes, reception and a register that keeps the history.
Visitor and contractor management, compliance, and emergency mustering in one operational platform. One roll, every gate, in real time.
Ordered by how long it can safely wait.
Most recent check-in first.
Most site access problems are really reconciliation problems. The sign-in sheet, the contractor spreadsheet and the induction folder describe three different populations, and on the morning it matters nobody can say which of them is right.
Each of these describes a different population, and reconciling them is somebody’s afternoon. The question they are all trying to answer is the same one.
Nobody signs out. The last four pages are people who left hours ago.
Last edited in March. Two of the insurances on it have since lapsed.
Paper. During an evacuation it is inside the building you just left.
A visitor invited on Monday, a contractor onboarded in March and an employee scanning in this morning are the same kind of object in the same system.
One person, one profile, with every visit, document, induction and decision attached to it. A repeat registration reuses the profile instead of forking it, and a duplicate is refused rather than merged by accident.
The dashboard headcount, the on-site roster, the evacuation roll and the muster count are one number from one source. That is not an efficiency — it is the reason the fourth one can be trusted.
The screen says so and shows no figure at all. A headcount that is quietly wrong is more dangerous than one that is visibly missing.
Scroll, and the console follows. Each step is the screen that actually handles it.
A host invites a visitor, an administrator invites a contractor, or somebody registers themselves at the door. Every route creates one record, and the invitation already knows the site, the visit window and what that site requires.
Fourteen arrivals. Anything held is first.
A held visit is cleared or denied by a named person, and the decision stays on the record. Screening is fail-closed: a source it cannot reach returns “review”, never “clear”.
Documents are read by OCR and approved by a person — never by the platform on its own. Inductions are passed, policies acknowledged, and the register’s status is derived from all of it rather than typed in by whoever asked last.
| Contractor | Trade | Status | Inductions | Insurance |
|---|---|---|---|---|
| D. OkaforNorthline Electrical | Electrical | Active | Compliant | 14 Mar 2027 |
| S. BaptisteRedgum Scaffold | Scaffolding | Pending | Compliant | 02 Aug 2027 |
| L. MoreauKestrel Mechanical | Mechanical | Pending | 1 outstanding | 19 Jan 2027 |
| P. AdeyemiArdent Traffic | Traffic control | Suspended | Locked out | Expired |
Status is derived from the evidence on file and an administrator’s approval. Nobody types it in, which is what stops a register drifting away from what is actually verified.
A QR pass with a display code and an expiry tied to the visit window. Where a site has a geofence the device reports coordinates and the server decides, so a photographed QR code is worth nothing from the car park.
Headcount per site, scoped to what you may see.
A user scoped to one site sees one site — enforced on the endpoint, not by hiding a row. A site whose roster cannot be read shows no number at all rather than a zero.
A server-sent event stream keeps the list current. The dashboard headcount, the evacuation roll and the muster count are one number from one source, so they cannot disagree with each other.
| Person | Assembly point | Status |
|---|---|---|
| A. Whitmore | Assembly A | Accounted for |
| D. Okafor | Assembly A | Accounted for |
| S. Baptiste | Not reached | Outstanding |
| J. Callaghan | Assembly B | Accounted for |
The roll starts from the live on-site list, so it is already correct when it is needed. It downloads as a PDF for a warden who is off the network.
Every consequential action is written to an append-only, hash-chained log with a verify endpoint. Reports export to CSV, Excel and PDF, on demand or on a schedule you set.
Append-only and hash-chained. A verify run reports a failed check differently from a broken chain, because conflating them either raises a false alarm or hides a real one.
One live roster per site, read from the same source as the dashboard headcount, the evacuation roll and the muster count, so the three cannot disagree with each other.
Documents verified, induction passed, policy acknowledged, screening clear. The register’s status is derived from that evidence rather than typed in by whoever asked last.
An append-only, hash-chained audit log with a verify endpoint, and reports that export to CSV, Excel or PDF on a schedule you set.
A visitor invited on Monday, a contractor onboarded in March and an employee scanning in this morning are the same kind of object in the same system. That is what makes the roster trustworthy.
Invitations, pre-registration, QR passes, reception and a register that keeps the history.
Onboarding, documents, inductions, approval, shifts, timesheets and work orders.
Document groups, expiry monitoring, policy acknowledgement and incident reporting.
A live on-site roster, geofenced check-in, access credentials and emergency muster.
Analytics, scheduled reports, exports and an audit log you can verify.
80 permissions, 9 roles, site scoping, SSO with MFA, retention and integrations.
Seven steps, in order. Every one of them writes to the same record, which is why the last one can be reported on and the fifth one can be trusted.
A person exists in the system before they exist on the site.
The invitation carries the site, the visit window and what is required.
Identity, documents and screening are settled before arrival, not at the door.
A QR pass at reception, a kiosk, or a phone with no app installed.
The on-site list is live, and it is the same list everything else reads.
When something happens, the roll is already correct.
Departure is an event, not an absence of one.
Seven views of the same platform, chosen by the job you would be doing in it. Reconstructions of the real console — drawn rather than screenshotted, so they can be shown publicly without carrying anybody’s names, sites or compliance status onto this page. Every control is the product’s own; every person is invented.
Ordered by how long it can safely wait.
Most recent check-in first.
On site now, active contractors, documents pending review and credentials expiring soon — the four the console computes, over a roster kept live by a server-sent event stream. Beside them, everything waiting on a person, ordered by how long it can safely wait: a visitor held at a gate ranks above a credential with thirty days on it. When the roster cannot be read the screen says so rather than showing a number it cannot stand behind.
Occupancy as height, the geofence as a ring, and the whole estate on one plan. Choose a site to scope it the way the product scopes it — or activate a muster and watch every site change state at once.
Check-in coordinates are verified against this boundary on the server. A user scoped to this site cannot read the others — through the console or the API.
Drawn in CSS rather than WebGL: a 3D renderer would cost more than this entire website transfers. Every site, figure and boundary is invented; sites, geofences, per-site occupancy, site-scoped access and mustering are all real capabilities.
An emergency is the wrong moment to discover that the sign-in book is in the site office. Activating a muster turns the live on-site list into a roll, and the count of who is still outstanding is the number in front of the warden.
| Person | Assembly point | Status |
|---|---|---|
| A. Whitmore | Assembly A | Accounted for |
| D. Okafor | Assembly A | Accounted for |
| S. Baptiste | Not reached | Outstanding |
| J. Callaghan | Assembly B | Accounted for |
The roll starts from the live on-site list, so it is already correct when it is needed. It downloads as a PDF for a warden who is off the network.
Arrivals, occupancy, compliance and activity over time — with the product’s own honesty about what a number does and does not mean. An average taken over days that saw no arrivals is not an average of anything, and the panel says so on screen rather than in a footnote.
Last 14 days, Harbour Depot.
The average counts only days that saw arrivals, and the panel says so. A mean that divides by fourteen when two of them were a closed weekend is a smaller number than the truth.
Hiding a button is not access control. In VCMS a permission is checked on the endpoint, and a user scoped to one site cannot read another one by calling the API directly.
VCMS does not ask your organisation to come and look at it. Each destination below is implemented, and each one refuses by naming the exact setting it is missing rather than failing quietly.
Your own endpoint, with a signature it can verify.
Cards into the channel the site team already watches.
List items, and a document library mirrored from approved evidence.
Push datasets, so the figures land in the reporting you already run.
Google or Microsoft sign-in, honouring your own MFA policy.
Email through your SMTP, or a delivery provider. SMS as an opt-in.
Barrier release can be handed to a site access control system over a documented, signed bridge. Where no bridge is configured the platform reports that it commanded nothing — it does not draw a success state over a door that never opened. Access control vendors the platform does not integrate with are deliberately absent from this page, and the build fails if one of them appears on it.
The problems differ by industry, but they rhyme: a workforce that changes weekly, evidence that expires, and an obligation to know who was where.
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 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.