Flooding strategy for Watton a step closer after visit by floods authority

Flooding in Watton, photo by Neal Trafankowski

Flooding in Watton, photo by Neal Trafankowski - Credit: Archant

Residents who were hit badly by this summer's floods are a step closer to making their homes safer after a meeting between town bosses and the floods authority.

Streets around Watton were submerged and houses flooded after heavy rain on June 23, causing an outcry from the public for a solution to the town's problems. The neighbouring village of Saham Toney was also affected.

But after visiting five badly affected areas with members of Norfolk County Council and Anglian Water, Watton Town Council are forging ahead with a flooding strategy.

A report on the meeting from the town council concludes that 'development needs to be looked at carefully and adequate systems must be adopted to take the storage of water. Developers must be pushed to get it right'.

The five sites visited – Watton Green, Canon Close, Jubilee Road, Brandon Road and Saham Road – demonstrated to the flood authority the widespread nature of the problem.


You may also want to watch:


In total 24 people attended the site visits, including members of housing campaign group What Watton Wants.

Following June's heavy rainfall the county council has said it will produce a flood risk assessment, which is expected to be available by the end of the year.

Most Read

In order to help compile this assessment, county council flood manager Graham Brown offered to attend a future Watton Town Council meeting.

The county council also suggested that town councillors compile evidence of flood risks to present to Breckland Council to inform its developing Local Plan.

Become a Supporter

This newspaper has been a central part of community life for many years. Our industry faces testing times, which is why we're asking for your support. Every contribution will help us continue to produce local journalism that makes a measurable difference to our community.

Become a Supporter
Comments powered by Disqus