For the officer on a shared phone
The next shift sees everything you typed
Practical habits: start a new chat for a new task, clear at handover, and keep anything worth keeping in the site's own document instead.
Build an AI companion · session 3 of 4
Memory is what makes a companion useful and what makes a shared phone risky. This session is the habit that keeps both true.
Six decisions about memory: what remembering means in plain terms, one task one chat, clearing before handover, a resident's details from last week, who can read the history. The safe way to keep useful notes.
Corporate pricing on request. Course funding application status: pending.
The scenario
Memory is the difference between a tool you brief each time and one that already knows your post. That is useful, and on a shared phone it is also the thing that carries the last officer's mistakes into your shift.
Officers rarely think about it, because a chat looks like a conversation and conversations end. A chat does not end. It sits on the phone, and often on an account, until somebody clears it.
The habit is small and fits the handover everyone already does: new task, new chat; shift change, clear it. Anything worth keeping goes in the site's own record.
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 on a shared phone
Practical habits: start a new chat for a new task, clear at handover, and keep anything worth keeping in the site's own document instead.
For the supervisor
A companion that remembers a resident's details is holding personal data on a shared device. This session makes the clearing habit part of the handover.
For the agency
One officer's convenience becomes the next officer's exposure. A short session on memory and clearing is the cheapest control the agency has.
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.
One printed marker where the post phone is kept.
One task one chat, clearing at handover, the details from last week, and who can read history.
The same clearing step every shift change, like signing the log - not a decision to be remembered.
One row, the same five fields as every run in the department.
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 3 of 4 in Build an AI companion.
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
Build an AI companion · session 3 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.