“1. What is the current annual cost of the contract that Detroit will replace? The current contract combines both the system and service. Project Detroit will replace the systems element once the current contract expires. A separate procurement will be used to secure a supplier for a new service-based contract. TfL is not billed separately for the system and service elements of the current contract, however, it is estimated that the total annual cost for the system that Project Detroit will replace is approximately£8m . 2. Have attempts been made to negotiate a renewal price of that contract? No attempts been made to negotiate a renewal price of the existing contract. TfL is building a new core technology platform for road user charging to replace the currently outsourced system, so a renewal of the existing contract has not been sought. 3. If they have, what is the quoted price to keep it running? Not applicable (see 2 above). 4. If attempts have not been made, why haven’t they? 5. Assuming a formal decision has been made not to renew or seek to renew the contract in 2026, please provide a copy of the official record of that decision and of the internal documents that recommended not renewing and explaining the rationale for that decision. Attempts have not been made because the current service contracts which support the delivery of Road User Charging (RUC) Operations expire in September 2026 and TfL is preparing to procure replacement contracts for the services which will support RUC operations after they expire. [6.] On Detroit how much of the total resource (in terms of cash (£ and %) and headcount (£, numbers of staff and %) and physical infrastructure (£ and %)) is dedicated to the pay per mile element of the project? No resource, headcount or physical infrastructure on Project Detroit is dedicated to pay-per mile. The scope of the project is to replicate the capability of the existing charging systems which support the business operation of the Congestion Charge, the Low Emission Zone (LEZ), the Ultra Low Emission Zone (ULEZ), Direct Vision Standard and, from 2025, charges for the use of the Silvertown and Blackwall tunnels. TfL teams are not undertaking any work on pay-per- mile road user charging schemes. As has been explained previously, pay-per-mile charging has been ruled out by the Mayor and no such scheme is on the table.”
“If an existing supplier is not asked to provide a quote to continue, which would be unusual, particularly if it has built the relevant infrastructure, there must be a record of the decision and I am looking for the official record of that decision and the rationale for it. I refuse to believe that in taking such a decision, there is no official record nor is there a written recommendation and rationale justifying why it would be better to develop in house than continue with the existing supplier.”
“I can confirm that there is no ‘official record of that decision’ but the matter was considered within a closed (non-public) meeting of the Programmes and Investment Committee and Agenda Item 20 sets out the detailed rationale behind the decision, for their attention and consideration, with The Committee asked to approve the paper at this time. It is this document which we consider is met by the parameters of your request.”
“1. The exempt paper contains three paragraphs that present legal advice on issues of procurement and contract law that relate to the content of the paper. 2. The paper does not contain any details of actual contract negotiations, but it contains information relevant to negotiations that would take place, given that the paper is seeking procurement authority to enter into such negotiations. 3. The Tribunal asked TfL whether a further summary of the exempt paper could be provided, while recognising that this would probably not provide the detail Mr Tarsh was looking for. TfL’s position was that it had already taken a decision, pursuant to Part VA LGA 1972, about what information could be disclosed, and had included as much information as possible in the open paper for the meeting and the minutes of the meeting. In responding to the Request, it continued to rely on that protection, and so any further summary would, in the circumstances of this case, undermine the confidentiality of proceedings for which Part VA LGA provides. 4. The Tribunal questioned TfL on whether it held more information in scope of the request. Ms Edney confirmed that preparatory work had taken place in 2021 (as referred to in paragraph 20 of TfL’s skeleton argument), but that the Exempt Paper contained the recommendation, and the rationale for it, to the body with formal authority to approve Project Detroit, and that it was therefore the only paper within scope of the request. As to the ‘official record’ of the decision, TfL accepted that the relevant part of the minutes of the PIC meeting on2 March 2022 would be within scope of that part of the Request. Those are, however, public, and are contained in the Open Bundle.”
“3.12 Although the project had been progressing well during 2024, it was significantly impacted by the cyber incident in September 2024 which limited system access and therefore development work. Delivery timescales for the BOps system being built in-house had aligned with those for the RUC Re-let project, as critical activities for integration and testing of the system could only take place once the new suppliers were appointed. 3.13 Given the RUC Re-Let prolongation, the estimated cost to deliver the project increased substantially, which, considering TfL’s wider financial context, resulted in a review of delivery options for the BOps system. Details of this review are outlined in the paper on Part 2 of the agenda and concluded with the decision in January 2025 to revert to an outsourced solution for provision of the BOps system.”
“On the basis of my experience of working on papers to be submitted to PIC, I assess that, if Agenda Item 20 had been disclosed in February 2024, then this would have deterred officials in future from being as full, frank and unvarnished in future papers to PIC. If we generally had to disclose exempt papers following information requests in similar circumstances to these, then that effect would have been all the stronger. I think that, realistically, officials would couch the papers in more ‘vanilla’ language. For example, rather than being granular and frank with the PIC about which options were under consideration and what the risks and opportunities were in respect of these options, officials would make more general statements about various options being considered. I also believe that the papers submitted for PIC meetings, and the meetings themselves, would become more performative, and information would be exchanged more by way of informal briefing.”
“54. Commercially sensitive information that goes before the PIC in private proceedings is often closely bound up with information that is sensitive for other, non-commercial reasons. Those drafting papers for PIC therefore rely on the privacy of the proceedings overall in order to give full and frank advice on the range of factors the PIC will need to take into account, and PIC members rely on the privacy of the proceedings overall to discuss that full range of matters. For example, frank discussion of sensitive issues can be required. We might advise that the financial case for a particular option or scheme depended on the level of stakeholder support or buy-in for that scheme, and give advice in relation to that (for example, if the financial case turned on an expectation of future funding or reimbursement from City Hall). Though the public parts of PIC papers are cleared by the Mayor's Office, there is not the same level of review for sensitivity or communications risk in relation to exempt papers, as those papers have to give a full and unvarnished account of the facts to ensure that PIC has the full picture. 55. That means that we cannot realistically say, at any point in time, that the overall sensitivity of the commentary in an exempt paper has dissipated, even if the immediate commercial sensitivity of that information is less than it was at the time the paper was drafted. The risks and considerations discussed in that commentary and advice might not be sensitive at the time that question is asked, but they may then become sensitive. Therefore, I do not think that it would be a significant reassurance, to PIC or those advising PIC, to be told that information in exempt papers was only likely to be disclosed under the information rights legislation if that disclosure would not have an immediate adverse impact on ongoing commercial negotiations. This is one reason why the confidentiality of PIC's confidential proceedings needs to be preserved, and not just the confidentiality of the commercial information discussed in those proceedings so far as it remains commercially sensitive. 56. It should also be noted that the commercial sensitivity of information can wax and wane over time. For example, if comments are made about a particular supplier’s performance, then those might be sensitive when they are made (because the contract is ongoing), less sensitive a year later (because the contract has been performed), but more sensitive a year later than that (because a further contract has by that time been concluded with the same supplier). That is not uncommon at TfL. For those reasons, again, it would not be a significant reassurance to those drafting private PIC papers if they thought that, at some future point in time, TfL’s decision on whether to disclose the paper following an information rights request would have to be based on the commercial sensitivity of the information alone. 57. Another reason that this would not provide adequate reassurance is that commercial sensitivity is somewhat subjective. There is no prescriptive set of rules about what is sensitive and what is not: reasonable people can disagree about this, and we make decisions about what is sensitive based on our commercial instincts, experience of what has been considered sensitive before as well as an understanding of the market and what information might advantage (or disadvantage) a particular actor in that market. Because we are keen to keep as much information in the public papers as possible, in order to facilitate transparency and public scrutiny so far as possible, there is often considerable discussion internally about these issues. That again means that, in practice, it is not going to be precisely foreseeable to the official who is drafting an exempt PIC paper what information might be considered commercially (or otherwise) sensitive to a future official that is considering whether to disclose that exempt PIC paper at a later point in time, in response to an information request or otherwise. The risk that something rightly considered sensitive by the author is wrongly considered nonsensitive by an official later in time is exacerbated by the fact that there is a reasonable degree of churn on project teams. It follows that, the less that officials drafting these papers can rely on the legal protections for private PIC proceedings that exist under legislation, the more they will need to ‘blur out’ the most potentially sensitive details when drafting private PIC papers, reducing the quality of PIC’s decision-making. 58. Ultimately, for all these reasons, it is the confidentiality of the proceedings themselves that enables the PIC to operate effectively in its private proceedings, and not just the confidentiality of specifically commercially sensitive information in the proceedings.”
“Information relating to the financial or business affairs of any particular person (including the authority holding that information).”
“Information in respect of which a claim to legal professional privilege could be maintained in legal proceedings.”
“Business Operation Services (BOps) and Enforcement Operation Service (EOps) are currently provided by Capita, and Detection and Enforcement Infrastructure (D&EI) by Siemens; both contracts expire in September 2026 without any options for extend or renew. TfL Technology and Data (T&D) team are undergoing feasibility work to build an in-house BOps system that could replace part of the operating system (highlighted above). The working assumption is that the people and processes elements of the BOps, the EOps and D&EI contracts will be re-procured. While initial planning indicates that a decision regarding procurement isn’t needed until early in 2023, potential earlier delivery of Silvertown and Blackwall in 2024/25, and a potential Boundary Charge in 2023, means we need a decision in June 2021.” b. Information on Slide 65 of that document which identifies the decisions which need to be made in June 2021, starting with “Re-procurement in 2026 – Do we plan to build the BOps system to take over operation of all existing and planned charging schemes in-house or outsource?” c. Information on Slide 72 of that document which says: “We cannot legally extend or renew the existing contracts, and the working assumption is that the people and processes elements of the BOps, the EOps and D&EI contracts will all be re-procured.”
“59. I acknowledge, of course, that TfL officials would still be duty-bound to give advice to PIC to the best of their ability, even if the information in this case (and any cases involving sufficiently similar circumstances) had to be disclosed. It is not that I think that they would cease to be independent, impartial and conscientious in giving advice to the best of their ability, if disclosure took place in this case and in similar circumstances. However, the characteristics of the information that goes into exempt papers to PIC mean that, in practice, what it would mean to give advice to the best of officials’ ability would change. Consideration of what needs to be kept private in PIC decision-making, in order to promote the public interest and enable PIC to secure value for money, is positively required of TfL officials: that is exactly why they need to think about what to exempt for the purposes of the local government legislation. If they started to become more circumspect in their advice to PIC, then I think that would be consistent with them giving responsible consideration to the risks to TfL arising from wider disclosure of information before the PIC. 60. I should also say that my colleagues and I are already well aware that any information we produce and exchange is subject to the information rights legislation and so it is always possible in principle that it may have to be disclosed, subject to any applicable exemptions or exceptions. We do not labour under the misapprehension that the privacy of our ‘safe spaces’ is absolutely guaranteed, or that it is absolutely guaranteed in perpetuity. However, where particular proceedings have specific legal protections for their confidentiality, that does provide officials with more reassurance about the confidentiality of information forming part of those proceedings. I think it is reasonable for officials to proceed on the basis that, where there is a law providing that certain information is “excluded” from publication, it should generally not be published without sufficiently compelling reasons to override that protection.”
“43. TfL was still in contract negotiations with Capita and Siemens regarding the BOps inhouse and re-let projects and supplier relationships could have been impacted by the release of such commercial information. Ongoing discussions and negotiations with these suppliers at that time included discussions about delivery of TUC, delivery of Project Detroit, the re-let, and negotiations around exits from their current contract in 2026 (which was then expected to be the timescale). There would also have been regular ‘change request’ processes under the contracts, whereby we would ask for a quotation for particular changes to the system or additional works under the contract, they would review our requests and send an impact assessment and a quotation, and we would then negotiate cost in light of that quotation. These change requests would have ranged in value from the hundreds of thousands of pounds to the millions.”