The body corporate wants a report. You want to stop writing them.
Estate contracts are won and lost on reporting. The operator who can show response times per incident, on demand, without assembling anything, is a different proposition to the one who emails a spreadsheet on the fifth of the month.
- Client view
- Their site only, enforced by the database
- Response time
- Detection → named acknowledgement
- Reporting
- A byproduct of the shift, not a task
Give the client their own view — and only theirs
A trustee can log in and see incidents on their estate: what happened, when, how long it took somebody to acknowledge it, and the evidence attached.
They cannot see your fleet, your other clients, your staff list, or an incident on another property. That separation is enforced by the database rather than by which screen they are shown — which is the difference between a permission and a promise.
The number they will ask about
Response time, measured from detection to a named person acknowledging — not to a vehicle arriving, which nobody can verify, and not to a controller clicking something, which proves only that a controller was awake.
Until you are keeping that number automatically, you are guessing at it. And the month a client asks for it is never the month you have time to reconstruct it.
What the monthly report stops being
A person assembling a document from a WhatsApp group, a folder of clips and their own memory of a Thursday. The report is the byproduct of the shift, not a task after it.
See what a client sees
A sandboxed night shift — one aircraft, one estate, one intruder — ending in a real court-ready PDF. No signup, nothing to install.