The real reason NHS Risk Register is a State secret?

By Tony Collins

Yesterday  (15 May 2012) the Information Commissioner Christopher Graham issued a finely-crafted report to Parliament on his concerns about the Government’s use of a ministerial veto to stop publication of the Transition Risk Register relating to health service reforms.

Graham’s concern is that the veto represents a new and worrying approach to Freedom of Information.

Graham cannot do anything about the veto but he can warn MPs when he feels the Government has gone too far. This he has done in his report which says that the previous three occasions on which the ministerial veto has been exercised related to the disclosure of Cabinet material under FOIA. Now the Government has applied the veto to information held by the Department of Health.

Says yesterday’s report: “ The Commissioner would wish to record his concern that the exercise of the veto in this case extends its use into other areas of the policy process. It represents a departure from the position adopted in the Statement of Policy and therefore marks a significant step in the Government’s approach to freedom of information.”

The Government’s decision to ban publication of the health service risk register is particularly relevant to IT-related projects. This is because the government uses exactly the same arguments to ban contemporaneous publication of Gateway reviews and other independent assessments of IT-related projects and programmes.

Risk registers and Gateway reviews of IT-enabled change projects are similar. They are designed to identify all the main risks associated with the project or programme and have a red/amber/green system of rating the risks.

The Government’s argues that risk registers (and Gateway reviews) are researched and written in a “safe space” that allows civil servants to give advice and recommendations in a frank way. This candour would be compromised if the civil servants thought their advice would be published, says the Government.

In issuing a veto on the health risk register Andrew Lansley, the Health Secretary said, in essence, that he could not trust civil servants to be entirely honest if they knew their reports would be made public.

Said Lansley:  “If risk registers are routinely or regularly disclosed at highly sensitive times in relation to highly sensitive issues, or there is legitimate concern that they could be, it is highly likely that the form and content will change: to make the content more anodyne; to strip out controversial issues or downplay them; to include argument as to why risks might be worth taking; to water down the RAG [red,amber, green] system.

“They would be drafted as public facing documents designed to manage the public perception of risk; not as frank internal working tools. These consequences (many of them insidious) would be to the detriment of good government.”

Lansley also wanted to ban publication to pre-empt sensational media coverage.  In this he was repeating the arguments made by civil servants under Labour who refused, under the FOI Act, to publish risk registers and Gateway reviews.  Said Lansley “I consider that the form and the frankness of the content of TRR [health service Transition Risk Register] would have been liable to create sensationalised reporting and debate.

“The content would also have been inherently highly open to misinterpretation by both the press seeking a headline and/or for political reasons. The likelihood of this occurring is particularly acute where the subject matter is, as with the Transition programme, controversial and the proposals at a highly sensitive stage.”

But the Commissioner did not accept that disclosure of the Transition Risk Register would affect the frankness and candour of future risk registers. The Commissioner also said that a ministerial veto should, by law, be made only in exceptional circumstances.  But the Government has failed to explain why there are exceptional circumstances in this case.  Said the Commissioner:

“The Commissioner does not consider that sufficient reasons have been given as to why this case is considered to be exceptional, particularly in light of the [Information] Tribunal’s decision dismissing the Department’s [Department of Health’s] appeal.

“The Commissioner notes that much of the argument advanced as to why the case is considered to be exceptional merely repeats the arguments previously made to Commissioner and the Tribunal and which were in part dismissed by the Tribunal.”

Graham concludes:

“In light of previous commitments he has made, and the interest shown by past Select Committees in the use of the ministerial veto, the Commissioner intends to lay a report before Parliament under section 49(2) FOIA on each occasion that the veto is exercised. This document fulfils that commitment.

“ Laying this report is an indication of the Commissioner’s concern to ensure that the exercise of the veto does not go unnoticed by Parliament and, it is hoped, will serve to underline the Commissioner’s view that the exercise of the ministerial veto in any future case should be genuinely exceptional…

“The arguments employed by the Department at the Tribunal and by the Secretary of State in explanation of the subsequent veto, both in the Statement of Reasons and in exchanges in the House of Commons around the Ministerial Statement, certainly use the language of ‘exceptional circumstances’ and ‘matter of principle’. But the arguments are deployed in support of what is in fact the direct opposite of the exceptional – a generally less qualified, and therefore more predictable, ‘safe space’.

“As such, the Government’s approach in this matter appears to have most to do with how the law might be changed to apply differently in future. This question falls naturally to consideration by the Justice Committee who have been undertaking post-legislative scrutiny of the Act.”

Comment:

The reason for the veto in the case of the health service risk register has little to do with protecting a safe space for frank discussion.

Civil servants already compile risk registers, Gateway reviews and similar reports on the basis that they may, at some point, be published. Officials are no more likely to be frank if they know their reports will be confidential than more guarded if they know the documents will be published. They will do what their job entails. Their job requires honesty. They will do that job whether or not reports are published.

The real reason for the veto – and the refusal of departments to publish all contemporaneous internal reports on large and complex programmes, particularly those with a large IT element – is that some new schemes within Government operate at a shambolic level.

Any new government, whatever its hue, soon learns to keep secret the fact that such programmes are sometimes characterised by near anarchy.

One outsider to the UK government, Australian David Pitchford, discovered the truth when he became Executive Director of Major Projects within the Efficiency and Reform Group which is part of the Cabinet Office. Pitchford may not have realised his comments would be reported when he told a project management conference in 2010 that “nobody in the UK Government seems to know how many projects they have on the books, nor how much these are likely to cost”.

He found that projects were launched, and continued, without agreed budgets or business cases.  Today, there is better scrutiny of major projects, by the Cabinet Office’s Major Projects Authority. But the MPA is limited in what it can do or scrutinise. Which leaves government in a general mess when it comes to implementing anything new.

Evidence for this mess comes from the National Audit Office. Its auditors tend to investigate departments as a whole more than they do specific projects but when they do the careful reader can see that projects such as the Rural Payments Agency’s Single Payment Scheme (a scant regard for public funds, said the NAO) and the C-NOMIS project for the prison service (kindergarten mistakes, said chair of Public Accounts Committee) were without a structure. Chaos prevailed – and ministers were among the last to know.

Publication of project reports encourages professionalism. Departmental heads can be held to account if Parliament knows what has gone wrong. That’s precisely the reason departmental heads don’t want risk registers and other project reports published. It’s why all internal reports on Universal Credit, the government’s biggest IT-related project, are kept secret in spite of FOI requests.

The ministerial veto in the case of the NHS risk register is the government and civil service colluding in keeping the public and Parliament in ignorance of internal management’s inability to run complex new projects and programmes in a professional way.

Ministers and permanent secretaries don’t especially mind media criticisms that are based on speculation. They don’t want their critics having authoritative internal reports. That’s why the Cabinet agreed the health service veto – and it’s one reason the government has a not-very-hidden aversion to the FOI Act.

The coalition cannot justly claim to cherish open government while it is refusing so many requests under FOI to publish contemporaneous taxpayer-funded reports on its major schemes.

We agree with the Information Commissioner that use of the ministerial veto is a step too far. No number of announcements by the Cabinet Office on open government will gloss over the fact that the coalition is even more secretive about mega-projects than Labour. That’s saying something.

US federal CIO points to greater consolidation of government email systems

By David Bicknell

It is interesting to see how the US Federal CIO Steven VanRoekel is pushing US departments to rationalise their email systems.

The Labour Department is the latest to be earmarked for email consolidation with seven contracts for separate email systems set to be shrunk down to one, the Washington Business Journal reported.

The federal government needs to eliminate duplication to save dollars but also to free up time and resources in agencies’ acquisition offices so more effort can be put into transformative information technology projects, VanRoekel told the recent Congressional Forum on Technology.

“There’s an effort under way to start to look at how many [information technology] systems people are running in these agencies,” he said. “How many email systems? At the Department of Labor there are seven. There’s an opportunity there to save money.”

VanRoekel pointed to rationalisation success at other departments. Three years ago, he suggested, the Agriculture Department was managing 21 email contracts and 1,000 mobile contracts to implement primarily a BlackBerry service.

The department reduced those numbers to one and three respectively. The new email system cost one-third as much as the systems that had been in place, and the mobile computing blanket purchasing agreements saved Agriculture 18 percent from its budget

Consolidation efforts also need to be strategic to ensure fair competition among contractors, VanRoekel said.

“Should we go extreme on consolidation, and run one email system? The Canadian government has done this; one email, one procurement system,” he said. “Contemplating how we’d manage that at our scale is one factor. But also, if we the government were to pick the winner, we would do a great disservice to business. We need to strike that balance.”

Australian payroll IT project cost grows from $64m to over $400m

David Bicknell

In Australia, the state government in Queensland is coming to terms with a failing IT project whose cost has grown from $64.5m to $412m.

The payroll system for Queensland Health first went live in early 2010, prompting thousands of employees to be underpaid, overpaid or not paid at all, and triggering a subsequent critical report by the state’s Auditor General. 

Late in 2010, the Bligh government said $209m would need to be spent to fix the system in the following three financial years, on top of the original $64.5 million implementation cost.

Now, according to The Brisbane Times, the cost of the failed payroll system will reach an estimated $412 million by the end of June this year, with further costs likely to be incurred in the future.

Failure to prepare: Government slammed over health payroll bungle

Smart state’s technology spending up in the air

Are SIAMs the new SIs?

In this guest blog, John Jones and John Pendlebury-Green, co-founders of strategic sales architects Landseer Partners, take a look at the development of a new generation of outsourcing in ICT and the creation of a new breed of integration and manageement specialists dubbed ‘SIAMs’. This article is also carried on Landseer Partners’ website.

We now live in an age of austerity where we have to live within our means and this includes the Government  which has just announced the need for Departments to find a further £16bn in savings. 

All Departments and Agencies are having to make real year-on-year cuts to their budgets – effectively having to do  the same for less money for some considerable time to come.  This is leading to new models for the delivery of services (third generation outsourcing) as Government becomes more about “policy and strategy” and leaves the delivery of public services to the private sector.

Industry has already played a major part in first and second generation of outsourcing including what is now more commonly called “outcome-based contracting”. 

The recent contract awards of new prison builds and operations similar to the likes of G4S and Interserve provide exemplars of outcome-based contracting. The Work Programme Initiative at the Department of Work and Pensions is another relatively recent example of second generation outsourcing with payment linked directly to outcomes.  Lessons learned are only now emerging as to the efficacy of these contracts.

What is interesting is that now we are starting to witness a new third-generation of outsourcing in ICT – Service Integration and Management (SIAM).  The consequences for the ICT Industry and the delivery of ICT within and to Government are likely to be profound. 

At Landseer Partners, we believe that the shape and players of the ICT market will change significantly in the next two to five years.  The net effect on the role of existing System Integrators (SI) is likely to be significant.

So what is SIAM all about and, importantly, what will make SIAM a success and its implications for the big SIs?

SIAMs are the ICT Managing Agent for the Customer

So, what are SIAMs – well, for starters, there is no agreed de facto industry definition of what a SIAM is. Rather, there are emerging trends in the private sector and in the current government procurements at the Ministry of Justice (MoJ) and the Foreign and Commonwealth Office (FCO) that identify key characteristics of what Service Integrators and Management Services may look like. 

For instance, the MoJ and FCO both plan to award contracts to SIAM providers that can successfully demonstrate the ability to integrate services and manage a number of Tower service providers that (typically) provide one or more commoditised services of: data hosting, LAN/WAN provision, Applications Management and Support and some Security related services.  Importantly, the SIAMs will be characterised by:

  • Taking the risks for “end to end” delivery of the services and their continuing operations
  • Creating new commercial constructs to balance risk versus delivery
  • Not necessarily holding direct contracts with the Tower service providers
  • Providing full 24/7 service desks to support national and global needs of the customer
  • Working hand-in-glove and be contract-managed by the retained Intelligent Client Function (or Informed Partner as they are sometimes known) of the Contracting Authority

In effect, the UK public sector is now requesting what has long happened in the construction industry; they are looking to award contracts to Managing Agents to help deliver and manage critical  ICT services back to Departments/Agencies.

Expected Benefits

So, with the advent of SIAMs  what are the expected benefits?  Reading the prospectuses of the government procurements we would expect the benefits to be large and varied and include:

  • Reduced cost of ICT services to the commissioning Department/Agency – this might come about by greater efficiencies in programme delivery; but significant cash savings are also expected as staff are transferred move to more cost-effective private sector pensions schemes
  • Better risk management with continuous incentives to improve service quality to users
  • Greater innovation by the SIAMs, possibly by the use of niche SMEs which will assist with more agile delivery and innovation methods

The Future

Given the real lack of experience and reliable data on the likely impact of the creation of SIAMs it is difficult to say at this particular time whether SIAMs will effective in the longer term]– will SIAMs be effective in the longer term?  Will they help to drive down cost of ICT services?  Will they help in the delivery of better public services?

Landseer Partners’s view is that, although it is early days, SIAMs are likely to be here to stay, at least in the foreseeable future. The status quo, keeping large in-house Intelligent Customer Functions and Service Desk provision, is  neither desirable nor efficient and future procurements will build on the lessons learned from the current MoJ and FCO procurements.

The key thing now is for System Integrators to recognise that change is in the air, that different business models are appearing and that, to be in the market, a change in attitude, behaviours and delivery will be needed in order to become Service Integrators and Managing Agents to Government.

The story behind India’s struggling Aakash IT project

By David Bicknell

The New York Times has carried a couple of excellent blog posts reporting on India’s struggling “Aakash” IT project.

The India Ink posts detail the story behind a plan to introduce a cheap computer built for Indian students. As the blog explains, last October, the Indian Ministry of Human Resources Development unveiled the new, $35 computer.

Now, more than six months later, with thousands of university students still waiting for the laptop, “the tale of the Aakash looks a bit like an Indian soap opera, complete with a convoluted storyline, multiple characters, and massive personality clashes.”

As India Ink says, the Aakash project, if successfully completed, could enable millions of students to connect with the larger digital world, and is being closely watched outside India as the national government tries to attract foreign investment in public-private partnerships for everything from infrastructure to vocational training.

“The original idea behind the Aakash seemed pleasantly simple. A cheap computer would benefit Indian university students by enabling them to watch lectures or get lecture notes and other class information online. In 2009, a team of government researchers developed the basic design for the low cost device.

“The job of putting the project out to bid fell to I.I.T. Rajasthan, which by spring of 2011 had received 477 million rupees — about $9.2 million — in government funds to pay for procuring and testing 100,000 low-cost tablets. In writing the tender, I.I.T. Rajasthan detailed the technical specifications for the tablet but did not specify the criteria for testing and approving the devices, according to a government source involved in the project. That omission was to prove disastrous.

Here is Part One of the tangled tale of the project, which involves issues with procurement, outsourcing, testing and governance.

And here is Part Two.

India’s $35 Aakash tablet comes apart
Aakash Tablet Problems: India’s $35 slate slammed by testers

Whitehall defies NAO and Cameron on publishing status of big projects

By Tony Collins

Government action to cut the number of failures of big projects including those with a major ICT component has made a difference, the National Audit Office reports today.

In its report “Assurance for major projects”  the NAO is largely supportive of actions by the Government, , the Cabinet Office’s Major Projects Authority and the Treasury in setting up reviews of major high-risk projects, including ICT-based programmes, to ensure that if they are failing they are put back on track or cancelled.

The NAO says the Government’s decision to “dismantle” the NPfIT was taken after the project was assessed by the Major Projects Authority.

But the report also shows how civil servants have managed to defy a mandate from the Prime Minister, and a separate NAO recommendation in 2010, for information on the status of big ICT and other high-risk projects to be published.

Says the NAO report

“The ambition to publish project information, as part of the government’s transparency agenda, has not been met.

“Our 2010 report recommended that the government should publicly report project status. We consider that public reporting of project information is key to providing greater accountability for projects and improving project outcomes… Regular transparent reporting of performance which highlights successes and non-compliance would also help to build an enduring assurance system.”

Separately in the report the NAO says

“There has been a lack of progress on transparency.  The [Cabinet Office’s Major Projects] Authority has not yet met its commitment to publish project information in line with government’s transparency agenda. The Authority cannot deliver this objective on its own. Senior level discussions are ongoing, between Cabinet Office, HM Treasury and departments, on the arrangements for public reporting.”

Should ministers intevene to force publication?

But the NAO report does not raise the question of why ministers have not intervened to force civil servants to publish the status information on high-risk projects.

Campaign4Changehas argued that publishing status reports on big ICT projects and programmes would be the most effective single action any government could take to reduce the number of failures. (see “Comment” below)

Prime Minister’s 2011 mandate

The NAO’s 2010 recommendation for status information on major projects to be published was backed by a mandate from the Prime Minister in January 2011 which included the undertaking to “require publication of project information consistent with the Coalition’s transparency agenda”.

The House of Commons’ Public Accounts Committee has recommended that departments publish information on the state of their major IT-based projects and programmes; and the Information Commissioner has rejected civil service arguments for not publishing such information.

In addition Francis Maude, the Cabinet Office minister, said, when in opposition, that the Conservatives, if they gained power,  would publish “Gateway” review reports soon after they are completed.  Gateway reports are similar to the assurance reviews carried out for the Major Projects Authority.

Yet none of this has happened.

The “rebel” civil servants

How is it that a group of civil servants who are opposed to publishing information on the status of large risky projects can defy the Prime Minister, Francis Maude, the National Audit Office, and the all-party Public Accounts Committee? Those recalcitrant civil servants argue that assurance reviewers would not tell the whole truth if they knew their assessments would be made public.

But how do we know they tell the whole truth when the reports are kept confidential? The Information Commissioner has pointed out in the past that civil servants have a public duty to be candid and honest. If they are not because their reports are to be published, they are failing in their public duty.

Today’s NAO report says there are differences of opinion among civil servants over whether to publish status information on projects.

Says the NAO

“There has been some support for greater transparency from departments who believe that tracking and publishing major milestones could create helpful tension in the system.

“However, concerns have been raised that increased transparency could limit the value of assurance, as it could inhibit assurance reviewers and project staff holding full and frank discussions.

“Some senior project staff also have concerns that public reporting could have a negative commercial impact, and would prefer delayed rather than real-time public reporting.”

The Cabinet Office told Campaign4Change in 2010 and 2011 that instead of publishing status reports on each major project, it will publish an annual report on the state of its programmes.

But that hasn’t happened either.

Says the NAO:

As well as the objective to publish project information, the [Major Projects] Authority has not yet met its objective to publish an annual report on government’s major projects.

“The Authority initially expected to publish an annual report in December 2011 but is now expecting the report to be published in May or June 2012. The format of the annual report, and the information it will contain, has yet to be decided.”

Comment:

Many times over the last 20 years I have said that publishing status reports on major IT-based projects and programmes would be the most effective single action any government could take to deter departments from going ahead with overly ambitious schemes that are doomed to fail. If, against good sense, impractical schemes are approved, publishing status information will make all the difference.

Permanent secretaries will not lose sleep over a failing project, but they will not want information on it published – which is why that information should be published.

Publishing status information would give civil servants a good reason to tackle weaknesses as they developed.  Permanent secretaries may not mind losing public money on a failing project or programme. They will always fear embarrassment, however.

Who is really in control of Whitehall – civil servants or No 10? David Cameron’s office has issued a mandate that requires status information on projects to be published. The NAO has issued a similar recommendation. How long can the civil service hold out against the political will?

Links:

NAO report – Assurance for major projects

Firecontrol – same mistakes repeated on other projects

The debate over G-Cloud – have your say

By David Bicknell

A debate is running over the Government’s plans for G-Cloud. It follows Chris Chant’s Unacceptable IT is pervasive blog on his departure, a response to the comments received on Chant’s blog by his successor, Denise McDonagh, about Cloud Cynicism, and now, and this must break some new ground, a government-hosted ‘crowdsourcing’ opportunity for you to have your say and influence the debate.

Please add your thoughts here

MyCSP becomes first public sector mutual spin-out

By David Bicknell

An article on the Daily Telegraph website suggests that this week will see the creation of the government’s first public sector mutual spin-out. 

MyCSP will be spun out from the Department for Work and Pensions (DWP) and “transformed into an independent mutual that will give staff an unprecedented say in how the business is run and the chance to share in the new company’s profits.”

A 25% stake in MyCSP will be divided between the agency’s 500 staff, with a 40% sold off to a major player in the financial services industry. The company will try to win new business from the public and private sectors.

The Telegraph reports that ministers believe mutualisation will halve MyCSP’s administration costs. Although staff will become members of the private sector, they will retain their public sector pensions.

MyCSP has signed a 10-year contract to administer the civil service pension scheme, which has around 1.5 million members. At the end of this contract, the new mutual will have to compete against other private sector pension adminstators to run the scheme.

Lord Hutton of Furness, a former Labour minister, will be the chairman of the MyCSP. He said he hoped this was the “first of many” mutuals to be spun out of the public sector.

“Creating mutuals are a very exciting way for people on the front line of the public sector to take ownership and responsibility for the services they provide,” said Lord Hutton.

“They get a voice on the board and a share of any profits. I hope this model will lead to better performance and better value for the taxpayer.”

He argued that the old model of public sector monopolies were “not fit for the 21st century”, and added that the greater squeeze on taxpayers’ money ensured that poor performance in the public sector could “no longer be tolerated”.

“There is no such thing as a status quo in the public sector worth defending – we must have a relentless pursuit of excellence,” he said.

“I am a very strong supporter of what this Government is trying to do with public service reform particularly with a view to mutualisation.”

MyCSP’s private sector partner will be the Equiniti Group’s Paymaster business, which will hold a 40 per cent stake, with the government holding 35 per cent and the employees 25 per cent under a model based on the much-quoted John Lewis model of mutual ownership , which rewards employees with profit-related bonus schemes.

Related articles

Mutualised civil service pension service is launched

Hutton to head up Whitehall mutual

Equiniti Group’s Paymaster business partners with first central government mutual

Is DWP stance on Universal Credit reports mocking FOI?

By Tony Collins

The Department for Work and Pensions, which has remained as secretive over the progress or otherwise of its IT-based projects as before the 2005 Freedom of Information Act, has, as expected, rejected our FOI request for reports on the state of the Universal Credit project.

We have appealed and the DWP has, as is customary, delayed its response. It appears that the Department works on the principle that the longer it delays FOI responses the more out of date will be its reports when the Information Commissioner eventually rules they must be published.

In its reply to us, the DWP gave reasons for hiding a report it has already put in the public domain: a “Starting Gate Review” of Universal Credit.

Hiding reports under its jumper

The review was carried out in February 2011. That the DWP is keeping under its jumper a public report suggests that its responses to the FOI Act owe more to instinct than proper consideration.

The DWP also refused to publish, under the FOI Act, a Universal Credit “Project Assessment Review in November 2011” by the Cabinet Office’s Major Projects Authority.

These are the reasons Ethna Harnett, Universal Credit Division, DWP,  gave for refusing our FOI request for Universal Credit project progress reports:

– “Further reviews, by the Major Project Authority and by the National Audit Office are planned.”

– “Elements of the information you requested is being withheld as it falls under the exemption in Section 36 (2) (b) and (c) of the Freedom of Information Act. This exemption requires the public interest for and against disclosure to be balanced.”

– “The information you have requested includes details of a sensitive nature whose publication would prejudice effective conduct of public affairs. There is a strong public interest in the Department maintaining an efficient and effective risk management and assurance process and in ensuring that this process is not undermined by premature disclosure particularly where risks are not yet fully mitigated.”

– “There is also a strong public interest in the Department being able to carry out and use frank assessments, including unrestrained and candid contributions from business areas. ”

– “The assurance reports produced by the Major Project Authority are not shared beyond the Senior Responsible Owner and interested parties within Government.”

– “DWP Ministers have, however, committed to update Parliament on the Universal Credit programme through written ministerial statements. These statements are available on the Parliamentary website – www.parliament.uk.”

– “The Major Projects Authority will publish information on the progress of the Government’s high-risk and high-value projects, referred to collectively as the government major projects portfolio, alongside the first annual report at the end of this financial year.”

Comment:

The DWP has never met any of our FOI requests and has, in every case, delayed its responses to our requests for internal appeals. The result of the appeals is always the same – the upholding of the original decision. We are in awe of the DWP’s ability to detach its IT operations from the FOI Act.

The DWP considers it is acting in the public interest: that assessments of its IT-based projects such as Universal Credit would not be candid if they were put in the public domain.

But if the DWP had got this right and that its assurance reports would be less effective if published, we’d expect to see successes with major DWP IT-based projects. We don’t see the evidence.

Indeed the signs are that Universal Credit, the DWP’s biggest project, is in trouble; and after 20 years the Department is still having trouble combining its various benefit systems.

The National Audit Office has qualified the DWP’s accounts every year for the last 23 years, largely because of the level of official error and fraud.

Is this a department that is getting IT right?  There is no evidence it is; and some evidence suggests it isn’t.

The DWP needs to change. It needs to see openness as an opportunity not a threat. Openness would show that officials are prepared to be measured publicly against the findings of their assessment reports. That needs self-confidence.

On the other hand secrecy permits an uneasy introspection, allows weaknesses to take hold, and gives officials comfort in not changing.

Somerset Maugham put it well in his excellent book Of human Bondage. He said: “Like all weak men he laid an exaggerated stress on not changing one’s mind.”

Time for truth on Universal Credit

Millions of pounds of secret DWP reports

Universal Credit latest

FOI blog

Trying to kill the FOI Act?

Government publishes data on £70 billion of future contracts

By David Bicknell

The Government has published data on £70 billion of potential future government contracts, with Cabinet Office minister Francis Maude arguing that the move marks a new era in openness about its long-term business needs.

“We have published details of £70 billion of potential Government business. Publishing data on what we plan to buy – whether it’s tunnels or computers – means we can identify skills gaps sooner and give industry a heads up so UK businesses are in a better position to compete,” he said.

The data published of potential future contracts over the next five years, covers 13 different sectors including construction, property, medical and police equipment. The publication of the data increases the potential opportunities for SMEs to bid for government business.

Information Age magazine has reported that the £70bn includes £2.5bn worth of IT projects.

Data on the contracts can be found at Contracts Finder

£70 billion of potential government business published to boost UK growth