How Guardly works during a shift
Guardly is the operating system OVIT built for physical security. During a shift, the guard clocks in with a geofenced check-in and opens their assignment, patrols run on defined checkpoint routes, an incident is logged, escalated and closed with evidence and timestamps, the handover goes into the same record, and in the morning the client sees the closed events with their documentation. Everyone works on one shared record; each person reads from it what their own decision needs.
Updated: 5 min read
What is Guardly, and who uses it during a shift?
Guardly is OVIT’s platform to plan, deploy, monitor and improve security operations. During a shift four roles use it on the same record: the field officer, the operations team, the client and management.
- Field officer: sees the task, the location and the history of that point before arriving.
- Operations team: sees the status of every site and approves the response.
- Client: sees the closed event with complete documentation.
- Management: sees performance trends across the whole network.
The Guardly screens on the website are illustrative, drawn with placeholder data, because client operations are confidential. The modules behind them run in production every day.
What happens at the start of a shift in Guardly?
The guard clocks in with a geofenced check-in at the site and opens their assignment: post, tasks and instructions. The operations team sees in the same record who has started and where they are.
- Shift schedule: who covers which post is set in Guardly, together with the handovers.
- Clock-in: the start is recorded with a geofenced clock-in, tied to the client’s site.
- Assignment: the guard sees their missions for the shift.
- The previous shift’s handover: anything left open is already in the record.
The operations team sees live guard locations. Nobody needs a phone call to find out whether the post is covered.
How are patrols recorded in Guardly?
Patrols run on defined routes with checkpoints, and every pass goes into the same live record the operations team and the client see.
Routes and checkpoints are set per site. The record shows which points were visited and when, and the guard can add a time-stamped note or photo when they find something. How to design a route, how often it should run and what a scan proves are covered in the guide to checkpoint patrols.
A missed checkpoint shows up in the record just as a visited one does. That is the point: a gap cannot hide inside a summary.
What happens when an incident occurs during the shift?
The incident is logged with its source, severity, assigned owner and response protocol. The operations team triages and escalates it, the guard sent to it receives instructions, and every step is time-stamped through to closure.
- Signal: the event enters the record, from the guard or from a system such as a gate controller.
- Triage and escalation: the operations team sees source, severity, owner and protocol together, and notifications are routed to whoever needs them.
- Dispatch: the guard receives the order with the location, an estimated arrival time, the verification rules and the evidence to bring back.
- On-site verification: the guard’s note and photo, time-stamped.
- Closure: the outcome, the cause and the next preventive step are recorded, and the closure is shared with the client.
The result is one evidence chain: the same event, from first signal to closure, in one record. How to write the incident report itself, and how to keep fact apart from opinion, is covered in the guide to the incident report.
How does a shift handover work in Guardly?
The handover is recorded in the same record as the shift. An open event is not rewritten on another sheet: it passes to the next team as the same event, with its full history.
- What stays open: events in progress, pending items, anything that needs another check.
- What changed: a door that will not lock, an expected visitor, a new instruction.
- Clock-out: the end of the shift is also recorded with a geofenced clock-out.
The aim, as OVIT puts it: every handover, every incident and every review should leave the next shift better informed than the last one.
What does the client see the morning after a shift?
They do not wait for a document: their team sees the same truth as the operations centre, from the first signal to the final report, with closed events and their documentation.
- The night’s events: what happened, who handled it, how it was closed, with the evidence.
- The patrols: which checkpoints were visited and when.
- What stayed open: with the shift handover.
- Digest reports: Guardly produces digest reports with version history.
For questions, team and client messaging runs through the platform, and at the operations desk a real person answers. What a good morning report should contain is covered in the guide to the shift report. To see Guardly working, book a demo from the platform page.
At a glance
- Guardly is OVIT’s platform: guard, operations team, client and management work on the same record.
- A shift starts and ends with a geofenced clock-in and clock-out, and the guard sees their assignment.
- Patrols run on defined checkpoint routes; a missed point is visible.
- An incident moves through signal, escalation, dispatch, verification and closure, time-stamped at every step.
- In the morning the client sees what the operations centre sees, without waiting for a document.
Frequently asked questions
Does Guardly replace the guard or the supervisor?
No. The judgment on the post and the decision on the response belong to people; Guardly keeps the picture, the coordination and the evidence in one record.
Why are the Guardly screens on the website “illustrative”?
Because client data is confidential. The website shows the platform’s structure with placeholder data; the modules behind the screens run in production.
Can I see Guardly before working with OVIT?
Yes. You can book a demo from the platform page or through the contact form.
Want us to look at your site?
Talk to the OVIT operations team — a real person answers.