AECOM report regarding the brighton i360

Anonymous User (Account suspended) made this Freedom of Information request to Brighton and Hove City Council

This request has been closed to new correspondence. Contact us if you think it should be reopened.

The request was refused by Brighton and Hove City Council.

Anonymous User (Account suspended)

I request sight of the in-depth AECOM report which I understand details the proposed brighton i360 project, its financial justification and the risk analysis. I understand this report forms the basis of the developer's/operator's decision to move forward with the project. I also understand this report underpins brighton and hove council's decision to borrow from the PWLB and lend on to the developer operator in order to allow the project to proceed.

I am interested to read this report because brighton and hove council are entering into a loan agreement with the PWLB which they must repay and which, should the brighton i360 fail as a business, the council will, nevertheless, have to honour. in a situation where the brighton i360 fails as a business, the developer/operator will not be in a position to repay the monies brighton and hove council has lent it, leaving the council in a position where it is unable to repay the PWLB loan without recourse to local taxpayers.

as a local taxpayer I therefore have a financial interest in the background information (the AECOM report) which has led brighton and hove council to borrow a large sum of money for this project.

Warning: This message has not yet been sent for an unknown reason.

Brighton and Hove City Council

“The full report is likely to become disclosable once the attraction is operational but in the meantime it remains confidential beyond the contents of the redacted report which was appended to the open committee report. (Exempt under S.22, intended for future publication) ”

WhatDoTheyKnow left an annotation ()

This request was made by an anonymous user through mySociety's now defunct FOI Register software ( The integration has now been removed. The external URL for the request was