Key takeaways
- HUMINT concerns human sources, not simply an analyst working with information.
- A source account needs context, corroboration and clear limits before a client relies on it.
- The brief should define the knowledge gap, permitted contact and report recipients.
What does human intelligence mean?
The UK Secret Intelligence Service’s FAQ identifies HUMINT as information collected from people. That describes the source of the information, rather than a particular report format or a guarantee of secrecy. Government intelligence services work within their own mandates; a business client should define its civilian research assignment and permissions separately.
In commercial use, the relevant task is structured human-source research. Someone may have first-hand knowledge of an operating process, a working relationship or a decision. The investigator must establish what that person actually knows and how their account addresses the client’s question. A conversation alone is not a supported conclusion.
It is also important to distinguish a person’s account from the analyst’s interpretation. If a source describes a delayed handover, that does not automatically establish why it occurred or who caused it. The finished assessment should preserve the difference between reported experience, corroborated events and unresolved explanation.
Which business questions can human sources help answer?
HUMINT is useful to consider when the material gap concerns experience or context that available documents do not explain. A client may need to understand how a service handover works in practice, what changed after a management transition or how different participants experienced the same event. The brief should name that gap before anyone is approached.
In a civilian HUMINT assignment, structured conversations with knowledgeable people can establish what they directly observed and where their account stops. The report should distinguish those observations from second-hand claims, opinions and inference. Before commissioning, ask how the provider will assess source knowledge and seek independent corroboration; a conversation alone cannot establish that a disputed event occurred exactly as described.
A corporate HUMINT brief can identify the relevant roles and periods without demanding a preselected answer. For example, ask what a source observed during the handover rather than asking them to confirm that a named manager undermined it. A source who cannot know the answer should be recorded as a limitation, not pressed into a broader claim.
What does a human account actually establish?
A client should be able to follow the basis of each material statement. Did the source see the event, participate in it, hear about it from someone else or offer an interpretation? These are different evidence positions even if the person speaks confidently.
| Source account | Initial significance | Useful clarification |
|---|---|---|
| I attended the handover meeting | A claimed first-hand account of that event | Which meeting, when and in what role? |
| A colleague said the team rejected the plan | A second-hand claim with another origin | Was the source present or repeating another account? |
| The new structure caused the delays | An explanation or judgement | What observed events or records support that explanation? |
| The process worked differently after I left | A claim potentially outside direct access | How did the source learn about the later period? |
The purpose is not to dismiss people’s experience. It is to give that experience the right evidential weight. One participant may know a narrow part of the process exceptionally well while having little visibility of the wider decision. The report should make that boundary clear.
How should a HUMINT finding be assessed?
Assess the source’s relevant access and the support for the individual claim separately. A senior title does not prove direct knowledge of every event. Several accounts are not necessarily independent if everyone heard the same original story. Look for records, dates or genuinely separate observations that can clarify the material point.
The UK government’s explanation of analytical uncertainty distinguishes a judgement’s assessed likelihood from the strength of its analytical foundations. A business report need not adopt a government rating system to apply the practical lesson: explain why the finding deserves weight and what could change it.
For a hypothetical handover review, one participant may describe a late instruction while another recalls an earlier version of the plan. Comparing their actual roles, dates and available documents may explain the difference. Until then, the report should show both accounts. The source-validation guide examines this assessment in more detail.
What should be agreed before approaching people?
Define who may be contacted, why their knowledge is relevant and what information the team is authorised to collect. Agree how accounts will be documented, who receives identifying details and how a source’s handling restrictions will be considered. A source contact can create practical consequences for the source or the organisation, so the proposed approach belongs in the mandate.
For UK personal information, the ICO’s current lawful-basis guidance requires an appropriate basis to be determined and documented before processing. The responsible parties should assess the actual purpose and data. Neither a business objective nor the term HUMINT settles those requirements.
Keep the instruction tied to a legitimate knowledge need. Do not assume someone may disclose another organisation’s confidential material or that the client’s request authorises private-account access. If a proposed conversation or collection raises a permission problem, resolve it with the responsible advisers before proceeding.
A checklist for the first HUMINT brief
Prepare a requirement that a proposed collector can assess without guessing the client’s expectations. The following checklist helps keep the assignment about relevant human knowledge and a reviewable finding.
- State the decision and the specific knowledge gap.
- Identify relevant roles, locations and periods.
- List what is already documented and what remains disputed.
- Define contact permissions, handling limits and report recipients.
- Request distinctions between direct knowledge, hearsay and assessment.
- Ask how material claims will be corroborated and uncertainty reported.
Use that brief when comparing HUMINT services. Ask what relevant access the proposed team can realistically assess, how it will document the accounts and what the client will receive if the evidence remains incomplete. Avoid equating a large contact list with a strong answer.
Human-source research can be combined with other methods where the question requires them. The HUMINT and OSINT comparison explains how people’s accounts and public-source evidence can contribute different parts of the same assessment.