LINEN LOSS ACCOUNTABILITY
Who is accountable for linen loss — the hotel or the laundry?
Accountability follows the scan record. IntelTagRFID is a UHF-RFID textile tracking and laundry reconciliation platform that matches every dispatched item against what the receiving site actually scanned, item by item and against the delivery note it travelled under. Each item is classified on-note, off-note, or no-dispatch-found. Because both legs of the cycle are recorded independently, a shortfall is attributed to a specific leg, collection and day rather than argued over as a monthly total. The question stops being whose word to take, and becomes which leg the record breaks on.
Why monthly totals never settle the argument
A monthly shortfall is a single number with no address. It cannot distinguish linen that never left the laundry from linen that arrived and was then carried out of the building, and it gives neither party anything to act on. Both sides can hold an honest view of the same total and reach opposite conclusions, which is why linen disputes tend to recur every month rather than resolve.
Reconciliation per delivery note, not per month
Every item is matched to the note it was expected on. On-note is the normal case. Off-note means the item arrived under a note it was not listed on. No-dispatch-found means there is no dispatch record for it anywhere, so either it was never scanned out or it entered the cycle outside the tracked process. Each note carries its own conversion percentage, and any figure can be opened down to the individual items behind it.
When the record points at the receiving scan, not the linen
Not every discrepancy is missing stock. Where off-note items cluster around one note number, the dashboard surfaces a likely-wrong-note suggestion with a confidence percentage — a deterministic heuristic over the scan pattern, not a prediction. That matters commercially: it separates an operator selecting the wrong note at the receiving bay from linen that genuinely did not arrive, and only one of those is a loss.
What a variance finding actually produces
Rolling send-versus-receive match ratios are computed per leg and compared against a configured alert floor, set by default at 95%, with a separate flag above 105% to catch a day that is receiving back more than it sent — usually a catch-up rather than a gain. Zero-scan days, where one party recorded nothing while the other recorded items, are identified separately because they are a process or equipment failure rather than a loss event. The output is a findings report with a plain-language root cause and numbered remediation actions.
Common questions
Neither party has to. Both legs are scanned independently, so the record itself shows which leg a shortfall sits on. The discussion moves from assertion to a specific collection on a specific day.
On-note means the item was listed on the delivery note it arrived with. Off-note means it arrived under a different note. No-dispatch-found means no dispatch record exists for it anywhere, which points either to a missed outbound scan or to an item entering outside the tracked process.
Yes. Conversion is measured per delivery note, so a discrepancy is located to the note, the day and the leg, and can be opened to the individual item identifiers behind it.
The rolling match-ratio alert floor is a configured setting, 95% by default, with a separate flag for days above 105%. Both are configuration, set per deployment — not a performance claim.
Yes. A rolling history window, 120 days by default, allows late or consolidated scans to be applied back to the days they belong to, so batched industrial data reconciles instead of showing a shortfall followed by a surplus.
Yes. A per-item audit reconstructs the full chronological history of a single tag across dispatch, receive, movement, stock-take, exit, return and allocation, pairing each dispatch with its subsequent receive to show complete or broken cycles.
Talk to Us
Tell us about your operation and we will come back with a practical assessment.