15.08.2013 Views

Termination of Tenancies for Tenant Default - Law Commission

Termination of Tenancies for Tenant Default - Law Commission

Termination of Tenancies for Tenant Default - Law Commission

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Assignment<br />

3.51 Most tenancies contain covenants prohibiting or restricting the tenant’s right to<br />

assign the tenancy. Such covenants may apply to assignments <strong>of</strong> the whole or<br />

part <strong>of</strong> the demised premises. The usual <strong>for</strong>m is that assignment without the<br />

landlord’s consent is prohibited. Statute has intervened to provide that where a<br />

covenant is so qualified, consent is not to be unreasonably withheld. 43<br />

3.52 An assignment in breach <strong>of</strong> covenant is unlawful but is nevertheless effective to<br />

transfer the tenancy to the assignee. A landlord may there<strong>for</strong>e be left with a new<br />

tenant who is not <strong>of</strong> his or her choosing. Under current law, an unlawful<br />

assignment may be a ground to <strong>for</strong>feit the tenancy (provided there is an<br />

appropriately worded <strong>for</strong>feiture clause).<br />

3.53 Under the statutory termination scheme, an assignment in breach <strong>of</strong> covenant will<br />

constitute tenant default (unless the covenant is excepted). However, strictly<br />

speaking, the breach was committed by the outgoing tenant who no longer holds<br />

the tenancy and not by the incoming tenant (the unlawful assignee) who was not<br />

subject to the covenant at the point at which it was broken. A landlord may only<br />

terminate a tenancy on the ground <strong>of</strong> a tenant default by the tenant and in these<br />

circumstances the current tenant has not committed a tenant default simply by<br />

accepting an unlawful assignment. 44<br />

3.54 Clearly this is unsatisfactory and capable <strong>of</strong> causing serious injustice to landlords.<br />

It could enable tenants to arrange sham assignments so as to avoid the<br />

consequences <strong>of</strong> any other tenant default that they might have committed.<br />

The CP’s provisional proposals<br />

3.55 The risk <strong>of</strong> assignment to avoid the scheme was recognised in the First Report<br />

and the CP. The CP provisionally proposed that a termination order should be<br />

made in a number <strong>of</strong> “Cases”. Case 2 was where the court was satisfied that a<br />

tenant had assigned “in order to <strong>for</strong>estall” the making <strong>of</strong> a termination order. Case<br />

3 was where the tenant default complained <strong>of</strong> was an unlawful assignment and<br />

no other order the court could make would be adequate or satisfactory.<br />

Consultation<br />

3.56 The CP’s proposals received a great deal <strong>of</strong> comment, much <strong>of</strong> it critical.<br />

Re<strong>for</strong>m recommendations<br />

3.57 As we explain in Part 5, we now intend to recommend a modified approach to the<br />

orders that the court may make under the scheme. We have moved away from<br />

reliance on pro<strong>of</strong> <strong>of</strong> specific “Cases”. We have concluded that the problems<br />

concerning unlawful assignments, which we previously sought to address by<br />

means <strong>of</strong> Cases 2 and 3, are best dealt with by creating an exception to the<br />

general rule that a tenant can only be liable <strong>for</strong> tenant default that took place<br />

43 Landlord and <strong>Tenant</strong> Act 1927, s 19.<br />

44 They may, <strong>of</strong> course, subsequently breach other covenants that bind them as the new<br />

tenant, entitling the landlord to take action against them under the scheme <strong>for</strong> those tenant<br />

defaults as well as the assignment.<br />

40

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

Saved successfully!

Ooh no, something went wrong!