Queue length vs. dwell time at a border crossing: what's the difference?

Two trucks can sit in the same backup and tell you completely different things depending on which number you're reading. A planner asking "how long is the line" and a planner asking "how long is each truck taking" are asking two separate questions, and mixing them up is how a shift gets staffed wrong.

Queue length: how far the line stretches

Queue length (sometimes called queue extent) is a distance measurement. It's how far the backup of vehicles runs back from the gate, booth, or primary inspection point, usually expressed in vehicles, in meters, or in "miles back from the port." If the line of trucks stretches past the last turnoff and onto the shoulder, that's a queue length problem. It tells you whether the approach road can absorb what's coming, whether a staging lot needs to open, and whether the backup is about to spill onto a public highway that isn't yours to manage.

Queue length is a snapshot. At any given moment, you can look at the approach and count how far back the vehicles go. It doesn't tell you why the line is that long or how fast it's moving. A 400-vehicle queue that's clearing at a steady clip and a 400-vehicle queue that's been frozen for two hours look identical from a single count.

Dwell time: how long each truck sits

Dwell time is a duration measurement, not a distance one. It's the time a single vehicle spends between arrival at the crossing and release, whether that's arrival-to-primary, primary-to-secondary, or full gate-to-gate. Dwell time is what shows up in trusted-trader program metrics, in carrier complaints, and in the KPI reports that go up to the port director.

A crossing can have a short queue and long dwell time at the same time. That happens when a few trucks are stuck in extended secondary inspection while the approach lane itself is clear, because most traffic is moving fine and only a handful are pulled aside. It can also run the other way: a crossing running three or four lanes at once can clear vehicles briskly even with a long visible backup, because more capacity is working the line than usual.

Why the two get confused

Most of the confusion comes from the fact that both numbers move together on a normal day. When processing slows down, trucks back up, so queue length grows and dwell time grows at the same time, and it's easy to start treating them as one reading. The split matters most on the days they diverge: a construction closure that shortens the approach lane but doesn't touch processing speed, a holiday surge where volume balloons but staffing holds, a system outage where every truck already through the gate is backed up waiting for paperwork to clear. On those days, a queue count without a dwell figure (or the reverse) gives you half the picture and the wrong half for the decision you're trying to make.

Dwell time is usually the port's own data, pulled from gate transaction logs, badge scans, or inspection system timestamps. It tells you what's happening to a vehicle once it's inside the processing chain. Queue length is what's happening outside that chain, on the approach, in the line of vehicles nobody has touched yet. One requires access to internal processing records. The other requires looking at the physical line itself, which is the part that doesn't show up in any gate log, especially at a crossing with no induction loop, no license-plate camera, and no one standing at the back of the line with a clicker.

That's the gap Queue Length Monitor is built to close: a VHR satellite or aerial pass over the crossing, read for how far the backup extends, delivered as a numbered briefing note with the marked-up image it's drawn from. It won't tell you dwell time. It will tell you, on demand, how far back the line goes right now, which is the half of the picture most crossings have no sensor for at all.

If your approach road has no camera and no loop counter, that's worth a look.