THE INTEL ANALYST ACADEMY
Professional Intelligence Training
Printable Lesson
Intelligence Report Components
The Intel Analyst Academy · Lesson Notes
A standardized report structure is not bureaucratic busywork -- it is a contract with your reader. Decision-makers who receive dozens of reports a day rely on predictable formats to find the information they need fast. This lesson breaks down each standard component, explains its purpose, walks through common mistakes, and shows how the pieces work together to create a coherent intelligence product.
These two sections are the most important real estate in your entire report. If your consumer reads nothing else, they will read these. Treat them accordingly.
The executive summary is a standalone miniature of your entire report. It should contain the bottom line, the key supporting evidence, and the primary implications -- all in roughly one-half to one full page. A senior leader should be able to read the executive summary, skip the rest, and still walk into a meeting with a sound understanding of the issue.
Purpose: Give the busiest people in the building everything they need in 60 seconds.
Common mistake: Writing the executive summary as a vague teaser ("This report examines the growing threat of...") instead of leading with the conclusion ("We assess with high confidence that the threat has increased by 40% since January because...").
Write your executive summary last, even though it appears first. You cannot summarize what you have not yet fully analyzed. Draft a placeholder, write the full report, then come back and distill.
Key judgments are your analytical conclusions stated as clear, declarative sentences with associated confidence levels. They are not summaries of facts -- they are assessments. Each key judgment should be something the reader could disagree with, because if it is merely a statement of undisputed fact, it does not need to be a judgment.
Good example: "We assess with moderate confidence that Country X will conduct a nuclear test within the next six months, driven by domestic political pressure and the completion of key technical milestones."
Bad example: "Country X has a nuclear program." (This is a fact, not a judgment.)
Key judgments are like movie trailers: they should tell you exactly what to expect without making you sit through the whole thing. Unlike movie trailers, they should not be misleading.
The background section answers the question: "What does the reader need to know to understand this analysis?" It provides historical context, relevant previous reporting, and the foundational facts that set the stage for your analytical sections.
Background is not a history textbook. Include only what is necessary to understand the current analysis. If the reader needs to go back to 1947 to understand your assessment of a 2026 cyber threat, you are probably including too much. A good rule of thumb: if removing a background paragraph does not diminish the reader's understanding of your analysis, cut it.
For recurring products (weekly updates, periodic assessments), keep the background section short and reference previous reports rather than repeating context. Your regular readers already have that foundation.
Common mistake: Using the background section as a dumping ground for all the research you did that did not fit anywhere else. If it does not directly support the analysis that follows, it belongs in an appendix -- or nowhere.
This is the main body -- the engine room of your report. Here you present your evidence, explain your reasoning, and build the case for your key judgments. Everything before this section sets the stage; everything after it draws conclusions from it.
The analysis section itself needs internal organization. Common approaches include:
A common trap is presenting pages of evidence without analysis, forcing the reader to draw their own conclusions. The opposite trap is making bold assessments without showing your work. The sweet spot is a clear pattern: evidence, then assessment, then implication, repeated for each major point.
The analysis section is where you prove you are not just a very expensive search engine. Anyone can find information. You are paid to make sense of it.
Common mistake: Burying the analytical point at the end of a long paragraph of evidence. Lead with the assessment, then support it. The reader should never have to hunt for your conclusion.
This section answers the most important question your consumer has: **"What happens next, and what does it mean for me?"** It projects forward from your analysis, identifies likely scenarios, and connects your findings to the decisions your consumer faces.
Good outlook sections present a range of possibilities with associated likelihoods, not just a single prediction. They also identify indicators the consumer should watch for -- signposts that would indicate which scenario is unfolding.
Example: "If the government proceeds with the proposed reforms (which we assess as likely), expect moderate protests in the capital within two weeks. If it reverses course (less likely), opposition groups will likely interpret this as weakness and escalate demands."
Appendices are where you put the material that supports your analysis but would clutter the main narrative: detailed data tables, full source citations, technical methodology notes, extended timelines, biographical sketches, or large-format maps.
The key principle: appendices should be referenced from the main text. An appendix that nobody knows exists is an appendix that does not exist. Use clear cross-references ("See Appendix B for the full timeline") so readers know where to find supporting detail.
Think of your report components as a pyramid. The executive summary is the tip -- sharp and visible. Key judgments, background, and analysis form the body. Appendices are the broad base that supports everything above. Each layer serves a different reader with a different amount of time.
No component exists in isolation. The executive summary distills the key judgments. The key judgments are supported by the analysis. The analysis builds on the background. The outlook projects from the analysis. The appendices provide depth for anyone who wants to verify the evidence. When all components align, the reader experiences a smooth flow from "what do I need to know?" to "what should I do about it?"
When they do not align -- when the executive summary promises something the analysis does not deliver, or the key judgments contradict the outlook -- the reader loses trust. Internal consistency is not optional.
Every intelligence report, regardless of type or format, shares common structural components. Understanding these components helps analysts write more effective reports and helps consumers navigate them efficiently:
The title is the most important single element of any intelligence report. A good title tells the consumer what the report is about, what the key judgement is, and why they should read it:
For reports longer than two pages, the executive summary is mandatory. It should be self-contained - the consumer should understand the assessment, the supporting reasoning, and the implications without reading the main body:
Beyond formatting, the structure of an intelligence report reflects the rigour of the analytical process:
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.
