FOI request detail

Stratford Station Entrance Development

Request ID: FOI-0077-2122
Date published: 11 May 2021

You asked

We are aware of the planning application submitted to the London Legacy Development Corporation (LLDC) by Stratford Garden Development Limited for a multi-use entertainment venue on land to the west of Angel Lane, Stratford (application ref: 19/00097/FUL) (the Sphere Application). We are also aware that the applicant is proposing a new entrance to Stratford station. We request: (a) Copies of all correspondence between Transport for London and LLDC regarding the proposed new entrance to Stratford station; (b) Copies of all correspondence between Transport for London and the applicant (or their appointed agents) regarding the proposed new entrance to Stratford station; (c) Copies of all correspondence between Transport for London and other organisations regarding the proposed new entrance to Stratford station; and (d) Any work carried out to review the impact of the proposed new entrance to Stratford station. This request is limited to communications from 1 January 2021 onwards only.

We answered

Our Ref: FOI-0077-2122 Thank you for your request received on 14 April 2021 asking for information about Stratford Station. Your request has been considered in accordance with the requirements of the Freedom of Information Act and our information access policy. I can confirm that we do hold the information you have requested. However, we are refusing your request under section 14(1) of the Act, which provides an exemption to the disclosure of information where a request is considered to be ‘vexatious’. In reaching this conclusion we have drawn on guidance from the Information Commissioner’s Office (ICO) that can be found on its website here: https://ico.org.uk/media/1198/dealing-with-vexatious-requests.pdf. You will note that this guidance includes the following advice to public authorities: “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 circumstances”; “Sometimes a request may be so patently unreasonable or objectionable that it will obviously be vexatious….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 take into account the context and history of the request, where this is relevant”; “The information Commissioner recognises that dealing with unreasonable requests can place a strain on resources and get in the way of delivering mainstream services or answering legitimate requests.” “Section 14(1) is designed to protect public authorities by allowing them to refuse any request which have the potential to cause a disproportionate or unjustified level of disruption, irriation or distress”. “…the concepts of ‘proportionality’ and ‘justification’ are central to any consideration of whether a request is vexatious”; The guidance includes some specific indicators to help public authorities judge whether or not a case should be considered vexatious. This includes the following: “Burden on the authority: the effort required to meet the request will be so grossly oppressive in terms of the strain on time and resources, that the authority cannot reasonably be expected to comply, no matter how legitimate the subject matter or valid the intentions of the requester”; “Frequent or overlapping requests: the requester submits frequent correspondence about the same issue or sends in new requests before the public authority has had an opportunity to address their earlier enquiries”. “Disproportionate effort: the matter being pursued by the requester is relatively trivial and the authority would have to extend a disproportionate amount of resources in order to meet the request.” The ICO’s guidance states that one of the indicators of a request which may fall under section 14(1) is that it “appears to be part of a completely random approach, lacks any clear focus, or seems to have been solely designed for the purpose of ‘fishing’ for information without any idea of what might be revealed.” The ICO guidance provides the following examples of a ‘fishing expedition’ request which may fall under section 14(1) if it: - Imposes a burden by obliging the authority to sift through a substantial volume of information to isolate and extract the relevant details; - Encompasses information which is only of limited value because of the wide scope of the request; - Creates a burden by requiring the authority to spend a considerable amount of time considering any exemptions and redactions. Our view is that all three of these examples apply in this instance. We consider that providing the requested information would place an unreasonable burden on us as it would be necessary to review all of the requested information in significant detail to ascertain whether an exemption might apply to any of the information contained within the correspondence. Given the volume of information caught by your request, the process of reviewing and redacting the information would be disproportionate to the benefit of providing it. Therefore, due to the wide and unfocused scope of your request, we are refusing it under section 14 (1) of the FOI Act. Our principal duty is to provide an effective transport service for London and we consider that answering this request would represent a disproportionate effort. It would be a significant distraction from our work managing the TfL network, requiring re-allocation of already limited resources and placing an unacceptable burden on a small number of personnel. We do wish to clarify that whilst we consider that your request falls under section 14(1) of the FOI Act, this does not reflect a conclusion that it has been your intention to deliberately place an undue burden on our resources. If you would like to re-submit a more focused, specific request then we will, of course, consider it. For example, part of the burden in reviewing the documents captured by your request is due to the large number and size of the email attachments, which exceed 1,000 pages in length. Much of this will be some unavoidable duplication as well as drafts at various stages of drafting, all of which would need to be manually reviewed for any possible exemptions which may apply. A request that omitted the attachments from the correspondence is less likely to raise concerns about the disproportionate effort required to answer it. You would of course then be able to submit a subsequent request for any attachments of interest. With regard to part (d) of your request, please see our response to the London Legacy Development Corporation (LLDC) of 9 February 2021 which details work we have done to review the impact of the proposed new entrance to Stratford Station: http://planningregister.londonlegacy.co.uk/swift/apas/run/WCHDISPLAYMEDIA.showImage?theSeqNo=169250&theApnkey=8120&theModule=1 http://planningregister.londonlegacy.co.uk/swift/apas/run/WCHDISPLAYMEDIA.showImage?theSeqNo=169251&theApnkey=8120&theModule=1 If you are considering submitting a further FOI request please think carefully about whether the request is essential at this current time, as answering FOI requests will require the use of limited resources and the attention of staff who could be supporting other essential activity. Where requests are made, please note that our response time may be impacted by the current situation. Please see the attached information sheet for details of your right to appeal. Yours sincerely Gemma Jacob Senior FOI Case Officer FOI Case Management Team General Counsel Transport for London [email protected]

Back to top

Want to make a request?

We'll email you the response within 20 working days.


We'll publish the response online without disclosing any personal information.