Build an AI companion · the AI line
Anybody can open a free tool and get clever answers. These four sessions are about the part that makes it usable at a post: one job, written rules, a cleared phone. A test that is written down.
Build an AI companion is four sessions of about fifteen minutes each, for an officer or supervisor who wants to build one properly. Session one fixes the single job and the line it never crosses. Two writes the rule sheet, including what it must say when it does not know. Three is memory on a shared post phone and the clearing habit at handover. Four is the five-minute test, recorded, that lets a supervisor approve it. No product is named, no personal details are used, and the run writes the same five-field record as every other course in the department.
Corporate pricing on request. Course funding application status: pending.
The four sessions
Any session can be run on its own. Together they take an officer from an idea to a companion with a written job, a rule sheet and a recorded test.
A companion is a helper you set up yourself. Decide its one job first, and you will not spend a month correcting it.
Rules are what turn a clever chat into a tool. Six decisions on writing rules it can follow, and that you can check.
What it remembers stays on the phone and in the account. Six decisions on starting clean, and on clearing before the shift changes hands.
A companion earns trust the way a new officer does: by being tested on the questions you already know the answers to.
Why this line exists
Officers are already building AI companions - free tools, an hour of curiosity, one useful answer. A shift that quietly starts relying on it. Nothing about that is careless. What is missing is the paperwork that makes a tool safe: one job, written rules, a cleared phone, a test on file.
Without it, the first person to notice a problem is usually the last person who should have to. An officer, mid-shift, with a confident wrong answer and a member of the public in front of them.
These four sessions put the paperwork in place, in plain English, at the desk. And leave the officer with a companion they know the edges of.
What changes, and for whom
For the officer building one
One job, a short rule sheet and a clearing habit. That is the difference between a tool your supervisor can approve and an app that quietly answers for you.
For the supervisor
This line gives both in writing: the ban list it must refuse. A five-minute test with results kept on site - so approval rests on evidence.
For the agency
Better a controlled tool inside a written job, with a rule sheet and a recorded test. An experiment on a shared phone, holding a resident's details, is not worth the risk.
These are descriptions of the work this training addresses. They are not client results and not a promised saving.
How an agency runs the line
Nothing here needs a classroom, a training day or a new device.
The sessions stand on their own. For a first build, take them in order: the job, the rules, the memory, the test.
One printed marker per session. No classroom, no training day, no new device beyond the phone already at the post.
Both live on site, dated, where a supervisor can see them. They are the evidence that the companion was checked.
Every session writes the same five-field row as the rest of the department.
Every session writes the same five-field record. The four sessions file the same way as the rest of the department, with the same bar asked of every officer. Which is what makes the record 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 printed points
Print each marker, fix it at the point named, and the session runs there on the officer's own phone.
OYA-AR-AICOMP-1Guard house desk - the companion's job
OYA-AR-AICOMP-2Desk board - the rules sheet
OYA-AR-AICOMP-3Post phone - clearing what it remembers
OYA-AR-AICOMP-4Desk board - the test sheetEvery 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.
Before you run it
The next step
Four sessions, fifteen minutes each, at the desk and on the phone the officer already carries.
Post training. Not a SACE programme.