Intelligence report example (Appendix A)
Intelligence management — Authorised Professional Practice
Summary
This page provides an example of an intelligence report, including a structured template for officers to follow. It outlines various elements that should be included in an intelligence report, such as the report title, date and time, source evaluation, and handling codes. Additionally, it describes the different categories for evaluating the reliability of the source and the knowledge level of the information provided. Officers are guided on the importance of accurate and complete reporting, which supports effective intelligence management within policing operations.
Key principles
- 1Follow the structured template for reporting.
- 2Evaluate source reliability and information assessment accurately.
- 3Use defined handling codes for information sharing.
Defined terms
- Source evaluation
- 1 - Reliable, 2 - Untested, 3 - Not reliable
- Information assessment
- A - Known directly to source, B - Known indirectly to source but corroborated, C - Known indirectly to source, D - Not known, E - Suspected to be false
- Handling code
- P - Lawful sharing permitted, C - Lawful sharing permitted with conditions
- Action condition
- A1 - Covert development, A2 - Covert use, A3 - Overt use
- Sanitisation condition
- S1 - Delegated authority, S2 - Consult originator
Full guidance
Intelligence report example (Appendix A)
Intelligence cycle, tasking and coordination and completing an intelligence report
This page is from APP, the official source of professional practice for policing.
| | | | --- | --- | | Government security <br>classification | Official<br><br>Secret<br><br>Top secret | | Organisation and <br>officer | | | Date and time of report | | | Source or intelligence source reference (ISR) | | | Report URN | | | Source evaluation | 1 - Reliable<br><br>2 - Untested<br><br>3 - Not reliable | | Information or intelligence assessment | A - Known directly to source<br><br>B - Known indirectly to source but corroborated<br><br>C - Known indirectly to source<br><br>D - Not known<br><br>E - Suspected to be false | | Report title | | | Person record | Name<br><br>Date of birth<br><br>PNC ID | | Operation name and number | | | Information content | | | Handling code | P - Lawful sharing permitted<br><br>C - Lawful sharing permitted with conditions | | Action condition (only relevant if handling <br>code C selected) | A1 - Covert development<br><br>A2 - Covert use<br><br>A3 - Overt use | | Sanitisation condition (only relevant if handling <br>code C selected) | S1 - Delegated authority<br><br>S2 - Consult originator |
Do not provide personal information such as your name or email address in the feedback form. Read our privacy policy for more information on how we use this data
What is the reason for your answer?
APP is the authoritative source for UK policing practice and is updated over time. For the current, official version — including any operational detail not reproduced here — go direct.
Read the full APP guidanceSource: College of Policing — Authorised Professional Practice · Crown copyright, licensed under Open Government Licence v3.0. Summary fetched 2026-06-27.