Cambridgeshire residents invited to shape rural community future
Summarised from 2 outlets · Updated 18 Nov, 14:09 · Archive
Cambridgeshire and Peterborough residents are being asked to share views on rural communities through an anonymous survey.
Residents across Cambridgeshire and Peterborough are being asked to share their views on the future of rural communities through the Future Rural Cambridgeshire Residents' Survey. The anonymous survey takes about 15 minutes to complete and covers topics including housing developments, population growth, vital services and treasured community assets. Feedback from the survey will inform plans for the next five years.
Dr Wray Irwin of Wray Irwin Associates said: 'With new houses and roads transforming familiar places and the government's drive for local devolution, there are many questions about what might be lost. This is the chance for residents to speak up and have a real opportunity to shape their neighbourhoods.'
In addition to the survey, residents can attend workshops across the region throughout November and December. These include sessions at Newton Village Hall on 21 November, Needingworth Village Hall on 25 November, West Wickham Village Hall on 28 November, Abbotsley Village Hall on 1 December, Cottenham Community Centre on 3 December, and Little Downham Village Hall on 10 December.
How it is being reported
- Cambridgeshire residents urged to shape the future of rural communitiesResidents are being urged to help shape the future of rural communities across Cambridgeshire and Peterborough.Cambs Times · 18 Nov, 13:32
- Cambridgeshire residents urged to shape the future of rural communitiesResidents are being urged to help shape the future of rural communities across Cambridgeshire and Peterborough.Ely Standard · 18 Nov, 13:32
In this story: Cambridgeshire · Peterborough · Cambridgeshire ACRE · Wray Irwin Associates
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)