Yard management projects stall on a hardware question more often than on a software one. Somebody asks whether the system needs RFID, and the project acquires a capital line, a site survey and a six-month delay before anyone has agreed what problem the technology is meant to solve.
This guide separates the four identification options, states what each one actually solves, and describes the situations where the honest answer is that you need none of them.
The question behind the question
Identification technology answers one question: which asset is at which point, without a human typing it. Everything else a yard management system does, including move orders, dock assignment and dwell measurement, works without any of it.
So the decision is not “do we need RFID” but “where does manual identification actually cost us”. On most sites the answer is the gate, and only the gate.
The four options
Manual entry at the gate
A guard or driver enters the trailer number. Costs nothing to install, adds two to four minutes per vehicle and produces a predictable error rate on digits. Perfectly adequate below roughly forty vehicles a day, and it is where most sites should start.
ANPR: automatic number plate recognition
Cameras read the tractor plate at the barrier. It identifies the vehicle without stopping it and works with any carrier, since every truck has a plate and needs no equipment fitted. Its limitation is that it identifies the tractor, not the trailer, which matters the moment you run drop-and-hook. Recognition degrades with dirt, snow and low sun, so plan for a manual fallback rather than treating it as absolute.
RFID
A tag on the trailer, readers at gates and zones. This is the only option that identifies the trailer itself and can locate it inside the yard rather than only at a boundary. It also requires tagging every trailer that will enter, which is straightforward for a captive fleet and a real problem for a site handling hundreds of third-party trailers a week.
Telematics and driver app
Position comes from the vehicle already reporting it, or from the driver’s phone at check-in. No site hardware, works across carriers who are connected, and gives nothing for carriers who are not. This is the same connection that produces freight visibility, which is why yard and visibility projects are frequently the same project.
Choosing by operation, not by technology
Three patterns cover most European sites:
- Live loading, mixed carriers, one gate. ANPR at the barrier plus booking data. The trailer identity comes from the booking, the vehicle identity from the plate, and no carrier has to fit anything. This is the highest return for the lowest disruption.
- Drop-and-hook with a captive trailer pool. RFID earns its cost here, because the asset you must track is the trailer and it sits on your site for days. Locating it is the actual problem, not identifying it at the gate.
- High volume, third-party trailers, several gates. Telematics and driver check-in, with ANPR for the vehicles you cannot connect. Tagging trailers you do not own does not scale.
The costs nobody puts in the business case
Hardware quotes cover purchase and installation. Three recurring costs usually appear later:
- Tag lifecycle. Tags are lost, damaged and replaced. A captive fleet needs a replacement process, not a one-off purchase.
- Reader maintenance. Gate equipment lives outdoors and gets hit. Budget for it.
- Exception handling. Every automated identification system has a failure rate, and every failure becomes a manual process. If that process is not designed, it becomes a queue.
The exception path deserves specific attention. A gate that works automatically 95% of the time and has no defined procedure for the other 5% performs worse than a fully manual gate, because the failures arrive unexpectedly and nobody is staffed for them.
When you need none of it
If your dwell problem is arrival clustering, identification technology will not touch it. Trucks queuing because forty of them were told to arrive at seven will still queue when the gate reads their plates automatically, only faster. That problem is solved by booking windows, which is what dock scheduling software does, and the measurement that tells you which problem you actually have is in our guide to yard dwell time.
The sequence that works on most sites: book the arrivals, measure the dwell, find where the time goes, and only then buy hardware for the interval that measurement identified. Sites that do it the other way round tend to end up with an accurate record of a queue they still have.
