Note · 26 October 2026
What is a numbered briefing note in queue monitoring?

If you've spent any time around a duty manager's desk at a land border crossing, you've heard the phrase "briefing note" tossed around for everything from a one-line radio call to a full shift handover packet. In queue monitoring specifically, a numbered briefing note means something narrower: a short, dated report tied to a single pass over a single crossing, with a reference number stamped on it so it can be filed, pulled up, and cited later without anyone having to describe it from memory.
That last part matters more than it sounds. Ask any ops desk that's tried to reconstruct "how bad was it at Gate 4 last Tuesday" from a mix of radio logs and someone's phone photos. A numbered note exists specifically so that question has a one-line answer: pull briefing note #0417, there's your queue length, there's the image it came from.
What goes into the note
A proper briefing note for queue monitoring has four things, no more:
The location. Which crossing, which lane or approach, which direction of travel. Border crossings often have more than one queue worth tracking (inbound trucks, outbound trucks, a separate commercial lane), so this isn't optional detail, it's the first line.
A timestamp. When the imagery was captured, not when the note was written. Those can differ by hours depending on tasking and processing, and a planner reading the note needs to know which one they're looking at.
The queue length estimate. How far the line of vehicles stretches back from the gate, read off the imagery. This is the deliverable, the thing someone on shift needed to know and didn't have a sensor loop or an officer on the ground to tell them.
The marked-up image. The picture the estimate was drawn from, with the queue extent marked on it. This is what turns a number into something a planner can actually check against their own judgment, instead of taking someone's word for it.
What a briefing note does not need: narrative filler, weather commentary, or speculation about why the queue is what it is. A dispatcher on their fourth crossing of the day wants the four facts above, in the same place every time, and nothing they have to read twice.
Why the numbering matters
Give each note a sequential reference and three things get easier. First, shift handover: the outgoing team can say "see note 118" instead of re-explaining a queue situation verbally to whoever's coming on. Second, pattern tracking: numbers let a planner line notes up in order and compare whether Thursday afternoons are consistently worse at a particular crossing. Third, accountability: when a note is cited in a staffing decision or an escalation to a terminal operator, the number is the paper trail. Nobody has to dig through a group chat to find the source.
This is also what separates a briefing note from a raw sensor feed or a live dashboard tile. A dashboard shows you the current state and then moves on; refresh the page and the old reading is gone. A numbered note is a record. It's built to be filed, referenced months later, and handed to someone who wasn't on shift when it was produced.
Where this fits without ground sensors
This format exists because most crossings and terminals have no loop detector or camera counting vehicles back from the gate. Answering "how long is the line right now" means looking down at it: a VHR satellite or aerial pass timed to when someone needs the answer.
That's the gap Queue Length Monitor is built around: an on-demand VHR pass over a crossing or terminal, delivered back as exactly the numbered briefing note described above, location, queue estimate, and the marked-up image it's drawn from.
If your crossing has no sensor and you're tired of guessing from a radio call, it's worth seeing what one of these notes looks like.