12.07.2015 Views

Developer Contributions SPD - Huntingdonshire District Council

Developer Contributions SPD - Huntingdonshire District Council

Developer Contributions SPD - Huntingdonshire District Council

SHOW MORE
SHOW LESS
  • No tags were found...

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

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

The <strong>District</strong> <strong>Council</strong>’s Approach to <strong>Developer</strong> <strong>Contributions</strong> 4<strong>Huntingdonshire</strong> LDF | <strong>Developer</strong> <strong>Contributions</strong> Supplementary Planning DocumentTable 6 Steps in the <strong>Developer</strong> <strong>Contributions</strong> ProcessSteps12345Planning ObligationsAs part of the documentation submitted with theplanning application, the developer provides draftPlanning Obligations Heads of Terms form, usingthe template that will be available on the <strong>District</strong><strong>Council</strong>’s website. Planning applications may notbe validated if the developer does not provide a draftPlanning Obligations Heads of Terms form.After the planning application is validated and thedraft Heads of Terms are agreed in principle, the<strong>District</strong> <strong>Council</strong>’s Legal Services team are instructedto prepare a draft Section 106 Agreement once theLocal Planning Authority is minded to approve theapplication.Once the developer and the <strong>District</strong> <strong>Council</strong> haveagreed the draft Section 106 Agreement, the S106Agreement has been signed and sealed andplanning permission has been granted, details willbe registered by the <strong>District</strong> <strong>Council</strong>’s Land Chargessection.The agreed Planning Obligations and their relevanttriggers are entered on the <strong>Council</strong>’s PlanningObligations database. Implementation of agreedprojects is monitored through to completion.On final payment of the outstanding S106contributions, the <strong>District</strong> <strong>Council</strong>’s Land Chargessection will remove the charge from the LandCharges Register.Community Infrastructure LevyThe developer provides the appropriatefloorspace details with the application,where available. An Assumption of LiabilityNotice should be completed and includedwith the paperwork.Once full details of the planning proposalare known, the <strong>District</strong> <strong>Council</strong> willdetermine the levy based on the adoptedcharges.If planning permission is granted, a LiabilityNotice will be issued and the levy rate willbe registered by the <strong>District</strong> <strong>Council</strong>’s LandCharges section.Once verification of commencement datehas been received, a Demand Notice/s willbe issued to the person/s liable to pay theCIL.On final payment of the outstanding CILcharge, the <strong>District</strong> <strong>Council</strong>’s Land Chargessection will remove the charge from the landcharges register.NB: the above table is for indicative purposes only.Legal Information4.13 <strong>Developer</strong>s will need to produce satisfactory proof of title for their particular site and all persons with aninterest in the development site including mortgagees, tenants and option holders must be party to theagreement.Local Land Charges4.14 Planning obligations have to be registered as local land charges. Applicants will therefore need to producetitle to the site and third parties, such as mortgagees, may have to be party to agreements.Inflation4.15 All <strong>Developer</strong> <strong>Contributions</strong> payments will be index linked to inflation. Any increase in the national All-inTender Price Index published from time to time by the Building Cost Information Service of the RoyalInstitution of Chartered Surveyor(s) will result in an equivalent increase in the value of financial contributionsand the figure for a given year is the figure for 1st November of the preceding year, as is the case with13

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

Saved successfully!

Ooh no, something went wrong!