Gateward · Intended workflow
How Gateward is intended to work
Five steps, in the order they would happen on site. Nothing here is operational yet.
- Step 01
The host pre-registers the visit
Before anyone arrives, the host records who is coming, when, and why. Contractors are registered against the contract period rather than a single day.
- Step 02
Screening runs before a badge exists
Each pre-registered person is checked against watchlists and denylists. Screening happens before badge issue, so a match is resolved at the point of decision rather than at the door.
- Step 03
Contractors acknowledge NDA and induction
A contractor cannot be granted first entry until the non-disclosure agreement and site induction have been acknowledged, and the acknowledgement is retained against the record.
- Step 04
Identity is confirmed at check-in
On arrival, identification is captured and a photo is taken. The credential issued is time-boxed to the visit or contract period and expires automatically at the end of it.
- Step 05
The host is notified on arrival and departure
Arrival and departure both notify the host, so responsibility for an on-site guest is explicit and the record shows when the visit actually closed.