Reconcile hotel linen batches before using a contractor’s water allocation

A linen delivery can be complete while its water evidence is missing. A month can also end with towels still at the laundry even though one wash run is already documented. Reconcile the two questions separately.

This guide is for hotel housekeeping, procurement and reporting teams reviewing outsourced laundry records. Its fictional example follows two dispatch batches through three dated wash runs. It produces a linen custody check and a limited contractor allocation, not a hotel water footprint.

Fix the selected batches and the cut-off

All quantities, dates and references below are invented. The example selects two towel batches from one hotel and one independent offsite laundry. It excludes all other linen activity. The selected batches have no opening balance, losses, exchanges, replacements or transfers to another contractor. Counts use individual towels throughout.

The June cut-off is midnight ending 30 June 2026, at UTC+05:30. The contractor records processing on the actual run date. The hotel records dispatch and physical return on their own dates. This is the agreed convention for this internal exercise, not a universal reporting rule.

Retain three connected schedules. The custody schedule links dispatch and return tickets by batch ID. The processing schedule links each batch or rewash portion to its run ID. The allocation schedule links the run to its measured water record, weighed load records and supplied calculation. A single invoice cannot replace these relationships.

A wet dispatch-bag weight and a dry processing weight are different observations. Keep their labels and container tare instead of subtracting them as though they measured a loss. Here, towel counts close custody; the supplier’s separately recorded dry weights support its stated allocation convention.

Fictional batch-to-run relationships. W9 rewashes 15 towels already counted in L31; it creates no new dispatch. The article gives the complete dated records and allocation arithmetic.

Close June with the outstanding towels visible

• L31: the hotel dispatches 300 towels on 28 June. Run W8 processes all 300 on 29 June. The laundry returns 285 towels on 30 June and records the remaining 15 as awaiting rewash. Those 15 have not returned to the hotel.

• L32: the hotel dispatches 200 towels on 30 June. The laundry receives them that day but does not process or return them during June.

At the cut-off, dispatched towels total 300 + 200 = 500. Returned towels total 285. The outstanding balance is 500 − 285 = 215: 15 from L31 awaiting rewash and 200 from L32 awaiting their first wash. The record closes arithmetically without pretending that every towel has returned.

On 1 July, W9 rewashes L31’s 15 towels; they return on 2 July. On 2 July, W10 processes L32’s 200 towels; they return on 3 July. The selected June dispatches now have 285 + 15 + 200 = 500 returns and no outstanding balance.

W9 is an additional processing event for existing towels. It is neither a new hotel dispatch nor 15 additional towels acquired. Keep the link L31 → W8 and the separate link L31 → W9. L32 links only to W10. This prevents the processing history from inflating the custody count.

Use the supplier’s run evidence, not a towel conversion

The fictional contractor supplies a convention for these selected runs: allocate each run’s measured incoming water in proportion to the hotel’s weighed dry textile mass in that run. Its tickets separately identify hotel and other-customer mass on a common dry basis. The hotel does not derive these weights from the towel counts.

Assume the supplied run measurements and mass records are complete, non-overlapping and correctly matched. The convention is stipulated for this exercise; it is not an industry factor or a recommended allocation method. The resulting estimates cover the selected runs only. They exclude the contractor’s other operations and any upstream textile production.

• W8, 29 June: 12 m³ incoming water; 600 kg total dry textiles; 150 kg attributed by the load ticket to L31. Allocation: 12 × 150 ÷ 600 = 3 m³.

• W9, 1 July: 1.5 m³ incoming water; 75 kg total dry textiles; 7.5 kg attributed to L31’s rewash portion. Allocation: 1.5 × 7.5 ÷ 75 = 0.15 m³.

• W10, 2 July: 10 m³ incoming water; 500 kg total dry textiles; 100 kg attributed to L32. Allocation: 10 × 100 ÷ 500 = 2 m³.

Under the stated processing-date convention, June contains W8’s 3 m³. July contains W9 and W10: 0.15 + 2 = 2.15 m³. The three-run allocation totals 5.15 m³ across both months. Neither the June dispatch date nor the July return dates move all three estimates into one month.

Even if the rewash is free of charge, W9 remains in this processing schedule. Its physical record does not disappear when the invoice contains no extra charge. Conversely, a repeated invoice reference is not evidence of another wash run.

Keep the hotel’s own record identifiable

For comparison, the fictional hotel’s checked June incoming-water meter records 900 m³. Assume it covers all water entering the selected hotel premises, with no other supply route or onsite laundry. The independent contractor uses its own supply; no water moves from the hotel to that laundry.

GRI 303 addresses an organisation’s withdrawal and water-related impacts linked through business relationships. Its glossary and Disclosure 303-1 provide the reporting context.

The contractor allocation is not additional hotel withdrawal. Keep the hotel’s 900 m³ separate from the selected June laundry estimate of 3 m³; do not relabel 903 m³ as hotel withdrawal.

Ask for the missing link before closing the evidence question

Suppose W8’s 12 m³ record is absent. The 300-towel movement and the 150 kg load ticket can remain supported, but this example’s 3 m³ calculation cannot be reproduced. Ask for the run’s water measurement and its coverage. Do not fill the gap with a generic litres-per-kilogram figure.

If the supplier initially omits W9, ask whether the retained 15 towels were reprocessed and request the dated run link. Do not add 15 to the original dispatch. If the run occurred but its measurement is unavailable, retain the event and flag the allocation as unresolved.

At handover, housekeeping confirms the 215-towel June balance; procurement resolves the run links and supplier documents; the reporting owner labels the supported allocations and their limits. Preserve the June snapshot when July returns arrive. A later closure note can resolve the outstanding towels without rewriting June’s history.

These checks establish the stated record relationships and arithmetic only. They demonstrate no saving, service quality, regulatory compliance or complete laundry water assessment. For help organising a reporting handover, discuss the available records with Nitium Advisory.

Primary source checked 14 October 2026. This teaching case contains no actual hotel or contractor data and claims no independent professional sign-off.

Source

GRI 303: Water and Effluents 2018. Disclosure 303-1 and glossary: water withdrawal.