Reference · built on requestOperator by FibricFacilities & comfort

Janitorial Routing

Orders cleaning tasks by traffic, open requests, and shift assignments and proposes a route for each cleaner.

Request accessPricing ↗

About

A cleaning crew starts each shift with a fixed route drawn up months ago. The busy floors get the same pass as the empty ones, and requests that came in overnight are found on the way. Janitorial Routing draws the route each shift instead. It reads open cleaning requests and recurring tasks from Corrigo, Jira Service Management, or ServiceNow, occupancy by area from LoRaWAN sensors or BACnet/IP objects, and who is rostered on the shift from Deputy, When I Work, or Connecteam.

It then proposes an ordered task list per cleaner: requests first, then the areas with the most traffic since their last clean, then the remaining recurring work. The supervisor approves or reorders it, and each cleaner receives their list in Teams or Slack. It never assigns a shift.

This is a reference listing. It documents what Fibric would read from Janitorial Routing and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Open work orders and their priority, work zone, and due time from Corrigo, or requests and queues from Jira Service Management and ServiceNow
  • Recurring cleaning tasks and their last completion time per area, from the same work-management system
  • Occupancy and motion uplinks by area from LoRaWAN sensors, or occupancy state and change events from BACnet/IP objects
  • Who is rostered on the coming shift, and in which area, from Deputy rosters, When I Work shifts, or Connecteam scheduler shifts
  • Task completion events as cleaners close them, so a route can be re-proposed mid-shift when a request lands
  • Floor and area adjacency from your site map, so a route does not send a cleaner back and forth between floors

Proposed actions

  • Target capability: propose an ordered task list per rostered cleaner for the coming shift, with the reason each area is placed where it is
  • Target capability: propose assigning each task in the work-management system to the cleaner whose route holds it, once the supervisor approves
  • Target capability: propose sending each cleaner their list in Microsoft Teams or Slack at shift start, and an update when a request is added
  • Target capability: propose moving a new request to the top of the nearest cleaner's route during the shift, for the supervisor to confirm
  • Target capability: propose dropping a low-traffic area from tonight's route and noting it for the next, when the shift is short-staffed

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Route tonight's crew by today's traffic

    LoRaWAN motion sensors show which meeting rooms were used today. The operator reads the Deputy roster for the night shift and proposes each cleaner's Corrigo task order, busiest rooms first, for the supervisor to approve in Teams.

    With LoRaWAN Network, Deputy, Corrigo Enterprise, Microsoft Teams

  • Put overnight requests at the front

    Requests logged in Jira Service Management since the last shift go to the top of the nearest cleaner's list. The operator proposes the assignment and the Slack message, and re-proposes when a new request lands mid-shift.

    With Jira Service Management, Slack

  • Cover a short-staffed shift

    If the When I Work roster shows one cleaner fewer than usual, the operator proposes which low-traffic areas to skip tonight, using BACnet/IP occupancy, and notes them for tomorrow's route in ServiceNow.

    With When I Work, BACnet / IP, ServiceNow

Requirements

  • A work-management connector holding the cleaning tasks: Corrigo Enterprise, Jira Service Management, or ServiceNow
  • A scheduling connector for the crew roster: Deputy, When I Work, or Connecteam
  • Occupancy sensors by area through the LoRaWAN Network or BACnet/IP connector; without them, requests and recurrence alone order the route
  • A Microsoft Teams or Slack connector to deliver each cleaner's list
Authentication
Reads tasks, sensors, and rosters through the credentials your work-management, sensor, and scheduling connectors hold, and writes assignments and messages through those same connectors after approval; it holds no credentials of its own.

Limits

  • It orders tasks. It does not change who is on shift, extend a shift, or call anyone in; that stays in your scheduling system.
  • Traffic ordering needs an occupancy sensor per area. Areas without one are placed by their recurrence and last clean.
  • Travel time between areas comes from the adjacency you provide, not from indoor positioning.
  • A route is a proposal to the supervisor. Cleaners receive it only after that approval, and the supervisor can reorder it at any time.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Janitorial Routing ↗

Questions and answers

What does a person approve?
The supervisor approves each shift's routes before any cleaner sees them, and each mid-shift change. The proposal shows every task in order, the traffic or request that placed it, and who it goes to. Reorder it, move a task between cleaners, or dismiss it.
What record is left?
A receipt per shift: the roster read, the sensors and requests used, the route proposed, what the supervisor changed, the assignments written to the work-management system, and the messages sent. Completed and skipped tasks are noted against it.
Does it ever assign work on its own?
No. Assignments and messages are written only after the supervisor approves a route, once each. It never edits the roster, clocks anyone in, or closes a task; cleaners and supervisors do that in the systems they use today.
Ask about Janitorial Routing

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy