15.08.2013 Views

(Redacted) - Responses 105 to 130 - Law Commission

(Redacted) - Responses 105 to 130 - Law Commission

(Redacted) - Responses 105 to 130 - Law Commission

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Consultation response 106 of <strong>130</strong><br />

10.38 We ask consultees <strong>to</strong> tell us their views about the procedure for enforcing removal. Should<br />

the onus remain on landowners <strong>to</strong> take proceedings? If so, what steps, if any, should be<br />

taken <strong>to</strong> make the procedure more efficient?<br />

Consultation Paper, Part 5, paragraph 5.49.<br />

We appreciate that the current position that the landowner can only serve a notice once the lease,<br />

licence or other arrangement has come <strong>to</strong> an end cannot be retained. Also the fact that the<br />

Landowner has <strong>to</strong> apply for a double order - one <strong>to</strong> enforce removal and one for removing it in<br />

default seems illogical.<br />

We suggest that the Landowner should still be responsible for serving the initial notice but we<br />

also suggest a standardised notice process has <strong>to</strong> be incorporated within a new/revised Code. All<br />

notices whether served by Landowners or Code Opera<strong>to</strong>rs should be standardised. At the<br />

moment only the Counter-Notices are standardised and in our experience it can be difficult <strong>to</strong> tell<br />

what amounts <strong>to</strong> a code notice. Also the notices should be served on any party with an interest or<br />

in occupation/sharing/using the land. This information could be ascertained in a similar way <strong>to</strong><br />

section 40 of the Landlord and Tenant Act 1954.<br />

The current 28 day time limit is not long enough especially if the Code opera<strong>to</strong>r was minded <strong>to</strong><br />

vacate the site. In our experience the average time <strong>to</strong> move a site is two years.<br />

10.39 We ask consultees <strong>to</strong> tell us whether any further financial, or other, provisions are<br />

necessary in connection with periods between the expiry of code rights and the removal of<br />

apparatus.<br />

Consultation Paper, Part 5, paragraph 5.50.<br />

Our view is that landowners/licensors would be reluctant <strong>to</strong> accept payment for this interim period<br />

because of the potential risk of waiving the breach. However once the opera<strong>to</strong>rs has removed the<br />

apparatus the landowner/ licensors should be able <strong>to</strong> claim payment equal <strong>to</strong> the letting value of<br />

the property under the code for this intervening period.<br />

10.40 We provisionally propose that Code Opera<strong>to</strong>rs should be free <strong>to</strong> agree that the security<br />

provisions of a revised code will not apply <strong>to</strong> an agreement, either absolutely or on the<br />

basis that there will be no security if the land is required for development.<br />

Do consultees agree?<br />

Consultation Paper, Part 5, paragraph 5.51.<br />

We do not agree. In our experience if there is an option for the Landowner <strong>to</strong> exclude security of<br />

tenure rights then they will insist upon it. Also with the suggestion that the security of tenure rights<br />

under the Landlord and Tenant Act 1954 will also be excluded then Opera<strong>to</strong>rs will be left with no<br />

security of tenure at the end of the contractual period.<br />

This is unacceptable given that our cus<strong>to</strong>mer contracts extend beyond the term of our land<br />

agreements. Our cus<strong>to</strong>mer contracts often extend beyond the term of our land agreements either<br />

because a new cus<strong>to</strong>mer has come on<strong>to</strong> a site after the initial acquisition or because we have<br />

acquired a new cus<strong>to</strong>mer portfolio as the result of a corporate merger or acquisition.<br />

Page 1370 of 1868

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!