'Shamed' councils hit out at Y2K slur


'Shamed' councils hit out at Y2K slur

Caroline Davis

Caroline Davis

Ten councils that were "named and shamed" over Y2K preparations have hit out at the Audit Commission and the Government's Action 2000 taskforce after experiencing a completely trouble-free millennium changeover.

Six English and four Scottish councils were given a red light by Action 2000 last July and were named, while red lighted private sector organisations were allowed to remain anonymous.

Nigel Nicholson, head of IT at Rugby Borough Council, told Computer Weekly that being "named and shamed" was a kick in the teeth for his staff. "The Audit Commission asked us what we were doing," he said, "and we told them honestly. The next thing we knew was that we were being singled out for criticism. Despite the Audit Com-mission we stuck to our plan and had no major problems."

Angus McArthur, IT manager at Western Isles Council, reported no Y2K problems "of any significance" and expressed anger at the red coding.

John Serle, of the local government IT managers' body Socitm, said, "Naming and shaming was an unhelpful distraction. The Government wanted to make sure it could point the finger at someone if things went wrong."

Criticised councils


  • Charnwood Borough Council (Leicestershire)
  • Hart District Council (Hampshire)
  • East Northamptonshire District Council
  • Restormel District Council (Cornwall)
  • Rugby Borough Council (Northamptonshire)
  • Warwick District Council


  • Argyll & Bute Council
  • East Dunbartonshire Council
  • Orkney Council
  • Western Isles Council

Email Alerts

Register now to receive ComputerWeekly.com IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

COMMENTS powered by Disqus  //  Commenting policy