One Turnaround Column, Two Readers: Housekeeping and the Front Desk

The Problem Hiding in a Single Column

Picture a small flat in Sarawak with back-to-back bookings. Checkout is at 11am, the next guest arrives at 3pm, and the linen has to move through a laundry cycle in between. The host keeps a handover table shared between housekeeping and the front desk. One column is headed 'Ready by'.

Housekeeping reads that column as the time the used linen must be bagged and handed over for collection. The front desk reads the same column as the time clean linen will be on the shelf and available for the next room setup. Both readings are reasonable. Both are wrong for the other team. The result is a table that looks complete but produces two different expectations from one number.

This is not a people problem. It is a header problem. A single column is carrying two different meanings, and no amount of goodwill will reconcile them until the table says which meaning it holds. The fix is small: split the column, name each half for the action it describes, and add one row that shows the difference in practice.

Everything below is a working method you can adapt. Where a brand service is mentioned, it is drawn from supplied company information and cited; the rest is practical advice for hosts and accommodation operators.

Why 'Ready' Is a Dangerous Word on a Handover Table

Words like ready, done and cleared feel efficient because they compress detail. On a handover table, that compression is where mistakes live. 'Ready' does not say ready for what, ready where, or ready for whom.

A useful test is to ask whether a reader could act on the entry without asking a follow-up question. If housekeeping sees 'Ready by 1pm' and has to ask 'ready for pickup or ready on the shelf?', the column has failed. If the front desk sees the same entry and has to ask 'can I set the bed now?', it has failed again.

Two habits help. First, name columns after physical states rather than general progress: 'Bagged and collected', 'Returned and shelved'. Second, keep one column for one owner. If two teams need to know about the same batch of linen at different moments, that is two columns, not one.

This matters most when bookings are close together. A short gap between checkout and check-in leaves little room for a misunderstood timestamp, and the cost of a wrong reading is a delayed room setup rather than a corrected spreadsheet.

A Fictional Flat With Back-to-Back Bookings

Take a two-bedroom flat, Unit 7, with a checkout at 11am and a check-in at 3pm the same day. The host uses an outside laundry service and keeps a handover table for the two teams.

The original table has four columns: Unit, Date, Items, Ready by. On the day in question it reads: Unit 7, 12 June, 2 bed sets and 4 towels, 1pm.

Housekeeping plans to strip the beds at 11:15am, bag the linen, and have it at the collection point by 1pm. The front desk, reading the same row, tells the incoming guest that the flat will be set by 1pm and starts arranging an early check-in. By 1:30pm the linen has left the building but has not returned. The front desk is now explaining a delay that was never a delay; the schedule simply meant something different to each reader.

Nothing was neglected. The table was ambiguous. The revised version below keeps the same information but removes the ambiguity by giving each team its own column and its own verb.

Revised Headers: Name Each Column for Its Action

Replace the single 'Ready by' column with three columns that describe physical states and owners:

Bagged and at collection point (housekeeping) — the time the used linen is bagged and waiting for the laundry service. Collected by laundry (housekeeping or driver) — the time the bag leaves the property. Returned and shelved (front desk) — the time clean linen is back in the store and available for room setup.

Each header now contains a verb and a place. A reader cannot easily mistake 'bagged and at collection point' for 'returned and shelved'. The owner in brackets tells each team which entry they are responsible for updating.

If you also track guest-facing promises, add a fourth column, 'Flat set for guest', owned by the front desk. That separates the linen milestone from the room-readiness milestone, which are related but not the same event.

Keep the table to one row per unit per turnover day. Long tables with merged cells are harder to read at a glance, and the whole point is a glance.

One Sample Row, Rewritten

Here is the same day rewritten with the new headers. The values are illustrative, not a schedule to copy.

Unit: 7. Date: 12 June. Items: 2 bed sets, 4 towels. Bagged and at collection point (housekeeping): 12:45pm. Collected by laundry: 1:10pm. Returned and shelved (front desk): 2:20pm. Flat set for guest: 2:45pm.

Read this row as a story. Housekeeping bags the linen before the collection window. The bag leaves shortly after. Clean linen is back on the shelf with time for the front desk to set the flat before the 3pm check-in. If any timestamp slips, the next reader can see exactly which stage moved and who owns it.

Notice that no single number now carries two meanings. The front desk does not need to interpret housekeeping's entry, and housekeeping does not need to guess when the shelf will be full. The row is longer, but it is read faster because each reader goes straight to their own column.

Where an Outside Laundry Service Fits

If you use an outside laundry service, the handover table is only as good as the collection and return windows you agree with the provider. Ask what time collections happen, what time returns are typically shelved, and how the provider confirms a batch has been received. Then build those windows into your columns rather than guessing.

Sinar Saredah Sdn Bhd provides laundry, dry cleaning and specialist cleaning services in Kuching and Miri, Sarawak, and its services include pickup and delivery. For hosts in those areas, that means the collection and return stages in your table can map to a service you can actually schedule against. The company also states that it is open every day, including public holidays, with drop-off from 7am, which is useful context when you are planning a turnover on a holiday weekend.

This is not a recommendation to change providers. It is a reminder that the table should reflect the real windows your provider works to, not an idealised version of them. If your provider's return window is later than your check-in, the table should show that honestly so the front desk can plan around it.

A Pre-Turnover Check the Host Can Run

Before the next turnover, run this short check. It is a set of author heuristics, not a certified audit, and you can score it however you like.

One: read each column header aloud and ask whether it contains a verb and a place. If not, rename it. Two: confirm every column has exactly one named owner. A column with two owners will be updated by neither. Three: pick the next turnover day and fill one row using only the new headers. If you have to explain a value to the other team, the header is still ambiguous. Four: check that the guest-facing promise (flat set) is a separate column from the linen milestones. Five: confirm the collection and return windows match what your laundry provider actually works to, including weekends and public holidays. Six: after the turnover, compare the planned timestamps with what happened and note which stage moved. That note is more useful than a general comment that the day was busy.

A simple pass mark is that both teams can read the row without asking a question. If they can, the table is doing its job. If not, the fix is usually another header, not another reminder.

Keeping the Table Useful Over Time

A handover table drifts when the people using it change. New housekeeping staff inherit the headers without the conversation that produced them, and the old ambiguity can creep back through shorthand.

Two small habits protect against that. First, keep a one-line note at the top of the table explaining what each column means, written in plain language. Second, review the headers whenever a turnover goes wrong, and ask which column was misread rather than who misread it. That keeps the conversation on the table, where the fix is cheap.

If your property handles specialist items alongside everyday linen, such as curtains, carpets or soft furnishings, keep those on a separate line with their own collection and return stages. Sinar Saredah's services also cover carpet cleaning, curtain cleaning, wedding gown cleaning, shoe cleaning and soft toy cleaning, so a host with mixed cleaning needs may find it simpler to track those items on a second table rather than crowding the linen row.

The goal is modest: one table that two readers can use without translating it for each other. Get the headers right, show one honest sample row, and check it before the next turnover.