AI at the gate · session 4 of 4

The account the officer signs, and the tool that drafted it

A report is read weeks later by people who were not there, sometimes at an inquiry. What it says is the officer's responsibility - not the software's, and not the supervisor's.

Six decisions about the written record: a summary that left out the unlocked fire door, a clip someone wants forwarded to a chat group, what belongs in an account and what does not, a report for another officer's decision, an AI-assisted draft. Two timestamps that disagree. It is the session that keeps the other three from being undone by a bad write-up.

Corporate pricing on request. Course funding application status: pending.

Session4 of 4 in AI at the gate
Decisions6, one correct answer each
Marker1 printed point at the report desk
Recordthe five fields, same as every run

The scenario

The incident account, the system log, and the evidence rules around both

An incident takes four minutes. The account of it is read for months: by a supervisor, by a tenant, by an insurer, sometimes by a court. Almost everything that goes wrong afterwards goes wrong in the writing, not in the incident.

The tools have changed what writing looks like: a dictated summary, a drafted paragraph, a report built from a few key words. They have not changed who signs it. The officer does, and that is the fact this session is built on.

Four habits come out of it: read what you sign, keep the facts and the order yourself, name who decided, and never quietly make two records agree.

The six decisions are the ones that actually go wrong on a quiet shift. They are, in the order the run puts them:

  • The AI summary that dropped the unlocked fire door
  • The clip somebody wants forwarded to a staff chat group
  • What belongs in an account of an incident, and what does not
  • The report for a decision another officer made and signed for
  • The AI-drafted report, and what the officer still owns
  • Two timestamps that disagree, and the wrong way to fix them

What changes, and for whom

Three people, three different changes

For the officer writing it

You sign it, so it has to be yours

The tool that drafted the words does not answer for them. This session is about reading the draft against what actually happened, and about the parts only the officer knows. The order of events and the decisions.

For the supervisor

Most complaints turn on the report, not the incident

An account with the facts, the actions and the authoriser in it ends most disputes in a paragraph. One with omissions ends in a meeting. Fifteen minutes at the desk is cheaper.

For the agency

The record is the agency's protection and its exposure

Footage forwarded to a chat group, a report signed for someone else's decision, a timestamp quietly edited. Each one turns a routine incident into a liability. The session trains all three.

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

One run, start to record

About ten minutes at the post, on the officer's own phone, with a supervisor on site.

Scan the marker at the report desk

The marker goes where reports are written. The overlay marks the desk, the log terminal and the incident points the account has to cover.

Read the overlay

The account points and the escalation line appear over the live picture, anchored to the desk.

Take the six decisions

Each one is a writing decision with a consequence, with immediate feedback.

Write the record

The run closes with the five-field record - the same record every other session produces.

The trainee list

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 4 of 4 in AI at the gate.

A completed session produces one row, in these five fields

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.

The five fields every run here writes, plus the score and the time on task, kept in the agency's own record.
FieldWhat it carries
NameAs written in the agency's own staff record. Nothing else is stored about the officer.
NRIC / FINThe last four characters only. The full number is never entered and never leaves the phone.
Training providerWhichever 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 titleStates the technology: the training programme or session plus Augmented Reality (AR) Simulation Training.
Date of trainingThe 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.

What this package does not claim

The limits, stated on the page rather than found later

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.

  • Nothing here is legal advice. Record keeping, footage and personal data are governed by the PDPA and the agency's own policy. The session only trains the habits that keep an officer on the right side of them.
  • It does not replace the agency's report format, its escalation matrix or its discipline process.
  • It does not claim any AI drafting tool is accurate or safe. It assumes the tool may be wrong, which is why the officer reads what he signs.
  • A drill is not a guarantee, and no report has ever prevented an incident. What it does is give the agency a record in the officer's own words, in the order events happened. Written to be read by people who were not there. Whether it holds is for the inquiry to decide, not something this page can promise.

Questions about this session

Straight answers

Is this about any particular AI writing tool?
No. The rules - the officer reads it, corrects it and signs it. The facts and the order stay the officer's - apply to every drafting tool, and they will outlast all of them.
Is this a SACE course?
No. It is post training on the record, and it carries no mandated volume. The three SACE programmes remain the licence-renewal line.
Does the session give legal advice on the PDPA?
No, and it says so on the page. It trains the habits - ask before copying, do not forward footage, keep the record to its purpose. And the agency's own policy decides the detail.
How long does it take?
About fifteen minutes, scored at the same house standard as every other course here.

AI at the gate · session 4 of 4

Run it on your site before your officers do

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.