The Collection Gap

The collection gap is the interval between the moment a plan is finished and the moment it executes. Planning effort is front-loaded; the environment's changes are not. Everything that shifts in that interval — closures, incidents, weather, crowds, local decisions made by people who have never heard of your operation — arrives against a plan that has already stopped listening.

Every team that plans anything knows this interval. Fewer treat it as a phase of the operation with its own work.

What actually changes in the gap

Run any operation with a week between plan-lock and execution and the environment will have moved by day seven. The categories are boring, which is why they get missed:

• Infrastructure: road closures, construction starts, transit disruptions, utility work at or near the venue.
• Scheduled events that weren't on the calendar when you looked: permits get issued weekly; a march, festival, or filming closure can appear inside your window with days of notice.
• Incidents: crime near your routes, a police operation, a fire that changes building access — none aimed at you, all of it shaping your ground.
• Weather: not "will it rain" but what rain does to your timeline, your alternate routes, and your outdoor exposure points.
• The venue itself: staffing changes, a second event booked into the same complex, a renovation that closed the corridor your diagram still shows open.

None of these are exotic. Each one is discoverable from open sources, usually days before it matters. The problem is not availability of information. The problem is that nobody's job is to keep looking.

Why the gap exists

The gap is structural, not a discipline failure. Planning is an event; monitoring is a process — and small teams are staffed for events. The advance gets budgeted, assigned, and completed. Watching the environment afterward is nobody's task, has no deliverable, and produces nothing on most days. Work with no owner or output loses to work with deadlines. Every time.

The military solves this with dedicated collection: intelligence sections tasked to watch named areas and report against named conditions. Small teams — a two-person detail, a small-office task group, a relief crew — don't have that section. They have the same need with none of the structure.

Closing the gap manually

You can run mission-scoped collection with a browser and discipline. The method matters more than the tools.

1. Write down what would change your plan. Not "monitor the situation" — specific conditions tied to decisions you already made. If Route A's bridge closes, we shift to Alternate B, which adds twelve minutes. If a permit is issued for the square across from the venue, we move the arrival to the dock. Doctrine calls the underlying idea an indicator tied to a decision point; the label matters less than the linkage. If a change wouldn't alter a decision, you don't need to watch for it.

2. Pick sources against those conditions. Local outlet feeds for the area around each fixed point. The city's permit and road-closure pages. Transit alerts. Weather with hourly resolution for your window. A search alert on the venue's name and the principal's public schedule. Five to eight sources, chosen once, beats "check the news."

3. Set a cadence and an owner. Fifteen minutes at the same time each day, one named person, from plan-lock to execution. Tighten to twice daily inside 48 hours. The cadence being small is what makes it survive; the owner being named is what makes it happen.

4. Log what you saw — including nothing. One line per check. A log that says "checked, no change" forty times has value: when something does appear, you know it's new, and you know when it appeared.

Where the manual method strains

Honesty about the failure modes: the manual watch degrades exactly when you need it most. During execution — when the team is busiest — the check gets skipped. Across multiple simultaneous missions, the source list balloons past what fifteen minutes covers. In an unfamiliar region, you don't know which local sources are worth reading. And the person doing the checking is usually also the person doing everything else; attention is the one resource small teams cannot surge.

That's the shape of the problem: not a knowledge gap, a bandwidth gap. The information is public. The method is known. What's scarce is a person with time to keep looking.