THE INTEL ANALYST ACADEMY
Professional Intelligence Training
Printable Lesson
Evaluating Collection Plans
The Intel Analyst Academy · Lesson Notes
Collection feels productive. People are tasked, folders thicken, a dashboard goes green. None of that answers the only evaluation question that matters: did we fill the gap that justified the plan, in time for the decision, with evidence we can stand on? This lesson is the after-action for a collection plan — how to score it without vanity metrics, when to retask, and when to stop.
> A collection plan that was never reviewed is a diary. Flattering to the author. Useless to the person who needed an answer.
The intelligence cycle already tells you feedback exists. The collection-planning process already names evaluation as a phase. This lesson is what you actually write down so the next plan is not a sequel to the same mistake.
Put the original gap statement at the top of the review. If you cannot find it, that is finding number one: you collected without a decision to serve. Reconstruct it if you must, and mark it reconstructed so you do not pretend the plan was tighter than it was.
Then answer, in order:
A plan can be busy and fail all four. A plan can look thin and pass. Judge the gap.
Vanity metrics: number of reports, number of sources "touched," pages produced, hours charged. They measure motion. Use these instead.
Add a fifth only if it changes a future task: what we collected that nobody asked for, and whether it opened a real new gap or merely a longer annex. Bonus collection is not free. It costs the element you did not fill.
Evaluation that never changes the next task is a book report. You have three honest moves.
Do not retask to punish a collector for a negative result you yourself defined as useful. That is how you train people to hide negatives, and then your coverage marks become fiction.
Keep it to a page. Longer reviews do not get read, which means they do not change plans.
File it where the next planner will trip over it, attached to the register, not in a lessons-learned folder that is actually a landfill.
Requirement owners do not want a lecture on the intelligence cycle. They want to know whether to decide. Say it in their units.
"You asked whether Supplier Q's filings show a default before 1 June. They do not, in the public record we were allowed to use, as of 20 May. We did not get a second source on operational delays. I would not treat the financial silence as proof the deliveries are safe. The gap on delays is still open. I recommend you either accept that uncertainty for the June tender or slip the tender. I am not tasking further financial collection. It answered."
That is feedback. "Collection efforts are ongoing" is what you say when you do not want to be evaluated.
Sometimes the review shows the failure was upstream. The gap was vague, the source match was the discipline you happened to own, the task smuggled the verdict. Say that. Blaming the take for a bad task is how the same task gets issued next month with a new suspense date. The other lessons on this path — gap analysis, source matching, task writing — exist so this paragraph gets shorter over time. If it does not, the evaluation is decorative.
You receive this "result" on the diesel-supplier question from the source-matching lesson.
The OSINT return includes: the supplier's annual report, which is unqualified and silent on covenants; three trade-press articles that all quote the same company statement about "robust logistics"; no court filings found in the two jurisdictions you named; nothing on actual delivery performance. It arrived four days before the tender meeting. Nobody tasked a second source.
Write the one-page after-action.
You may not award the plan a pass because the collector was fast.
Continue your training
This lesson is part of The Intel Analyst Academy — professional intelligence analysis training built for analysts. Explore the full course library, structured learning paths, and practical tools at theintelanalystacademy.com.