Security patrols and incidents in one traceable flow.
A security operation produces paper every hour: patrol logs, incident reports, lost property entries, footage request forms. When those records live on clipboards, in group chats or in separate spreadsheets, patterns go unnoticed, accountability gets fuzzy and an audit becomes a scramble. Tenderely BPM ties patrol rounds, incident handling, lost property and CCTV requests into one structured flow that guards can use from a phone and managers can review from anywhere.
What does a security operation repeat every day?
01
Patrol rounds
Guards move through a fixed set of checkpoints on a schedule. Without a structured log, there is no way to tell whether a point was visited or simply skipped.
02
Incident reporting
When something happens, someone writes it down. The first account captures what was seen; the investigation adds what was found; management decides what happens next.
03
First response handover
The guard who spots an incident hands it to a supervisor, who may escalate further. Each handover needs to carry the full context, not just a verbal summary.
04
Lost and found property
Items are handed in, described, stored and either claimed or disposed of. A register that is a notebook gives no search, no audit trail and no reminder when storage time expires.
05
CCTV footage requests
Someone asks to review camera footage. The request, the reason, who authorised it and what was done with the recording all need to be logged to meet data-protection obligations.
06
Shift handover
The outgoing team passes open incidents, unclaimed property and anything unusual to the incoming team. When the handover is verbal, things fall through.
Where does this break down today?
The patrol log proves nothing
A paper sheet signed at the end of a shift shows the guard was present, not which points were visited and when. In a dispute or an inspection, that difference matters.
Incidents lose detail on the way up
The first report goes to a supervisor by phone or message. By the time it reaches management, the original wording has been summarised, and what was actually said is gone.
Lost property is ungoverned
Items sit in a box or a drawer. Nobody is reminded when the retention period ends, nobody can search by description, and when something goes missing from that box there is no record of who had access.
CCTV requests leave no trace
A manager verbally authorises someone to pull footage. Under data-protection rules that transaction should be documented — but if the documentation is an e-mail thread it is effectively invisible in an audit.
What changes with Tenderely BPM
01
Every checkpoint is a timestamped record
Guards log each patrol point from their phone as they move. The time, the point and who logged it are captured at the moment it happens, not reconstructed at the end of the shift.
02
Incident steps are enforced, not suggested
First response, investigation and management review are sequential steps in one flow. The next step does not open until the previous one is completed, so nothing is skipped and every stage is recorded.
03
Conditional routing without code
A minor incident can close at supervisor level; a serious one automatically branches to management review. The rule lives in the flow, not in somebody's judgement on the day.
04
Waiting steps remind themselves
Set an SLA on any step and the system notifies when time is running out. An incident that should have been reviewed in four hours does not sit quietly for four days.
05
Lost property and CCTV requests are searchable and auditable
Every item entered and every footage request authorised becomes a structured record. Tenderely keeps the full audit history — who created it, who changed it, who approved it and when.
06
Guards already in your system
Security personnel are linked to the personnel record you already have on the platform. There is no duplicate roster to maintain.
FAQ
Can guards use this without a laptop?
+
Yes. The same flows run in the iOS and Android apps, so a guard on foot can log a patrol point, open an incident or record found property from their phone. Approvals and reviews happen on mobile too, so a supervisor does not need to be at a desk.
Can we control who sees incident reports?
+
Yes. Role- and unit-level permissions decide who can open, edit or approve each record. A guard may submit a report without being able to view other guards' submissions, and sensitive fields can be hidden from specific roles.
How does the CCTV request log help with data-protection compliance?
+
Each footage request is a structured record: who requested it, the stated reason, who authorised it and what action was taken. The audit history is preserved automatically, so you have a documented trail without assembling it from e-mail threads.
Can an outsider such as a contractor or a visitor report an incident?
+
Yes. A public form can be published as a link so that anyone with the link can submit a report without needing an account. The submission lands as a record in your flow and follows the same review steps as an internally created incident.
Does this work alongside the security module we already have, or does it replace it?
+
The module installs into Tenderely BPM and connects to any personnel or HR records you have already set up on the platform. It is a starting point: the forms, workflows and dashboards are pre-configured, and you adjust them to your site's layout and rules without writing code.