Government updates Technology Code of Practice 'to better meet CTO needs'

Government CTO Andy Beale wants feedback on draft document by 8 July

The government is aiming to update its Technology Code of Practice in a bid to better meet its departmental CTOs' needs.

In a blog post, government CTO Andy Beale explained that the Government Digital Service (GDS) had introduced the Technology Code of Practice back in 2013 to give CTOs guidance on the way best to design, buy and build technology and digital services to meet user needs.

He said so far it has been used to examine and challenge government spending on technology through the spend controls process and it had given GDS a way to engage with departments and agencies to help them revise and improve their technology plans.

Now, Beale said, the government wants to revamp the code to ensure it stays as up-to-date as possible.

He said that the new document reflected an increased focus on good commercial behaviours.

"We also want to recognise the variety of strategic, commercial and business contexts in which government technology work happens, and enable departments and agencies to deliver great technology that meets their needs," Beale explained.

The draft document urges departments to carefully consider the user, the strategic context and the organisational context when they think about implementing new technology.

It also tells departments to use a technology pipeline, make things open by using open standards and ensure a level playing field for open source software when they choose technology.

The draft document outlines how departments should choose cloud first, including objectively evaluating potential public cloud solutions before considering any other option, and demonstrating that the solution chosen represents the best value for money.

The government has a history of duplicating similar systems across departments, and the document urges services, information, data and software components to be made available to all departments to avoid duplication and prevent redundant investments.

Among other advice on buying technology solutions, a key section urges departments to "enter into sensible contracts". Contracts must not be allowed over £100m in value unless there is an exceptional reason, and where economic, should include a break clause at a maximum of two years that allows the department to terminate the contract should they wish to, with minimal exit costs.

The document reminds CTOs that suppliers must not provide either systems integration, service integration or service management services at the same time as providing a component service within that system, and that contracts will not be automatically extended unless there are extenuating circumstances.

Beale said that government was also looking at reviewing the spend controls process, for which it will be publishing more details in the future.

The government is looking for responses to the draft version of the Technology Code of Practice, with the deadline for feedback on Friday 8 July 2016. Feedback can be left by emailing here, or commenting on the blog post here.