Reference · built on requestOperator by FibricFacilities & comfort

Cleaning Verification

Checks scheduled cleaning against door events and task completion and proposes sign-off or a re-clean.

Request accessPricing ↗

About

A cleaning task marked complete is a claim. Cleaning Verification checks it against the building. For each scheduled task it reads the completion time from Corrigo, Jira Service Management, or ServiceNow, then looks for the door events a clean would leave: a crew badge or a door-opened event at the room's door from Brivo, Kisi, Verkada, or your access control system, and motion in the room from LoRaWAN or Disruptive Technologies sensors, inside the task's window.

When the events line up it proposes sign-off. When the door never opened, or the room saw no motion in the window, it proposes a re-clean and a note to the supervisor. A person approves both. The operator never closes, reopens, or rates a task on its own.

This is a reference listing. It documents what Fibric would read from Cleaning Verification 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

  • Task completion events and times from Corrigo work orders, Jira Service Management requests, or ServiceNow records, with the assignee and the space
  • Access events per door from Brivo through GET /events/access, Kisi lock.opened and reader.access events, or Verkada door_opened and credential events
  • Door state and credential use from your local access control system, so a badge at the janitor closet and the room door both count
  • Motion events from LoRaWAN sensors or Disruptive Technologies MOTION_DETECTED events in the cleaned room, with timestamps
  • The cleaning schedule per space and the window each task must fall in, from your work-management system or a list you provide
  • Which credentials belong to the cleaning crew, so a tenant opening the door is not read as a clean

Proposed actions

  • Target capability: propose sign-off on a completed task whose door and motion events fall inside its window, for the supervisor to approve
  • Target capability: propose a re-clean task when the task was closed but the room's door recorded no crew credential in the window
  • Target capability: propose a note to the supervisor when tasks are closed in bulk with no matching door events across several rooms
  • Target capability: propose a rating or verification comment on the Corrigo work order, where your account uses VerifyWorkCommand
  • Target capability: propose a sensor or reader check when a door reports no events for days while tasks there are closed

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

What you can build

  • Sign off the night clean each morning

    Corrigo shows last night's tasks complete. The operator matches each to Brivo access events at the room door within the task window and proposes a sign-off list for the supervisor, with the exceptions on top.

    With Corrigo Enterprise, Brivo Access

  • Catch the tasks closed from the van

    Several Jira Service Management tasks close at the same moment while Kisi shows no lock.opened event on those floors. The operator proposes re-clean tasks and a note to the supervisor naming the rooms.

    With Jira Service Management, Kisi

  • Check a room with no badge reader

    A conference room's door has no reader, so the operator uses Disruptive Technologies motion events in the room and the ServiceNow completion time. Motion in the window proposes sign-off; none proposes a re-clean.

    With Disruptive Technologies, ServiceNow

Requirements

  • A Corrigo Enterprise, Jira Service Management, or ServiceNow connector that holds the cleaning tasks and their completion times
  • An access control connector with event access for the doors of the cleaned spaces: Brivo Access, Kisi, Verkada, or your local system
  • A list of the crew's credentials and the door for each cleaned space
  • Motion sensors in the cleaned rooms through the LoRaWAN Network or Disruptive Technologies connector; optional, but they catch a badge-and-leave
Authentication
Reads task, door, and sensor events through the credentials your work-management, access control, and sensor connectors hold, and writes sign-offs, re-clean tasks, and notes through the work-management connector after approval.

Limits

  • It checks presence, not quality. A crew that badged in and left at once passes the door check; motion is the only further evidence.
  • Rooms whose doors are propped or on a free-access schedule leave no credential event; those rooms are checked on motion alone, or not at all.
  • It proposes sign-off, re-clean, and notes. It never closes, reopens, or rates a task without approval.
  • Event retention differs by platform. Tasks older than the window your access platform keeps cannot be checked after the fact.

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 Cleaning Verification ↗

Questions and answers

What does a person approve?
Each sign-off, re-clean task, note, and rating. The proposal shows the task, its completion time, the door and motion events found or not found in the window, and the crew credential involved. Approve it, dismiss it, or send it back with a comment.
What record is left?
A receipt per task checked: the events matched, the window used, the proposal made, who approved it, and what was written to the work-management system. Rooms that could not be checked are recorded as unchecked, not as failed.
Can it close or reopen a task on its own?
No. It reads completions and door events and proposes. Sign-offs, re-cleans, notes, and ratings are written once, after approval, through your work-management connector. It never changes door schedules or credentials.
Ask about Cleaning Verification

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