Orders and sites
The order generates the shifts. The site provides the geofence, contacts and prices.
Creating an order
Enter the customer, site, period, shift length, break and number of employees. The system generates the individual shifts from these details. The shift length can be between 15 minutes and 24 hours on a quarter-hour grid.
You also add staffing requirements: qualifications and required skills. Skills are notices during staffing, not blocks. The "Additional requirements" field is free text for informing the deployed employees and is not evaluated during assignment. Create skills beforehand under Settings, Master data.
Instead of a site, you can also enter a free-form address through "Use address", provided the selected category does not require a site.
The order, site and customer forms no longer close when you click outside them. They close only through "Cancel", the X or Escape. This prevents partially completed input from being lost.
There is a hard upper limit of 500 shifts per order. If it is exceeded, use a longer shift or a shorter period.
On the server, the order window always encloses its shifts. A shift created outside the current window expands the order. Moving and deleting shifts adjust it accordingly.

Order overview and quick staffing
Under Orders, the order overview is a separate tab next to the order list. It has three views: "Monthly schedule", "Monthly schedule (open)" with only unstaffed shifts, and "Staffing" with target, actual and open positions for each order. The "Staffing" table can be sorted by each column.
Clicking a shift row opens a dialog with two parts. The top shows the shift details: time, location, customer, activity, contact, staffing status and requirements. The bottom contains "Staff" with a search field and suggestions. "More" loads additional suggestions. For each employee, you can see how familiar they are with this specific site. A search also finds occupied and absent employees, who are then labeled accordingly.
If the shift is already staffed, the employee appears at the top as "Currently assigned" with the "Keep" button. After staffing, the dialog closes and the row shows the new employee.
Employees without the required qualifications remain visible but appear more faintly with details of what is missing. This applies to qualifications, skills and the category. The Staff button remains available, but the server then rejects the assignment.
Important context: This list is deliberately simpler than automatic staffing and therefore sorts differently. Do not be surprised if someone is listed first here but is not the first suggestion from the automatic process. The assignment itself passes through the same rule gate as everywhere else. There is no less strict path around the rules here.

Today in view, position retained
When opened, the monthly list in the order overview jumps to the first shift running today, or otherwise to the next shift that starts. After a shift is staffed, the list stays in exactly the same position. In "Monthly schedule (open)", a shift that has just been staffed remains visible until you change the view, so it does not jump away from under the pointer.
A shift dialog shows its prerequisites under "Requirements": required qualifications and skills, additional requirements, clothing specifications and the employee category. This lets you see who the shift needs before staffing it.
What is deliberately not included
Two terms from other systems have no equivalent here. Otherwise they can cause misunderstandings:
- There are no order items as separate objects. The position is the shift, and one shift is one seat. Where the interface says "open positions", it means a count of shifts.
- There are no open-ended framework orders. Every order has an end date.
Service templates, rolling out recurring services
For recurring services, the order contains the "Service templates" card. A template is a master record with times, weekdays, quantity, activity and requirements. Create one through "Create template".
"Roll out" uses it to generate actual shifts for a period of no more than 92 calendar days, optionally as drafts. The result states how many shifts were created, how many already existed and how many would have fallen outside the order period. A second rollout for the same period therefore creates no duplicates.
For individual cases, you can still use Duplicate, "Copy to days" and copying at order level.
Merging and copying
Orders can be merged when the customer and location match, with no more than 100 at a time. When copying, all times are shifted by the same interval. Staffing can optionally be copied as well. Employees who are then unavailable appear with a reason in a skipped list instead of causing the entire operation to fail.
Sites
A site holds the address, coordinates, geofence radius (50 to 2000 meters, default 200), contacts, hourly rates for each activity, access permissions for the customer portal and, under "Public holidays at the site", the federal state and municipality for the deployment location's public holiday calendar.
In the site list, "Shifts" opens the site's upcoming shifts. There you can create a shift directly, use an existing shift as a template or delete an unstaffed shift. Staffed shifts can be deleted only in Dispatch.
A site cannot be deleted while orders are linked to it or evidence data such as Wachbuch entries and patrol scans exists. This is intentional because this data is subject to retention requirements.
Contacts exist at three levels: in the order, where they are copied to every shift, at the site and for the customer, where several contacts can be stored with role and phone number.

Deployment plan, the site map
Each site has a graphical site map. You can place posts, entrances, cameras and assembly points, draw buildings and routes, block zones and store an instruction for each element.
Posts on the site map receive their own geofence, providing a more precise check-in than the site radius alone.
Coordinates at the site are required. The plan cannot be edited without them. Only Dispatch may save it.
See Operations center for details.
Maintaining hourly rates
You maintain hourly rates at the site, per employee category or as an activity rate, in a customer price list, on the order or as the customer's standard rate. If a rate is missing, invoice creation stops with a notice.
If a deal is linked to the customer, its rate for each employee category is added as a separate level.
For details, see Invoicing and controlling.
Related
- Schedule and dispatchSite rows against a time axis. Drag, extend, split and staff shifts. A set of rules checks every assignment.
- Invoicing and controllingChecked hours become a draft invoice. You maintain the hourly rates at the site, at the customer, in a deal or on the order.
- Guard PatrolsCheckpoints at the site, patrols in the app, and evidence in the Cockpit. This also includes an honest explanation of what a scan proves.
Updated on: 03.09.2026