Understanding Intelligence Requirements

Every intelligence product begins with a question. It might be a detective asking who is responsible for a series of burglaries, a corporate security team investigating insider risk, or a due diligence analyst assessing a potential acquisition. Regardless of the subject matter, the role of an intelligence analyst is the same: to reduce uncertainty and support better decision-making.

It is tempting to think that the next step is collecting information. In reality, analysts must first understand exactly what they have been asked to do.

Many intelligence failures can be traced back to poorly defined requirements rather than poor analysis. If the wrong question is asked, or if the analyst misunderstands what the customer actually needs, even an excellent intelligence product may fail to support the decision it was intended to inform.

For this reason, analysts must spend time defining the intelligence requirement before querying a commercial database or social media profile.

What is an intelligence requirement?

An intelligence requirement is the question that intelligence is intended to answer. While this sounds straightforward, requirements are often far broader than they first appear. A customer may ask for a report on a particular individual or crime type, but that request rarely represents the underlying decision they are trying to make.

For example, a request to "produce a report on vehicle theft in the city centre" could have several different objectives. The customer may want to identify where to deploy additional patrols, prioritise surveillance activity, or prepare for a strategic meeting. Each objective requires a different type of intelligence product.

Good analysts therefore look beyond the wording of the request and seek to understand the decision that the customer is trying to make.

Understanding the customer's needs

Intelligence exists to support decision-makers, not simply to answer interesting questions.

One of the most valuable habits an analyst can develop is asking, "What decision will this intelligence support?" The answer often changes the entire direction of the assessment.

Before beginning any work, analysts should understand:

• Who is requesting the intelligence?
• Why do they need it?
• What decision are they trying to make?
• What questions need answering?
• What information do they already have?
• What level of detail is required?
• When is the intelligence product needed?

A chief executive preparing for a board meeting is unlikely to require the same level of operational detail as an investigator preparing to execute a search warrant. Understanding the audience allows the analyst to produce intelligence that is relevant, proportionate and useful.

Defining the scope

Without clearly defined boundaries, intelligence requirements have a habit of expanding as new questions emerge. This phenomenon, often referred to as scope creep, can quickly turn a manageable task into an open-ended investigation.

Establishing the scope at the outset helps ensure that the work remains focused and achievable. Scope should normally define:

• The subject of the assessment.
• The time period being examined.
• The geographical area.
• Any specific organisations or individuals to include or exclude.
• The information sources that will be used.
• The expected output.

Clearly defining what falls outside the scope is just as important as defining what falls within it.

Terms of Reference

Many intelligence units formalise these discussions through a Terms of Reference document, although some will keep it as informal as an email. A  Terms of Reference document acts as an agreement between the analyst and the customer. It records exactly what is being produced, why it is required and how success will be measured.

Although formats vary between organisations, a Terms of Reference will typically include:

• The customer requesting the work.
• The analyst responsible.
• The purpose and objectives.
• The intelligence requirement.
• The scope of the assessment.
• Relevant timeframes.
• Deadlines and milestones.
• The expected intelligence product.
• Any assumptions or limitations.

Agreeing these details before work begins helps avoid misunderstandings later in the investigation and provides an audit trail explaining why particular analytical decisions were made.

Asking better questions

The quality of intelligence is closely linked to the quality of the questions being asked. Poorly defined questions tend to produce descriptive reports that summarise information without adding much value. Well-defined questions encourage analysis.

Consider the difference between asking: "Tell me everything you know about this company." and "Does this company present any financial, reputational or regulatory risks that would affect our decision to acquire it?"

The second question is far more focused. It immediately helps the analyst prioritise information, identify relevant intelligence gaps and determine what evidence is likely to influence the final assessment.

Whenever possible, intelligence requirements should be framed as decision-support questions rather than requests for information.

Managing expectations

One of the less visible aspects of intelligence work is managing customer expectations. Analysts are sometimes asked to answer questions that cannot reasonably be answered with the available information or within the available timeframe. Agreeing to unrealistic requirements rarely benefits anyone. 

Instead, analysts should discuss what can realistically be achieved and explain any limitations before work begins. This may involve narrowing the scope, extending deadlines or agreeing to produce an interim assessment while additional collection continues.

Managing expectations is not about avoiding difficult work. It is about ensuring that intelligence remains credible and proportionate.

Intelligence requirements evolve

Although a Terms of Reference provides direction, it should not be viewed as a rigid document.

As new information emerges, priorities often change. An investigation may uncover previously unknown individuals, reveal new risks or identify intelligence gaps that require additional collection. Customers may also refine their questions as they develop a better understanding of the problem.

For this reason, intelligence requirements should be reviewed throughout the assessment. Significant changes should be discussed with the customer and, where appropriate, reflected in an updated Terms of Reference. This ensures that the analyst remains focused on answering the right question rather than simply continuing with the original plan.

Well-defined requirements produce better intelligence

The most effective intelligence analysts are not necessarily those who collect the most information or produce the longest reports. They are the ones who consistently answer the questions that matter.

By taking time to understand the customer's objectives, define the scope of the work and agree clear Terms of Reference, analysts create the conditions for effective intelligence long before collection begins. The result is intelligence that is focused, proportionate and directly relevant to the decisions it is intended to support.

Every stage of the intelligence process depends upon asking the right question first. Get the requirement wrong, and every subsequent stage becomes more difficult. Get it right, and collection becomes more focused, analysis more meaningful and the final intelligence product far more valuable.