AI at the gate · session 2 of 4
Every gate has a queue of things that do not fit the system: a pass that will not read, a visitor nobody confirmed, an instruction from a supervisor by phone. The decision is small. The record of it is not.
Six decisions about the exceptions: the pass that will not scan, the instruction from a supervisor, the unannounced visitor, the expired pass, the driver who turns aggressive. The line you write afterwards. The session trains the habit that separates a defensible post from an indefensible one: decide, then record the reason, at the moment it happens.
Corporate pricing on request. Course funding application status: pending.
The scenario
A gate that only ever matches never needs an officer. The officer exists for the exception. The pass that will not read. The driver nobody logged. The caller who says he is expected. The supervisor on the phone who says to let this one through.
Each of those decisions is small, and each one is invisible a month later unless it was written down. This session is about the writing down as much as the deciding. Your line has to show somebody who was not there three things: what the system showed, what the officer did, and who stood behind it.
An officer who decides well and records it is doing the whole job. An officer who decides well and says nothing has left the agency with a decision it cannot defend.
The six decisions are the ones that actually go wrong on a quiet shift. They are, in the order the run puts them:
What changes, and for whom
For the officer at the desk
The reader handles the ninety vehicles that match. You handle the ones that do not, and you are judged on those. This session is a rehearsal of the six that go wrong most often, with the reason each one has to be written down.
For the supervisor
An officer who logs your instruction is protecting you both. An officer who can say no politely to a caller is worth more than one who cannot. Both habits are trained here, at the desk, in fifteen minutes.
For the agency
Tenant complaints and access disputes are settled by the exception log, not by memory. An agency whose officers write a complete line at the time has a defensible record; one that does not, does not.
These are descriptions of the work the training addresses. They are not client results and not a promised saving.
What the officer does, in order
About ten minutes at the post, on the officer's own phone, with a supervisor on site.
The marker goes at the desk where the log terminal sits. The overlay marks the desk, the barrier line and the visitor bay, so the decisions happen in the geography of the actual post.
The exception point, the walk line and the person to call appear over the live picture, anchored to the desk.
Each is an exception an officer meets in the first month, with immediate feedback and the reason the log line matters.
The run closes with the five-field record, the same as every other course here.
Every session writes the same record, so four sessions make one page of that officer's training history, and the same five fields are asked of the newest officer and the most senior one - which is the part of it that is fair. The run is written to the agency's list in the five fields the checklist reads.
This page is the session. The run itself is on the player: open it here - the practice run needs no camera. It is session 2 of 4 in AI at the gate.
This is post training, so there is no assessor to satisfy - but the record matters anyway: it is how an agency shows what its officers were trained on, in what order, and when.
| Field | What it carries |
|---|---|
| Name | As written in the agency's own staff record. Nothing else is stored about the officer. |
| NRIC / FIN | The last four characters only. The full number is never entered and never leaves the phone. |
| Training provider | Whichever name the checklist route puts here: the agency's own name when the agency delivers the training in-house, or the service provider's name when a provider delivers it - in that case the checklist also asks the agency to submit the provider's invoice showing simulation training was used. The field is left blank on purpose: it is typed, not assumed. |
| Course title | States the technology: the training programme or session plus Augmented Reality (AR) Simulation Training. |
| Date of training | The date the run was completed, written from the device at the time of the run. |
The record lives on the officer's own phone until it is exported or printed, so the habit is: run it, then save the list. The house standard is 80 per cent, which is a fair bar for six decisions, and a failed run is a re-run rather than a mark against an officer.
Every course here is honest about what it is and what it is not, because a package that oversells itself is the one that lets an agency down in front of an assessor. Read these before you book anything.
Questions about this session
AI at the gate · session 2 of 4
Fix one marker at the real point, open the session on a phone, and see whether the overlay holds where your officers actually stand. That is a fair test, and it takes three minutes.
Corporate pricing on request. Course funding application status: pending.