Last reviewed: Next review due:
Police FOI: scope and structure
England and Wales have 43 territorial police forces, each a separate public authority subject to FOIA 2000. Beyond the territorial forces, the British Transport Police (BTP), Ministry of Defence Police, Civil Nuclear Constabulary, HMICFRS (the inspectorate), the College of Policing, and the IOPC are all separately subject to FOIA. Police and Crime Commissioners (PCCs) are also public authorities — useful for financial and governance data.
Police Scotland is subject to FOISA 2002 (Scottish Information Commissioner). The Police Service of Northern Ireland (PSNI) is subject to FOIA 2000 but with a higher threshold on national security and counter-terrorism exemptions. Each force has a dedicated FOI team or single point of contact — most accept requests by email.
Before filing, always check data.police.uk, which publishes monthly crime, outcomes, and stop-and-search data for England, Wales, and Northern Ireland. Check HMICFRS PEEL inspection reports and the IOPC annual statistics. Many requests can be answered — or significantly contextualised — from these open sources before a formal FOI is needed.
High-value police FOI topics
- 1Officer numbers by rank, ethnicity, and gender — workforce diversity data by force and year.
- 2Complaints against officers: total received, outcome categories, and time to resolution — broken down by department or rank.
- 3Misconduct outcomes: number of officers dismissed, reduced in rank, or given final written warnings in each year.
- 4Vetting failure rates: number of officers and staff who failed vetting, by reason category.
- 5Use of force by type (taser, CS spray, physical restraint) by force area and demographic breakdown of subjects.
- 6Body-worn video: compliance rates, number of occasions recording was not activated, footage deletion.
- 7Custody deaths: number of deaths during or following police contact, outcomes of internal and IOPC investigations.
- 8Stop and search beyond published data: breakdown by ward or local area, outcomes below force level.
- 9Watchlist and facial recognition: number of enrolments, number of alerts, false positive rates where known.
- 10Sexual misconduct allegations against officers: number referred to misconduct proceedings per year.
Red flags in a police FOI refusal
- S.31 law enforcement cited for aggregate historical statistics — past data rarely prejudices ongoing operations.
- S.40 personal data used for aggregate counts or workforce statistics — aggregate data is not personal data.
- S.31 applied to use-of-force statistics without explaining the specific prejudice to law enforcement.
- A refusal to confirm or deny (s.1(1)(a)) that falls back on s.31 without specifying the nature of the harm.
- S.24 national security cited without reference to a specific operational context — not all policing is national security.
- S.12 cost limit used for requests that ask for statistics the force already collects for its own management purposes.
- The force redirecting you to data.police.uk when that source does not cover the specific breakdown you requested.
- A misconduct outcome withheld under s.40 when the College of Policing Barred List is already a public register.
Police FOI request checklist
- Checked data.police.uk for crime, outcomes, and stop-and-search data before filing.
- Checked HMICFRS PEEL inspection reports for the force I am investigating.
- Checked IOPC annual statistics for misconduct and complaints data at national level.
- Confirmed which entity holds the data — the territorial force, PCC, IOPC, HMICFRS, or College of Policing.
- For Scotland: addressed to Police Scotland with FOISA and Scottish Information Commissioner in mind.
- Specified data by calendar or financial year to match force reporting periods.
- Asked for aggregate counts or statistical breakdowns, not personal officer data.
- Assessed any likely s.31 argument and prepared a counter-argument based on the public interest.
- Set a 20-working-day deadline reminder and prepared a follow-up template.
- If refused under s.31: drafted an internal review citing the specific claimed prejudice and the public interest in police accountability.
Build your police FOI request
Our FOI Request Builder includes police-specific templates covering use-of-force, misconduct, vetting, and workforce data for all 43 England and Wales forces.
Open FOI Request BuilderCommon mistakes
- Requesting data that is already on data.police.uk — this will be refused under s.21 (accessible by other means).
- Asking for named officers' disciplinary records — ask for aggregate outcomes by rank or category instead.
- Not cross-referencing HMICFRS PEEL reports before filing — inspectorate data often contains the context that makes FOI-disclosed statistics newsworthy.
- Accepting a s.31 refusal without challenging whether the claimed prejudice is real and substantial.
- Forgetting to include the College of Policing and IOPC as separate FOI targets when investigating national misconduct trends.
- Not requesting from the PCC as well as the force — PCCs hold governance and financial oversight data that forces do not.
- Treating Police Scotland the same as England and Wales forces — FOISA applies, and the Scottish Information Commissioner is the regulator.
Related guides
Primary sources
- data.police.uk — open crime, outcomes, and stop-and-search data
- HMICFRS — PEEL inspection reports and data (justiceinspectorates.gov.uk)
- IOPC — annual statistics and investigation summaries (policeconduct.gov.uk)
- College of Policing — Barred and Advisory Lists (college.police.uk)
- Freedom of Information Act 2000 — s.31 law enforcement exemption (legislation.gov.uk)
- Scottish Information Commissioner (itspublicknowledge.info)
- WhatDoTheyKnow — police force FOI requests (whatdotheyknow.com)