The Pre-Travel Intel Brief: A Working Method

A pre-travel intelligence brief is the short written product that tells a team what the environment holds before they commit to it: what's normal, what's active, what's unknown. It exists to support decisions, not to document effort.

This post is the assembly step. The collection work underneath it (building a baseline over weeks, running wide-net feeds, rating what comes back) is covered in Monitoring a Region Before You Travel and What GDELT Is and Isn't Good For. What follows is one way to turn that collection into a page someone can act on at 0500. Not the only way. A working one.

Start with requirements, not sources

The brief exists to support specific decisions. Go/no-go on a route. Posture — footprint, visibility, how hard the movement needs to be. Timing, meaning whether the window should move. And what to watch once the team is committed.

Before anyone opens a browser tab, write the three to five questions the team actually needs answered. For a two-day principal movement through a secondary city, that might be: Is anything scheduled or unfolding along the airport-to-venue route inside the window? Has the baseline shifted in the last two weeks? Is there reporting that touches the principal, the venue, or the profile of this movement? Where does a casualty go, and how fast?

Everything that doesn't serve one of those questions is collection discipline — worth doing, worth logging, not the brief. The common failure mode is the reverse: start from what the feeds produced, organize it by source, and hand the team a summary of the internet. Requirements first. Sources serve them.

A structure that works

This is the structure we use. Adapt it freely; the sections matter less than the order of operations they force: read, baseline, change, threat, support, gaps.

1. BLUF. Three sentences, maximum. The overall read, the one thing that changed, the one thing you couldn't confirm. If the reader stops here, they should still make a better decision than they would have without the brief. Writing it last and putting it first is the discipline.
2. Environment baseline. What normal looks like in that place — traffic rhythm, protest tempo, crime pattern, police posture. This is where the layered monitoring method pays off: if you've been watching the region for weeks, this section takes five minutes. If you're building it the night before, say so in the gaps section.
3. Active conditions. What's scheduled or unfolding inside the window: protests, sporting events, state visits, weather, transit strikes. Every item carries a source and a rating. Wide-net feeds like GDELT cue; named sources confirm. And that division of labor is the difference between "something may be happening near the venue" and "transport union confirmed a Thursday strike, named outlet, dated."
4. Threat picture. Specific to this principal and this movement, stated plainly. Not the country threat overview, but the part of it that touches your route, your venue, your profile. If there's nothing, say there's nothing, and say what that means:

Absence of reporting is not absence of threat. It's absence of reporting.

1. Medical and infrastructure. The nearest trauma-capable facility and the time to reach it from each phase of the movement. Comms coverage along the route. Anything that changes the support plan — a hospital diversion, a dead zone, a bridge under repair. This section is short, and it's the one the team reaches for when the day goes wrong.
2. Gaps. What you didn't check, couldn't confirm, or ran out of time on, itemized explicitly. "No local-language source coverage." "Venue interior not assessed." Name a gap and the team lead gets to decide what to do about it; hide it and the decision gets made for them by omission.

Keep it to one page

If it doesn't fit on a page, it's a file, not a brief.

The team reads a page. Nobody reads a dossier at 0500 in a hotel lobby. Everything that supports the page (the source log, the screenshots, the full route survey) lives in the file, and the brief points to it. Compression is the analyst's job, not the reader's.

Source every claim

Every claim in the brief carries its source and rating, inline or in a footer. "Per local news" is not a citation; a named outlet with a date is. "Widely reported" is not a rating. The rating discipline doesn't need to be elaborate: a reliability letter and a credibility number, or even a three-tier confirmed/probable/unverified scheme applied consistently, beats prose hedging every time. If you're building a source stack from zero, the rated list in OSINT Sources for Protective Work is a starting point.

This footer discipline also makes the brief auditable after the fact. When something in it turns out wrong (and something eventually will), you want to know which source failed, not which analyst to blame.

Brief at commit, update on change

The brief is a snapshot, and the environment doesn't hold still. One cadence that works: brief at the commit decision, update when something material changes, and re-brief — not patch — if the window slips more than a day. A brief written Tuesday for a Thursday movement that slid to Saturday isn't slightly stale; its active-conditions section is describing a different city.

The update is one line if one line is what changed. Resist the urge to reissue the whole page for a weather revision. A team stops reading updates that are mostly restatement.

The structure survives the format

Sometimes there's no time to type. A voice note that walks the six sections in order counts. So does a photographed map with the route and the trauma destination marked. The structure is what carries the value, not the document — a team that has internalized BLUF, baseline, conditions, threat, medical, gaps can pass a usable brief over a phone call in ninety seconds.

We keep a fill-in version of this structure, a pre-travel intelligence brief template with the six sections and a sourcing footer already laid out, and a downloadable copy is headed to this resources section. Until then, the section list above is the template. It fits on an index card.