We use cookies on our website to improve our service to you, by continuing you agree to our use of cookies. However you are able to update your settings at any time.

Cookie Settings

We use 2 types of cookie. You can choose which cookies you're happy for us to use. You can set your cookie preferences by clicking ‘cookie settings’ at the bottom of the page.

Cookie Policy

A cookie, also known as an HTTP cookie, web cookie, or browser cookie, is a piece of data stored by a website within your browser on your device, and then subsequently sent back to the same website by the browser. Cookies were designed to be a reliable mechanism for websites to remember things that you had done there in the past, which can include having clicked particular buttons, logging in, or having read pages on that site months or years ago.

We use cookies to store information about how you use the Elmbridge News website, such as the pages you visit.

Strictly Necessary Cookies

These cookies cannot be disabled

These cookies are necessary for the website to function. They always need to be on. They are normally set in response to your interactions on the website e.g. logging in etc.

Cookie Name Maximum retention period
.ASPXANONYMOUS 69 days, 10 hours, and 40 minutes
.DOTNETNUKE session
DotNetNukeAnonymous 2 hours
__RequestVerificationToken session
authentication session
dnn_IsMobile session
language session
LastPageId session
StayInEditMode session
Cookie Name Maximum retention period Purpose
.ASPXANONYMOUS 69 days, 10 hours, and 40 minutes This cookie is used by sites using the .NET technology platform from Microsoft. It enables the site to maintain an anonymous user-id to track unique users within a session without them logging in or otherwise identifying themselves.
.DOTNETNUKE session Issued by DNN, necessary for site functionality, including forms authentication, created when a user logs in.
DotNetNukeAnonymous 2 hours This cookie is set for forms authentication
__RequestVerificationToken session Anti-forgery cookie set by web applications built using ASP.NET MVC technologies. It is designed to stop unauthorised posting of content to a website, known as Cross-Site Request Forgery. It holds no information about the user and is destroyed on closing the browser.
authentication session A DNN forms authentication cookie (created when a user logs in).
dnn_IsMobile session A DNN cookie used by the CMS to determine if the Visitor is browsing from a Mobile Device.
language session A DNN cookie is created called "language" to store the current language - in a monolingual install this is simply the browser default language, but if the site supports multiple languages then this may be different based on the language selected by clicking in the languages skin object.
LastPageId session A DNN cookie used by the CMS to store the TabID of the last visited page.
StayInEditMode session A DNN cookie used by the CMS to determine the UI state across postbacks (whether or not to reload the page with the 'Editing' interface).

Performance Cookies

These cookies allow us to monitor traffic to our website so we can improve the performance and content of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited or how you navigated around our website.

Cookie Name Maximum retention period
_ga 2 years
_gid 24 hours
Cookie Name Maximum retention period Purpose
_ga 2 years Used to distinguish users.
_gid 24 hours Used to distinguish users.

Functional Cookies

These cookies enable the website to provide enhanced functionality and content. They may be set by the website or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

Cookies:

Currently we are not utilizing these types of cookies on our site.

Targeting Cookies

These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.

Cookies:

Currently we are not utilizing these types of cookies on our site.

Skip to main content

Community

Statement on the Jolly Boatman

Statement on the Jolly Boatman

Updated 16 August

Update: 16 August 2022

On the 19 July 2021 the Council refused Planning Permission for the development of the former Jolly Boatman site at Hampton Court Station in East Molesey (opposite Hampton Court Palace). The applicant appealed this decision and following a public inquiry on the 8 July 2022 the Planning Inspector issued his decision that the appeal was allowed and therefore permission has been granted for the development.

There is no right of appeal against an appeal decision but there are other avenues of challenge and today after careful consideration of the Planning Inspector’s reasons for approving the development, and having taken specialist legal advice, the Council has served the Secretary of State with the claim form for a Planning Statutory Review. This request for a review seeks to quash the appeal, on the basis that the Inspector failed to give legally adequate reasons for his disagreement with the advice of Historic England.

The first stage in the process is that the Council is required to obtain permission for the courts to proceed. If the Council is given permission to proceed a hearing will take place for a judge to consider the matter. Any hearing may take many months before it is heard.

Please note that the status of the new Local Plan has no bearing on the outcome of this planning appeal. All applications are determined on their own merits, taking into account policies set out in the National Planning Policy Framework. The adoption of a new Local Plan will not prevent urban sites such as this coming forward, even if they are not identified in the plan as an allocated site.  


Update: 27 July 2022

On the 19 July 2021 the Council refused Planning Permission for the development of the Jolly Boatman site at Hampton Court. The applicant appealed this decision and following a public Inquiry on the 8 July 2022 the Planning Inspector issued his decision that the appeal was allowed and therefore permission has been granted for the development.

After careful consideration of the Planning Inspector’s reasons for approving the development and having taken specialist legal advice, the Council has served the Secretary of State with a letter of claim setting out that it is considering issuing a planning statutory review, which would seek to quash the appeal, on the basis that the Inspector failed to give legally adequate reasons for his disagreement with the advice of Historic England. The Secretary of State has until 4pm on 9 August 2022 to respond. After the response is received the Council will consider the next steps.

Whilst we are seeking representations on our draft Local Plan please remember that the status of the new Local Plan has no bearing on the outcome of this planning appeal. Whilst all applications are determined on their own merits, the principle of the redevelopment and the natural churn of brownfield sites within our towns and villages is set by National Planning Policy. The adoption of a new Local Plan will not prevent urban sites such as this coming forward, even if they are not identified in the plan as an allocated site.

 

 

Date published:
Categories: