Structure standards around real room situations
Departure and stayover need different lists because their operating goals differ.Gather recurring room situations with housekeeping and front desk. Define the result for departure, occupied stayover, long-vacant room and vacant room before release.
Separate required standard, category-specific points and one-off guest requests. Do not put every exception into the common state list.
Design the standard from real room situations rather than one universal cleaning list. Separate at least departure clean, occupied stayover service, vacant-room inspection and any supervisor quality step. Define the starting condition, guest promise and final state for each list. A departure list prepares an empty room for the next guest; a stayover list delivers an agreed service while the room remains occupied; a vacant inspection checks readiness without pretending a new full clean; supervisor approval verifies a completed result. Keep booking-specific requests, such as cot preparation or allergy-safe bedding, linked to the stay instead of turning every exception into a permanent task. Keep technical defects and date-bound unavailability in rooms and blocks because they affect inventory. Before writing tasks, walk one representative room of each category with the housekeeping lead and note the observable sequence, hotel standard, safety checks and handoff points. The structure is complete when staff can choose the right list from the room situation without guessing.
| Layer | Example | Where maintained |
|---|---|---|
| Required state task | Clean bathroom surfaces and check dry | Settings → Housekeeping |
| Category-specific | Check studio kitchenette | Hotel standard and suitable extra task |
| Booking request | Prepare baby cot | Booking/room context |
| Defect | Leak or broken lock | Rooms and block |
Write short, unambiguous and verifiable tasks
A verb, an object and a visible result are usually enough.Start tasks with concrete actions such as change, clean, refill, check, document or release. Name the object and measurable outcome.
Limit the standard list to tasks required for every room in that state. Test wording with a new employee and rewrite anything that needs hidden context.
Write each task as one observable action with a visible completion criterion. Replace “ensure perfect bathroom” with instructions such as clean and dry washbasin, test the drain, replace towels to the configured quantity and inspect mirror and fittings under light. Start with a verb, name the object, state the required result and add a threshold only when staff can verify it consistently. Split tasks when different failures require different corrections; combine them only when they are always performed and checked together. Keep the order aligned with the physical route from preparation through cleaning, replenishment, function test and final inspection. Avoid slogans, unexplained abbreviations and policy text inside every item. A checklist guides work; training material explains the wider method. Test wording with a new employee and a supervisor: both should understand what to do, what “passed” looks like and where to report a deviation. If two people produce different interpretations, revise the central wording before release.
| Too vague | Better | Verification result |
|---|---|---|
| Clean room | Change all bed linen and make bed without creases | Bed is visibly complete |
| Check bathroom | Clean taps, mirror and shower; check surfaces dry | No residue or wetness |
| Refill everything | Refill towels and amenities to category standard | Target quantity is present |
Create state tasks centrally in STRYK
One maintenance source powers digital view, workflow and PDF.Open Settings → Housekeeping, choose an active state and order its tasks from preparation through cleaning and amenities to final inspection. Verify the saved tasks reload.
Settings store state tasks as the shared source. Day plan and STRYK PDF use the same data, so do not duplicate them in local templates.
Maintain status tasks only in Settings → Housekeeping and edit one operating state at a time. Confirm the state name and whether it applies to an occupied or vacant room before changing its list. Add tasks in execution order, remove true duplicates and preserve any critical inspection step even when it rarely fails. Save through the product, wait for the visible success state and treat an STRYK error as a failed save. Leave settings, reopen the same state and compare every task and its order. Then load the housekeeping plan for a test date to confirm the day view receives the saved `status_tasks`. Do not keep a spreadsheet, local storage list or manually edited PDF as a second source. If a wording change must be scheduled for a future standard date, document the rollout and training decision rather than silently changing instructions mid-shift. Central maintenance is successful when the same ordered tasks survive reload and appear for the intended room state in operations.
Save and verify safely
- 01Choose state
Edit only tasks for this operating state.
Correct context - 02Set order
Map workflow from preparation to inspection.
Executable without jumps - 03Wait for save state
Do not treat error as success.
Saved visibly - 04Reload
Leave settings and reopen.
Tasks reload identically
Keep extra states operationally valid
A housekeeping state describes cleaning and inspection, not every room issue.Use only genuine housekeeping extras such as Supervisor approved or Do not disturb. Defect, out of order, maintenance and renovation belong to room blocks.
For each extra state ask whether it describes real housekeeping, occupancy is clear and tasks are needed. If it must block sales, it is in the wrong place.
Enable an extra state only when it describes a genuine housekeeping condition that staff must recognise in the cleaning workflow. Supervisor approved can represent a defined quality gate after work is done. Do not disturb can represent an occupied guest declining or delaying service and should connect to the hotel’s retry and welfare procedure. Defect, out of order, out of service, maintenance, renovation and room deactivation do not belong here: they influence availability, sale and check-in and must use the room or block process. For every proposed state, answer four questions: what observable situation starts it, whether the room is occupied or vacant, which tasks or decision end it, and whether it must block inventory. If the fourth answer is yes, route it outside housekeeping. Keep the number of states small enough for immediate recognition, define their permitted transitions and test that staff cannot use an attractive label to bypass a required inspection or technical decision.
| Case | Right place | Why |
|---|---|---|
| Supervisor checked room | Housekeeping extra state | Quality step in cleaning workflow |
| Guest requests no service | Do not disturb | Occupied operating state |
| Lock defective | Room/block | Check-in and sales may be affected |
| Two-week renovation | Room/block | Date-bound unavailability |
Build distinct departure and stayover lists
Preparing for the next guest differs from servicing an occupied room.The departure list prepares a vacant room for the next guest and covers linen, bathroom, surfaces, floor, waste, stock and inspection. Ready follows inspection, not automatic task completion.
The stayover list respects the active stay and personal belongings. Its end state is stayover service done, not Ready.
Build the departure and stayover lists from different promises. For a departure room, include linen and bed setup, bathroom sanitation, surfaces and floor, waste, towel and amenity quantities, equipment function, visible damage check, booking-specific preparation and final vacant-room inspection. The list leads to Done and, after the required quality control, Ready. For an occupied stayover, include only the agreed service: enter according to the guest and property rule, respect personal belongings, refresh bed and bathroom within scope, handle towels and consumables to policy, remove waste and record Do not disturb or an unresolved request. The room remains occupied and ends as Stayover service done. Do not copy the departure list and delete a few lines; that approach leaves dangerous release language and unnecessary handling of belongings. Use room-category variants only for real differences such as kitchenette, balcony, sofa bed or accessibility equipment, while keeping a common core so quality can be compared.
Test checklists in the real day plan
A list is approved only when it remains clear during real work.Use one departure, one stayover and one vacant check room in Hotel Nordlicht. Assign active staff and verify the expected tasks appear in useful order without hidden explanation.
Observe length, duplicates and missing criteria. Edit centrally, reload and repeat the same case until the workflow passes visibly.
Test the lists in the isolated Hotel Nordlicht hotel account with controlled records, never in an existing customer or unrelated test hotel. Prepare at least three cases on one known date: a departure followed by an arrival and special setup, an occupied stayover with a guest preference, and a room where a sale-affecting defect is discovered. Use an active test housekeeper, assign the room, press Start only at actual execution and work every displayed item in order. Observe unclear wording, missing quantities, duplicated actions, excessive scrolling and any step that requires oral knowledge. In the defect case, verify that staff stop release, report the concrete issue and use the room/block workflow instead of inventing a housekeeping state. Reload after every central correction and repeat the same scenario so results are comparable. Record expected list, actual list, completion state and exception outcome. The test passes only when a trained operator can complete the case without hidden instructions and the shared room state remains truthful.
Three required test cases
- 01Departure + arrival
Full clean, extra request and inspection to release.
Ready only after inspection - 02Stayover
Respect belongings and complete daily service.
Stayover done, still occupied - 03Defect during work
Stop checklist, report concretely and trigger room workflow.
No false release
Approve digital view and PDF together
A standard applies only when every intended work format shows the same content.Open the STRYK PDF for the same date and compare room, state, assignment and tasks. Fix the central task or renderer rather than creating a second manual PDF.
Have housekeeping lead and an operating staff member approve completeness and usability. Record approval date, cases and next review.
Treat the digital plan and printable day plan as one housekeeping standard. For the same test date and selected document language, compare room number, movement, assignment, state and every checkbox task. Preview, download and print should show the same rooms, assignments, states and tasks. If something is missing, correct the central checklist once. Check long wording, special characters, column width and page transitions so no instruction is cut off or assigned to the wrong room. Have the housekeeping lead approve completeness and an operating employee approve clarity and practical sequence. Record version date, tested room cases, reviewers, open corrections and next review trigger. Review after a renovation, new equipment, changed service promise, recurring defect or material process change, not after every casual preference. The release is complete when central settings, digital day plan and PDF show the same tasks and both reviewers can reproduce the expected final states without private notes.
Checklist approval
- Every active state has a short clear and logically ordered list.
- Departure, stayover and vacant room were tested on real test rooms.
- Extra states describe housekeeping only; defects and blocks remain in rooms.
- Digital view and PDF show the same tasks in the selected language.
- Housekeeping lead and operating test user confirmed usability.
