Operational partnerships - Use of force reporting SOP (O43i)

1. Summary of changes

1.1. This standard operating procedure has been reviewed in February 2024 - no amendments to content made. 

2. What this procedure is about

2.1. This SOP outlines the requirement for officers and staff to record data surrounding their use of force in accordance with the NPCC use of force collating project, launched on 1 October 2016. Use of force data will be collected from April 2017 for the police annual data return (ADR) to the Home Office on an annual basis.

2.2. Use of force data will be published locally on a quarterly basis on the external Kent Police website and internally to relevant stakeholders and groups.

Compliance with this procedure/SOP and any governing policy is mandatory. 

3. Detail the procedure

3.1. A record is to be completed on the use of force form as soon as is practicable and preferably within the tour of duty the force was used. If you are going on a period of leave then this should be completed before you go.

3.2. Each member of staff is required to record their own use of force. A record is to be completed when an individual officer or member of police staff uses force. If an officer/member of police staff uses force on more than one person, a new report will be completed for each person on whom force is used.

3.3. Recognising the potential lack of detail, one record should be completed where force has been used over a period of time against person/s not subsequently apprehended in a designated public order event.

3.4. Where the incident doesn’t occur in your home force area, officers should complete their own force’s records.

3.5. A record is to be created when one of the following techniques or tactics is used:

• handcuffing (compliant)
• handcuffing (non-compliant)
• unarmed skills (including pressure points, strikes, restraints and take downs)
• use of dogs
• drawing or use of baton
• drawing or use of irritant spray
• limb/body restraints
• spit guard
• conductive Energy Device (CED currently TASER - in any of the seven categories of use)
• AEP: aimed or discharged
• firearms: aimed or discharged
• other/improvised

3.6. Where the use of force is associated with the arrest of a subject, fully justified reasons for it should be included in any statement of evidence completed by the officer.

3.7. If the subject on whom force is used is not arrested, fully justified reasons for the use should be included in a PNB entry by the officer (along with the decision not to arrest).

3.8. If force is used on a subject in custody, a full record of it should be endorsed on the detained person's custody record along with the submission of the form.

3.9. The completed use of force form will be submitted electronically and stored as a survey entry. Officers are presented with the option to print a copy of the completed form before it is submitted. The mobile first team should be contacted regarding access to the data. 

4. Equality Impact Assessment (EIA)

4.1. An EIA has been carried out and shows the proposals have no potential or actual differential impact on grounds of race, ethnicity, nationality, gender, transgender, disability, age, religion or belief or sexual orientation.

5. Risk assessment

5.1. This SOP has been assessed as medium risk.  

6. Consultation 

• Staff Safety Training Unit
• Professional Standards
• Health and Safety
• Human Resources
• IT Security
• Estates
• Equality and Diversity
• Legal
• Freedom of Information
• Police Federation

7. Monitoring and review

7.1. The SOP will be monitored by the Staff Safety Training Unit via the Force Health Advisory Board. The SOP will be reviewed every two years with the next review scheduled for February 2026.

8. Security

8.1. Kent Police have measures in place to protect the security of your data in accordance with our Information Management policy.

9. Retention and disposal of records

9.1. Kent Police will hold data in accordance with our Records Review, Retention and Disposal policy.