RFID Linen Pilot Acceptance: Washing, Handovers and Billing
A practical worksheet for operations, stores and project teams.
By addanode · Published 5 November 2026
An RFID laundry pilot checklist should connect three tests: the tag and attachment through actual treatment, reading under representative loads, and independently checked handovers between hotel and laundry. Keep those results linked by item and batch. The rollout decision should state the conditions observed, exceptions still open and billing evidence accepted by both parties, without turning a supplier's wash-life rating into a customer result.
Choose a bounded route with accountable owners
Select a route that includes the relevant linen categories and real treatment process. Identify the hotel dispatch owner, laundry receiving owner, process owner, clean-dispatch owner and hotel receiving owner. The same person may hold several roles, but the pilot should show who confirms each reference count and who resolves disagreement.
Define the trial period and the decision it supports. An initial trial can establish attachment suitability, operating workflow and observed performance over the treatment cycles completed. It cannot prove a service life that has not yet elapsed. Keep longer-term inspection and replacement decisions as a continuing follow-up with their own evidence.
Use the hotel and commercial-laundry tracking scope to connect the pilot to census, tagging labour, software and training. The existing RFID linen technology guide provides background; this worksheet focuses on the evidence needed to accept a particular route.
Download a matrix that joins the three test dimensions
Download the linen pilot acceptance CSV. Each template row combines a treatment stage, load condition and handover. Copy rows to cover the actual combinations in your pilot. The file includes fields for independent sender and receiver records, RFID observations, exception ownership and billing reconciliation; blank results are intentionally unmeasured.
Create a sample register before treatment. Record the textile category, physical item identity, tag identity, tag product, batch and attachment method. Read each identity back and inspect the seam or pocket. Retain a way to identify the physical item independently so a failed tag does not make the sample disappear from the trial history.
Agree the planned sample sizes and repetitions with both parties. Include the categories that are operationally important or difficult to handle. Keep exclusions visible, such as textiles that cannot accept the proposed attachment. A trial made only of convenient new towels should not be used to approve every linen category in the hotel.
Record treatment conditions as performed
Obtain the actual recipe and finishing process, including chemicals, wash stages, extraction, drying, ironing or pressing. Record the process reference and the observed cycle history for each sample or controlled batch. If a condition is unavailable, mark it unknown and assign a follow-up instead of replacing it with a catalogue value.
The Zebra washable laundry tag specification lists treatment conditions and attachment options, and calls for purchasers to determine suitability in their own application. Use the exact proposed supplier's documentation to design the test. Its stated warranty or performance conditions are not measurements from your laundry.
Inspect the textile and attachment after the agreed checkpoints. Record seam damage, tag movement, snagging, discomfort or appearance issues as well as readability. A tag can remain readable while its attachment fails the hotel's practical requirements. Keep removed or failed samples in the denominator relevant to the test, with the reason for their disposition recorded.
Cross treatment stage with representative load conditions
| Treatment stage | Load condition | Handover evidence |
|---|---|---|
| Before treatment | Dry items and an independently counted sample | Initial register and sender reference |
| Dirty dispatch | Actual dampness, compression and mixed categories | Hotel dispatch and laundry receipt records |
| After recorded treatment | Representative folding and packing | Process reference and inspection outcome |
| Clean dispatch | Actual cage fullness and neighbouring stock | Laundry dispatch and hotel receipt records |
| Rewash or exception | Segregated rejected or disputed items | Reason, owner and corrected transaction |
This is a starting matrix, not a complete factorial requirement for every site. Select the combinations needed to test the route's credible conditions, and explain any omitted cases. Record cage or trolley type, load arrangement, reader configuration and movement. A successful dry single-item read cannot establish a full damp-cage result.
Include dense and mixed loads, neighbouring tagged linen, pauses and repeated passes. Distinguish a tag detected outside the batch from an item that actually belongs in the handover. If additional handling is required to complete the count, record that effort as part of the workflow rather than omit it from the result.
Keep both parties' references independent
At each selected handover, the sender and receiver should establish their own reference count or item list. Record the method, person and time. Do not copy the RFID result into both reference fields; that would make the system appear to agree with itself. Where item-level manual identification is impractical, document exactly what the independent reference can and cannot verify.
Preserve disagreements before reconciliation. A sender record of one quantity and a receiver record of another may reflect split delivery, timing, physical shortage or counting error. Assign an owner and obtain the supporting evidence before agreeing the reference. A disputed baseline cannot fairly establish a read-accuracy result.
Once the reference is agreed, compare expected identities with those captured and inspect the resulting dispatch and receipt events. Use the separate definitions in the read-point acceptance guide. Keep capture, stray reads, false events and unresolved quantities visible; a single summary percentage cannot explain a disputed delivery.
Trace exceptions through treatment and return
Create explicit outcomes for missing tags, unreadable tags, damaged attachment, unexpected items and open handover disputes. Link each exception to the sample and batch. The responsible person should record the investigation, correction and whether the item returned to service, was retagged or was withdrawn.
Do not equate every read failure with lost linen. Equally, do not clear a physical shortage merely because a similar category was seen later. Retagging should preserve the original item history, while a replacement textile should receive its own identity. These distinctions keep the pilot from producing a misleading loss figure.
A dispatch record also does not establish a completed wash. A textile might be rerouted, rejected or returned without treatment. Count wash cycles only when the process provides a defensible association with completed treatment. Where the association is at batch level, record that basis and the controls used to maintain batch membership.
Reconcile a sample bill under the actual contract
Identify whether the charge basis is pieces, weight, rental, treatment category or a combination. For weight-based billing, retain the scale reference alongside item observations. For piece billing, map the accepted item categories and quantities to the contract lines. A tag count does not rewrite the agreed charging method.
Include partial deliveries, rewash, rejected stock and replacement charges where relevant. Compare the proposed bill with the accepted handover and treatment evidence. Record any difference, the party responsible for resolving it and the approved outcome. Use a non-posting comparison or an agreed controlled process so trial records do not accidentally create duplicate invoices.
The finance representatives should confirm that the evidence supports reconciliation, while operations confirms the physical workflow. Neither acceptance substitutes for the other. A well-read cage linked to the wrong account or billing period remains an unsuccessful business result.
Make the rollout decision specific and reviewable
Set acceptance criteria before reviewing results. Cover attachment condition, identity capture, correct handover events, exception workload and billing comparison. Define what requires a retest and what can remain an explicitly controlled limitation. Retain unsuccessful runs and corrective actions alongside successful ones.
The final record should name tested textiles, tag and mounting versions, treatment conditions, observed cycles, load arrangements and software configuration. State unresolved items and the responsible owners. A later change to chemistry, packing, tag construction or read-point layout should trigger a review of the affected evidence.
Plan a staged census and tagging schedule using the accepted process. Include staff training, spare tags, replacement history and a manual fallback. The asset-tracking service and logistics context explain the wider delivery. Provide linen samples and actual treatment details to scope the first route with both parties.
Frequently asked questions
How many wash cycles must a pilot prove?
Agree a programme suitable for the initial decision and record the cycles actually observed. There is no universal number established by this guide. Claims about longer service life require additional evidence beyond a shorter pilot.
Can the laundry provide both reference counts?
Both parties should retain independent evidence for the handovers being accepted. If one party cannot independently verify an item-level list, record that limitation and agree another reference method before interpreting the result.
Does a good read result validate the invoice?
No. The accepted items must also map to the correct contract basis, account, period and treatment rules. Keep the billing comparison and its approval separate from the technical read test.
Define a first stage your team can verify.
Tell us the site, equipment, existing records and the decision you need to improve. We will use those inputs to discuss the scope and acceptance evidence.