Shifts and tasks.
The schedule, the briefing that opens a shift, the cleaning board, and the task board the rest of the day runs on.
The shape of a day
Two surfaces carry most of an operational day. Shifts answers who is working, when, and what they need to know before they start. Tasks and Projects answers what has to happen, who owns it, and whether it is done.
Almost everything else arrives on one of the two. A guest request becomes a task. A flagged issue becomes a task. A flow output becomes a task or a briefing. If you want to know what changed today, those are the two places to look.
Shifts
The schedule
The week, by department and by property. Who is on, who confirmed, and where the gaps are. A supervisor builds it, or a flow drafts it from tomorrow's occupancy and the supervisor publishes it — either way it is a draft until somebody publishes, and a published change is recorded rather than announced verbally to whoever was standing there.
Open shifts are visible as open, which is the point. A shift nobody has taken is easier to fix on Tuesday than at 06:00 on Saturday.
The briefing
A shift opens with a briefing instead of with a conversation in a corridor. What carried over from the last shift, what is arriving, what is broken, what the department needs to watch.
This is the handover that otherwise does not happen. Not because anyone is careless — because the outgoing supervisor left at 15:05 and the incoming one arrived at 15:20, and the only record of the intervening problem was a message in a group chat that has since scrolled.
The cleaning board
Housekeeping's own view of the property: each room's state, who it is assigned to, and how the load falls across the team. It is the one place a supervisor can read the whole floor without walking it, and the one place an imbalance — one attendant with fourteen rooms, another with six — is obvious before the shift ends rather than after.
Tasks and Projects
What a task carries
| Field | What it decides | | ---------------- | ---------------------------------------------------------------------------------------------- | | Property | Which hotel the work belongs to. Nothing becomes portfolio-wide by accident. | | Department | Where it routes, and which knowledge base an agent reads when helping with it. | | Assignee | The person on the hook. A department with no assignee is a queue, not an owner. | | Due | When it stops being fine. A board where everything is due today is a board nobody reads. | | Checklist | The steps inside the task, ticked as they are done, so a half-finished job hands over cleanly. | | Recurrence | Whether it comes back, and how often. | | Linked procedure | The standard this work follows, attached rather than remembered. |
The board
A kanban board per department or per project: columns you name, cards you drag, one glance to see what is stuck. Keep the columns few enough that a supervisor can read the board without scrolling sideways. The board is not the plan — it is what the plan looks like at 11:00 on a Thursday.
Recurrence
Work that repeats is defined once and comes back on its schedule: the monthly deep clean, the filter change, the fire-door check, the quarterly mattress rotation. The value is not the reminder. It is that the recurring work is on the same board as everything else, so it competes for the same hours honestly instead of being the thing that quietly never happens.
Templates and checklists
A task template carries its checklist with it, so the fourth deep clean is the same deep clean as the first, done by someone who was not there for the first three. Where a procedure exists in the department's knowledge base, link it to the template once and every task made from it arrives with the standard attached.
A shift, worked through
At 15:40 Lena M. opens the evening shift at Marina Bay Hotel. Her briefing lists what came over from the day: two rooms out of order, one late check-out extended to 18:00, and a lift engineer due at 17:00 who will need a service card.
Three tasks carried across the handover. One was raised by housekeeping and routed to maintenance — the air conditioning in a suite is blowing warm — and arrives with the unit's manual already cited, so Karim R. reads the model's procedure before going up rather than after.
Nothing in that paragraph is new work. All of it used to live in a group chat, a notebook and somebody's memory.
Internal chats, briefly
Conversation still has to happen, and Internal Chats is where it happens next to the record instead of in a personal account: channels per department or property, direct messages, threads on a specific thing.
The useful part is classification. A message that is actually a piece of work — "can someone look at 412, the kettle is dead" — is recognised as one, and can become a task on the right department's board rather than scrolling past the top of the screen.
Where to go next
- Knowledge bases — the procedures a task links to.
- Flows — what drafts a rota or a briefing before a person publishes it.