The deployment is complete, the readers are working, and the tags are being read. That leaves the question that matters most to management: Has the RFID project lived up to its promises?
An article published this week by RFID News (Matt Houldsworth, October 23, 2026) proposes a method for conducting a post-deployment review. Here are the key takeaways, and how to apply them to your project.
The Tag-LOC system is a tracking system for industrial applications.
- Conduct a review 6 to 12 months after the system goes live, once usage patterns have stabilized.
- Start with the initial business case: each promised benefit becomes a measurable metric.
- Track three categories of metrics: business benefits, operational health, and team adoption.
- Isolate the effect of RFID from other changes, ideally using control sites.
- If the results are disappointing, look for the cause in the infrastructure, processes, or data.
Why Conduct a Review After Deployment?
The initial business case as a starting point
The calculation of RFID return on investment is generally performed before the purchase. The post-deployment review is an extension of this process: it verifies, with supporting figures, that the expected return has indeed been achieved. It builds on the original business case. If the project promised faster inventory counts or more reliable stock levels, it is necessary to specify how this is verified and with what data. Without translating this into measurable metrics, the assessment remains merely an impression.
When to do it
According to the article, the review takes place six to twelve months after the system goes live. Before that, the focus is primarily on the learning period.
The Three Categories of Indicators
Business Benefits
These are the results promised by the business case. The article provides examples of how to formulate objectives: reducing inventory cycle time from 4 hours to 45 minutes, or increasing inventory accuracy from 72% to 95%, as measured by a physical audit. These are examples, not guaranteed results: your goals depend on your specific context.
Another suggestion mentioned: reducing costs associated with lost or rented equipment, to be verified in the maintenance and purchasing data.
Operational Health
These metrics indicate whether the system is operating as expected: read rate by zone, tag failure rate in the field, system availability, and middleware error rate.
Adoption by the teams
High-performance technology is of no use if it isn’t utilized. Next steps: tracking the frequency of handheld reader use, monitoring the completion rate of periodic counts, and observing actual workflows.
Isolate the effect of RFID
Better results after deployment do not prove that RFID is the cause: procedures, teams, or the product line may have changed at the same time.
Before-and-After Comparison
That’s the bare minimum. It requires an assessment of the initial situation, which is why it’s important to include it in the business case from the start.
Pilot Sites and Phased Rollout
Where possible, the article recommends control groups: sites without the technology, or a phased rollout. The difference between sites with and without the technology can then be more reliably attributed to RFID.
Identifying Underperformance
If the results fall short of expectations, the article identifies three categories of causes.
| Cause | Signs | Response |
|---|---|---|
| Infrastructure | Insufficient reading coverage, poorly placed antennas | Add or reposition equipment |
| Adoption of Processes | Teams that circumvent the system (probably the most common cause, according to the article) | Training, process redesign, management support |
| Data Quality | Data entry errors, damaged tags, missing tags on incoming products | Data quality audit, often the first step |
In the same vein, RFID Journal published an opinion piece on October 23 titled “Why RFID Projects Fail: The Problem Is Usually Not the Technology”: the title aligns with this assessment, though we have not been able to read the content.
Document and Capitalize
The final step is to document the findings and share them. Future projects—whether at other sites or for other purposes—will then be based on actual experience rather than assumptions.
6-Step Review Checklist
- Review the business case and convert each benefit into a measurable metric.
- Measure business outcomes and operational health.
- Assess actual adoption by the teams.
- Compare with a method that isolates the effect of RFID.
- Identify gaps: infrastructure, processes, data.
- Document and share the findings.
Get support for your RFID project
A post-deployment review often reveals issues that can be resolved on-site: labels that don’t fit their surfaces properly, poorly positioned antennas, or a need to reconsider the choice between a gateway and a mobile terminal. Depending on the issue identified, these pages can help you:
CIPAM supports traceability projects from analysis through maintenance: project analysis, consulting, equipment integration, maintenance, and after-sales service. To discuss your current situation, schedule an appointment with an expert, or contact us with your initial business case and your first set of readings.
Sources: RFID News, “Post-Implementation Review: Measuring What Your RFID System Actually Delivered” (October 23, 2026); RFID Journal, “Why RFID Projects Fail” (October 23, 2026, title only). Photos: DC Studio, DC Studio, and DC Studio on Magnific.