Lambeth adopts CIL charging schedule

Out-Law News | 07 Aug 2014 | 3:35 pm | 1 min. read

Lambeth Council will implement community infrastructure levy (CIL) in its area from 1 October following adoption of its charging schedule in July.

Under the adopted charging schedule, the borough will be split into three charging zones for residential developments. Developments in 'zone A', which covers Waterloo and Vauxhall, will be subject to a rate of £265 per square metre. In 'zone B', which includes Kennington, Oval and Clapham, a rate of £150 per sq m will apply and in 'zone C', encompassing Streatham, West Norwood, Streatham Hill, Tulse Hill, Brixton and Herne Hill, the rate will be £50 per sq m.

Hotel and office developments will be charged rates of £100 per sq m and £125 per sq m, respectively, in 'zone A', with a nil rate levy applied in the rest of the borough. The Council initially proposed rates of £250 per sq m for hotel developments in 'zone A' and £100 per sq m in the rest of the borough but the examining planning inspector recommended reduced rates based on representations on construction costs from hotel company Travelodge.

A borough-wide rate of £215 per sq m will apply to student accommodation. This is a reduction from the rate of £360 per sq m proposed by the Council, after the examining inspector accepted representations about additional costs incurred by student accommodation providers in transferring schemes from their construction arms to their operational arms.

Retail warehouse, supermarket and superstore developments will attract a borough-wide rate of £115 per sq m and all other uses will attract a nil rate levy.

The draft charging schedule was recommended for adoption by an examiner in May following consultation in July and August 2013.

In addition to CIL charged by the Council, any developments in the borough will also be subject to mayoral CIL. The mayoral CIL charge in Lambeth is £35 per sq m on all uses except for health and education purposes, which are exempt from mayoral CIL.

We are processing your request. \n Thank you for your patience. An error occurred. This could be due to inactivity on the page - please try again.