The backlog contains any services that are due but could not yet be scheduled. The backlog is used by soobr to keep the workload of the cleaning tours as constant as possible. The backlog usually contains services that are less time-critical and can be performed at a later time.

Backlog

Simple example of backlog

On a business entity there is a cleaning tour with the maximum duration of one hour. On Monday services are due, for which 1 hour and 10 minutes are needed. The planning algorithm schedules the most important services or areas, such as the daily cleaning of the toilets. A month's cleaning in an office, for example, could then be added to the backlog. On Tuesday, only 50 minutes of work are added, and thus the monthly cleaning in the office can now be carried out.

Backlog for sensor-based business units

In sensor-based business units, the cleaning frequencies on sensor-based areas such as meeting rooms are dynamic. This means, for example, that on a Friday with a low building occupancy rate, few meeting rooms are due for cleaning. As long as there are enough less important services in the backlog, these services can be processed on Friday.

Backlog on non-sensor based business units

soobr calculates the execution time of the services due per area on the basis of the performance figures. The maximum duration of the cleaning tour is never exceeded. A manual distribution of the surfaces to the cleaning tours is usually very time-consuming with an exact calculation. Here also the backlog is used. Areas that do not have to be carried out on certain days are automatically distributed over the week by the backlog. The same applies to non-weekly work such as monthly cleaning, provided that the performance figure for monthly cleaning is shown.