Category Archives: public sector

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.

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

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

Cash-strapped council IT teams to get backing for innovation projects

By David Bicknell

IT teams in cash-strapped councils are being given a helping hand to drive new IT projects where teams believe technology innovation could drive positive change in local communities.

It follows the launch of a Future Fund created by mobile telecomms company O2 to help forward-thinking councils get to grips with new methods of engaging their staff, citizens and communities.

Successful local authorities applying for the scheme will be awarded access to O2 consultancy time, services and technology to help them turn their project ideas into reality.

The Future Fund open for applications on 25th April with three grant funding packages available to the value of £125,000, £75,000 and £50,000.

60 councils attended the launch event with the scheme focused on authorities developing ideas and services against three broad themes: reducing cost and improving efficiencies; finding new ways of engaging with citizens; and empowering the community to do more for itself.

Each of the topics points to more effective service delivery, by empowering staff or by expanding the concept of ‘self-service’.

To support the Fund’s launch, O2 plans to showcase 17 different parts of its business, each with their own unique slant on the digital age, from established technologies such as wi-fi to ‘people’ skills, social media expertise, mobile advertising and location-based services, as well as business engagement and apps development. Councils will be able to pick which selection of services to use to build their idea and weave into their bid.

O2 says it has created the Future Fund through its Local Government Futures Forum, which aims to understand what the role of IT should be in modernising councils in challenging times.

It argues that as technology advances at a rapid pace, with people creating and consuming data in more diverse and immediate ways, councils face a challenge to use these channels to demonstrate communications nous and find new ways to engage with their communities.

A recent consultation exercise found that budget cuts across the public sector have resulted in an expected automatic squeeze on resources, with mounting pressure across all departments to operate more efficiently and do more with less. 

With ongoing pressure to reduce spending, council decision-makers are opting for solutions that make an immediate impact – cutting services, and in turn cost – rather than looking at ways of adapting them, with IT departments facing an uphill struggle to retain and control their destinies, often competing for de-centralised budgets across multiple teams with no place or input at a board level.

Ben Dowd, Director of Business at O2 says: “O2 believes that the right application of technology has the potential to drive real change. Our findings through our work with local government IT departments support this belief. What is different is that the Future Fund will give a glimpse of what is possible with a bit of imagination and we will support the winning bids by providing investment in their IT infrastructure coupled with resource and expertise.

“So it is up to the councils to determine how it can be applied to their own council, citizens or community, ultimately giving local government the ability to shape their own destiny in a project they are passionate about.”

Applications for the Fund will be judged by a panel of experts from O2 and independent parties. Councils will then have eight weeks to develop and deliver their ideas, before selection takes place later this year.

www.o2.co.uk/futurefund

Freedom of Information failures shine light on governments’ records management projects

By David Bicknell

The struggles that a number of governments and agencies are having in coping with Freedom of Information (FOI) requests has raised questions over the need for – or the status of – their IT projects for records management.

The UK government is itself in a tizzy about the number of requests it receives.   And it appears from this ZDNet article Down Under that state governments and public services in Australia are struggling to keep up too.

The article cites a recent report from the Victorian auditor-general that the Victorian Department of Human Services (DHS) needs a new electronic records-management system. It argues that not only is the department completely failing to fulfil FOI requests, which was the topic of the audit, but it is also probably losing hours of staff time as employees comb through its records for the information they need to do their jobs.

Apparently, the DHS received 1047 FOI requests in 2010-2011. However, instead of meeting the 45-day deadline for fulfilling these requests, the average fulfilment time was 75 days.

Admittedly, Australia has had 30 years of dealing with FOI, where here we have had twelve. But the report’s background and conclusions on FOI make for informative reading.   I wonder how many government departments and councils it might apply to over in the UK; what IT projects (if any) they have underway in terms of electronic records management; and just how long it might be before a similar critical report is written here.

Background

Freedom of information (FOI) is a cornerstone of a thriving democracy. FOI upholds the public’s fundamental right to access information held by the government. The community’s ability to scrutinise public sector activities and hold the government of the day accountable for its decisions is affected by the transparency and accessibility of government information.

Since the Freedom of Information Act 1982 (the Act) was introduced, both the number and the complexity of requests for information have increased considerably. In 2010–11 there were 34 052 FOI requests, compared to 4 702 requests in 1984–85, the first full year the Act was in operation.

The Victorian Ombudsman identified systemic problems in his 2006 review of FOI. These included a lack of timely responses, inconsistent application of the Act and lost or non‑existent documents. In his 2011 Annual Report the Ombudsman concluded that these problems still remained five years later.

The audit examined the extent to which all 11 Victorian public sector departments and Victoria Police meet the requirements of the Act and associated guidelines. A detailed assessment of the effectiveness and efficiency of FOI processes in Victoria Police and the Department of Human Services (DHS) was also performed. These two agencies were selected because they process 68 per cent of the FOI requests received by the 12 agencies audited.

Conclusions

Since FOI legislation was introduced 30 years ago, Victoria has gone from being at the forefront of FOI law and administration to one of the least progressive jurisdictions in Australia. Over time, apathy and resistance to scrutiny have adversely affected the operation of the Act, restricting the amount of information being released. As a result, agencies are not meeting the object of the Act, which is ‘to extend as far as possible the right of the community to access information’.

The public’s right to timely, comprehensive and accurate information is consequently being frustrated. The Victorian public sector’s systemic failure to support this right is a failure to deliver Parliament’s intent.

The prevailing culture and lack of transparent processes allow principal officers—secretaries and chief executive officers of agencies—to avoid fulfilling their responsibilities. Principal officers are not being held to account for their agency’s underperformance and non-compliance:

  • In 2010–11, the average response time for eight of the 12 audited agencies exceeded the statutory deadline for responding to applicants’ requests.
  • Of these agencies, four exceeded the 45-day time limit for over half of their requests.
  • None of the agencies adequately complied with the mandatory reporting requirements of the Act.
  • The principal officers of the Department of Premier and Cabinet (DPC), the Department of Health (DOH) and DHS have not managed adherence with ministerial noting periods consistent with the Attorney-General’s 2009 Guidelines on the Responsibilities and Obligations of Principal Officers and Agencies(the FOI Guidelines). This has led to delays in the release of documents.
  • Agencies have not managed to reach agreement on a consistent, whole‑of‑government approach to the proactive release of information, which would reduce the reliance on FOI processes for the release of non-personal information.
  • The more detailed review of DHS and Victoria Police revealed serious flaws in record keeping practices and FOI searches.

The cumulative effect of the multiple cultural and process issues is that the community does not receive the information it is entitled to receive, when it should receive it. Agency senior management is aware of these longstanding issues and their consequences, but has not taken sufficient action to address these systemic weaknesses.

This points to an absence of leadership and responsiveness, and a willingness of agencies to compromise the fundamental public service principles of integrity, accountability and respect. These are values that all public sector officials are expected to demonstrate under the Code of Conduct for Victorian Public Sector Employees. Principal officers who do not observe these values are failing the community and Parliament.

Embedding the appropriate pro-disclosure culture and processes, which underpin the intent of the Act, requires effective leadership. The Department of Justice (DOJ) has not adequately championed FOI across the public sector and, as such, has not satisfactorily fulfilled its role as the lead agency for FOI.

The introduction of the FOI Commissioner presents an opportunity for more proactive FOI leadership—in particular driving the cultural shift that is necessary to provide better quality services to the community. Significant change will only be possible if the commissioner is granted sufficient powers and resources. Since these amendments have not yet commenced, recommendations relating to the lead agency for FOI are addressed to DOJ, but will subsequently need to be reviewed once the FOI Commissioner has been appointed.

Findings

Department of Justice leadership

As the lead agency for FOI, DOJ is accountable for providing agencies with guidance and advising the minister responsible for the administration of the Act through the production of annual reports to Parliament on FOI performance. There have been significant shortcomings in the department’s approach in both of these areas.

Freedom of information culture and practices

DOJ has not adequately promoted and modelled the intent of the Act and accepted better practice, either in its own department or across the public sector. Specifically, DOJ has not:

  • developed a proactive release framework for agencies
  • addressed its own or other agencies’ processing delays
  • complied with the reporting or timeliness requirements of the Act, nor encouraged other agencies to do so
  • complied with the five-day ministerial noting time frame before documents are released.

The tolerance of these longstanding substandard practices, particularly with regard to proactive release, reflects an apathetic and obstructive culture. DOJ has acknowledged that it could have taken a stronger approach with agencies, but stated that its ability to address substandard practices is limited because it does not have adequate powers to mandate good practices. This lack of powers is not sufficient justification for DOJ to not exercise leadership. Further, there is no evidence that DOJ sought to extend its powers to address its inability to achieve an acceptable level of practice, consistent with the object of the legislation.

Proactively releasing information is an effective means of disseminating the maximum possible amount of information. It is recognised as better practice and, accordingly, is the approach adopted in other jurisdictions. Although Victorian agencies are publishing information, this does not necessarily constitute proactive release unless they have properly assessed the information to determine whether it is of significant public interest, appropriate, accurate, accessible and easy to use. This, combined with the continued reliance on formal FOI applications, means Victoria is less progressive than other jurisdictions.

Performance reporting

The apathy with regard to FOI is also evident in the reporting regime. The minister responsible for the Act relies on DOJ to collect, check and prepare data for inclusion in the FOI Annual Report to Parliament. However, DOJ is not reporting to the minister aspects of agencies’ performance as the letter and spirit of the Act requires.

DOJ does not report on measures that are explicitly specified in the Act, including disciplinary action taken against officers in respect to the administration of the Act, such as a breach of duty or misconduct.

DOJ collects information on the timeliness of agencies’ responses to FOI requests but does not include this information in the minister’s report to Parliament. Although DOJ is not specifically required to disclose this information to the minister, it is not precluded from doing so. Releasing agencies’ timeliness statistics would be in the spirit of the Act and encourage better performance.

Parliament and the public have the right to know if agencies’ performance is unsatisfactory. DOJ’s lack of comprehensive and transparent reporting in relation to the minister’s annual report does not satisfy the community’s expectations of a public sector agency.

Training

Training is an effective way to instil a positive FOI culture in agencies and to emphasise the importance of openness and transparency. DOJ’s FOI training program places too much emphasis on basic administrative process, rather than the intent of the Act. An important opportunity to promote a positive pro-release FOI culture has been missed.

Agency management

Timeliness of response is a good indicator of senior management’s attitude towards the importance of FOI. The number and complexity of requests can influence performance against the statutory time limit, however, the onus is on principal officers to provide adequate resources and support to meet the timeliness requirements. Only two of the audited agencies meet both the 45-day time limit and the five-day ministerial noting period.

Of the 12 agencies audited, only four had average request processing times that met the 45-day statutory limit in 2010­–11. These were the Department of Education and Early Childhood Development, Department of Transport, Department of Primary Industries and Department of Treasury and Finance. The worst performing agencies were Victoria Police, DPC and DHS, which averaged 98, 92 and 75 days respectively.

Victoria’s underperformance against its legislative target is even more concerning when compared with other states. Other states have better processing completion rates against shorter or similar standard time limits. Extensions to these time limits may be granted, in certain circumstances.

The five-day ministerial noting period recommended in the FOI Guidelines was exceeded by eight of the 12 agencies. The worst performing department was DPC, with an average noting period of 41 days. One FOI request was with the Office of the Premier for 88 days. DHS and DOH also recorded noting periods in excess of 20 days. Long noting periods delay the release of information and impede the effective operation of the Act.

When agencies do not respect the FOI Guidelines, this not only compounds the delays in processing FOI requests but also contributes to the public perception that there is political interference in the FOI process, particularly when there is repeated consultation between an agency and a minister’s office on requests.

Victoria Police and DHS have both attempted to improve the timeliness of their responses. At Victoria Police, timeliness improved when additional resources were temporarily assigned to the FOI unit, while DHS improved its response time by prioritising requests.

Department of Human Services and Victoria Police

An effective FOI system relies on strong agency leadership and support, a robust understanding and application of the Act, good records management, appropriately defined searches and open communication with applicants.

DHS and Victoria Police, the two agencies reviewed in more detail, have significant deficiencies in these areas. As a consequence, the public is being denied access to information.

Processing fees and waiver of time frame

DHS is offering applicants the opportunity to waive processing charges if they forgo the requirement for DHS to meet the 45-day processing time limit. DHS is not advising applicants who have little or no money and are seeking information that relates to their personal affairs that they have a right to request a waiver of charges under the Act without waiving the 45-day time limit.

This unacceptable practice was not observed in any of the other audited agencies. It allows DHS to extend its time frame for responding to requests without recording those requests as overdue, giving the mistaken impression that the department’s timeliness performance is better than it actually is.

Records management

DHS and Victoria Police need to address deficiencies in their record keeping practices as a priority. Records are being lost, disposed of incorrectly or rendered inaccessible.

DHS’s record management facility has inappropriate physical storage conditions—causing records to deteriorate—and inefficient indexing systems. As a result, information cannot be found when needed.

Although Victoria Police has a policy outlining the appropriate storage of records, it has not addressed the informal practice of police officers storing records, such as note books, at their homes. This practice increases the likelihood that these records may be lost or difficult for Victoria Police to locate.

Search techniques

DHS and Victoria Police both need to remedy weaknesses in their FOI searches to provide appropriately scoped responses.

DHS does not include records held by its contracted community service organisations (CSO) in the FOI requests the department processes. Instead, DHS refers applicants to the relevant CSOs. The quality of record keeping practices of CSOs varies widely and, consequently, so does the amount of information available to DHS’s clients.

DHS is failing to discharge its obligations to its clients. The Act refers to ‘possession’ when defining a document, not ownership. DHS has a right to possess CSO records under its service agreements, therefore CSO documents are subject to the Act. Furthermore, the department is contravening the specifications set out by the Public Records Office Victoria and the FOI Guidelines.

Victoria Police’s FOI unit does not conduct sufficiently thorough and diligent searches. The unit does not inspect proof of disposal documents to confirm whether documents cannot be provided because they no longer exist.

Related Links

FOI debate: the genie of freedom will never be put back

One in three public bodies failing on freedom of information requests

Why nations – and organisations – fail

By David Bicknell

I just came across an excellent piece by Craig Dearden-Phillips on why nations – and organisations – fail.

In it, he discusses a book,  ‘Why Nations Fail’, by Daron Acemoglu and James Robinson.

He writes: “The opener of the book contrasts two halves of a city, Noglales which straddles the Mexico-US border. One sits in the region on Sonala, Mexico, the other in Arizona, US. Here the people, culture, climate and operating conditions are the same. On one side of the border, incomes are many times higher, there are good public services and crime is uncommon. On the other, people are mostly poor, there are few public services and crime is rampant because the state isn’t in real control on the ground.

He continues: “Perhaps what has capitivated me most, though, is the read-across to why certain types of public services fail, despite wonderful resources and high levels of native talent. Analogous to the extractive and exclusive institutions described at state level in this book could be placed the large public sector monopolies which still dominate much of public service in Europe and certainly in the UK.

“Here, power is often monopolised and change, even ‘good change’ does run against the interests of many of those involved. Initiative is often powerfully suppressed. It is hard, frequently impossible, to set up in business against these monopolies and there are often few political processes which can be used to break these systems down.

“What am I thinking of here? Well, if you haven’t guessed, I am alluding to many of the organisations from which spin-outs do or don’t emerge.

“The truth of the matter, and I see this every day, is that setting up a new business to deliver public services feels like it probably does to set up any ordinary business in parts of the developing world. You need the buy-in of a variety of power-brokers, all of whom need to see their interests satisfied. You need to go through all sorts of bureaucratic processes to show you’re not a risk and are ‘worthy’ of delivering services.

“From there, you need to make all sorts of promises to the system that its interests will not be threatened and create opportunities for the system to have it’s say even when the business is up and running.

“All of this, of course, creates a massive disincentive for any sane person in public services who wants to change things. The risks are massive – to career, to sanity, to reputation – that most people, quite understandably either stay put or move out. Those that try to start a public service business have to run a gamut that looks far more like something you’d see in Mexico than in Midshire, UK.”

Dearden-Phillips makes some excellent points and the whole piece is worth reading.

New York’s CTO to leave as row deepens over city’s handling of IT projects

By David Bicknell

New York, New York (So Good They Named It Twice) – as the song goes -though not so good at delivering successful IT projects, it would seem.

According to The New York Times, the city’s chief technology official Carol Post has resigned after clashing with a deputy mayor over the management of several costly, ambitious IT projects.

According to the newspaper, city government spokespeople said Ms. Post, who is the commissioner of the Department of Information Technology and Telecommunications, should not be blamed for the mismanagement of the $2.3 billion 911 project, whose problems predated her arrival in the job. She is reported to be leaving to take up a new position at the New York Law School. 

Post’s departure  was announced a day before New York’s mayor, Michael Bloomberg said the city would challenge a judge’s order to release a report by consultants McKinsey on an overbudget, much-delayed modernisation of the city’s 911 emergency calls and dispatching system.

According to The New York Times story, concerns have been expressed about the cost of an upgrade to CityNet, the city’s internal data network; there are continuing problems and shortcomings with CitiServ, a data centre that was supposed to consolidate dozens of city agency servers; and a shortage of users for NYCWin, a secure municipal wireless network.

The wireless network cost $500 million to build and a further $40 million a year to operate, and is underused and arguably outdated.

CityNet has experienced interruptions in service, despite a system of redundant fiber optic rings intended to enable it to withstand a breakdown. The $95 million CitiServ project is reported to have confounded agency officials, with the technology department, DoITT, struggling to migrate old systems into the new data centre.

“The technology department is officially referred to by its acronym, DoITT, but is sometimes derided as “Don’t Do It” by city workers who seek to avoid working with the department,” The New York Times said.

Of Post’s departure, Bloomberg said, “Over the past ten years, we have fundamentally transformed the operations of New York City agencies and elevated New Yorkers’ expectations of how efficient, user-friendly and transparent their government should be, and a large part of that is because of the tirelessness and talent of Carole Post. From her work at the Department of Buildings to the Mayor’s Office of Operations to DoITT, Carole has brought agencies together in common cause, finding efficiencies, defining legal strategies and creating collaborations that use taxpayers’ dollars more effectively. There’s nobody better to help a great institution like New York Law School climb to new heights, and though I’m very disappointed to see her go, I wish her well in tackling this new challenge.”

NY’s CTO Resigns, As Some Question Bloomberg’s Handling of City’s Tech Projects

New York’s emergency call IT project: just seven years behind schedule and $1bn overbudget

Mutuals likely to be focus of Government Right to Provide plans expected today

By David Bicknell

The Government looks set to make an announcement about mutuals today as part of ‘Right to Provide’ plans due to be unveiled by David Cameron. The likelihood of an announcement appears to have been leaked.

Here’s today’s Daily Mail’s take on the proposed announcement.

More details to follow

Updated: Rights to Provide Plans focus on “potential offered by mutual models”

Universal Credit: who’ll be responsible if it goes wrong?

By Tony Collins

When asked whether Universal Credit will work, be on budget and on time, Ian Watmore, Permanent Secretary, Cabinet Office, gave a deft reply. He told Conservative MP Charlie Elphicke on 13 March 2012:

“From where I sit today, I think all the signs are very positive. I am never going to predict that something is going to be on time and on budget until it is.”

If the plans do not fall into place who, if anyone, will be responsible? In theory it’ll be Iain Duncan Smith, the Secretary of State for Work and Pensions. But as Watmore told the Public Administration Committee, there are several other organisations involved. Although the DWP and HMRC are building the IT systems, the success of Universal Credit also relies on local authorities, which are overseen by the Department for Communities and Local Government.

There are also the Cabinet Office and the Treasury whose officials seek to “ensure that what is going on is appropriate” said Watmore.

If Univeral Credit goes awry all the departments may be able to blame the private sector: the employers that must pass PAYE information to HMRC so that the Revenue’s Real-Time Information element of Universal Credit can work.

David Gauke is the minister responsible for HMRC so would he take some of the blame if Real-Time Information didn’t work, or was not on budget, or was delayed?

Or would the main IT suppliers Accenture and IBM take any of the blame? Highly unlikely, whatever the circumstances.

There is also a dependency on the banks.

But nothing is wrong … is it?

All those putatively responsible for Universal Credit continue to say that all is going well.

Duncan Smith told the House of Commons on 5 March 2012:

“We are making good progress towards the delivery of universal credit in 2013, and I have fortnightly progress meetings with officials and weekly reports from my office. I also chair the universal credit senior sponsorship group, which brings together all Government Departments and agencies that are relevant to the delivery of universal credit.

“Design work is well under way and is being continually tested with staff and claimants, and the development of the necessary IT systems will continue in parallel.”

He said that universal credit will reduce complexity by putting together all the benefits that are relevant to people going back to work – though benefit systems that are not relevant to the coalition’s “Work programme” will not be included in the DWP’s Universal Credit IT consolidation.

To reduce risks Universal Credit will be phased in over four years from October 2013, each stage bringing in a different group of claimants.

But …

Campaign4Change has asked the DWP to publish its various reports on the progress of Universal Credit and it has refused, even under the Freedom of Information Act. It seems the DWP’s secretiveness is partly because all of the risks related to Universal Credit have not been mitigated. We will report more on this in the next few days.

Meanwhile to try and answer the question in our headline: who’ll be responsible if Universal Credit goes wrong? The answer is: the private sector probably. Or rather nobody in the public sector.

Can hundreds of millions be spent on Universal Credit in an agile way?

Universal Credit suppliers Accenture and IBM look to India for skills.

Is Universal Credit a brilliant idea that’s bound to fail?

Universal Credit latest

Universal Credit and the banks.

Should Francis Maude say “no” to so many projects?

By Tony Collins

When Jack Straw was Secretary of State for Justice and Lord Chancellor, he told MPs on the Constitutional Affairs Committee in 2007 that when he abandoned projects there was a fuss at first and soon nobody noticed the project did not exist.

“There is always the option to abandon things. I did that in the Foreign Office with much complaint that the world might end.

“What happened was that we saved a lot of money and no one ever noticed the fact that that scheme did not exist…it is very frustrating that so many people, including the private sector, are taken in by snake oil salesmen from IT contractor who are not necessarily very competent and make a lot of money out of these things. I am pretty intolerant of this.”

Andrew Tyrie (Conservative): Do you suggest that the public sector has been taken in by snake oil salesmen?

Straw: I am saying that we are all taken in. There are plenty of disastrous IT examples in the private sector, BP and Sainsbury being two of them.

Tyrie: I was looking at the public sector.

Straw:

“I was looking at both. I think we all face problems whereby unless we are total IT experts there is a danger of being taken in by snake oil salesmen… It is a real problem and it is one that is inherent in IT; it is not just a problem for the public sector.

“The difficulty is that in the case of the public sector it is taxpayers’ money, not shareholders’ or customers’ money, and the mistakes are much more visible, but plenty of companies in the private sector have similar problems.”

Comment:

Should the Cabinet Office Francis Maude say “no” to so many projects? Clearly he’s doing the right thing if Straw’s remarks are anything go by. Would a  private sector board that has to watch every penny launch costly IT-related projects that weren’t really needed?