A Hotel Linen Log for Matching a Week Number to Its Calendar Dates

Why a Week Number Alone Is Not a Date

A linen report that refers to "week 1" is only useful if everyone reading it agrees which seven days that means. The label is a shorthand, and shorthand breaks down the moment two people count from different starting points. A housekeeping supervisor may count the first week from the day the hotel opened its doors for the season; a storekeeper may count from the first Monday of the month; a supplier's clerk may count from the first day a bundle was collected. All three can honestly write "week 1" and mean three different date ranges.

The fix is not to ban week numbers. They are convenient for rosters, batch planning and repeating schedules. The fix is to make every week number carry its dates in the same line of text. Once the dates sit beside the number, the label becomes a check rather than an assumption, and a reader who disagrees with the counting method can still see exactly which days are covered.

This guide is written for a hotel coordinator in Sarawak who has to reconcile a linen log against a calendar. It does not describe any provider's processing schedule, turnaround or terms. It is about the internal paperwork that decides which dates a batch belongs to before anything leaves the property. Where a property works with an external laundry service, the written terms that apply when linen is accepted are a separate matter and should be read on their own.

Choose One Counting Rule and Write It Down

Before any week number appears in a log, the property needs a single written rule for how weeks are counted. Three common rules are worth considering, and each has a cost.

The first is the ISO-style week, where weeks start on Monday and week 1 is the week containing the first Thursday of the year. It is precise and internationally recognised, but it can put late-December days into week 1 of the following year, which surprises staff who think of the year as ending on 31 December.

The second is the calendar-month week, where week 1 is simply the first seven days of the month starting on the 1st. This is easy to explain and easy to check by hand, but the weeks drift against the days of the week, so "week 1" may begin on a Saturday one month and a Wednesday the next.

The third is the operational week, where the property defines its own week boundaries around its busiest changeover day. A hotel that turns over most rooms on a Friday might run its linen week from Saturday to Friday so that each week contains one full turnover cycle.

Whichever rule is chosen, write it at the top of the log template in one sentence, with an example. A rule that lives only in one supervisor's head will not survive a change of shift. The aim is that a new clerk can read the rule and reproduce the same dates without asking anyone.

A Worked Crossover Example for Week 1

Suppose a property uses the operational week and decides that its linen week runs from Sunday to Saturday. It also decides that week 1 of a new operating year begins on the first Sunday of January. In a year where 1 January falls on a Wednesday, the first Sunday is 5 January. Week 1 therefore runs from Sunday 5 January to Saturday 11 January, and week 2 begins on Sunday 12 January.

Now look at what happens at the other end. The days from Wednesday 1 January to Saturday 4 January sit before week 1 begins. They are not in week 52 of the previous year under this rule, because the previous operating year ended on its own last Saturday. They form a short stub period that needs its own label, for example "pre-week 1" or "year opening, 1–4 January".

This is the crossover that causes most confusion. A clerk who assumes week 1 starts on 1 January will place the 1–4 January batches into week 1 and then find that week 1 contains eleven days instead of seven. A clerk who assumes the previous year's week 52 runs to the end of December will double-count those same days. Writing the stub period explicitly removes both errors.

The same logic applies at the end of the year. If the last Saturday of December falls on the 27th, then 28–31 December is a closing stub. Label it, date it, and keep it out of both the numbered weeks.

Deciding Where a Sunday Batch Belongs

Sunday is the awkward day in most linen logs, because it is both a rest day for some staff and a busy checkout day for many hotels. The question is not whether Sunday counts, but which week it counts towards.

Under a Sunday-to-Saturday rule, a Sunday batch opens a new week. A bundle collected or counted on Sunday morning belongs to the week that starts that day, even though the calendar week most staff picture begins on Monday. Under a Monday-to-Sunday rule, the same Sunday batch closes the week that began six days earlier. Both are defensible; mixing them is not.

The practical test is to ask what the batch is being matched against. If the log exists to compare linen issued against rooms turned over, then the week boundary should follow the turnover cycle, so that each week's linen and each week's room nights line up. If the log exists to match invoices to delivery dates, the boundary should follow whatever date the delivery note carries, and the log should record that date rather than a week number alone.

A simple convention helps: never let a Sunday batch sit in a row labelled only with a week number. Give it a date, and give the week it belongs to a start and end date on the same row. If a batch spans midnight, record the date the count was completed, and note the earlier date in a remarks column.

Building the Log Columns

A workable linen log needs more columns than a week number and a count. The following set is a starting point that a coordinator can adapt; it is an author's suggestion, not a standard.

Week label: the number, written as "W01" so that sorting works. Week start and week end: two date columns, always filled. Batch date: the actual date the linen was counted, collected or returned. Day of week: a short text field, so a Sunday batch is visible at a glance. Item type and quantity: sheets, pillowcases, bath towels, hand towels, bath mats, table linen, each on its own row or its own column. Condition note: stained, torn, missing, or returned short, with a count. Reference: the delivery note or internal docket number. Remarks: free text for stub periods, split batches and anything that does not fit.

Two habits make these columns work. First, fill the week start and week end before filling any counts, so the date range is fixed before numbers arrive. Second, treat the remarks column as part of the record rather than an afterthought; a stub period explained in remarks is far easier to audit than one reconstructed from memory months later.

Reconciling the Log Against the Calendar

Once the log has dated weeks, a short reconciliation step catches most mismatches before they reach an invoice or a stock report.

Start by listing every week label used in the period and checking that the date ranges are contiguous, with no gaps and no overlaps. A gap usually means a stub period was left unlabelled. An overlap usually means two people counted the same days under different rules.

Next, check that the number of days in each labelled week is seven, except for the stub periods, which should be shorter and clearly marked. A week showing eight or nine days is a signal that a boundary was applied inconsistently.

Then check the batch dates against the day-of-week column. If a row says Sunday but the date falls on a Tuesday, either the date or the day is wrong, and the count on that row should be treated as unverified until it is corrected.

Finally, compare totals across the boundary. The last batch of one week and the first batch of the next should not both claim the same items. Where a batch genuinely spans a boundary, split it and record the split in remarks rather than assigning the whole batch to one side.

These checks are quick on a well-built sheet and slow on a poorly built one, which is itself a reason to fix the columns early.

Where an External Laundry Service Fits In

The log described here is an internal document. It records what the property counted and when, and it gives every week number a date range that a reader can verify. It does not describe what happens to linen after it leaves the property.

Where a hotel in Kuching or Miri works with an external laundry service, the property's own records and the provider's records need to meet at a shared reference. The batch date and the delivery note number are usually the strongest common fields, because both sides can point to the same piece of paper. A week number alone is a weak reference, since the provider may count weeks differently.

Sinar Saredah Sdn Bhd provides laundry, dry cleaning and specialist cleaning services in Kuching and Miri, Sarawak, and its written customer terms apply when it accepts items, linen, garments and other cleaning requests. Those terms sit alongside quotations, invoices, branch notices and written service confirmations, so a coordinator should read them as a set rather than in isolation. The terms do not replace the property's own log; they define the paperwork that surrounds an accepted batch.

For hotel linen specifically, the practical step is to agree with the provider which date field both sides will quote, then make that field a required column in the log. Everything else, including the week number, becomes a convenience for internal reporting rather than a point of dispute.

A Short Checklist Before the Log Goes Out

Before a linen log is circulated or used to support a report, run through these questions. They are a coordinator's checklist, not an audited standard.

Is the counting rule written at the top of the sheet, with one worked example? Does every week label carry a start date and an end date? Are stub periods at the start and end of the year labelled and dated separately? Does every Sunday batch have a date and a day-of-week entry? Are the date ranges contiguous, with no gaps and no overlaps? Does any labelled week contain more than seven days? Do the batch dates agree with the day-of-week column? Is any batch counted twice across a boundary? Is the shared reference field, such as a delivery note number, filled for every external batch? Are remarks used to explain splits, stubs and corrections?

A log that passes these checks is not necessarily perfect, but it is readable by someone who was not present when the counts were made. That is the real test of a week-number system: whether a colleague on the next shift can reconstruct the same dates without asking.