AI at the gate · the AI line
A reader, a camera and a report tool each make a small decision and report it with confidence. Nobody trains the officer on the difference between what that decision is worth and what gets assumed about it. This is that training.
AI at the gate is four sessions, about fifteen minutes each, taken at the officer's own post: what a gate reader actually decides, how the exceptions and the log really work, what perimeter analytics flags and misses, and how the written account has to hold. Twenty-four decisions in total, six in each session, every one explaining what the system knew at that moment. Every session ends with the same five-field completion record the rest of the department uses: the officer, who delivered the training, the session, the date and the score. It is a record that the session was taken; it is not a certificate and not an assessment of competence.
Corporate pricing on request. Course funding application status: pending.
The four sessions
Any session can be run on its own. Together they walk a new officer through the reader, the exceptions, the perimeter and the written account.
What a reader really decides: a plate match, a flag, a blank - and the driver check it never makes.
The exceptions that fill a shift: a pass that will not read, an instruction by phone, a log line that holds.
Perimeter alerts, false alerts, blind spots - and why an uncounted dismissal is how a breach gets missed.
The account the officer signs: AI-drafted summaries, footage requests, and two timestamps that disagree.
Why this course exists
Every gate, camera and report tool in a security post makes a small decision and reports it with confidence. Officers are rarely trained on the difference between what those decisions are worth and what gets assumed about them.
AI at the gate is four sessions about that difference, taught where it shows up. At the barrier. At the exception desk. Along the perimeter. At the desk where the account is written.
Each session takes about fifteen minutes at the post on the officer's own phone. Each ends with the same record every other course here produces - so the agency keeps a history, not a memory of a briefing.
What changes, and for whom
For the officer at the gate
This is the part no product manual covers: what the reader, the analytics and the report tool can each actually decide. The judgement that stays with you when they are wrong.
For the training manager
Four sessions of about fifteen minutes, run at the post on the officer's own phone. Every one leaves a record, so the training does not wait for the next classroom date.
For the agency
Every reader and camera an agency installs needs officers who know what it decides and what it misses. These four sessions are that training, and they produce the agency's own record of it.
These are descriptions of the work this training addresses. They are not client results and not a promised saving.
How an agency runs the course
Nothing here needs a classroom, a training day or a new device.
Any session stands on its own. The order below suits a new officer: the reader, the exception, the perimeter, then the written account.
One marker per session, fixed at the point it names - the barrier head, the exception desk, the camera pole, the report desk.
About fifteen minutes each, on the officer's own phone, with a supervisor on site rather than in a room.
Every session writes the same five-field record, so four runs make one page of an officer's training history.
The markers are codes, not products. An agency with three sites prints the same four sessions for each one.
Every session writes the same five-field record. Four sessions make one page of an officer's training history, with the same standard asked of every officer. Which is the only way a record like this is fair. Content written September 2026.
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.
The markers
Each session has its own marker, fixed at the point that session is about: the barrier head, the exception desk, the camera pole, the report desk. Print them at about 80mm square, tape them flat, and keep them clean. A crease across the code is the one thing that stops a lock.
They are codes, not products: an agency with three sites prints the same four markers for each one, and if you would rather the codes were named after your own checkpoints, that can be done before the first session runs.
OYA-AR-AIGATE-1Barrier reader head - driver's window side
OYA-AR-AIGATE-2Gatehouse desk - exception log terminal
OYA-AR-AIGATE-3Fence-line camera pole - rear perimeter
OYA-AR-AIGATE-4Guard house desk - report writing stationEvery 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 course
The next step
One session, one printed marker, one officer's phone - fifteen minutes to see whether the overlay holds where your officers actually stand.
Corporate pricing on request. Course funding application status: pending.