Named Areas of Interest: Where to Point Attention

A named area of interest (NAI) is a specific place you have decided to watch because something observable there would change a decision you have to make. Naming it is the whole point: an area with a name has an owner, a question, and a trigger, while an area without one is just terrain you feel vaguely uneasy about.

Where the idea comes from

NAIs come out of military intelligence collection planning, where they travel with two companions. Indicators describe what you expect to see if a particular thing is happening. Decision points describe what you will do about it. The three work as a set, and pulling any one of them out breaks the other two. An area with no indicator gives the watcher nothing to look for. An indicator with no decision gives the person running the movement nothing to act on.

The other half of the inheritance matters just as much. NAIs fall out of the environment and threat analysis you have already done; they are not brainstormed in a room at the end of the planning session. If you have worked through the terrain, the traffic patterns, the population, and what someone with hostile intent would plausibly do with all of it, the candidate areas tend to name themselves. If you skipped that work, you are guessing at places to point people and calling it coverage. Our walkthrough of IPB for protective intelligence covers the analysis that feeds this step.

The three parts every NAI needs

A place, defined tightly. "Downtown" is not an NAI. "The garage ramp at the west entrance" is. Tight definition is what makes an observation assignable: a person can stand somewhere, point a camera somewhere, or search a feed against somewhere. Loose boundaries produce loose reporting, and loose reporting produces the kind of update that sounds like coverage without containing any.

An indicator. What specifically would you see there that means something? "Anything suspicious" is not an indicator. A vehicle that stays past the loading window is. A crowd forming before the permitted start time is. A closed lane on the approach is. Write the indicator so that two people watching the same place would agree on whether it happened. That agreement is the difference between a report and an impression.

A decision it feeds. What changes if the indicator appears? Maybe you shift the arrival to the secondary door. Maybe you hold the vehicles a block out. Maybe you move the departure fifteen minutes earlier. If nothing changes, the NAI is decoration and should be deleted. That deletion is the discipline that keeps a watch list from growing until nobody reads it.

Most bloated NAI lists fail the third test, not the first two. The places are real and the indicators are reasonable, but no one ever asked what the team would actually do differently, so the list becomes a record of anxiety rather than a plan for attention.

Picking them for a protective movement

Derive NAIs from the geometry of the plan you already have. One way we do it:

• Arrival and departure points. Highest exposure, shortest reaction time, and the two moments where the schedule is most predictable to anyone watching.
• Choke points on the primary route. The places where you lose the option to change course. Our piece on choke point analysis goes into how to find and rank them.
• The venue's public approach. Where uninvolved people mix with the movement, and where a gathering forms before anyone reports it.
• The overnight location. Long dwell time, thin manning, and the phase where attention naturally slackens.
• The one or two spots the red cell reached for during the tabletop. If an adversarial review kept returning to the same alley or the same parking deck, that is a candidate you did not have to invent.

Then cap the list. A small team can realistically hold a handful of NAIs, not thirty. An NAI nobody is actually watching is worse than no NAI at all, because it produces false confidence in coverage: the brief says the west approach is covered, everyone stops thinking about the west approach, and no one is looking at it. If the list runs long, the answer is not more names. The answer is deciding which places would actually change what you do, and cutting the rest.

Assigning them

Every NAI gets a name (a person, not a shift), a means, and a reporting path. The means can be eyes, a camera feed, a source, a sweep of open reporting. The reporting path is who hears about it and how fast, which is the part teams skip most often and regret most reliably.

Written out, one line per NAI:

Place → indicator → decision → owner → how.

That five-item line is the whole product. It fits in the brief, it reads aloud in about eight seconds, and it survives contact with a busy detail leader. Anything longer stops being a collection plan and starts being a document.

Worth saying plainly: the team executing the movement owns the plan. Intelligence work supports that plan, sharpens it, and sometimes argues with it, but the detail leader decides. NAIs are a way to make support specific enough to be useful, not a mechanism for someone outside the movement to run it.

NAIs have a clock

They open and close with phases of the movement. The garage ramp matters for twenty minutes around arrival, then stops mattering. The airport approach matters twice, hours apart, and not at all in between. The venue's public entrance matters from doors-open until the principal is inside.

Put the window in the line, next to the owner. Watching everything all the time is how attention gets spent on nothing, and it burns out the people you will need alert during the phases that count. Closing an NAI is a real action, and someone should say it out loud on the net: that one is closed, stop watching it.

Where these lists go wrong

• Too many. The list outgrows the team's capacity to watch, and coverage becomes nominal.
• No indicator. "Watch the crowd" tells a person to look without telling them what they are looking for.
• No decision. The observation arrives and nobody knows what to do with it, so it goes in a report nobody reads.
• Assigned to "the team." Shared ownership is no ownership. A specific person's name is what makes the report happen.
• Never closed out. NAIs from a previous phase, or a previous trip, stay on the list because deleting things feels like lowering the guard. It is the opposite: a stale list hides the live ones.

None of these failures look like failures in the moment. They look like thoroughness, right up until the brief has twenty-two lines and the team is actually tracking four of them.

The bridge between assessment and collection

NAIs are how an environment assessment becomes actual collection. They turn "we're worried about the west side" into a specific question, assigned to a specific person, tied to a specific choice: watch the garage ramp between 1310 and 1330, tell me if a vehicle sits past the loading window, and if it does we move arrival to the north door.

That translation is also what makes collection scoped to the mission rather than to the world, which we get into in what mission-scoped collection means. Adapt the shape to your team. The parts that do not bend are the three questions: where, what would I see, and what would I do about it.