Few industries place such high demands on shift scheduling as private security: sites need round-the-clock coverage, employees need the right qualification for each post, and absences rarely come with advance notice. This article covers the legal guardrails under German law, what a good schedule needs to contain, and where spreadsheet templates hit their limits.
Why shift scheduling in security is different
A shift schedule in the security industry is more than a list of names and times. It has to represent several layers at once:
- Continuous coverage: Many sites run 24/7. Every gap isn't just a planning mistake, it's a breach of contract with the client.
- Qualification binding: Not every employee can take every post. An expertise exam under § 34a GewO (the German Trade Regulation Act), a first-aid certificate, or firearms training determine who can be deployed where.
- Multiple sites: Anyone managing ten sites is effectively planning ten sub-schedules that share staff, which makes double-booking almost inevitable without a system that checks for it.
- Last-minute changes: Sick notices on a Sunday evening, additional patrols after an incident, events with extra staffing needs.
The legal guardrails from the German Working Hours Act
In Germany, the shift schedule has to stay within the bounds of the Working Hours Act (Arbeitszeitgesetz, ArbZG). The most important rules in practice:
- Maximum working time: 8 hours per working day, extendable to up to 10 hours if the average over six months doesn't exceed 8 hours (§ 3 ArbZG).
- Rest period: After a shift ends, at least 11 uninterrupted hours of rest are required as a rule (§ 5 ArbZG). A night shift ending at 6 am and an early shift starting at 2 pm the same day therefore don't fit together.
- Breaks: At least 30 minutes for more than 6 hours of work, at least 45 minutes for more than 9 hours (§ 4 ArbZG).
- Sunday and holiday work: Exceptionally permitted for the security industry (§ 10 ArbZG). But: at least 15 Sundays per year must remain work-free, and a substitute rest day must be granted within two weeks for Sunday work, or within eight weeks for holiday work (§ 11 ArbZG).
- Night work: Additional protections apply to night workers, including the right to occupational health check-ups and to reasonable compensation (§ 6 ArbZG).
What a shift schedule should contain, at minimum
Regardless of the tool, every schedule should include:
- The site or object and post
- Date, shift start and end, including breaks
- The assigned employee, with the qualification required for that post
- A reachable contact person for questions and emergencies
- The status or version of the plan, so it's clear what's currently valid
Spreadsheet templates: where they work, and where they fail
For a single site with a fixed team, a spreadsheet is a legitimate starting point: rows for employees, columns for days, done. The problems start with growth:
- Version chaos: As soon as the plan is shared by email or messenger, multiple versions circulate. No one can be sure which file is current.
- No conflict checking: A spreadsheet doesn't notice when an employee is scheduled at two sites at once, falls short of the required rest period, or lacks the qualification for a post.
- No confirmation: Whether an employee has seen and accepted their shift stays unclear, until they don't show up.
- Duplicate data entry: Planned hours have to be re-entered for payroll and reconciled against actual times worked.
The digital alternative
Specialized scheduling software addresses exactly these points: the schedule exists centrally and up to date for everyone involved, conflicts such as double-bookings or missing qualifications become visible while planning, employees receive their shifts as a push notification on their phone and confirm them there. Hours actually worked flow into timesheets and payroll preparation without being re-typed.
For what that looks like in practice, see the overview of GuardEinsatz's features, and the direct comparison with Excel and WhatsApp makes the day-to-day difference concrete.