Breach reports a court can check for itself
A breach becomes a signed evidence document, with the location history behind it. Each document carries a hash and a verification code, so a court can check a printout has not been altered.
Signed evidence documents
A breach report sets out the order, the condition broken, the alarm, the positions before and after, and how the control room responded, with a map. It is signed by the issuing officer.
- Official letters and SMS to the person produced from the same case
- Location history for any period, on the same footing
A code a court can verify
Every document carries a hash of its contents and a verification code. Anyone holding the printout can check the code against the platform and see whether it matches what was issued.
The court portal
A court registrar sees the court's own cases and nothing else: the people the court has placed on monitoring, a compliance summary for each, and the evidence reports requested and received.
Evidence requests
The court requests a report for a case and a period, the agency produces it, and the registrar downloads it from the portal. Each request, each document and each download is written to the audit trail.
See it on your own cases
Send us the orders your agency places on monitoring, how many people are on monitoring or expected to be, and how alarms are handled today. An engineer replies with a pilot plan, a deployment plan and a proposal.