HOW IT WORKS
How Does RFID Linen Tracking Work?
RFID linen tracking works by attaching a small, sealed radio tag to every item, then reading those tags automatically at each point the linen moves through. Because the tags can be read in bulk without line of sight, counting stops being a separate task and becomes a record of movement the operation was already performing.
The result is that every sheet, towel, scrub set or uniform has a traceable history: where it has been, how many times it has been washed, who last held it, and whether it completed its last cycle.
Step one: tagging
Each item receives a UHF RFID tag, either sewn in or heat-sealed on. The tag is passive, meaning it has no battery — it draws power from the reader’s radio field when scanned. That is why laundry tags survive years of industrial washing with no maintenance.
The tag carries a unique identifier. Everything else — item type, owner, wash count, current location — is held in the system and linked to that identifier.
Step two: read points
Readers are installed at the points where you need visibility. A typical deployment covers some combination of tagging, dirty receive, heat seal, item movement, rewash, mending, packaging, exit monitors and handheld stock-take positions.
Which points you cover determines what the system can tell you. Readers at dispatch and receive answer “did it arrive”. A reader at the wash tunnel answers “was it actually washed”. Readers at doorways answer “did it leave the building”.
Step three: the cycle is reconciled leg by leg
Linen moves in a loop, and each directional movement is a leg. A hospital loop has four: clean linen out of the laundry, clean into the hospital, dirty out of the hospital, and dirty back into the laundry.
Every dispatch is matched against its corresponding receive, item by item, using the item code and the delivery note. Each item is classified as on-note, off-note, or no-dispatch-found, and per-note conversion rates show how much of each consignment was accounted for.
This is the difference between knowing that linen is disappearing and knowing where. A shortfall attaches to a specific leg, a specific collection and a specific day, rather than appearing as an unexplained gap at month end.
Step four: exceptions surface automatically
Rather than requiring someone to interrogate the data, the system pushes the exceptions forward.
Items are bucketed by days since their last scan, from a week through to never-seen, so stock that has gone quiet appears on a follow-up list. Items whose last scan was at an exit point are flagged as leakage, grouped by door and by item type. Where off-note items cluster around one note number, the system suggests a likely wrong-note entry with a confidence percentage, separating operator error from genuine loss.
Reports are delivered on a schedule — daily reconciliations, weekly variance analysis, monthly management reports, and summaries over email or WhatsApp — so stakeholders receive them without logging in.
Step five: lifecycle and replacement
Because every wash is recorded against the tag, each item accumulates a lifetime wash count. That count is banded against a rated wash life configured per deployment, since fabric, chemistry and process vary between sites.
Items are grouped into replacement bands — early, mid, due soon, over life — and an end-of-life forecast projects from recent wash rates when each item type will reach its threshold and how many replacements to order. Procurement is planned from data rather than from an empty linen store.
What about a single disputed item?
Any individual tag’s complete history can be reconstructed: every dispatch, receive, in-plant movement, stock-take, exit, return and allocation, in chronological order, with each dispatch paired to its subsequent receive to show whether the cycle completed or broke.
That is usually what ends a dispute. Aggregate totals can be argued with; an item-level timeline cannot.
Does it need a separate process?
No, and that is the point. Because RFID reads in bulk and through fabric, scanning happens as trolleys and bundles move through positions they already pass. The tracking is a by-product of the existing workflow rather than an additional handling step.
Where a site’s process differs — different numbers of legs, different data flows — a per-customer process profile adapts the system to that model rather than requiring the site to change how it works.
Request a Linen Loss Assessment
Send us your issue and return records and we will show you where the items are actually going.
Talk to Us
Tell us about your operation and we will come back with a practical assessment.