Short answer. Guarding software holds four things. The post schedule: one person per shift and per post, with replacements. Taking the post: a check-in on site, on the phone, and an alert if nobody has checked in ten minutes after the hour. Rounds and the incident log: each checkpoint read with the time, each event written with its photos. Hours: delivered per site, matched against the contract, sent to the customer. In this page's example, a site covered at 98.3% still leaves three nights with nobody at the post.
This page is for those who run a guarding or surveillance company, from a few sites to several wilayas, and for companies that manage their own security teams. The definitions come from public sources: security guard, guard tour patrol system, shift work, geofence, near-field communication, service-level agreement. The site, its shifts, its rounds and its absences are a constructed example. The page covers neither approval and the rules of the profession, nor labour law and payroll, and quotes no hardware price.
Five situations the customer sees before you do
The figure sets five situations side by side, without a tool and with one.
The trade. A security guard is a person employed to protect an organisation's assets from a variety of hazards. They hold a post, control access at building entrances and vehicle gates, patrol, take notes and report. What you sell. Hours of presence at a post, and rounds: nothing the customer can check for themselves at night. The empty post. It is the first situation, and the most costly: the customer learns of it before you do.
The round not done. A signed notebook proves nothing, neither for you nor against you. The incident with no trace. A call at midnight, then nothing written: the next day, nobody knows what was done. Disputed hours. Attendance sheets copied out at month end, against the customer's memory. The replacement nobody can find. One person's phone book. In all five cases the information existed; it did not reach the right place, nor in time.
A shift, in six steps
The figure follows a shift, from the schedule to the report.
The schedule. Shift work is a practice designed to keep a service operational at all times; its shift plan, or rota, is the central component. Here each shift has a post, hours and a person; the logic is that of team scheduling, applied to posts that must be held without a break. Taking the post. That is the accented step. The guard checks in on site, on the phone; the application verifies the position by geofence, a virtual perimeter around the site, or by the post's tag.
The tag. Near-field communication links two devices at four centimetres or less: you have to be standing at the post to read it. Without a network. An isolated site or a basement: the check-in is recorded offline and sent up afterwards, see the offline application. Handover. Instructions passed on, equipment counted, confirmation by both people. The report. Hours, rounds and events of the shift, with no retyping. And the time clock? It suits a head office; across twenty sites the phone replaces it, see the time clock and mobile check-in.
A post to cover, 180 times a month
The figure shows a month of shifts on a site with three posts.
The count. Three posts, day and night, thirty days, twelve-hour shifts: 180 shifts, 2,160 hours to cover. In the example. 171 shifts are held as planned; 6 are held by a replacement found in time; 3 are left empty, three nights, that is 36 hours. Coverage rate: 98.3%. What the figure says. Almost nothing: 98.3% looks excellent, and the customer only remembers the three nights.
The alert. Ten minutes after the shift is due to start, with no check-in, the control desk is warned, through the channel that arrives, see notifications. The delay can be set. The replacement. The tool proposes guards who are available, who respect the rest rules you have set, and who already know the site. The service level. A service-level agreement is an agreement, typically a binding contract, between a service provider and a customer: if yours provides for a coverage rate or penalties, the calculation is made on the same check-ins. What is measured. Shifts covered, late starts, empty posts and their duration, per site and per month.
«98.3% looks excellent, and the customer only remembers the three nights.»
The round, proven point by point
The figure shows a site, its eight checkpoints and the four rounds of one night.
Guard tour control. It is a system for logging the rounds of personnel on patrol. At each point, the guard reads a tag with the phone, which records the time; the system keeps the checkpoint's identifier, the date and the time, and produces summaries that highlight missed points and rounds. In the example. Eight points, a round every two hours: 32 readings expected in the night. The 22:00 and 00:00 rounds are complete. The 02:00 round reads six points of eight: points 5 and 6, at the back of the site, are skipped. The 04:00 round is not done.
The result. 22 readings of 32, that is 69%; in the notebook, four rounds were signed. During the night. A late round shows at the control desk, which calls the guard: the 04:00 round could have been caught up. The incident log. Each event is written at the time: the hour, the place, what was seen, the people informed, with photos, see photos that stand as proof. Supervisory visits. They too are readings. What the customer sees. The morning report, or access to their own sites, see the customer area.
«In the notebook, four rounds signed. On the tags, twenty-two readings of thirty-two.»
Eight weeks, site by site
Eight weeks in the example, starting with a pilot site.
Scoping. One week: your sites, your posts, the hours sold, your instructions and your current timesheets. The sites. Each site receives its posts, its checkpoints and its instructions; the tags are fitted in one visit. The schedule. It takes over your current rotas before improving them.
The phones. The application runs on ordinary phones, in Arabic and in French, with large buttons: take the post, read a point, write an event. The pilot site. One site, two weeks, then the others. What the software does not do. It does not keep watch in place of the guards and replaces neither training nor supervision: it proves what was done, and flags what was not. The durations are those of a constructed example.
What is inside guarding software
The figure stacks five layers; the second is the reference for all the others.
- What you receive: the schedule per post with replacements; on-site check-in, offline; the empty-post alert; rounds read point by point; the incident log with photos; hours delivered per site; the customer report; customer access.
- What the company avoids: the empty post learned from the customer, the round signed and not done, the incident with no trace, hours argued over at every month end, the replacement looked for by phone at 10 pm.
- What is measured: shifts covered; late starts; empty posts and their duration; round points read and missed; events per site; hours delivered against hours sold.
- What Symloop does: scoping your sites and posts, the schedule, the guards' application, rounds, the incident log, the calculation of hours, the report and customer access, rights per role, in Arabic and in French.
Sites and posts. What the customer bought: posts, hours, rounds, instructions. The schedule. That is the accented layer: presence, rounds and hours are compared with what it had planned. Presence and the field. Check-ins, rounds, incident log, supervisory visits.
Hours. Delivered per site and per person, they are matched against the contract and exported to your invoicing and your payroll, with no retyping. Rights. The person in charge of a site sees that site, a customer sees their own, management sees everything, see roles and rights. Steering. Sites in alert, empty posts, missed rounds, on a dashboard. Ready-made or custom. Guard tour and incident log applications exist and suit a few sites. Custom work is justified when the schedule, the check-ins, the rounds and the hours billed have to be linked, when your customers need access, or when several wilayas have to be covered.
- How do you run a security guard company?
- By proving the presence you sell: a schedule per post, an on-site check-in each time a post is taken, rounds read point by point, an incident log written at the time, and hours calculated on those check-ins.
- What software for a guarding company?
- Software that holds sites and posts, the shift schedule, on-site check-in, rounds, the incident log and hours delivered per site, with an application on the guards' phones.
- How do you know a post is not covered?
- By the absence of a check-in: ten minutes after the shift is due to start, with no check-in on site, an alert goes to the control desk, which arranges the replacement.
- How do you prove a round was done?
- By reading a tag at each checkpoint: the system records the point, the date and the time. In the example, 22 readings of the 32 expected.
- What is an electronic incident log?
- The journal of a post's events, kept on a phone: the hour, the place, what was seen, the people informed and the photos, written at the time and searchable per site.
- Is one phone per guard needed?
- One phone per post is often enough: each person signs in on it when taking the post. On some sites, a personal phone also works.
- Does the application work without a network?
- Yes. Check-ins, round points and events are recorded offline and sent up as soon as the phone finds a network again, with their real time.
- Can the customer see what is happening on their site?
- If you decide so: access limited to their sites, with post coverage, rounds and events, or a report sent every morning.
- How do you calculate the hours to bill?
- From the check-ins at the start of the shift and at handover, per site and per shift, matched against the hours in the contract. The detail goes with the invoice.
- Does the software replace supervisory visits?
- No. It shows where to go: sites in alert, missed rounds, posts taken late. Those visits are recorded too.