# Daily Operations Flow Overview

**Version:** 2.0
**Date:** 2026-08-20
**Supersedes:** v1.0 (2026-06-15), which described a day shift and called it the day.
**Type:** Method, with the shift board that corrected it

---

## Why this version stopped calling it a daily loop

Version 1.0 described a hotel's day as a loop: set up in the morning, turn the
rooms at midday, land the arrivals in the afternoon, hand over at night. It is the
standard picture and it is what most operations manuals show.

It is also, at this property, wrong by about eight hours.

Reading the actual housekeeping department board at **Westmark Fairbanks** against
the room blocks it was supposed to serve produced a question the standard picture
cannot answer, and answering it changed the shape of the document.

---

## 1. The question the board raised

Roughly **58 rooms carry occupancy windows like `1:30p–11p` and `8p–2a`**, and
some departures leave the property at **04:15**.

Those are not guest-leisure patterns. They are rest blocks for crews working a
transport schedule, and they invert the assumption underneath every daily-loop
diagram: that a room is vacated in the morning, serviced at midday, and reoccupied
in the afternoon.

**A room occupied from 8pm to 2am is dirty at 2am and needed again that evening.**
No amount of morning-shift efficiency touches it.

So: *who services rooms on that cycle?*

## 2. The answer, which was already on the board

The property was already doing it. The board shows a distinct block of room
attendants on **3:00p – 11:30p**, staffed, alongside the conventional day shift:

| Group | Hours |
|---|---|
| Management / supervisors | 7:00a – 4:30p |
| Inspectors / leads | 8:00a – 4:30p, or 8:00a – 3:00p |
| Room attendants, day | morning through afternoon |
| **Room attendants, evening** | **3:00p – 11:30p** |

**The finding was not that a shift was missing. It was that the shift existed and
the operating documents did not mention it.** The written picture of the day
stopped at 4:30pm; the actual operation ran to 11:30pm and served a category of
room the documents did not describe.

> **The general lesson: read the shift board against the room blocks before you
> write the day down.** A daily-flow document that contradicts the roster is worse
> than none, because it trains people into a picture their own building disproves.

## 3. The day, as it actually runs

### Morning — set up

- Review arrivals, departures and stayovers in aggregate.
- Group arrivals into waves (see *Arrival-Wave Room-Blocking Methodology*).
- Check inventory against par and flag shortages (see *Inventory Par-Level
  Tracking Template*).
- **Read the overnight handover** — what the evening shift left, and which
  off-cycle rooms turned after the day team went home.
- Brief on priorities, not individuals: which wave, which floors, which types are
  tight.

### Midday — turn the rooms

- Housekeeping works the prioritised board: departures in wave order, stayovers on
  schedule.
- Front desk tracks readiness by wave and assigns units as they clear.
- Hold the flex buffer for walk-ins and re-rooms.
- Reconcile at midday and re-sequence. The morning plan was a hypothesis.

### Afternoon — land the arrivals

- Check in against ready rooms, wave by wave.
- Keep a short watch list of any reservation still waiting on a room, and clear it
  first.
- Replenish floor closets to baseline so the evening shift starts stocked.
- **Hand over to the evening shift explicitly.** This is a shift change, not a
  wind-down, and it is where the day's information is most often dropped.

### Evening — the second turn

- Service the off-cycle rooms as they vacate.
- Prepare rooms for arrivals landing after the day team has gone.
- Carry the exceptions forward in writing.

### Night — the audit and the early departures

- Close the day's accounting.
- Stage anything needed for departures leaving before the morning shift arrives.
- Leave the handover the morning brief will read.

## 4. Where the handoffs actually are

Most of what goes wrong in a day goes wrong at a boundary, not inside a
department:

- **Housekeeping → front desk**, on room readiness. The failure is a room ready in
  the system and not in reality, or the reverse.
- **Front desk → housekeeping**, on late checkouts and re-rooms. The failure is a
  change the board never hears about.
- **Day shift → evening shift.** The largest and least documented boundary at this
  property, precisely because the written day did not acknowledge it existed.
- **Evening → night → morning.** Three handovers in eight hours, usually between
  the fewest people on duty.

**Instrument the boundaries, not the departments.** A department's own metrics
will look fine while the handoff between two of them is where the day is lost.

## 5. What transfers, and what does not

The loop, the handoff list and the rule in section 2 are general.

The **evening shift is not general** — it exists here because this property serves
crew rest blocks on a transport cycle. A property without that business may
genuinely finish at 4:30pm, and adding a second turn there would be cost with no
work behind it.

**The transferable instruction is the diagnostic, not the answer:** before writing
your day down, pull the occupancy windows on your own blocks and check them
against your own roster. If there are rooms occupied on a cycle your shift pattern
does not cover, you have either an undocumented shift or an uncovered category,
and it is worth knowing which.

---

*Version 2.0. Superseded versions stay listed rather than disappearing. Shift
structure is operational; no employee name, no schedule row for any individual,
and no guest information appears in this document.*