General Regulatory Chamber
Information Rights
Considered on the papers on 9 May 2023 and 19 July 2023. |
||
B e f o r e :
TRIBUNAL MEMBER Rosalind Tatam
TRIBUNAL MEMBER Naomi Matthews
____________________
Jonathan Hayes |
Appellant |
|
- and - |
||
The Information Commissioner (1) The Chief Constable of Leicestershire Police (2) |
Respondents |
____________________
____________________
Crown Copyright ©
Decision: The appeal is Allowed
Substituted Decision Notice: A substituted decision notice is made as described in paragraph 35 below.
MODE OF HEARING
BACKGROUND
…the Professional Standards Department of the Leicestershire Police Force has said between the 12th of October 2018 and the 23rd of October 2018 "faults causing blank emails to be received and the wrong date stamp to be applied were identified within the Force's 'Openscape' system", see the attached letter…and I believe these to be associated with the contact Us email contactus2@leicestershire.pnn.police.uk. In light of this and in accordance with the Freedom of Information 2000 [sic], please provide me with the total number of emails this happened to, the number of senders of emails this happened to and how many of these senders were external to the Force, the total number of emails received by the Force within the above period and then let me know whether this sort of fault has ever occurred before or after the period and if they have let me know the number of times it has occurred and the number of senders it happened to.
3. It can be seen that Mr Hayes' request for information encompassed a number of sets of information:
(a) the "total number of emails this happened to" during the period of the request (i.e. the numbers received as blank with an incorrect date stamp);
(b) the "number of senders of emails this happened to" during the period of the request, which should have been the same as the total number of emails (unless at least one sender sent two or more emails during the period to which the request related);
(c) how many of the "senders of emails this happened to" were external to Leicestershire Police Force;
(d) the total number of emails received by the Force during the period of the request;
(e) whether this "sort of fault" had occurred before 12 October 2018 or after 23 October 2018;
(f) if so, how many times and 'the number of senders it happened to'.
6. Mr Hayes complained to the Information Commissioner and it seems that this prompted the Police Force to conduct an internal review of their response to Mr Hayes' request. The outcome of that review was communicated to Mr Hayes in writing on 17 May 2019. The Force relied on section 12 of FOIA, namely that the costs of complying with the request would exceed FOIA's cost limit. Seeking to identify the number of emails affected would be "incredibly time consuming" and impractical. The Force informed Mr Hayes that there was no further information that they could provide "in relation to your request".
7. The Information Commissioner considered Mr Hayes' complaint against the Force's response to his request for information. The Police Force's submissions to the Commissioner included the following assertions:
(a) the Force sent and received over 100,000 emails every day so that more than one million emails fell within the period of Mr Hayes' request;
(b) since it was impossible to ascertain which senders used Microsoft client products without manually reviewing each email, more than one million emails would need to be checked in order to comply with Mr Hayes' request.
8. The Commissioner's decision notice shows that she understood the Police Force's case to be that, in order to comply with Mr Hayes' request, it would be necessary for the Force to 'manually review' over "one million records". Such an exercise would exceed the appropriate cost limit under section 12 of FOIA. No sampling exercise was required "given the volume of records and the investigations and assurances of Leicestershire Police which were based on advice from its IT specialists".
9. The Commissioner also considered whether the Police Force had complied with its duty to provide advice and assistance to Mr Hayes under section 16(1) of FOIA. The Force appeared not to have considered this, which was itself a breach of section 16(1). However, given the Police Force's representations, the Commissioner's decision notice "did not order any steps" to rectify this breach. The decision notice indicates that the Commissioner believed compliance with Mr Hayes' request would have involved police staff viewing some million emails. On that basis, the Commissioner had no doubt that the appropriate costs limit would be breached no matter what advice and assistance were given to Mr Hayes. Mr Hayes appealed to the First-tier Tribunal.
55. In my judgement, there were two possible readings of Mr Hayes' request. Mr Hayes either sought information restricted to the 'contactus' email address referred to in his request (narrow reading) or he sought information related to all emails received by the Force during the period of his request, whether from internal or external senders (wider reading). In my judgment, both readings were tenable. The former due to the way in which Mr Hayes introduced his request that is by describing a particular 'contactus' email address, and the latter due to that part of the request which referred to senders external to the Police Force. I shall not express any view as to which reading I prefer since this case is to be remitted to the Tribunal.
56. Under the narrow reading of Mr Hayes' request, that is limited to the 'contactus'
email address, it was surely implausible that over a million items of data fell within the scope of Mr Hayes' request. It could not reasonably be supposed that Leicestershire Police Force would receive some 100,000 emails daily at an email address that must have been created as a means for members of the public to contact the Police Force. Had the Tribunal approached the strike-out application on that narrow reading of Mr Hayes' request, there must have been a significant chance that it would not have concluded that the appeal had a realistic prospect of success.
57. In my judgment the Tribunal overlooked a relevant consideration namely that, were the narrower reading of Mr Hayes' request correct, the Police Force's claim to
have received 100,000 emails daily could not have been plausible. By proceeding on the basis that the wider reading applied, as the Tribunal seems to have done, the Tribunal failed to address the point that, if the narrower reading applied, the Police Force's reported receipt of 100,000 emails daily could not have been correct. An alternative analysis is that the Tribunal failed to give adequate reasons for approaching Mr Hayes' appeal on the basis that the wider reading of his request for information was correct. Either way, the Tribunal's decision involved an error on a point of law. I should, however, add that I very much doubt the Tribunal would have struck out Mr Hayes' appeal if it had been informed that, if Mr Hayes' request were limited to the 'contactus' email address, it could have been complied with without exceeding the section 12 FOIA costs limit. The Police Force's failure to inform the Commissioner that, on the narrower reading, the request would not exceed the section 12 cost limit almost certainly led the Tribunal to make an error that would not otherwise have been made.
CONINUATION OF THE APPEAL IN THE FIRST TIER TRIBUNAL (FTT)
The appeal will decide the following issues:
a. Did s.12(1) of FOIA entitle Leicestershire Police to refuse to comply with the request, on either:
i. the wider interpretation of the request considered in the Decision Notice of 24 September 2019; or, applying s.16(1)
ii. the narrower interpretation set out in the decision of Upper Tribunal Judge Mitchell of 23 March 2022?
b. If not, can Leicestershire Police now provide such information as FOIA required it to disclose?
c. If the answer to (b) is no, why?
d. Should the appeal be allowed and, if so, what substituted decision notice should be made?
…in light of the developments during the course of the Upper Tribunal proceedings, the Commissioner would now consent to a substituted Decision Notice that should have required Leicestershire Police to seek clarification of the request pursuant to s.1(3) FOIA, and provide the following reasonable advice and assistance to the Appellant:
a) Explain to the Appellant that the email issue had only affected emails in relation to the "contact us" email address
b) Confirm that a narrowed request focusing on the 'contact us' email address could have been responded to (at the time of the request - see below comments on whether the information is still held).
…is prepared to concede that, given the ambiguity of the phrasing of the request, it would have been prudent to make a request for clarification and/or advise that the fault was only known to manifest in the 'contactus' mailbox and that, had it been, it is likely that the limited ambit of the request could have been identified and, had that occurred before the 13th February 2019 when the issue ceased to manifest (and not the 23rd October 2018, as erroneously stated in previous submissions), it would theoretically have been possible to comply with the request
1. The Decision Notice is substituted to have recorded that the Second Respondent should have initially sought clarification of the Appellants request pursuant to s.1(3) FOIA, and provided reasonable advice and assistance under s.16 FOIA explaining that that the email issue had only affected emails in relation to the "contact us" email address.
2. However no steps are now required as the Second Respondent has confirmed it is not able to identify the affected emails given that the error which caused the issue has been fixed.
…the Commissioner notes the reference made by Leicestershire Police in its submissions to the Upper Tribunal that it no longer holds the relevant data from 2018. The Commissioner invites Leicestershire Police to explicitly confirm whether the information sought in the request for information, on a narrow interpretation, is still held.
The Second Respondent [the Leicestershire Police], in order to release capacity on its Storage Area Network, in October 2021 deleted email server backups prior to September 2021 and e-mails related to the 'contactus' e-mail address prior to March 2021;
5.4 By e-mail to the Second Respondent dated the 24th August 2022, the Appellant suggested that it would be possible to identify affected e-mails by searching for e-mails which had been sent to the senders of those e-mails notifying them that no content was showing.
5.5 The Second Respondent concedes that, post 13th February 2019, it may have been possible to identify affected e-mails by searching for e-mails sent to the senders of e-mails which appeared blank, but that was not possible by the 24th August 2022.
FURTHER SUBMISSIONS AND EVIDENCE
If clarification had been sought and a narrower interpretation had been applied before the 13th February 2019, manual searches of the mailbox in question may have allowed us to comply with the request within the FOI cost limit, thus negating our reliance on a Section 12 exemption.
With regards to email retention from any mailbox received in our Force we previously utilised a system called CommVault which stored and logged all deleted emails. However, during the Beck and Janner Public Inquiries it was identified that this system was not fit for purpose and it was decommissioned. This occurred many months prior to Mr Hayes FOI request being received.
Without the CommVault system, the Force relies on Microsoft Exchange for the storage of e-mail and our Force retention policy for emails has been explained above. Our current Force processes ensure even where a user intentionally deletes an email, it will be logged and stored on our wider Force 'back-up' dataset.
The main purpose of these back-ups is part of our Microsoft Exchange Disaster recovery process and is about restoring the server rather than an individual mailbox.
The back-ups for the emails referenced in Mr Hayes FOI request (October 2018) were stored and held in Force until October 2021. In October 2021 the Force was upgrading its network to a more reliable hybrid Cloud environment, as opposed to the outdated 'on-premise' network that was originally in place. This on-premise network was running low on storage capacity that affected the day to day running of policing operations and critical police infrastructure. Examples of issues being experienced at the time include, but are not limited to:
- Slow performance of operational databases, including system crashes that affected day to day policing operations
- Servers going offline or acting irregular causing time and expense to investigate and resolve the issues.
- Storage capacity being reached in critical business areas reducing the speed of operations but also the amount of new data that could be stored.
Our I.T Department recently estimated that to extend our on-premise infrastructure to meet the needs of the Force and maintain good stability and performance would cost approximately 3.2 million pounds, whereas a hybrid environment would cost less than half of this.
The network issues being experienced at the time of the deletion in October 2021 subsequently became overseen by a Gold Group chaired by a Ch Supt and it currently meets monthly to track and monitor the situation, such was the scale of the issue at the time.
Due to the urgent nature of the issue, the decision to delete data which was considered non-critical, such as general e-mail correspondence, was taken without reference to any ongoing proceedings before the Upper or First Tier Tribunal.
The Second Respondent now manages the process of data management through the agency of a Gold Command Group chaired by a senior officer, to ensure that proper measures are in place to ensure that data related to, for example, legal proceedings is appropriately identified and preserved.
In the circumstances, the Second Respondent concedes that any revised Decision Notice should reflect the fact that relevant data was deleted while proceedings were still extant.
You should be cautious about deleting any information that is subject to an information request as you may be legally obliged to communicate that information to the requestor.
You should preserve any information you identify as falling within the scope of an information request to prevent its deletion or amendment. The ICO recognises this is not always possible. If you fail to do so, you will leave yourself open to accusations that you have committed a criminal offence.
The exact information you need to provide may depend on whether a request has been submitted under FOIA or the EIR.
If you are following good records management practices, you should have a disposal schedule. It should identify and describe the records which you can dispose of in accordance with a defined timetable. Having a defined, consistently followed, policy is the best way to avoid committing a criminal offence.
DISCUSSION
1. The Decision Notice is substituted to have recorded that the Second Respondent should have initially sought clarification of the Appellant's request pursuant to s.1(3) FOIA, and provided reasonable advice and assistance under s.16 FOIA explaining that that the email issue had only affected emails in relation to the "contact us" email address.
2. However no steps are now required as the Second Respondent has confirmed it is not able to identify the affected emails as they were deleted in October 2021 at a time when the Second Respondent had been made a party to an appeal to the Upper Tribunal (for which permission to appeal had been granted) which related to the information requested.
Recorder Stephen Cragg KC
Sitting as a Judge of the First-tier Tribunal
Date: 24 July 2023
Date Promulgated: 28 July 2023
Note 1 https://ico.org.uk/for-organisations/foi-eir-and-access-to-information/freedom-of-information-and-environmental-information-regulations/retention-and-destruction-of-information/
[Back]