Security guard software
for public institutions
A public contract is graded on records: who entered the building, whether the patrol was really made, which officer was on the post and whether their documentation was in order. All four are captured as the shift happens, and every change to them is written to an activity log with a name and a time.
Real product screenshots
Where public contracts get into trouble
Access records that cannot be produced
The entry book exists, but finding who came into the building on a given morning means reading handwriting nobody can read.
Documentation that expires quietly
An officer whose training or licence lapsed months ago is only discovered when the institution asks for the file.
Reporting that eats the supervisor's week
Assembling attendance, rounds and incidents by hand every month is time nobody has, and the result is still contested.
How a public institution runs on CGuardPro
Entries recorded as they happen
Visitors, contractors and vehicles are registered with who authorised them and the plate, with entry and exit times, and the log stays searchable afterwards.
Patrols verified, not signed
QR checkpoints along the route, validated against position, sequence and the hours the rule applies to, so a completed round means a walked round.
Every officer with their own file
Identification, training and licences with their expiry dates, swept automatically so the ones coming due surface before anyone asks for them.
An activity log behind everything
Changes to schedules, reports and records are written with the person and the time, so the file can be explained rather than defended.
What the institution gets
- Searchable visitor and vehicle records with authorisation and exit times
- Patrols verified by time, position and identified officer
- Officer documentation with expiry dates and automatic reminders
- Attendance recorded per post, with late arrivals visible as such
- An activity log naming who changed what and when
- Exportable records for the period the contract asks for
Frequently asked questions
Can we produce the access records for a specific day? +
Yes. Every entry records the visitor or contractor, who authorised it, the vehicle and plate, and the entry and exit times, and the log is searchable by date, site and person.
How is a patrol proven rather than claimed? +
Each checkpoint scan carries the time, the phone's position and the identified officer and is validated when it reaches the system, so a scan made from the wrong place or out of sequence does not count as a completed point.
Does it track our officers' training and licences? +
Yes. Each officer has a document file with expiry dates, and the ones coming due are raised automatically instead of being noticed when the institution asks for the file.
Can we show who changed a record and when? +
Yes. Changes are written to an activity log with the person and the time, and you can read the log for one person or for one site — which is usually what a review actually asks for.
Does every officer see everything? +
No. Roles decide what each person reaches, and they are editable: an officer sees their own shifts and posts, a supervisor their area, a manager their contract. Permissions can also be granted or denied to one specific person.
Can the institution consult the activity without going through us? +
Yes, if you want them to. Their portal is limited to their own sites and shows the rounds completed, the reports filed and the incidents raised, with the real times.
Records that answer the question
Book a demo and we walk one public building with you: the entry log, the verified round, the officer's file and the activity log behind all of it.