Skip to content
DT Nova
Services

Security guard scheduling software for guarding companies and security teams

Security guard scheduling software has one job above all others: no post left empty. Every client site and every post is covered around the clock by a guard who holds a valid licence and has been trained for that site, working time stays inside the rules, a no-show is caught within minutes, and the hours your client is billed for match the hours that were actually guarded. We build custom security guard scheduling software for guarding companies, event security firms and in-house security teams, hosted in the EU, and your company owns the code.

  • You see the result before it goes live
  • Fixed price for the agreed scope, in writing before work starts
  • Source code, domain and accounts in your company's name

Request a quote

Why guard scheduling is its own problem

Most shift tools start from a team and ask who works when. Guarding starts from the client contract. A shopping centre needs two guards at the entrance from opening to closing and one patrol all night; a logistics site needs a gatehouse staffed every hour of the year; an event needs forty licensed door staff for six hours on one Saturday. Each of those is a post with fixed hours and fixed requirements, and an empty post is not a staffing gap, it is a breach of contract and a security risk.

The work is also continuous. The United States Bureau of Labor Statistics describes security guards as usually working shifts of about 8 hours on rotating schedules, notes that night shifts are common and that guards often must work around the clock because many buildings operate 24 hours a day, and reports that security guards held about 1.3 million jobs in 2025 (Occupational Outlook Handbook, read on 11 November 2026). Large numbers of part-time guards, guards who work for several sites in one week and short-notice orders from clients make the schedule change every day. A spreadsheet survives that until the first week someone is ill on a night shift.

What the system does

PartWhat it handlesWho uses it
Sites and postsClient sites, posts, post hours, post orders and the requirements of each postOperations managers
ScheduleRotating patterns, open posts, swaps, holidays and short-notice client ordersSchedulers
Licences and trainingLicences, site inductions and other qualifications with expiry datesSchedulers, HR
Check-in and no-show alertsArrival at the post, late or missing guards, replacementsDuty supervisors
Guard tours and incidentsCheckpoint rounds, missed checkpoints, incident reports with photosGuards, supervisors
Client reporting and billingHours delivered per post, extra orders, tours and incidentsAccount managers, finance
Payroll exportHours, nights, weekends, overtime and allowances by pay rulesPayroll

Our employee scheduling software page covers shift planning in general, and workforce management software covers forecasting and time tracking. This page is about what guarding adds.

Posts, post orders and coverage

Each post is stored with its hours, its location on the site and its post orders: what the guard does there, who to contact, what to check and what to do in an alarm. Guards see the post orders in the app before the shift starts, so a guard covering an unfamiliar site at short notice is not left to guess. Requirements sit on the post, not in the scheduler's head: a valid licence for the right activity, induction for that site, and where the contract demands it, first aid, fire warden training, a control room qualification, a language, or security clearance from the client.

Coverage is planned per post and per hour. The schedule shows every hour of every post as covered, open or at risk, and an open hour three weeks out is visible today rather than the evening before. When a client orders extra guards for an event or a weekend, the order is added as temporary posts with their own requirements, and the extra hours flow into the invoice.

Licences, site training and who may stand where

Licensing is the rule a guarding schedule must never break. In England, Wales and Scotland, the Private Security Industry Act 2001 makes it an offence for a person to engage in licensable conduct except under and in accordance with a licence (section 3), and the Security Industry Authority licence, once issued, is valid for three years (UK regulated professions register, security guard entry). In the United States, the Bureau of Labor Statistics notes that most states require that security guards be licensed by the state in which they work. (All read on 11 November 2026.) Licence types, training hours and renewal rules differ by country and state, so they are configured per jurisdiction, not hard-coded.

The system stores every licence and qualification with its number, type and expiry date, and checks them on the date of each shift. A guard whose licence expires on the 14th cannot be placed on a post on the 15th, and both the guard and the scheduler are reminded weeks before. Site inductions are tracked the same way, so a replacement guard sent to a site at night is one who has been there before or has completed its induction.

Working time, nights and long duties

Guarding runs on nights, weekends and long duties, which is exactly where working time rules bite. In the EU, the Working Time Directive sets a minimum daily rest of 11 consecutive hours per 24-hour period, an average working week of no more than 48 hours including overtime, and normal hours for night workers of no more than an average of eight hours in any 24-hour period. It also allows derogations for security and surveillance activities requiring a permanent presence in order to protect property and persons, particularly security guards and caretakers or security firms, provided the workers concerned are afforded equivalent periods of compensatory rest (Directive 2003/88/EC, Articles 3, 6, 8 and 17(2) and (3)(b), read on 11 November 2026). Whether a derogation applies, and how compensatory rest is counted, depends on national law and the collective agreement.

In the United States, federal rules let an employer and employee on duty for 24 hours or more agree to exclude a regularly scheduled sleeping period of no more than 8 hours from hours worked, but an interruption of the sleeping period to go back on duty counts as hours worked, and if the employee cannot get at least 5 hours' sleep the entire period counts (29 CFR 785.22, read on 11 November 2026). The system records interruptions on long duties for exactly that reason. Rest periods, weekly limits, night limits and compensatory rest are checked when the schedule is made, so the planner sees a conflict before the guard does.

No-shows and filling open posts

A post that starts at 22:00 with nobody at it is the worst moment in a guarding company's night. The guard checks in from the app at the start of the shift; if nobody has checked in a set number of minutes after the post starts, the duty supervisor gets an alert, and so does the guard. The guard being relieved is held at the post until a replacement checks in, where the contract and working time rules allow it.

Replacements are offered in the order you set: guards already trained for that site first, then licensed guards who have completed the induction, then the rest, and in each group those with rest time and weekly hours left. Overtime is offered fairly and recorded, and a supervisor can see the whole night's coverage on one screen. The same logic fills open posts days ahead: guards see open shifts in the app and claim the ones they qualify for, and nobody can claim a post they are not allowed to stand at.

The guard app

Location is recorded at check-in, check-out, checkpoints and incidents during working time, not tracked continuously, and never outside shifts. For how location works on phones and what each platform allows, see our guide to mobile app geolocation.

Client reporting and billing from the same records

Clients want proof: hours guarded per post, tours completed, incidents and what was done about them. Because all of it is recorded as it happens, client reports are produced from the same data the operation runs on, and a client portal can show them live. Billable hours and paid hours are kept apart, because a client contract and a pay agreement rarely count time the same way: a client may pay for a full post while a guard is paid for a split shift, or the other way round. Extra orders, rate differences for nights and public holidays, and missed hours that must be credited are all calculated from the records. For portals clients log in to, see website portal development; for the link to payroll and accounting, see API integration.

Ready-made guard management software or custom?

There are established guard management and workforce products, and for a company with standard contracts and one pay agreement, one of them may be enough. Where it is, we will say so. Custom software pays off when your contracts, post requirements, pay rules or client reporting do not fit what a product assumes, when you run guarding next to other services such as cleaning or reception, or when you want the schedule, the client portal and billing in one system you own.

SituationReady-made productCustom software
Standard posts, one pay agreementUsually enoughRarely worth building
Several countries or states with their own licence rulesDepends on the productRules configured per jurisdiction
Client-specific reporting and contract termsStandard reportsBuilt around your contracts
Guarding next to other site servicesSeparate toolsOne schedule for all services
Data location and ownershipThe vendor's platform and regionYour account, EU data region

Data protection

A guarding system holds personal data about guards, including licence details and location at work, and often about people involved in incidents. The GDPR requires that personal data is adequate, relevant and limited to what is necessary for the purposes for which it is processed (Regulation (EU) 2016/679, Article 5(1)(c), read on 11 November 2026). That is why location is recorded only at defined events during working time, incident reports have retention periods, and access is limited by role and site. The system runs in an EU data region, and every change to a schedule or record is logged.

How we build it

  1. Map your posts and rules. We go through your contracts, post requirements, licence rules, pay agreement and how a night with a no-show is handled today, and write it down for your approval.
  2. Scope and fixed price in writing. Sites, posts, rules, the guard app, client reporting, integrations and what the first phase leaves out.
  3. First version on real schedules. Last month's posts and guards run through the system next to your current schedule, so gaps in the rules show up before anything goes live.
  4. Go live with one region or client group. Schedulers and supervisors use it daily, rules are tuned, and the old schedule stops when the numbers say so.
  5. Measure and extend. Open hours, late fills, no-shows and overtime are compared with the start, then the next region, the client portal or billing is added.

For agencies that schedule sworn officers rather than guards, see police scheduling software; for standby duties and on-duty rotations, see our guide to standby and rotation scheduling.

You own it

As a standard term, the source code sits in a repository in your company's own account, and the database and hosting are in your name in an EU data region. The rules are readable configuration you can change. You can keep us for maintenance, run it yourself or hand it to another team. See prices.

Questions we get

What makes security guard scheduling different from ordinary shift scheduling?

A guarding schedule starts from posts, not from people. Each client site has posts with fixed hours, often around the clock, and each post has requirements: a valid licence, site induction, sometimes first aid, a language or a control room qualification. An empty post is a breach of contract, so the schedule has to catch a guard who has not arrived within minutes and fill the post from guards who are allowed to stand there.

Can the system stop us from assigning a guard whose licence has expired?

Yes. Licences, site inductions and other qualifications are stored with their expiry dates, and the planner cannot place a guard on a post whose requirements that guard does not meet on that date. Guards and managers get reminders well before a licence or qualification runs out, so renewals are started in time.

How does the system know a guard has arrived at the post?

The guard checks in from the guard app at the start of the shift, and the app records the time and checks that the phone is at the site. If nobody has checked in a set number of minutes after the post starts, the duty supervisor is alerted and can send a replacement. Location is only recorded at check-in, check-out, checkpoints and incidents during working time, not around the clock.

Can the same system handle guard tours and incident reports?

Yes. Patrol routes are made of checkpoints, usually NFC tags or QR codes on site, and the guard scans each one on the round. Missed or late checkpoints show up straight away. Incidents are reported from the app with time, place, photos and a short description, and go to the supervisor and, where the contract says so, to the client.

Can we bill clients from the same records?

Yes. Hours delivered per post, extra hours ordered by the client, tours completed and incidents all come from the same records, so invoices and client reports are built from what actually happened. Billable hours and paid hours are kept apart, because a client contract and a pay agreement rarely count time the same way.

Who owns the software and the data?

Your company. The source code sits in a repository in your own account, and the database and hosting are in your name in an EU data region. You can keep us for maintenance, run it yourself or hand it to another team.

Get a written quote

Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.

See every price · Contact details

Request a quote