Security example
Long Lever Security
Patrol and keyholding reporting
How officer reports were captured once and turned into client-ready evidence of patrols and response times, without anyone assembling it by hand.
- Work type
- Capture and client reporting
- Built for
- Managing director and clients
- Time to first report
- First patrol cycle
- Document
- Example brief
Paper → one place
Officer reports
Standardised fields, same shift routine
Response times
Measured
Not estimated after the event
Client-ready
Evidence
Produced without manual assembly
The problem
Officer reports were written on paper and sent in by phone photographs. Turning them into something a client could see, and measuring response times, was a manual job that rarely got done.
When a client questioned a patrol, the answer depended on someone scrolling through their phone.
What we did
We captured the reports in one place, standardised the fields, and produced clear evidence for clients alongside response time measures.
The shift routine did not change, which is why it held. Officers record the same things in a tidier way, and the client view builds itself from those records.
What was put in place
- Standard fields: site, time, check completed, exceptions
- One record per visit, captured at the point it happens
- Response times measured from the same records
- Client view published without manual assembly
The result
Client-ready evidence of patrols and response times, produced without anyone assembling it by hand.
The same evidence now supports renewals and new bids, because it is a record rather than a recollection.
About this example
Real work, Long Lever name
Your version
Your name, your logo, your colours
Want to see the schools side?
Long Lever Partnerships · example document. Organisation names in this document are fictitious and used to illustrate real work; no client, supplier or individual is identified. Everything shown can carry your own name, logo and colours.