Note · 9 November 2026

Sizing satellite tasking cadence around a seasonal produce rush at the border

Three semi trucks driving in a line along a highway through a forested, mountainous Arizona landscape.

Every ag-heavy crossing has a window where the queue stops behaving like the rest of the year. Avocado season at a Southwest land port, citrus coming north out of a Gulf terminal, a strawberry run that turns a quiet gate into a six-hour backup by mid-morning. Everybody sees the rush coming. What's harder to pin down is how often to look once it starts.

Tasking a daily VHR pass for the full eight-week window is the easy answer and usually the wasteful one. Tasking nothing and waiting for the radio call from the gate is the cheap answer and usually the late one. The right cadence sits between those two, and it's set by how fast the queue moves during the surge, not by the calendar.

What changes during a produce rush, and what doesn't

The crossing's geometry doesn't change. The lane count, the inspection booths, the staging area where trucks pull off before the final approach, all fixed. What changes is arrival rate and dwell time, and those two move together during a seasonal surge in a way they don't the rest of the year. A refrigerated load sitting in line degrades. Drivers know it, brokers know it, and that pressure compresses the window where a queue reading stays useful. A queue estimate from Tuesday doesn't tell you much about Thursday's rush hour.

That's the first sizing question: how long does a queue state stay representative once the trucks start stacking for citrus or berries? At most ag crossings during peak, that's hours, not days. A single daily pass timed to mid-morning will catch the worst of it most days, but it'll miss the crossing's second peak if the rush runs a double-hump pattern, which produce crossings often do when a border station eases restrictions late in the shift to clear backlog before close.

Setting cadence: daily baseline, on-demand on top

The approach that holds up across different produce seasons is a daily baseline pass through the known peak window, with on-demand passes layered on for the days that break pattern. A grower cooperative calling ahead about a bumper week, a sister crossing reporting unusual congestion, a holiday that compresses two days of volume into one. Those are the triggers for an extra tasking request, not a fixed weekly schedule.

Where this gets wrong most often is treating the whole surge window as uniform. The first two weeks of a produce rush and the last two rarely look alike. Early season, volume ramps unevenly as growers test the market and brokers feel out capacity. Late season, everyone's trying to clear remaining inventory before the crossing's allocation tightens, and that's usually when the worst backups happen. A planner sizing cadence around the midpoint of the season, rather than the tail, tends to under-task right when it matters.

A rough rule that's worked for planners we've talked to: run the baseline cadence loose through the first third of the window, tighten it through the middle, and keep on-demand capacity held in reserve specifically for the final two weeks. That's when a single bad day costs the most in spoiled loads and driver detention claims.

Reading the pass once it lands

None of this matters if the pass comes back and nobody can read queue length off it quickly. A raw image with a queue buried in it still needs someone to measure vehicle count and estimate distance back from the gate, and during a surge that's exactly when the ops desk has no spare hands for that. Queue Length Monitor turns each tasked pass into a numbered briefing note, location, estimated queue length, and the marked-up image it's drawn from, so the pass is usable the moment it lands instead of sitting in a queue of its own waiting for someone to interpret it.

If your produce season is a few weeks out and you're still working out how many passes to budget for it, get in touch and we'll help you size the cadence against your crossing's own pattern.

Start a pilot

← Back to the blog