Sign pointing in wrong direction
Reported via iOS in the Road sign damage category by Nigel Shoosmith at 14:33, Sat 16 March 2019
Sent to Bath and North East Somerset Council 2 minutes later. Council ref: 1574104.
Sign should be pointing down the Fosseway path.
Thank you for your report, it will be reviewed by the appropriate team.
Posted by Bath and North East Somerset Council at 14:35, Sat 16 March 2019
Three weeks from original report and the sign is still pointing in the wrong direction.
Posted anonymously at 17:20, Sat 6 April 2019
Still open, via questionnaire, 17:09, Sat 13 April 2019
And another month passes and nothing done. Come on B&NES, it's a five minute job. Would you like me to do it for you? No charge.
Posted by Nigel Shoosmith at 14:14, Wed 8 May 2019
Still open, via questionnaire, 17:52, Sat 11 May 2019
Same as last month. Nothing done. Reluctant to do the job myself because it'll probably confuse the council crew who would just point it back the wrong way again.
Posted by Nigel Shoosmith at 18:23, Sat 8 June 2019
Still open, via questionnaire
Questionnaire filled in by problem reporter
State changed to: Fixed
Posted by Nigel Shoosmith at 13:55, Sun 7 July 2019
We have looked into this issue and no action will be taken. We will continue to monitor this and take future action if required.
The report is now closed, further comments may not be monitored.
State changed to: No further action
Posted by Bath and North East Somerset Council at 13:21, Tue 13 August 2019
What do you mean "no action"? You've done the job and the sign's now pointing in the right direction. Oh, and another thing, the bloke who fixed the sign phoned me up to ask which way the sign is meant to be pointing, because he didn't know where the Five Arches Greenway is. Well, it's Bonkers and No Evidence of Sense Council. Can't expect any different, really, I suppose. Anyway, thanks to the bloke who fixed the sign and having the initiative to phone to confirm its correct position. Top work.
Posted by Nigel Shoosmith at 17:46, Tue 13 August 2019
This report is now closed to updates. You can make a new report in the same location.