Availability
The security officer states when they are available. A weekly pattern plus exceptions for individual weeks.
Weekly pattern and exceptions
The security officer maintains a recurring weekly pattern with three periods per day: morning from 6 to 14, afternoon from 14 to 22, and night from 22 to 6.
Individual calendar weeks can also be overridden as exceptions. An exception replaces the basic pattern for that week completely.
Exceptions extend up to 26 weeks into the future. Older ones are discarded when saving. The Cockpit shows the result in the employee profile, but nobody can change it there.
What availability does and does not do
This is the most important point in this chapter because more is often expected here:
- The matcher applies it strictly. A security officer is suggested only if their times cover the shift completely.
- The shift marketplace ignores it. A shift appears to the security officer even outside their availability.
- Direct assignment also ignores it. Availability is not part of the rule gate, so an assignment is never rejected for this reason.
Availability is therefore a preference for suggestions, not a block. If you need an actual block, use an absence.

A detail that may be unexpected
Anyone who maintains nothing at all is considered always available and is suggested everywhere.
By contrast, anyone who creates a weekly exception without any period is completely excluded from suggestions for that week. Maintaining nothing and maintaining an empty entry therefore have opposite effects.
Related
- The App for Security OfficersFive tabs, no password, and everything a security officer needs while on duty.
- AbsencesFive types, four states. And one type that is approved without blocking scheduling.
- Duty Roster and SchedulingSite rows on a timeline. Draw, resize, split and assign. A set of rules checks every assignment in the background.
Updated on: 03.09.2026