Reference · built on requestOperator by FibricHospitality & guests

Clean Sequence

Orders each attendant's room list from departures, arrival times, and stayovers, and proposes a new order as the day changes.

Request accessPricing ↗

About

A room attendant's list is set in the morning and wrong by mid-morning. A departure checks out early, an arrival calls ahead, a stayover puts out the do-not-disturb sign. Clean Sequence reads the day's departures and their checkout state, the arrival time each reservation carries, the stayovers, and the attendants on shift from Deputy or 7shifts.

It proposes the order of rooms on each attendant's sheet: departures with an arrival due first, then stayovers, then departures with no arrival. When a checkout posts or an arrival time moves, it proposes a resequence for that sheet only. The housekeeping supervisor approves each change from a phone.

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

  • Departures for the business date and their state, through Mews reservation states Started and Processed, apaleo checked-out webhooks, or OPERA Cloud reservation status
  • Arrival times on today's reservations, such as the estimated arrival time Cloudbeds keeps on a reservation or ScheduledStartUtc in Mews
  • Stayovers and do-not-disturb, through Cloudbeds housekeeping/room_condition_changed events and the doNotDisturb flag on the room's housekeeping status
  • Task sheets and attendant schedules, through getHousekeepingAttendantsSchedule and the taskSheets operations in the OPERA Cloud hsk module
  • Attendants on shift today, through the Roster resource in Deputy or shifts by location and role in 7shifts
  • Room state changes as they happen, through Mews ResourceUpdated webhooks and apaleo Unit changed events

Proposed actions

  • Target capability: propose an ordered room list per attendant, written through putTaskSheetRooms in OPERA Cloud once the supervisor approves
  • Target capability: propose moving one room between two attendants when one sheet runs long, with the credit count before and after
  • Target capability: propose a resequence of a single sheet when a checkout posts early or an arrival time moves, showing the rooms that swap
  • Target capability: propose a message to the housekeeping channel in Microsoft Teams or Slack with the changed sheet and the reason
  • Target capability: propose a Mews task for a rush room through tasks/add, with the arrival's ScheduledStartUtc as the deadline

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

What you can build

  • Put the room with an arrival due at the top

    A departure posts its checkout in Mews before midday and the next guest carries an early ScheduledStartUtc. Clean Sequence proposes that room ahead of the stayovers on the same sheet, and the supervisor approves in Microsoft Teams.

    With Mews, Microsoft Teams

  • Rebalance when an attendant calls in sick

    The Deputy roster shows one attendant fewer than the sheets assume. The operator proposes how the missing sheet's rooms split across the others, keeping each departure with an arrival due at the front, through putTaskSheetRooms in OPERA Cloud.

    With Deputy, Oracle OPERA Cloud

  • Skip the room with the sign on the door

    A Cloudbeds housekeeping/room_condition_changed webhook sets doNotDisturb on a stayover. Clean Sequence proposes moving that room to the end of the sheet and posting a note in Slack so the attendant does not knock twice.

    With Cloudbeds, Slack

  • Turn the rush room into a task

    apaleo reports a unit checked out and the incoming reservation already has that unit assigned. The operator proposes a rush task at the head of the sheet order and a message to the floor supervisor's channel in Microsoft Teams.

    With apaleo, Microsoft Teams

Requirements

  • A property management connector that exposes room state and reservation times: Oracle OPERA Cloud, Mews, Cloudbeds, or apaleo
  • For written task sheets, Oracle OPERA Cloud with the hsk module's taskSheets operations enabled for your application
  • A workforce connector with today's roster by role, such as Deputy or 7shifts, or a roster entered by the supervisor
  • A Slack or Microsoft Teams channel for the housekeeping office, where resequence proposals are approved
Authentication
Clean Sequence carries no login of its own. Departures, arrivals, room states, and rosters come through the property management and workforce connectors you connect; sheet changes go back through the property management connector after approval.

Limits

  • Mews, Cloudbeds, and apaleo expose room state and tasks but not attendant sheets; there the sequence is proposed as a list, not written.
  • Arrival times are only as good as the reservation carries. A guest with no time recorded is sequenced as a standard arrival.
  • It does not read Optii, Flexkeeping, or Amadeus HotSOS; a property on those systems receives proposals in its messaging channel.
  • Credits per room type are yours to set. The operator does not estimate cleaning times.

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 Clean Sequence ↗

Questions and answers

What does the supervisor approve?
The order of rooms on one attendant's sheet, or one room moving between two attendants. The card shows the sheet before and after, the checkout or arrival that caused it, and the credits. Approve as proposed, drag a room, or dismiss.
What is recorded for each sheet change?
A receipt: the previous order, the new order, the event that triggered it, who approved, when the PMS accepted the write, and how to restore the earlier order. Dismissed resequences are kept with the reason.
Does it ever change a sheet on its own?
No. It watches checkouts, arrival times, and room states and proposes an order. A sheet changes in OPERA Cloud only after approval, once. On Mews, Cloudbeds, and apaleo it never writes a sheet at all; the list is posted for the supervisor to act on.
Ask about Clean Sequence

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