Key takeaways
- Define the decision and information gap before commissioning interviews.
- Collection, source evaluation and analysis are connected but distinct stages.
- A completed assignment can leave questions unresolved; those limits belong in the report.
Start with the decision and the HUMINT requirement
A HUMINT requirement describes the knowledge a client needs from human sources and why it matters. “Tell us everything about this company” is too broad to guide collection or judge delivery. “What responsibilities did this executive personally hold during the implementation?” is a question that can be mapped to relevant experience, a period and possible supporting records.
State what you already know, which facts are disputed, the intended use and who will read the result. Explain whether the decision concerns proceeding, seeking clarification or changing an existing risk assessment. The provider should be able to tell you when the question is better answered by a document rather than an interview.
When comparing best HUMINT service providers, ask each firm to explain what information would actually change the answer. This is more revealing than an undifferentiated promise of access. Our HUMINT agency selection guide covers questions about the team and its proposed approach.
Agree scope, responsibilities and decision gates
Before enquiries start, agree the subjects, relevant period, countries, permitted activities and exclusions. Identify the person who can authorise changes. Document how unexpected sensitive information, conflicts of interest or a material increase in risk will be escalated. The same checkpoint should apply when a client asks for additional subjects midway through an assignment.
Personal information requires an appropriate basis for processing. The ICO’s current lawful-basis guidance says this must be identified and documented before use; the appropriate basis depends on the activity and circumstances. A commercial contract alone does not explain every use of personal information about third parties.
For a corporate HUMINT assignment, the agreement should also define deliverables and recipient restrictions. Specify whether you need an interim issues note, a final assessment, a presentation or a follow-up clarification. Do not equate payment for activity with a guaranteed substantive conclusion.
What are the stages and their outputs?
The sequence below is a practical commissioning framework. Work may move backwards when a contradiction changes the question or when relevant evidence proves unavailable. A responsible change is documented rather than hidden inside a revised narrative.
| Stage | Expected output | Buyer checkpoint |
|---|---|---|
| Requirements | Defined questions and existing information gaps | Would the answer affect the decision? |
| Scope and safeguards | Agreed boundaries, responsibilities and reporting format | Who approves a change? |
| Source enquiries | Relevant accounts with recorded context | What knowledge does each account contribute? |
| Evaluation | Assessment of directness, timing and limitations | Which accounts are independent? |
| Corroboration and analysis | Tested propositions and competing explanations | What supports or contradicts each judgement? |
| Reporting and review | Answers, confidence, gaps and next decisions | What remains unverified? |
The useful unit is a question answered to an explained standard, not a quota of conversations. Agree how the provider will describe unsuccessful enquiries or missing coverage without presenting either as proof that no relevant issue exists.
Collect relevant accounts without losing their context
The value of a human account depends on the speaker’s connection to the issue. A former project manager may know delivery decisions but have no direct knowledge of the financing. A commercial partner may know negotiation conduct but not internal board discussions. The report should preserve those boundaries instead of treating seniority as universal access.
For each material account, expect an explanation of the period covered, whether the person participated directly and whether they are describing observation, interpretation or something heard elsewhere. The client need not receive unnecessary identifying details to understand these limitations.
The ICO’s data minimisation principle supports keeping personal information relevant to the purpose. In this workflow, ask the provider to justify which account details belong in the client deliverable and which should remain restricted or not be retained. The goal is useful evidence with appropriate context, rather than an archive of everything a conversation happened to contain.
Evaluate and corroborate before reaching judgements
A collected statement is an input to analysis. Test whether it concerns the right person or organisation, whether the dates fit, whether knowledge was direct and whether an incentive could affect the account. Then compare it with documents, independently sourced accounts and plausible alternative explanations.
Fictional example: two former employees describe an executive as the project lead. Both learned this from the same internal announcement. A third participant describes a narrower role and supplies a dated responsibility record. The analyst should explain the common origin of the first two accounts and the significance of the conflict, rather than report a two-to-one vote.
The PHIA analytical standards provide a useful public reference for distinguishing assumptions, supporting judgements with evidence and acknowledging uncertainty. They govern a government assessment context; citing them is not private-sector accreditation. For a commercial buyer, the practical question is whether the provider can explain the reasoning behind its conclusion.
Review the report and close the assignment deliberately
At handover, read each key judgement alongside its evidence and limitations. A clear report answers the original questions, identifies those that remain open, explains material contradictions and distinguishes evidence from assessment. See the HUMINT report guide for a fuller review framework.
- Check that each agreed question receives an answer or an explicit gap.
- Ask which judgements rely heavily on one account.
- Confirm that hearsay is distinguished from direct experience.
- Review how contradictory material affected the conclusion.
- Agree the recipients and permitted use of the report.
- Record any follow-up decision and its additional scope.
Closeout should also resolve open administrative questions: which version is final, who can clarify it and whether further work has been authorised. A later development may justify reassessment; it should not silently change the date or meaning of the original conclusion. Avoid presenting an assessment based on a defined period as a permanent guarantee about a person or organisation.