Security guard software
for banks and branch networks
A branch network is many small posts where the same routine has to happen every single day, and be provable afterwards. Opening and closing attendance is verified against the branch, the round is scanned rather than signed, the panic alert reaches your monitoring center, and the whole history is there when the bank audits the contract.
Real product screenshots
What a branch network exposes
One officer per branch, and no way to see them all
Every branch has its own post and its own routine, and a supervisor can physically visit a couple of them in a day. Whatever is not recorded simply is not known.
Opening and closing taken on trust
The most sensitive minutes of the branch day are also the ones with the least evidence that the officer was actually there.
Audits that ask for a year of records
The bank asks for attendance, rounds and incidents across the whole network. Assembling that from spreadsheets is weeks of work and still full of holes.
How a branch network runs on CGuardPro
Attendance verified at the branch
Officers clock in with a selfie and the phone's position, checked against the post, so the opening is done by the assigned officer at the assigned place.
The branch routine as rules, not habit
Each post carries its own patrol rules — frequency, tolerance and the hours they apply — so opening, closing and the rounds in between are checked instead of remembered.
Duress goes to the monitoring center
The panic button opens an alarm with the officer identified and located, alerts the supervisors and the nearby officers, and stays open as a case until it is closed.
One live board for the whole network
Who is on duty, at which branch, which posts are uncovered and which alarms are open — across every branch, on one screen.
What the bank gets
- Opening and closing attendance verified by selfie and position
- Patrol rules configured per branch, checked automatically
- Panic and duress alerts routed into your monitoring center
- Alerts the moment a branch post is left without cover
- Officer credentials and training documents tracked with their expiry dates
- A full history per branch, exportable when the contract is audited
Frequently asked questions
How do we prove the officer opened the branch on time? +
The clock-in carries a selfie, the phone's position and the time, checked against that branch before the shift is accepted. Late arrivals and early departures are visible as such rather than being smoothed over.
Can each branch have its own routine? +
Yes. Rules are set per post: which checkpoints, how often, what tolerance and during which hours. A downtown branch and a supermarket branch can run completely different routines inside the same contract.
What happens when an officer presses the panic button? +
An alarm opens in your monitoring center with the officer identified and located, the supervisors and nearby officers are notified, and the alert stays open as a case until someone closes it — including when the same alert arrives more than once.
The bank audits us. Can we produce the records? +
Yes. Attendance, rounds, incidents and gate entries are stored per branch with their real times and can be exported for the period requested, instead of being rebuilt from spreadsheets.
Can it warn us before an officer's license expires? +
Yes. Each officer has a document file with expiry dates, and the system raises the ones coming due — so a lapsed credential surfaces in a report rather than in the bank's audit.
Who inside our company can see which branches? +
Roles decide it and you can edit them: a regional supervisor sees their branches, a dispatcher sees the live board, an account manager sees their client. Every action is written to an activity log with a name and a time.
See one branch, then the whole network
Book a demo and we set up a branch opening, its round and its duress alert — then show what the same thing looks like across a whole network.