Planning obligations are legal agreements made between the borough council and developers. They are also known as Section 106 agreements.
They can be applied when we grant planning permission and often include obligations to offset the impacts of a proposed development. This requires the developer to pay for things such as providing community infrastructure and affordable housing.
Most agreements are site-specific and relate to the policies contained within our adopted development plan, in accordance with the tests set out in the National Planning Policy Framework 2019 and the Community Infrastructure Levy (CIL) Regulation 2010.
Our planning obligations protocol provides best practice guidance on managing Section 106 planning obligations. We also publish an infrastructure funding statement, which sets out the types of infrastructure and projects we intend to fund through Section 106 income over the next reporting period.
Fees and charges
S106 monitoring fees:
The charge of £460 per obligation enable ongoing monitoring and reporting of S106 agreements and planning obligations. The charges are reviewed on a regular basis and updated as part of our S106 protocol.
S106 compliance requests:
A charge of £175 for compliance requests with an additional fee of £145 should a site visit be required.
- S106 fees were agreed at the meeting of the Cabinet 10 December 2024
Biodiversity Net Gain (BNG) monitoring fees:
There is a requirement to monitor the BNG offset which requires additional resources, the below monitoring fees were reviewed and agreed at Full Council 9th April 2024 and will be reviewed on a regular basis.
| Development site | Monitoring fee cost per project |
|---|---|
| Small/medium sites (up to10 units or 0.5ha) | £6,966 |
| Large sites (10+ units or 0.5ha+) | £13,819 |
Developer agreements
These obligations are normally shown against the relevant planning application. If you cannot find a specific legal agreement, email us at planning.obligations@tmbc.gov.uk with details.
Developer contributions data
Current reporting year
Previous reporting years
22/23
- developer_agreement_20230913.csv
- developer-agreement-contribution_20230913.csv
- developer-agreement-transaction_20230921.csv
21/22
- developer-agreement_20221201.csv
- developer-agreement-contribution_20221201.csv
- developer-agreement-transaction_20221201.csv
20/21
- developer-agreement_20211201.csv
- developer-agreement-contribution_20211201.csv
- developer-agreement-transaction_20211201.csv
19/20
