Submitted Sep 28, 2026
A lot of yards have already done the obvious thing. The clipboard is gone, there is a tablet in the guard shack, arrivals are captured in software, and somebody can run a report at the end of the week.
And the queue at the gate is the same length it was before.
This is the most common disappointment in yard technology, and it is not a failure of execution. The project did exactly what it was scoped to do. The problem is that digitising a process and automating one are different things, and the first does not lead to the second on its own.
What the Gate Is Actually For
The gate is not a checkpoint. It is the first step of a yard's job, and its function is to establish who has arrived, why, and what should happen next, in a form that every downstream system and person can act on without asking again.
Judged against that definition, most gates fail for a specific reason: they establish the information and then do nothing with it.
Ryan Arroyo, SVP of Product and Engineering at Terminal Industries, describes the pattern. "A truck arrives. They sign in with a paper and clipboard. And then that is just a step in this driver's process. But that doesn't help them achieve their goal. They're just going through this threshold. They check in. And then usually the answer is, well, now go to the next office."
His summary of the driver's experience is the line worth remembering: "It's like the waiting room goes to the next waiting room. You didn't actually get closer, but somehow you've just spent time filling paperwork out."
Replacing the clipboard with a tablet does not change that. The driver still checks in, still gets sent somewhere else, and still waits. The paperwork is faster and the outcome is identical.
Why Digitization Alone Does Not Reduce Dwell
The software still has to be told what happened
Here is the mechanism, and once it is visible it is hard to unsee.
"The majority of what is available today is documenting what has already happened," Arroyo says. "A truck moves through a gate, something happens, you have to remember to update the software to let the software know that the truck went by. And so it's not helping your operation. You've just added another task for your team to do: check in the truck, and then go to the software and check in the truck."
The conclusion follows directly. "It's just a digitisation process that adds work versus taking work away."
The test is simple. If someone at your facility performs an action and then separately records that action, you have added a step, not removed one. The record has value for reporting. It has no effect on throughput, because it is created after the throughput already happened.
The check-in does not trigger anything
A gate that captures data but does not initiate the next action has effectively stored it.
What the same event could do instead is start the work. The arrival is matched to a shipment, the driver is routed to a specific destination rather than to another office, the dock is notified, the dispatcher's queue updates. "The gate goes straight, tells the driver to go exactly to where they need to go," as Arroyo describes it, so the gate becomes "really step one of a process versus just an independent process that actually doesn't help them achieve their goals."
That is the difference between a digitised gate and an automated one, and it is not a feature difference. It is whether the gate is connected to anything.
The knowledge holding it together is in someone's head
There is a quieter problem underneath, which shows up when the person who knows how the yard works is unavailable.
"It was this concept of sort of tribal knowledge," Arroyo says. "I've been in so many yards where you ask them what is their process, or how do you know how to do things? And it's just this intrinsic: I just know. It's my yard, they're my trucks, I just know them."
He is not dismissive of it. After twenty years at one site, that knowledge is real and usually better than any documented procedure. The problem is what it is attached to. "That's maybe okay if you work there for twenty years and maybe you do have this intrinsic sense. But if that person leaves, how do you transfer that?"
Gate and yard roles carry high turnover. A process that lives in an individual's judgment is not a process, it is a dependency, and digitising the paperwork around it does nothing to capture it.
How to Tell What Is Actually Fixed and What Is Not
Terminal's team frames this using first-principles thinking, which is more useful here than it sounds because it forces a specific separation.
The method sorts every element of an operation into three buckets. Hard constraints cannot be violated: physics, time, law. Soft constraints can be changed but at a cost: labour, equipment, integration effort. Assumptions are things everyone treats as fixed that are simply inherited.
"What assumptions have been made in the past that are maybe invalid now?" Arroyo asks. "You always need a gate guard. You need a gate guard standing there. That was an assumption based on different thinking. And so now we say, well, maybe not."
Josh Kivenko, Terminal's Chief Marketing Officer, delivers the conclusion as a line the industry could stand to hear more often: "Clipboards are not a hard constraint."
Neither, on inspection, are most of the things a yard treats as immovable. A second check-in office is not a hard constraint. A physical stop at the gate is not necessarily a hard constraint, because the check-in could happen in the parking lot, on approach, or on the way to the warehouse. Safety, physics and law are hard constraints. Almost everything else is inherited practice with a cost attached.
Five Questions That Separate Digitised From Automated
When a truck checks in, does anything happen automatically? If the answer is that a record is created and a person then reads it, the gate is a form.
Does the driver go to one place or two? A second office after the gate is the clearest single indicator that the check-in did not resolve anything.
Is anyone entering information the system could have captured? Every field a human retypes is a field the sensors, integrations or documents already contain.
If the most experienced person at the site left tomorrow, what would stop working? Whatever the answer is, that is currently undocumented and unautomated regardless of what software you own.
Which of your gate steps are hard constraints? Sort them honestly. Most teams find two or three, and are surprised how much of the rest is inheritance.
The Autonomy Question Nobody Is Ready For
There is a version of this problem arriving on a timeline most operators have not planned for.
Kivenko asks it directly: "How does an autonomous truck deal with a manned gate?"
There is no good answer. Every part of the current gate process assumes a person in the cab who can hand over paperwork, answer a question, and be directed verbally. Remove the driver and the process has no path. The truck cannot present documentation to a guard, and the guard cannot tell it where to go.
Autonomous trucking arrives at facility gates before it arrives anywhere else in a yard, because that is the first thing a truck encounters. Operators who have digitised their gate but not automated it have built a process that specifically requires a human in the vehicle, at exactly the moment the industry is working to remove one.
This is not an argument for buying anything today. It is an argument for making sure that the gate project you scope this year does not have a human dependency baked into its design.
Frequently Asked Questions
Why didn't automating my gate check-in reduce wait times? Most likely because the check-in captures information but does not initiate the next action. If a driver still has to proceed to a second office, or a person has to read the record and then act, the gate has been digitised rather than automated and throughput will not change.
What is the difference between a digitised gate and an automated gate? A digitised gate replaces paper with software but still requires a person to record what happened and another to act on it. An automated gate captures the arrival from sensors and integrations without manual entry, and the arrival itself triggers the next step: routing, dock notification, dispatch update.
Why is tribal knowledge a problem in yard operations? Because it is a dependency rather than a process. Experienced yard staff hold accurate operational knowledge intrinsically, but it is not documented, not transferable, and is lost when they leave. Gate and yard roles have high turnover, so the knowledge holding the operation together is regularly at risk.
What is first-principles thinking applied to a yard? Sorting every element of the operation into hard constraints that cannot be violated (physics, time, law), soft constraints that can be changed at a cost (labour, equipment, integration), and assumptions that are simply inherited practice. Most gate processes contain far more assumptions than operators expect.
How will autonomous trucks interact with a staffed gate? They cannot, in the current model. A manned gate assumes a person in the cab to present documentation and receive verbal direction. Any facility expecting autonomous arrivals needs a gate process that does not depend on a human in the vehicle.
Where to Start
If the clipboard is gone and the queue is not, the project digitised the record rather than the work. Start by asking what the check-in triggers, because if the answer is nothing, no additional data capture will help.
Terminal's gate automation uses computer vision to capture arrivals without manual entry, and the arrival initiates the mission rather than filing a record. See what Terminal does at the gate, estimate the impact with the Yard Efficiency Calculator, or explore the platform and walk through gate automation yourself with no sales call.
This article draws on Lights-Out Yard Episode 1 with Ryan Arroyo, SVP Product and Engineering at Terminal Industries.
