Standard — every customer
Pass/fail on the criteria you select per scenario, completion status, full attempt history, CSV export.
Defencify VR, powered by AGOGE — available to security companies through Defencify.
How we score
AGOGE VR records what your officer saw, said and did — second by second — and turns it into a report a trainer signs. Pass/fail on the criteria you choose. The full picture when you want it.
| Reader | Their question | The page’s answer |
|---|---|---|
| Training officer / FTO | “Does this help me coach, or just grade?” | The timeline + labeled AI notes + your sign-off. Coaching mode by default. |
| Ops / owner (security co.) | “Will my client accept this as training?” | Pass/fail on criteria you choose, per role. Exportable. |
| Risk / counsel / insurer | “Can I prove this guard trained to a standard on this date?” | A timestamped, human-signed record. “Prove it,” not “did it.” |
| LE command | “Is this the thing our union is fighting?” | No. AI interprets; your trainer decides. Nothing about an officer is auto-scored into a file. |
Every session is read against three questions, not one blended score that hides which one someone missed.
Decision
Was the force option right for what was known at that moment — not in hindsight.
“Held fire while the hand was concealed — force matched what was known at 00:13.”
Communication
Did they identify themselves, give clear direction, and try words before tools.
“First command given at 00:02, no self-identification before it.”
Tactics
Distance, cover, positioning, and whether they called it in.
“Cover reached at 00:07; distance never closed inside the reactionary gap.”
A trainer can’t watch six things at once. The system records all of them, in order.
What they saw
the cue, the moment the object was confirmed
What they said
every command and radio call, timestamped
What they did
position, movement, tool selection
When
every one of the above, in order, down to the tenth of a second
The headset logs every event with a timestamp. Nothing is scored on the headset.
Intervals, distances, counts. Plain math, repeatable, no opinion.
Your criteria, your thresholds, your role profile → pass or fail.
The AI reads the evidence and writes what it sees, labeled as the AI's reading, citing the rule it applied and the timestamp.
Your trainer confirms, adjusts, or overrides — with a reason — and signs. That signature is the record. Not the AI.
Pass/fail on the criteria you select per scenario, completion status, full attempt history, CSV export.
The evidence timeline, the AI reading, the trainer-signed record, reaction intervals against the scenario’s decision window, trends over time, roster view.
Sold through Defencify — ask them for it.
A security officer who keeps distance, gives direction, and reports it did the job. A patrol officer with a duty to act is held to a different line. The same run can pass under one profile and fail under the other — and the report tells you which yardstick it used.
One real scenario run, fully interactive. Every number below is fabricated for demonstration.
Pass/fail is computed from the criteria your admin included for this scenario and role profile. Every line points at the moment in the run that decided it. No AI is involved in this block.
| Criterion | Result | Evidence |
|---|---|---|
| Engagement was appropriate (contact inside the protected post; disengage remained available) | Met | 00:00–00:07 |
| Identified self as security before first command | Not met | 00:01.8 — first utterance was a command; no "security" in transcript |
| Verbal direction given before any tool use | Met | 00:01.8, 00:12.1 |
| Reactionary gap ≥ 10 ft while unengaged | Met | min 11.4 ft at 00:06.9 |
| No draw / OC before a weapon was confirmed | Met | 00:13.2 — no tool drawn at any point |
| Reported to dispatch within 120 s of resolution | Met | 00:21.3 (8.1 s) |
| Shots on target ≥ 60% | Recorded | Excluded by your admin — no firearm in this loadout. Still recorded. |
What the trainee saw, what the subject did, what the trainee said and did — in order, with the derived intervals drawn against the scenario's expectation window. Early and late are both flags; nothing here rewards speed.
Never one blended number. Under each axis the AI's reading of the evidence is labeled as exactly that — an interpretation, citing the rule it applied and the timestamps it used — until a trainer confirms, adjusts (one band, with a reason), or adds to it.
SEC-DEC-02 No force option before a threat is confirmed; disengage-and-report is a correct outcome (CA BSIS Power to Arrest).ENG-01 Draw-to-shot faster than ~0.38 s implies anticipation (Blair 2011).SEC-COMM-01 Identify as security before directing a member of the public; never imply peace-officer status.SEC-COMM-03 State the reason for contact when time allows; direct commands over vague ones.COMM-PRO-01 Profanity flag (perceived-excessive-force finding); volume delta is descriptive only.SEC-TAC-02 Create distance and use cover before contact; hold position while a hand is concealed.SEC-TAC-05 Report to dispatch within the post-incident window; include subject status.M. Webb across 4 attempts of Federal Lobby (SEC-002). First-exposure runs are the honest number; repeats are partly recall.
Flagged: a repeat attempt of the same scenario appears in this trend.
| Trainee | Percentile | Flag |
|---|---|---|
| M. Webb | 82th | Standout |
| D. Price | 71th | — |
| E. Vasquez | 64th | — |
| A. Thompson | 58th | — |
| R. Chandler | 51th | — |
| K. Nguyen | 44th | — |
| J. Alvarez | 37th | — |
| S. Okafor | 29th | — |
| T. Brandt | 12th | Needs attention |
Every pass/fail is computed from the session’s event stream and is recomputable. Items marked AI interpretation are model output pending trainer confirmation.