Out-Law / Your Daily Need-To-Know

Chesterfield Borough Council has published its community infrastructure levy (CIL) preliminary draft charging schedule (PDCS)  (16-page / 1.33MB PDF) for a public consultation starting next week.

The Council has proposed to divide the Borough into four different residential charging zones, with rates ranging from £0 per square metre to £80 per sq m.

It has proposed that a nil rate zone is created in the Staveley Corridor, which comprises the areas of Brimington North to the north of the canal, Barrow Hill and New Whittington south of the rail line.

A 'low' zone with a rate of £20 per sq m would be created to cover Brimington North to the south of the canal, Brimington South, Lowgates and Woodthorpe, Middlecroft and Poolsbrook and St Helens if the rates are eventually approved.

A 'medium' zone with a rate of £50 per sq m will cover Barrow Hill and New Whittington north of the rail line, Old Whittington, Dunston, Moor, Loundsley Green, Brockwell, Holmebrook, Rother, Hasland, St Leonards, Hollingwood and Inkersall and a 'high' zone with a rate of £80 per sq m will cover Walton, West and Linacre under the proposals.

For retail developments falling within use classes A1 to A5, the Council has proposed to set a Borough-wide rate of £80 per sq m. A nil rate levy is proposed to apply to all other non-residential developments across the Borough.

The Council said that its viability evidence had indicated that most categories of commercial development are not viable in the current market circumstances, with the exception of food supermarket retail and general retail.

The Council said that, following new regulations requiring a proportion of CIL receipts to be passed to town or parish councils, it would work closely with Brimington Parish Council and Staveley Town Council to "ensure this element of CIL is managed and delivered effectively".

The Council will launch the consultation on 3 June and it will be open for comments until 15 July. It said it expects to adopt CIL in 2014.

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.