Guard management software: what to ask your provider for
Good guard management software shows you the same picture your provider sees: time-stamped patrols, incidents with evidence, reports, the shift roster and the history. Ask for access to the history, export of your data and access roles, written into the contract. If the provider cannot show you what happened last night without emailing you, you do not have visibility; you have promises.
Updated: 5 min read
What should a client be able to see in security guard software?
Five things: patrols, incidents, reports, shifts and history. All with a time, a place and a name, without anyone in between writing them up.
- Patrols: which checkpoints were scanned, when and by whom, and which were missed. See the checkpoint patrols guide.
- Incidents: what happened, when it was reported, with photos or notes, who acted and when it was closed.
- Reports: the shift report and periodic reports, available without asking. The shift report guide shows what they should contain.
- Shifts: who was rostered, who turned up and when, and how the handover went.
- History: all of the above for past months, searchable, not just today.
Why does it matter to see security data live?
Because a report that arrives afterwards shows only what someone chose to write. A live picture shows what is happening now, and makes the gaps visible.
A patrol recorded as it happens cannot be filled in the next morning. An incident opened in the system with a time leaves a trace even if nobody phones it in. That difference turns guarding from a promise into something you can measure.
OVIT runs on the Guardly platform: every post, patrol, access event and incident enters one live record, and the client’s team sees the same picture as the operations centre, from the first signal to the final report.
Who owns the security data, and can I take it with me?
The contract decides that, and you should be the one to set it. Ask in writing for your site’s records to be handed over in a readable format, and for what happens to them when the contract ends.
- Export: can you download patrols, incidents and reports in a format that opens without the provider’s software?
- Retention: how long is the history kept, and who decides?
- Exit: what do you take with you when you change provider, how quickly, and when is the data deleted from their system?
- Personal data: the records contain people’s names, times and locations; the contract must say who is responsible for them and what they are used for.
The history is the most valuable part of the relationship when you change company. The switching security company guide explains how to hand over without gaps.
Who should have access to guard management software?
Everyone only to what their job needs. A site manager sees their own site, head office sees all of them, and a guard sees only their shift and instructions.
- Access roles per site and per person that you can manage or change easily.
- Access removed immediately when someone leaves your company.
- A log of who viewed or changed what, so a record cannot be quietly corrected.
- Restricted visibility for sensitive incidents that not everyone should see.
What should I ask a security provider about its software?
Ask for a demo on a real site and ask ten specific questions. The answers should be shown on screen, not described.
- What do I see as the client, and what does only your centre see?
- Show me last night’s patrols: times, checkpoints, misses.
- How is an incident recorded, and how soon do I find out?
- Can anyone change an entry afterwards, and does the change show?
- How can I see who came on shift and when?
- How far back does the history I can see go?
- In what format can I export my data?
- What do I receive when the contract ends?
- How are my own people’s access rights granted and revoked?
- Can I message your centre through the system, and is that conversation recorded?
Put these next to the questions to ask before signing with a security company.
What are the warning signs in security guard software?
Data that only arrives as a PDF at month end, entries without a time or place, and a system the provider cannot show you live.
- Access only to summary reports, never to the original entries.
- Patrols at round times, all perfect, every night.
- No way to export, or export only “on request”.
- A demo that only ever uses sample data and never reaches a real site with your own access rights.
At a glance
- Ask to see the same picture as your provider: patrols, incidents, reports, shifts, history.
- Recording things as they happen makes gaps visible; reports after the fact hide them.
- Write data export, and what you receive at exit, into the contract.
- Role-based access, immediate revocation, and a log of every change.
- Ask for a demo on real data and the ten questions in this guide.
Frequently asked questions
What is guard management software?
A system that records guarding work as it happens (patrols, incidents, reports and shifts) and shows it to the client and to the operations centre.
Can I take my data with me if I change security company?
Only if the contract says so. Ask from the start for export in a readable format, a handover deadline at exit and a date by which the data is deleted from the provider’s system.
Is the security company’s monthly report enough?
No. A monthly report is a summary. You need access to the original entries, with time and place, to check what happened on a particular night.
Want us to look at your site?
Talk to the OVIT operations team — a real person answers.