What each instruction promised, and what the network actually did afterwards. Shown whichever way it went.
53 of 55 acted on46 expired undecided
0 of 2 readof outcomes due a reading
Nothing has been read yet, so there is nothing to set against the promises.
Totals across 0 measured of 2 outcomes
Measurements from two separate days are needed before a line can be drawn. Widen the period, or wait for the next reading.
| Outcome | Did it help | Promised | Measured | Against promise |
|---|---|---|---|---|
| 4DFD52D916:18–17:18 | Never verified | −0 | ||
| 6EC13CDB14:14–15:14 | Never verified | −0 |
Nobody confirmed this was actually applied, so there is no "after" to measure.
Recorded as your judgement, under your name — never as a measurement.
Recorded as your judgement, under your name — never as a measurement.
Only 3 proposals have been decided. Rates are not shown below 10, because a percentage on a handful of decisions moves too much to mean anything.
1 labelled example. This is an export for offline work — nothing in this platform retrains itself from it.
Only 0 proposals have been decided. Rates are not shown below 10, because a percentage on a handful of decisions moves too much to mean anything.
Officers have filed 0 reports. An accuracy figure is not shown below 10, because a percentage on a handful of reports moves too much to mean anything.
Counted across the whole system, never by officer. Whether per-officer response data may be held at all is an open question with the Public Security Directorate, and until it is answered the narrower reading stands.
1 labelled example. This is an export for offline work — nothing in this platform retrains itself from it.