Leave this site
We use some essential cookies to make our website work. We’d like to set additional cookies so we can remember your preferences and understand how you use our site.
You can manage your preferences and cookie settings at any time by clicking on “Customise Cookies” below. For more information on how we use cookies, please see our Cookies notice.
Your cookie preferences have been saved. You can update your cookie settings at any time on the cookies page.
Your cookie preferences have been saved. You can update your cookie settings at any time on the cookies page.
Sorry, there was a technical problem. Please try again.
This site is a beta, which means it's a work in progress and we'll be adding more to it over the next few weeks. Your feedback helps us make things better, so please let us know what you think.
FOI Reference: 989/2025
Request
I would like to request data under the Freedom of Information Act 2000 regarding arrests/charges for driving under the influence of alcohol/drugs.
3a) Please provide a month by month breakdown of the figures for each year
3b) Please also provide a breakdown by age of offender
4a) Please provide a month by month breakdown of the figures for each year
4b) Please also provide a breakdown by age of offender
If some parts of this request are easier to answer than others, please provide the easiest parts first rather than hold up the entire request. I would prefer to receive your response in electronic format.
If you decide to withhold some of the information requested using exemptions in the Freedom of Information Act, please inform me which exemptions you have used.
Under the Freedom of Information Act, you have 20 working days to respond to this request. I also request for notification to be sent to me on email to confirm you have received this request.
I can confirm that Dyfed-Powys Police does hold the information requested, as outlined below:-
Response Q1
2022 – 687
2023 – 597
2024 – 502
2025 – 394
Response Q2
2022 – 743
2023 – 617
2024 – 366
2025 – 336
Response 3a
Please note: The requested codes are not retrievable. However, below are the number of arrests for drink/drug driving offences, with the breakdown month on month.
Pre Niche (Old recording system) (Drink)
(Please use slider at base of table)
|
Arrest Codes |
Jan-22 |
Feb-22 |
Mar-22 |
Apr-22 |
May-22 |
Jun-22 |
Jul-22 |
Aug-22 |
Sep-22 |
Oct-22 |
Nov-22 |
Dec-22 |
Jan-23 |
Feb-23 |
Mar-23 |
Apr-23 |
To 11th May 2023 |
Total |
|
RT88007 Drive motor vehicle when alcohol level above limit |
19 |
27 |
21 |
35 |
23 |
19 |
32 |
37 |
24 |
28 |
21 |
28 |
33 |
21 |
25 |
37 |
6 |
436 |
|
RT88008 In charge of motor vehicle - alcohol level above limit |
2 |
0 |
1 |
1 |
1 |
2 |
2 |
0 |
1 |
2 |
0 |
0 |
1 |
1 |
0 |
1 |
1 |
16 |
|
RT88010 Fail to provide specimen for analysis - vehicle driver |
0 |
1 |
1 |
2 |
2 |
1 |
5 |
5 |
4 |
3 |
4 |
3 |
2 |
3 |
0 |
5 |
1 |
42 |
|
RT88011 Fail to provide specimen - person in charge of vehicle |
1 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
0 |
0 |
0 |
0 |
3 |
|
RT88339 Drive whilst unfit through drink |
2 |
5 |
1 |
5 |
9 |
4 |
3 |
1 |
5 |
4 |
2 |
4 |
5 |
0 |
1 |
0 |
1 |
52 |
|
RT88347 In charge of vehicle whilst unfit through drink |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
2 |
|
Total |
24 |
34 |
24 |
43 |
35 |
26 |
42 |
44 |
35 |
37 |
27 |
35 |
42 |
25 |
26 |
43 |
9 |
551 |
Post Niche (New recording system) (Drink)
(Please use slider at base of table)
|
Arrest Codes |
From 12th May 2023 |
Jun-23 |
Jul-23 |
Aug-23 |
Sep-23 |
Oct-23 |
Nov-23 |
Dec-23 |
Jan-24 |
Feb-24 |
Mar-24 |
Apr-24 |
May-24 |
Jun-24 |
Jul-24 |
Aug-24 |
Sep-24 |
Oct-24 |
Nov-24 |
Dec-24 |
Jan-25 |
Feb-25 |
Mar-25 |
Apr-25 |
May-25 |
Jun-25 |
Jul-25 |
Aug-25 |
Sep-25 |
Oct-25 |
Total |
|
RT88007 Drive motor vehicle when alcohol level above limit (recordable) |
10 |
35 |
31 |
29 |
17 |
25 |
20 |
29 |
20 |
23 |
19 |
25 |
26 |
25 |
14 |
26 |
25 |
19 |
28 |
28 |
18 |
23 |
26 |
20 |
32 |
22 |
23 |
32 |
21 |
6 |
697 |
|
RT88008 In charge of motor vehicle - alcohol level above limit (recordable) |
1 |
1 |
0 |
1 |
3 |
3 |
0 |
1 |
1 |
0 |
0 |
2 |
1 |
0 |
0 |
0 |
0 |
1 |
0 |
0 |
1 |
0 |
2 |
0 |
0 |
0 |
1 |
1 |
0 |
0 |
20 |
|
RT88010 Fail to provide specimen for analysis - vehicle driver (recordable) |
0 |
0 |
0 |
4 |
1 |
2 |
3 |
4 |
3 |
2 |
2 |
1 |
3 |
2 |
2 |
1 |
3 |
1 |
2 |
4 |
0 |
3 |
3 |
2 |
5 |
2 |
2 |
2 |
1 |
0 |
60 |
|
RT88011 Fail to provide specimen - person in charge of vehicle (recordable) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
0 |
0 |
0 |
2 |
|
RT88326 Attempt to drive motor vehicle - alcohol level above limit (recordable) |
0 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
|
RT88339 Drive whilst unfit through drink (recordable) |
3 |
2 |
7 |
7 |
6 |
1 |
4 |
1 |
3 |
5 |
3 |
1 |
2 |
2 |
3 |
4 |
6 |
2 |
3 |
1 |
0 |
1 |
5 |
4 |
3 |
3 |
4 |
1 |
1 |
1 |
89 |
|
RT88343 Attempt to drive vehicle whilst unfit through drink (recordable) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
|
RT88347 In charge of vehicle whilst unfit through drink (recordable) |
0 |
0 |
2 |
0 |
1 |
1 |
1 |
0 |
1 |
0 |
0 |
1 |
0 |
0 |
1 |
1 |
0 |
0 |
0 |
1 |
0 |
1 |
1 |
0 |
0 |
0 |
0 |
2 |
0 |
0 |
14 |
|
Total |
14 |
39 |
40 |
41 |
28 |
32 |
28 |
36 |
28 |
30 |
24 |
30 |
32 |
30 |
20 |
32 |
34 |
23 |
33 |
34 |
19 |
28 |
37 |
26 |
40 |
27 |
31 |
38 |
23 |
7 |
884 |
Response Q3b
Pre Niche (Old recording system) (drink)
|
Age |
2022 |
2023 - to 11th May |
Total |
|
17 |
2 |
1 |
3 |
|
18 |
7 |
2 |
9 |
|
19 |
9 |
7 |
16 |
|
20 |
11 |
3 |
14 |
|
21 |
5 |
4 |
9 |
|
22 |
10 |
2 |
12 |
|
23 |
10 |
5 |
15 |
|
24 |
7 |
7 |
14 |
|
25 |
9 |
6 |
15 |
|
26 |
12 |
5 |
17 |
|
27 |
12 |
2 |
14 |
|
28 |
11 |
0 |
11 |
|
29 |
8 |
2 |
10 |
|
30 |
12 |
3 |
15 |
|
31 |
12 |
4 |
16 |
|
32 |
14 |
4 |
18 |
|
33 |
11 |
4 |
15 |
|
34 |
16 |
3 |
19 |
|
35 |
10 |
1 |
11 |
|
36 |
9 |
6 |
15 |
|
37 |
13 |
2 |
15 |
|
38 |
10 |
3 |
13 |
|
39 |
6 |
6 |
12 |
|
40 |
12 |
2 |
14 |
|
41 |
13 |
3 |
16 |
|
42 |
12 |
4 |
16 |
|
43 |
10 |
6 |
16 |
|
44 |
7 |
2 |
9 |
|
45 |
6 |
4 |
10 |
|
46 |
7 |
1 |
8 |
|
47 |
4 |
1 |
5 |
|
48 |
6 |
5 |
11 |
|
49 |
8 |
1 |
9 |
|
50 |
6 |
3 |
9 |
|
51 |
5 |
1 |
6 |
|
52 |
9 |
2 |
11 |
|
53 |
4 |
1 |
5 |
|
54 |
5 |
2 |
7 |
|
55 |
7 |
2 |
9 |
|
56 |
7 |
2 |
9 |
|
57 |
0 |
1 |
1 |
|
58 |
2 |
2 |
4 |
|
59 |
4 |
1 |
5 |
|
60 |
1 |
1 |
2 |
|
61 |
4 |
1 |
5 |
|
62 |
3 |
1 |
4 |
|
63 |
3 |
0 |
3 |
|
64 |
2 |
1 |
3 |
|
65 |
4 |
1 |
5 |
|
66 |
1 |
0 |
1 |
|
67 |
3 |
1 |
4 |
|
69 |
2 |
0 |
2 |
|
70 |
2 |
2 |
4 |
|
71 |
3 |
0 |
3 |
|
73 |
0 |
1 |
1 |
|
74 |
1 |
0 |
1 |
|
76 |
1 |
1 |
2 |
|
78 |
1 |
0 |
1 |
|
79 |
1 |
1 |
2 |
|
83 |
1 |
0 |
1 |
|
Total |
393 |
139 |
532 |
Post Niche (New recording system) (drink)
|
Age |
2023 from 12th May |
2024 |
2025 |
Total |
|
Unkown |
1 |
2 |
0 |
3 |
|
16 |
0 |
1 |
0 |
1 |
|
17 |
0 |
4 |
2 |
6 |
|
18 |
9 |
8 |
2 |
19 |
|
19 |
6 |
5 |
7 |
18 |
|
20 |
7 |
6 |
7 |
20 |
|
21 |
4 |
5 |
5 |
14 |
|
22 |
5 |
4 |
7 |
16 |
|
23 |
7 |
8 |
4 |
19 |
|
24 |
7 |
9 |
2 |
18 |
|
25 |
7 |
6 |
8 |
21 |
|
26 |
6 |
8 |
5 |
19 |
|
27 |
3 |
10 |
7 |
20 |
|
28 |
4 |
10 |
14 |
28 |
|
29 |
9 |
4 |
8 |
21 |
|
30 |
8 |
7 |
2 |
17 |
|
31 |
7 |
5 |
7 |
19 |
|
32 |
3 |
16 |
2 |
21 |
|
33 |
12 |
8 |
4 |
24 |
|
34 |
9 |
14 |
7 |
30 |
|
35 |
12 |
8 |
14 |
34 |
|
36 |
6 |
10 |
9 |
25 |
|
37 |
7 |
6 |
10 |
23 |
|
38 |
8 |
3 |
9 |
20 |
|
39 |
7 |
6 |
10 |
23 |
|
40 |
10 |
14 |
10 |
34 |
|
41 |
4 |
16 |
5 |
25 |
|
42 |
1 |
8 |
5 |
14 |
|
43 |
6 |
12 |
8 |
26 |
|
44 |
5 |
5 |
9 |
19 |
|
45 |
8 |
9 |
4 |
21 |
|
46 |
3 |
3 |
4 |
10 |
|
47 |
1 |
6 |
7 |
14 |
|
48 |
2 |
4 |
4 |
10 |
|
49 |
1 |
5 |
7 |
13 |
|
50 |
7 |
3 |
3 |
13 |
|
51 |
8 |
8 |
6 |
22 |
|
52 |
7 |
7 |
3 |
17 |
|
53 |
3 |
3 |
8 |
14 |
|
54 |
5 |
7 |
5 |
17 |
|
55 |
3 |
5 |
2 |
10 |
|
56 |
3 |
6 |
4 |
13 |
|
57 |
1 |
8 |
4 |
13 |
|
58 |
3 |
6 |
6 |
15 |
|
59 |
1 |
5 |
1 |
7 |
|
60 |
2 |
1 |
4 |
7 |
|
61 |
3 |
4 |
2 |
9 |
|
62 |
0 |
5 |
1 |
6 |
|
63 |
6 |
1 |
0 |
7 |
|
64 |
2 |
2 |
1 |
5 |
|
65 |
3 |
1 |
2 |
6 |
|
66 |
2 |
5 |
3 |
10 |
|
67 |
0 |
2 |
0 |
2 |
|
68 |
1 |
2 |
0 |
3 |
|
69 |
0 |
1 |
2 |
3 |
|
70 |
1 |
5 |
2 |
8 |
|
71 |
0 |
1 |
1 |
2 |
|
72 |
1 |
0 |
0 |
1 |
|
74 |
0 |
1 |
0 |
1 |
|
76 |
0 |
2 |
0 |
2 |
|
77 |
1 |
0 |
1 |
2 |
|
79 |
0 |
2 |
0 |
2 |
|
80 |
0 |
1 |
0 |
1 |
|
81 |
0 |
1 |
0 |
1 |
Response 4a
Pre Niche (Old Recording system) (Drugs)
(Please use slider at base of table)
|
Arrest Codes |
Jan-22 |
Feb-22 |
Mar-22 |
Apr-22 |
May-22 |
Jun-22 |
Jul-22 |
Aug-22 |
Sep-22 |
Oct-22 |
Nov-22 |
Dec-22 |
Jan-23 |
Feb-23 |
Mar-23 |
Apr-23 |
To 11th May 2023 |
Total |
|
RT88340 Drive a vehicle whilst unfit through drugs |
0 |
0 |
2 |
2 |
1 |
2 |
0 |
1 |
0 |
0 |
2 |
0 |
2 |
0 |
0 |
1 |
0 |
13 |
|
RT88584 Drive motor vehicle with a proportion of a specified controlled drug above the specified limit |
2 |
5 |
4 |
7 |
3 |
6 |
8 |
7 |
3 |
3 |
6 |
3 |
6 |
8 |
2 |
6 |
2 |
81 |
|
RT88585 In charge of a motor vehicle with proportion of specified controlled drug above specified limit |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
|
Total |
2 |
5 |
6 |
9 |
4 |
8 |
8 |
8 |
3 |
4 |
8 |
3 |
8 |
8 |
2 |
7 |
2 |
95 |
Post Niche (New Recording system) (Drugs)
(Please use slider at base of table)
|
Arrest Codes |
12th May onwards 2023 |
Jun-23 |
Jul-23 |
Aug-23 |
Sep-23 |
Oct-23 |
Nov-23 |
Dec-23 |
Jan-24 |
Feb-24 |
Mar-24 |
Apr-24 |
May-24 |
Jun-24 |
Jul-24 |
Aug-24 |
Sep-24 |
Oct-24 |
Nov-24 |
Dec-24 |
Jan-25 |
Feb-25 |
Mar-25 |
Apr-25 |
May-25 |
Jun-25 |
Jul-25 |
Aug-25 |
Sep-25 |
Oct-25 |
Total |
|
RT88340 Drive a vehicle whilst unfit through drugs (recordable) |
2 |
1 |
2 |
2 |
1 |
1 |
1 |
5 |
2 |
1 |
3 |
3 |
3 |
1 |
5 |
5 |
1 |
5 |
0 |
3 |
4 |
1 |
9 |
5 |
4 |
1 |
3 |
4 |
1 |
1 |
80 |
|
RT88584 Drive motor vehicle with a proportion of a specified controlled drug above the specified limit (recordable) |
8 |
13 |
28 |
17 |
19 |
13 |
21 |
16 |
23 |
16 |
18 |
9 |
12 |
13 |
11 |
12 |
14 |
9 |
15 |
12 |
15 |
19 |
8 |
9 |
13 |
14 |
20 |
14 |
10 |
0 |
421 |
|
RT88585 In charge of a motor vehicle with proportion of specified controlled drug above specified limit (recordable) |
0 |
1 |
0 |
0 |
0 |
0 |
0 |
1 |
0 |
0 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
0 |
0 |
0 |
0 |
0 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
5 |
|
RT88586 Attempt to drive a motor vehicle with a proportion of a specified controlled drug above the specified limit (recordable) |
0 |
0 |
0 |
1 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
1 |
|
Total |
10 |
15 |
30 |
20 |
20 |
14 |
22 |
22 |
25 |
17 |
22 |
12 |
15 |
14 |
16 |
17 |
15 |
15 |
15 |
15 |
19 |
20 |
17 |
15 |
17 |
15 |
23 |
18 |
11 |
1 |
507 |
Response Q4b
Pre-Niche (Old recording system) (drugs)
|
Age |
2022 |
2023 to 11th May |
Total |
|
18 |
2 |
0 |
2 |
|
19 |
0 |
1 |
1 |
|
20 |
2 |
0 |
2 |
|
21 |
1 |
1 |
2 |
|
22 |
2 |
1 |
3 |
|
23 |
1 |
0 |
1 |
|
24 |
4 |
1 |
5 |
|
25 |
1 |
0 |
1 |
|
26 |
1 |
0 |
1 |
|
27 |
4 |
1 |
5 |
|
28 |
3 |
1 |
4 |
|
29 |
2 |
0 |
2 |
|
30 |
4 |
0 |
4 |
|
31 |
2 |
3 |
5 |
|
32 |
3 |
2 |
5 |
|
33 |
4 |
1 |
5 |
|
34 |
1 |
1 |
2 |
|
35 |
2 |
1 |
3 |
|
36 |
1 |
1 |
2 |
|
37 |
2 |
0 |
2 |
|
38 |
3 |
1 |
4 |
|
39 |
0 |
1 |
1 |
|
40 |
3 |
0 |
3 |
|
41 |
2 |
0 |
2 |
|
42 |
1 |
1 |
2 |
|
43 |
1 |
0 |
1 |
|
44 |
2 |
1 |
3 |
|
45 |
1 |
1 |
2 |
|
46 |
0 |
1 |
1 |
|
49 |
2 |
0 |
2 |
|
50 |
0 |
2 |
2 |
|
52 |
1 |
0 |
1 |
|
56 |
1 |
0 |
1 |
|
57 |
1 |
0 |
1 |
|
Total |
60 |
23 |
83 |
Post Niche (New recording system) (drugs)
|
Age |
2023 from 12th May |
2024 |
2025 |
Total |
|
17 |
4 |
3 |
2 |
9 |
|
18 |
2 |
7 |
8 |
17 |
|
19 |
3 |
7 |
5 |
15 |
|
20 |
6 |
9 |
5 |
20 |
|
21 |
7 |
6 |
4 |
17 |
|
22 |
4 |
9 |
4 |
17 |
|
23 |
9 |
8 |
4 |
21 |
|
24 |
5 |
6 |
2 |
13 |
|
25 |
9 |
4 |
8 |
21 |
|
26 |
4 |
2 |
2 |
8 |
|
27 |
5 |
7 |
7 |
19 |
|
28 |
8 |
4 |
2 |
14 |
|
29 |
5 |
10 |
9 |
24 |
|
30 |
2 |
6 |
5 |
13 |
|
31 |
4 |
6 |
5 |
15 |
|
32 |
6 |
5 |
3 |
14 |
|
33 |
10 |
8 |
1 |
19 |
|
34 |
5 |
4 |
9 |
18 |
|
35 |
8 |
9 |
3 |
20 |
|
36 |
5 |
8 |
8 |
21 |
|
37 |
4 |
8 |
4 |
16 |
|
38 |
5 |
5 |
2 |
12 |
|
39 |
3 |
7 |
5 |
15 |
|
40 |
0 |
7 |
6 |
13 |
|
41 |
4 |
5 |
3 |
12 |
|
42 |
5 |
3 |
2 |
10 |
|
43 |
1 |
3 |
5 |
9 |
|
44 |
4 |
6 |
4 |
14 |
|
45 |
3 |
1 |
6 |
10 |
|
46 |
2 |
3 |
4 |
9 |
|
47 |
3 |
4 |
4 |
11 |
|
48 |
1 |
3 |
1 |
5 |
|
49 |
1 |
1 |
2 |
4 |
|
50 |
2 |
0 |
0 |
2 |
|
51 |
0 |
1 |
3 |
4 |
|
52 |
0 |
1 |
3 |
4 |
|
53 |
2 |
2 |
0 |
4 |
|
54 |
0 |
0 |
1 |
1 |
|
55 |
0 |
1 |
0 |
1 |
|
56 |
0 |
1 |
0 |
1 |
|
57 |
1 |
1 |
0 |
2 |
|
58 |
0 |
0 |
2 |
2 |
|
59 |
1 |
2 |
1 |
4 |
|
60 |
0 |
0 |
1 |
1 |
|
62 |
0 |
2 |
0 |
2 |
|
64 |
0 |
0 |
1 |
1 |
|
65 |
0 |
1 |
0 |
1 |
|
66 |
0 |
1 |
0 |
1 |
|
70 |
0 |
1 |
0 |
1 |
|
Total |
153 |
198 |
156 |
507 |
Response Q5
Pursuant to the provision of Section 14(1) of the Freedom of Information Act 2000 (the Act) I have decided to refuse your request relating to Q5, as it has been deemed to be a ‘Vexatious Request.’
Section 14(1) – Vexatious requests of the Act provides:
Section 1(1) does not oblige a public authority to comply with a request for information if the request is vexatious.
I have taken cognisance of the Information Commissioners guidance on Vexatious requests which can be found at:
https://ico.org.uk/for-organisations/foi/freedom-of-information-and-environmental-information-regulations/section-14-dealing-with-vexatious-requests/
First and foremost when considering whether to make a request for information ‘Vexatious’ consideration has been given to the ICO Guidance in relation to vexatious requests (section 14) which stipulates what the ICO expects from a public authority when considering section 14(1). Gathering evidence in order to identify a developing pattern of behaviour is an important factor as well as the context and history in which a request is made will often be a major factor in determining whether the request is vexatious. The public authority will need to consider the wider circumstances surrounding the request before making a decision as to whether section 14 (1) applies.
ICO guidance on the subject states:
‘Section 14(1) may be used in a variety of circumstances where a request, or its impact on a public authority, cannot be justified. Whilst public authorities should think carefully before refusing a request as vexatious they should not regard section 14(1) as something which is only to be applied in the most extreme of circumstances.
In cases where the issue is not clear-cut, the key question to ask is whether the request is likely to cause a disproportionate or unjustified level of disruption, irritation or distress. This will usually be a matter of objectively judging the evidence of the impact on the authority and weighing this against any evidence about the purpose and value of the request. The public authority may also take into account the context and history of the request, where this is relevant.’
Accordingly, I have classified this request as vexatious under Section 14(1) by gathering evidence under the following indicators in order to identify whether the request is burdensome.
Burden on the Authority:
FOI legislation is designed to provide opportunities whereby the public can shine a torch on the decision making and workings of a public authority. However, this does not mean that information has to automatically be disclosed. To do so without some consideration would be reckless and likely to breach other relevant legislation, such as the Data Protection Act (DPA)/General Data Protection Regulation (GDPR).
In this particular case, it has been identified that there are a total of 424 records on the Force recording system, which details circumstances of the arrests relating to drink and drug driving cases between January 2025 and September 2025.
Prior to disclosing the requested information, the whole document would require reviewing, page by page, in order to establish whether or not there are any concerns with disclosing the contents detailed on each page. This is due to the fact that some of the information contained within will be sensitive/harmful to disclose to the public and would attract exemptions, such as but not limited to Section 40 (Personal Information), Section 31 (Law Enforcement) and where exemptions apply the information would need to be redacted.
To review all 424 entries, contains information relating to different subject matters, and to redact where necessary would be a time consuming task and it would be a burden on the force to undertake this task. This is due to the fact that the Freedom of Information (FOI) Decision Maker would be required to read through each one individually in order to identify all personal data contained within each record, namely personal information, such as names, vehicles locations that may identify an individual, in order to make the decision on whether exemptions apply, which exemptions apply, and to which part the exemptions apply to. For example, considerations for Section 40 in relation to any names, vehicles locations that may identify an individual, considerations for Section 31 in relation to any policing details, such as tactics or received intelligence, that would compromise law enforcement if disclosed etc. Following this process the FOI Decision Maker would then be required to redact any information from the document deemed as sensitive, and also draft their response detailing any exemptions being applied, ensuring public interest tests and harm tests are carried out where necessary.
It has been estimated that to review and to take into account the necessary considerations under the FOI Act would take a minimum of 5 minutes per page, which would equate to 35.33 hours. To undertake this task would require a Decision Maker within the FOI Unit to be abstracted from normal duties for approximately 4.5 working days in order to provide an FOI compliant response in respect of this matter. This does not take into account the amount of time it would take other police officers/staff outside of the FOI Unit away from their duties, to liaise with the FOI Unit regarding the information relevant to their business area.
As at 19/11/25, there are currently 3 FTE Decision Makers dealing with FOI requests and to abstract one of those Decision Makers from normal duties to undertake this one task would be a considerable burden on the Disclosure Unit, which would significantly undermine the units other obligations in the processing of the FOI requests and other disclosure work. Although there is no doubting the legal motives or responsibilities for requesting the said information, it is the opinion of Dyfed-Powys Police that the effort to meet the request will be oppressive in terms of the strain on time and resources that the authority cannot reasonably be expected to comply.
Additionally in considering the above I also make reference to a previous Decision Notice from the ICO, as outlined by the below link, whereby in similar circumstances the ICO concluded at that time that he accepts that the burden is such that it can be properly categorised as being grossly oppressive and dealing with the request under such circumstances cannot be justified. Accordingly, whilst he considers this case to be finely balanced, the Commissioner finds that section 14(1) has been appropriately applied in this instance.
https://ico.org.uk/media/action-weve-taken/decision-notices/2014/1025456/fs_50539606.pdf
Conclusion and Decision:
In considering the aforementioned facts I am satisfied that this request meets the criteria (as outlined below) pursuant to the provision of Section 14(1) of the Freedom of Information Act 2000 whereby the request is deemed to be ‘vexatious’ as it would pose a substantial burden on the authority.
Section 14(1) of the Act provides:
Section 1(1) does not oblige a public authority to comply with a request for information if the request is vexatious.
Accordingly, I have classified your request as vexatious under Section 14(1) for the reasons as outlined above.
It should be noted that as a result of the systems adopted by Dyfed-Powys Police in relation to the recording of such information that the information released may or may not be accurate.
(This is a response under the Freedom of Information Act 2000 and disclosed on 20/11/2025)
|
Os oes angen y wybodaeth yma arnoch yn Gymraeg, cysylltwch â: If you require this information in Welsh, please contact: |