Orders and Sites

You specify the customer, site, period, shift length, break and number of security officers. The system generates the individual shifts from this information. Shift length ranges from 15 minutes to 24 hours in quarter-hour intervals.

There is a strict maximum 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 window expands the order, while moving and deleting shifts adjust it accordingly.

The order overview shows the target, actual and open positions for each order. Clicking a shift row opens a staffing panel below it: required qualifications as chips and the ten best candidates, with each candidate's familiarity with this exact site.

Unqualified officers remain visible, appear dimmed and show what is missing. The Assign button remains available. The server then rejects the assignment.

Important context: The ranking here differs from automatic assignment. It considers only qualification, familiarity with the site and name, not workload, fairness rotation or distance. The assignment itself uses the same rule gate as everywhere else. There is no less restrictive route around the rules here.

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 you assign a shift, the list stays in exactly the same position and the open shift remains open.

An open shift also displays its requirements in a compact form: required qualifications, additional requirements, clothing requirements and employee category. This shows who the shift requires before you assign it.

Two terms from other systems have no equivalent here, which can otherwise cause misunderstandings:

• Order positions do not exist as a separate object. The position is the shift, and one shift is one seat. Where the interface says "open positions", it means counted shifts.
• There are no open-ended framework orders. Every order has an end date.
• There are no shift patterns or series. Instead, use Duplicate, "Copy to days" and copying at order level.

Orders can be merged if the customer and location match, up to 100 at a time. When copying, all times are shifted by the same interval, and assignments can optionally be included. Security officers who are then unavailable appear with a reason in a skipped list instead of causing the entire operation to fail.

A site includes an address, coordinates, geofence radius (50 to 2000 meters, default 200), contacts, hourly rates by activity and the settings that enable customer access.

A site cannot be deleted while orders are linked to it or evidence data such as security log entries and patrol scans exist. This is intentional because this data is subject to retention requirements.

Contacts exist at three levels: on the order (copied to every shift), on the site and on the customer (with multiple contacts including role and phone number).

Every site has a graphical layout: place posts, entrances, cameras and assembly points, draw buildings and routes, block zones and add an instruction to each element.

Posts on the site layout have their own geofence and therefore provide a more precise check-in than the site radius alone.

The site must have coordinates. Without them, the plan cannot be edited. Only the scheduling team can save it.

For details, see Operations Center.

From specific to general, the first match wins: site rate by employee category, then the customer's price list, then the activity rate at the site, then the order rate, then the customer's default rate. If there is no match, invoice creation fails with a notice.

If a deal is assigned to the customer, its rate by employee category is added as a separate level.

For details, see Invoicing and Controlling.