Skip to main content

Language: English / Gàidhlig

Loading…
Chamber and committees

Audit Committee, 08 Oct 2008

Meeting date: Wednesday, October 8, 2008


Contents


Section 23 Report


“Review of major capital projects in Scotland—How government works”

The Convener:

Item 3 on our agenda is a section 23 report on major capital projects. We are joined this morning by Sir John Elvidge, the permanent secretary, and by Alyson Stafford. Welcome to you both. We have not had the privilege, Sir John, of your attendance at the committee in this parliamentary session—although I do not know whether you have attended in previous sessions. We look forward to your contributions on two agenda items this morning. Thank you for coming along. Before we move to questions, do you wish to make some introductory remarks?

Sir John Elvidge (Scottish Government Permanent Secretary):

Only briefly—and thank you for the opportunity.

The first thing to say is that the report is an excellent piece of work by Audit Scotland. It is valuable and timely. Rather than any arguments over views of what would be desirable, the issues that arise concern how we should pursue the sensible direction of travel that the report sets out. We agree with the report that we should make progress, and in talking about how we can do that I will refer frequently to two main threads of activity. The first concerns the work of our infrastructure investment group, which Alyson Stafford chairs. The group brings the directors from our main directorates together with senior staff from our finance directorate, so that they can take an overview of our main strands of capital activity. The report clearly suggests that taking such an overview is sensible; indeed, the report refers to the existence of the group, which was set up in 2006. Much of what we have to say will be about how that group has developed its role and how it intends to continue to develop its role.

The other thread of activity to which we will refer frequently is the gateway process. The report refers to that process as an important tool. It is a system of regular reviews of major projects at critical stages; it is a kind of peer-review process that we apply to all high-risk or mission-critical projects with a value of more than £5 million. We now have a pool of more than 200 trained reviewers to carry out that process. They are partly drawn from within the Scottish Government, but they also come from the national health service, the university sector, the Association of Chief Police Officers in Scotland and local government. We have sought to make increasing use of that resource in achieving at an individual project level the broad objectives that the report signals are desirable. One instrument is about the overview, which the report rightly says is important, and one is about the way in which we try to keep close tabs on individual projects.

Thank you. Would Alyson Stafford like to say anything at this stage?

Alyson Stafford (Scottish Government Finance Directorate):

I have nothing to add. I am happy to respond to the committee's questions.

The Convener:

Before we move on to the committee's detailed questions, Sir John, can I ask you about your 200 trained reviewers? You said that they come from a broad range of backgrounds in the public sector, but how many of them have practical experience of major projects as distinct from academic knowledge?

Sir John Elvidge:

It depends what you mean by practical experience. Almost all of them have practical experience of overseeing projects in a senior management capacity. Some of them also have practical experience in more direct project management roles. I do not have a feel for the breakdown of the skill set. I do not know whether Alyson Stafford does.

The Convener:

Have many of them actually managed projects and taken decisions about how they develop rather than just having oversight and an interest in projects? I do not mean any disrespect to academics, but they can pontificate on things without ever putting a hand to the particular task. I am trying to get a feel for where the 200 people are coming from.

Sir John Elvidge:

Sure. I can certainly say that one would not describe many—if any—of them as academics. They all bring their working experience to bear on the process. For example, when I talk about the university sector, I am more likely to be talking about people who have been involved in the capital projects that the universities develop than about people with an academic interest in the issues. What we have is essentially a practitioners club—it is a peer-to-peer club.

Would it be possible to get some further information on that? It sounds interesting.

Alyson Stafford:

We are happy to arrange to provide that extra information. It is important to recognise the strength that we get from having a wide range of people from different sectors. Their experience is useful and they can draw upon it in providing peer reviews.

The gateway review teams always have the resource of an independent expert who operates at all the various levels of the gateway. That person is there to ask challenging questions and ensure that the review team is made up of the right personnel. Some members will be highly experienced and others will be there with inquisitive minds, but that richness is important.

Also, we are drawing into the gateway review pool people who will be running projects in future so that they can benefit from the experience of being part of the wider team. We will get a rolling programme of benefits from the work.

Murdo Fraser (Mid Scotland and Fife) (Con):

It is clear from Audit Scotland's report that, in many cases, the time and cost estimates for major capital projects are wildly optimistic and the final outturn costs are substantially higher. Will you say a little about the work that you are doing to try to improve the cost and time estimates for projects?

Sir John Elvidge:

Certainly—I will say a little and then ask Alyson Stafford to continue, because that question relates to the work of the infrastructure investment group.

There is an important distinction in the report between the accuracy of estimates and the degree of control from the contract stage onwards and in the first phase of planning. The report says, broadly speaking, that the level of good performance doubles as you move from one stage to the next.

I would argue that it is right that the first focus has been on controlling performance against contract costs and timing estimates at the time of entering into a contract. The report brings out the time interval between forming the first estimates of cost and time, and entering into a contract. That interval is highly variable, and in some projects it spreads over more years than one would think desirable. The area in which performance is in greatest need of improvement is the first stage, and that is where we are increasingly focusing our attention.

Alyson Stafford:

I will talk about the work around costs and then about the work around timing.

The cost of a construction project can be expressed in terms of capital cost or in terms of whole-life cost. The estimating processes for capital costs are based on established systematic methods that have been accredited by the Royal Institute of Chartered Surveyors. We have the "Construction Procurement Manual" and there is a team in the procurement directorate in the Scottish Government that specialises in providing the advice, the policy and the direction for that work, so that those processes are clearly set out. The manual states:

"Budget estimates"

for capital costs

"should … consist of a base estimate and a risk allowance."

In 2003, a requirement to bring in optimism bias was introduced through the Treasury green book, for projects that were to begin after that date. Optimism bias is a wonderful technical phrase that is about ensuring that there is an assessment of risk and how inflation can affect those early costs. Although a number of the areas that the review covers began before that key date, it is clear that that bias needs to be built into projects.

Whole-life costing is a key feature in achieving value for money, as set out in the "Construction Procurement Manual". The estimating processes for whole-life costs are much more diverse, and it is fair to say that practice varies across the industry.

It is only very recently—this year—that a standardised method has been published. That will help us in working towards a more consistent and wider application, and it will be an important part of taking forward the spirit and the recommendations of the Audit Scotland report. We can move it on through the infrastructure investment group, so that we are not just considering costs at the construction and the capital stage, but the whole-life costs.

The construction advice and the policy division in the procurement directorate are there to provide the help and assistance that is required. We are gathering material on estimates and costs, and we now have—as I mentioned—the standardised methodology for whole-life costing that was published this year. It is important that all new projects that are taken forward from this point bring that in as part of their estimates.

I will talk about time estimates and then say a little about the role of the gateway process. Although we now have measures and various modelling techniques that will help us effectively on costs, it is fair to say that it will be more difficult to address the timing aspects of projects effectively. The "Construction Procurement Manual" gives advice on the factors that should be taken into account when considering a project's duration. It is important that that assessment is carried out rigorously at the early stages of any project's development, through the work of the infrastructure investment group, which I chair. As the permanent secretary outlined, much of the emphasis has been on our management post contract award—on achieving rigour and ensuring that everything is followed through. However, our work is now turning to the early stages, with the aim of working through estimates and ensuring that rigorous early assessments are made of the risks on timing.

The read-across to gateway is important. I am sure that we all agree that, in parallel with the need for tools and mechanisms to be available, it is important that we follow how projects are lived out and that we continue to test whether people are following the original assumptions rigorously. The gateway process has an important role in that. As the permanent secretary explained, since 2005, it has been mandatory for projects that are mission critical or high risk and with a value over £5 million to go through the gateway process. Gateway has five stages in all. I can go through them in more detail, either in response to the present question or as we continue our discussions.

The five key stages are important, because they give a regular opportunity to continue to test the original assumptions, estimates and processes and the risk assessment of an individual project. A mixture of peer and external review is involved and a reporting mechanism feeds back to all the accountable officers wherever the project may sit. The project therefore gets the attention at the highest levels, either in an agency or in a portfolio area in the Scottish Government. Those follow-up mechanisms, in tandem with the continuing press for better means to support project deliverers, will be important to us in our next stage of evolution.

Murdo Fraser:

Thank you for that very full response. It sounds as though that is work in progress. Willie Coffey has more questions on that issue, but before I pass on to him, I have a question on a related topic. In relation to the departure of final costs and times from the estimates, has the Scottish Government done any comparisons between traditionally funded projects and those that are funded through public-private partnership or the private finance initiative?

Alyson Stafford:

For a comparison between the two, I would need to arrange a specific analysis to be shared with the committee. There is a distinction in the early stages of work before a contract is let. I am sure that colleagues will know that in PFI activity a longer period is required for project definition and specification. We want some of those disciplines to be supported in conventional projects, too, because the more we define up front, the more closely aligned are the early estimates, the prices at contract and the final delivery price.

The Convener:

You say that a standardised method of calculating the whole-life costs of projects has been published. Will that be applied to all projects henceforth, or will you apply it to projects that were commissioned in the past year and are still to be completed?

Alyson Stafford:

The expectation is that it will be applied to projects henceforth but, because it is part of a continuous review of existing projects, it is only sensible that we draw on it to determine whether any realignment is required.

So if we were to ask for the whole-life cost of any major public sector project that is still being developed, we would be able to get it?

Alyson Stafford:

You would for the new ones. We would need to test the standards at a particular point and it would depend on how developed the procurement project was. To be fair, we would have to consider it project by project.

Willie Coffey (Kilmarnock and Loudoun) (SNP):

Sir John Elvidge said that the level of good performance doubles as we move through the phases of a project. Audit Scotland's report showed that, between 2000 and 2007, 60 per cent of a broad range of 41 projects completed over budget and 66 per cent of them delivered late. I ask Sir John to comment on that in light of what he said about the level of performance doubling.

Alyson Stafford mentioned the green book guidelines that have been in place since, I think, 2003. Perhaps some of those guidelines have not been taken to heart, because there was slippage in project performance for four years after they were introduced. It is as though we are not learning the lessons of projects that overrun in cost and time. How can we ensure that the recommendations in the green book are fully implemented and actioned in all the capital projects that we are responsible for delivering?

Sir John Elvidge:

I was cross-referencing two statements in the Audit Scotland report, which I am not fast enough to find in the text. Broadly speaking, the first says that around two fifths of projects come in close to the original cost and time estimates and the second says that around four fifths come in close to the contract-stage cost and time estimates. I referred to the relationship between the two statements. Without taking up a lot of your time scrabbling through the report's individual paragraphs, I cannot give you the paragraph references, but I am confident that I am using the report's language in both cases.

Mr Robert Black (Auditor General for Scotland):

If it helps, paragraph 26 on page 12 of the report and the exhibits above it demonstrate the movements in cost.

Alyson Stafford:

The green book guidelines apply from project inception. A lot of the projects that Audit Scotland examined started quite a bit before those guidelines were introduced, but the infrastructure investment group and the gateway process are part of ensuring that there are other means of ensuring that that work takes place and that the guidelines and policies that exist are followed. Gateway review was introduced in 2005 and it will be a matter of working the stages through. Gateway reviews are going through their various stages in parallel with projects as they develop.

Willie Coffey:

Audit Scotland mentioned that estimates of construction costs varied wildly in comparison with those for general costs. That did not appear to be taken into account; it was as though there was a presumption that inflation would be the same for both, when in fact it was clear that construction costs were going over expected levels. That fact did not appear to fall back into project planning for future projects. Why?

Alyson Stafford:

That is a fair observation about the projects that were initiated in the timeframe covered in the Audit Scotland report. The infrastructure investment group focuses on that area, builds in such considerations and ensures that we keep in touch with the relative inflation rates at any particular time.

Moreover, the construction advice and policy division carries out a degree of what might be described as market tracking, which focuses not on the financial markets but on changes in the construction industry. Through a network of formal and informal contacts, the division takes soundings at various times from different construction organisations and uses that information in considering pertinent levels with regard to a particular programme of activity.

As you might expect, things change over time and we want to use advice from the construction team and from the gateway process of reviewing projects to ensure that people are working with the best available information. We must also ensure that everything is connected up so that all aspects of a project from estimate stage through the awarding of the contract to delivery are strongly aligned. Of course, post-delivery assessments are also important in ensuring that we are getting the benefits down the track.

The very nature of capital programmes means that they take place over a number of years. The fact is that these improvements are being made at a particular point; we have a snapshot of certain areas going back in time, and we want to build on that work.

An element of the gateway process—it is called lessons learned—captures lessons from gateway reviews. Reports have already been produced for 2005-06 and 2006-07, and another report capturing lessons from 2007-08 will be published shortly. Given its timing, the Audit Scotland report will prove valuable in that process. After all, we need to communicate the lessons that have been learned to ensure that people do not have to start with a blank sheet and can benefit from others' experiences.

Stuart McMillan has some questions on skills and expertise.

Stuart McMillan (West of Scotland) (SNP):

The Audit Scotland report says:

"Project management and governance arrangements of individual projects are broadly effective."

How do you know whether there are sufficient in-house skills in the smaller bodies to manage major capital projects?

Sir John Elvidge:

Evidence suggests that smaller bodies often do not have sufficient in-house skills. I was struck by the distinction made in the report between the performance of organisations that undertake many capital projects and those that do so infrequently. As one would expect, we have seen a clear difference in that respect. One thing we know is that smaller organisations are less likely to contain the necessary expertise to do anything that they do infrequently. As a result, we are not seeking to build expertise in every organisation, because in some organisations such expertise would be redundant some of the time.

Instead, our approach is a combination, first, of strengthening both the central expertise that small bodies can draw on—the construction procurement team that Alyson Stafford has referred to several times—and the connections between that central team and the bodies; and, secondly, of ensuring that the small bodies use appropriate external help at the right stage. That tends to be the post-contract stage, when reliance on external project management is greater.

It is harder to bring external help into those bodies at the earlier stage—"harder" is perhaps not the right word; I am sure that consultancy firms would happily sell all our smaller bodies help in every potential project, but that would not be a value-for-money approach to the problem. As such, we have tried to strengthen the central expertise on offer and the connections with the bodies.

Is that akin to what is happening in the police service with the Scottish Police Services Authority? It provides back-office functions for all eight police forces in Scotland. Is that the idea with the construction procurement team?

Sir John Elvidge:

It is different, in the sense that I would characterise work with the SPSA as the development of a shared service. It is bringing together in one place a capacity to do the job that everybody draws on. We offer individual bodies more of a source of advice, and we do not lift the management of an individual project away from a body to the central team. One is essentially a shared execution model; the other is essentially a shared advice and support model.

So a separate entity has not been created; the people are still in the current central Government unit.

Sir John Elvidge:

Yes.

What systems exist to ensure that project teams employ recognised quality standards in the planning and delivery of projects?

Sir John Elvidge:

That question takes us to the heart of one of the general issues: the distinction between giving people guidance and expertise on which to draw and what we might call enforcement—ensuring that people do what they are exhorted to do.

Broadly speaking, we are in a position to give the committee strong assurances about the best-practice guidance, which is constantly evolving. Alyson Stafford gave a good example of better guidance on whole-life costing, and that is one recent evolution. How we ensure that people are following the guidance is a separate question, and it is important to draw a distinction between projects that are inside the Scottish Government and those that are outside the Scottish Government.

Inside the Government, a management chain gives us a straightforward way of ensuring that the guidance is followed. As Alyson Stafford pointed out earlier, we use the gateway process to reinforce the effectiveness of that management chain. When it was originally conceived, the gateway process was designed as a source of peer advice for those running projects. The gateway review might involve criticism, but that criticism was given to the person who was running the project on the assumption that they would take that critical input and use it to correct the project. We came to the conclusion that that was perhaps not 100 per cent secure, so we moved away from the purity of a gateway model that insisted that the feedback was private to the project team. We now share the feedback with the next person up in the management chain and the accountable officer for the relevant budget. If the gateway review says at any stage that the guidance is not being followed, we have an effective alarm bell, which will allow more senior managers to move in and deal with the situation.

For projects outside the Scottish Government—which include a lot of the projects that the report covers—there is a completely different set of questions about enforcement. There is a much wider set of issues that concern the relationship between central Government and non-departmental public bodies, and the meaning of the arm's-length principle when it is translated into a field such as the one that we are discussing.

It might be sensible at this point to ask Alyson Stafford about the discussions in the infrastructure investment group about the intrinsically tricky issue of how to ensure that guidance is followed in organisations that one does not directly manage.

Alyson Stafford:

The infrastructure investment group is made up of the lead directors across the Scottish Government portfolio areas. Each of those directors has a relationship with a number of arm's-length bodies, either by being a Fraser figure for an agency, or by playing a leading sponsor role through a sponsor division in their own area.

The emphasis of the infrastructure investment group is: to ensure that each of those lead directors is much more closely linked to the activities of those bodies; to consider how that approach impacts on the overall budget management of our capital programme for the whole of the Scottish Government year on year; and to examine some of the standards and disciplines that those bodies use. That has been reinforced through specific directions to those individual directors in relation to where their accountability lies.

The statement of internal control lies within our annual process of assurance, which supports the production of the consolidated accounts. Through that mechanism, each director with those responsibilities must, in providing their assurances to their own accountable officers and ultimately to the principal accountable officer, address how they interact with those bodies and how they ensure that the funds that are being disbursed through that route are in line with the policies, processes and systems that we want to put in place.

That has all been reinforced, particularly over the past year, so there is much more of a signal and a requirement for directors across the Scottish Government to have those links. As I said, we have started to examine how individual budgets and the overall capital budget are managed. To give you an indication, the capital budget for the Scottish Government last year, in the areas that fall within the core aspects of management, came in within £2 million, which is just the right side of the line. That is a testament to the close working that is taking place and the links that directors within the organisation have to the NDPBs and other bodies through that route and those mechanisms.

Returning to Stuart McMillan's earlier question, members will not be surprised to learn that we have a series of specific skills development courses for senior people, to ensure that the early stages of the strategic project—the definition—can be supported. We have defined the competencies that people require in various areas. That is part of the Scottish Government's skills for success initiative, which contains an element on specific delivery skills for programme and project management. As well as being clear about where the responsibility sits and how people should carry out that role, we are ensuring that they have the tools to do that. That is true both at the strategic level and, as the permanent secretary explained, at the operational or delivery level.

Andrew Welsh (Angus) (SNP):

Does your system act after the event or can it pick up on problems before they become major? You mentioned the arm's-length principle in your relationship with outside bodies, and you said that an alarm bell sounds if something goes wrong, but is that system reactive rather than proactive?

Sir John Elvidge:

Yes and no. It is reactive in the sense that it is a review process so it always comes in after the event. However, it comes in not at the end of the project but at stages throughout the project. In that sense, the intervention can be made between the point when best practice is not being followed and the point when the consequences of that materialise in the way in which the project is being taken forward.

Strictly speaking, the process is always backward looking, but the point of having frequent gateway reviews at stages during the project is to try to get a bit of forward-looking action so that a mistake at the beginning does not necessarily mean that there is a poor outcome at the end.

Does that mean that you, as the principal accountable officer, are made aware of problems that are developing in a project, rather than the end of the project being reached before someone reports that there is a problem?

Sir John Elvidge:

I would not be made aware of that personally, except in the one area in which I am a budget accountable officer as well as the principal accountable officer. The accountable officer for the portfolio budget will be made aware if the gateway review shows that there is a problem with a project. That is one of the changes that we made in the past couple of years.

Are you suggesting that the accountable officers do not necessarily alert you, as the principal accountable officer, to emerging problems?

Sir John Elvidge:

Yes. Broadly speaking, their first instinct will be to try to fix the problem rather than tell me about it. In honesty, it probably depends how severe the problem is. I regularly talk to all the accountable officers one to one—on average, no less than once every two weeks—so if something is particularly worrying them about a major project, they will tell me. However, they do not automatically pass on the warning of a red gateway review assessment.

Let us consider a specific example. Were you made aware of emerging problems in the Stirling-Alloa-Kincardine railway project?

Sir John Elvidge:

Yes.

At what stage did that happen?

Sir John Elvidge:

You are testing my memory there.

The Convener:

If you cannot remember, perhaps you could revert to us with that information, because the issue is important. Are problems being picked up, and if so, what action is being taken? When you reflect on that and revert to us, will you tell us how many projects were brought to your attention as having significant risks in the past two years?

Sir John Elvidge:

I will do my best. As I said, the alerting normally takes place in conversation rather than on paper, so it will take a bit of digging into people's memories.

The Convener:

Can I tease that out? We are talking about major projects that involve millions of pounds, yet in terms of an audit trail and accountability, in general nothing is put on paper. Conversations take place. Is that not a strange way to manage a serious potential problem?

Sir John Elvidge:

We are getting into the theology of levels of accountable officer responsibility. I designate a series of accountable officers to manage discrete budgets because, if everything flowed to me, individual issues would not receive the attention that they need. The model is not built around the idea that I intervene personally in everything. The purpose of having the designated accountable officers is so that they take responsibility for dealing with issues within their budgets and tell me only if they experience some particularly acute problem. There is no institutional complacency—some of the most senior people in the organisation are brought in through their accountable officer roles to bear down on the problems.

The Convener:

I presume, therefore, that there must be records of warnings and alerts at accountable officer level, rather than at your level. From an audit perspective, those should be available if anyone wants to find out when a problem was first identified and what action was or was not taken. I accept the fundamental point that you cannot be involved in the micromanagement of every project. However, you are responsible for managing the accountable officers. How can you manage them, and how do you know whether they are doing a good job, if they do not tell you that there is a problem and there is nothing on paper to indicate that there is a problem?

Sir John Elvidge:

My safeguard system is sitting beside me. There is no realistic prospect of an accountable officer concealing from me a problem that has not been successfully addressed, not least because Alyson Stafford, as director of finance, would pick up the evidence of that, and she provides a second channel of information to me. I can say to you, hand on heart, that I do not suffer from accountable officers not telling me when they have problems.

That does not necessarily answer my question. I asked how you know whether they are doing a good job—whether they are competent—if you have not seen any written evidence of how they are managing.

Sir John Elvidge:

I have a series of measures of whether they are doing a good job. Again, the infrastructure investment group's work is important in that regard because it gives me assurance across the piece about how individual projects are being managed, so I certainly find out about failures. I also find that people are not particularly reticent about telling me about successes, so there is not much danger of me not knowing about the good bits.

You say that you find out about failures, but does that happen after the event? We are more concerned that you should be in a position to take action to prevent emerging problems from becoming failures.

Sir John Elvidge:

Let us try to be clear about what we are talking about: we are discussing the example of a project that had got into difficulty and in relation to which an accountable officer had not taken successful action. It must be right that the accountable officer is given the room to do their job, and I am confident that, if successful action was not taken, Alyson Stafford would tell me so through her overview. There is no absence of channels for telling me when the management of a major capital project might be in difficulty.

Okay. Does Alyson Stafford want to say something?

Alyson Stafford:

Yes. This would be a good point to say something about the gateway process.

Could you do so succinctly? We have a number of other questions to ask.

Alyson Stafford:

Of course. There are five stages in the gateway process: business justification; delivery strategy; investment decision; readiness for service; and gateway 5, which is the operations review and benefits realisation, after the delivery of the project. At each stage, a review is held by the review team that we described earlier. At times, more than one review will be held for each stage; there is scope for multiple reviews.

The permanent secretary has already said that, at times, reviews flag up a red gateway. "Red" means that corrective action is required. It does not mean that the project is doomed, and it does not mean that nothing can be done; it means that corrective action is required. For any of the stages, such a flag would go to the senior responsible owner of the project. It would be reported to the accountable officer as well. As you would expect, all our efforts are made to ensure that we deliver programmes and projects successfully.

Gateway is designed with that mechanism so that we can appraise projects regularly. We want to deliver the required outcomes for infrastructure investment across Scotland. Gateway is there to let us do that. It runs in parallel with the project so that we can minimise all the problems that committee members have been talking about. Members have been talking about projects going off track; gateway is about keeping projects on track. It is a review mechanism.

Each year, the infrastructure investment group identifies some key areas of work that each of the directors needs to link into. Accountable officers have to be good custodians of the public purse in each financial year. As finance director, I send a report to the strategic board each month. Part of that report will mention all the programmes of activity in the Scottish Government that are part of the capital budget, and it will set out the programmes that are over a certain level, asking whether they are on track and how they match up to the budgets that were set for them. Therefore, around the strategic board table, we can regularly assess the variants, if any emerge. As the permanent secretary has said, there is therefore another mechanism: over and above people's individual responsibilities, we have a collective way of taking stock every month.

Before I bring in James Kelly, do Stuart McMillan or Andrew Welsh have anything further to ask on this issue?

Andrew Welsh:

You have set up a structure in Government, with a gateway team, a gateway review and a five-stage process, but we also have to consider realities on site—as we know only too well in this building. Reports come in, but how can you compare those reports with what is actually going on? How can you close the reality gap, to ensure that the information that you receive is accurate and states what is really happening on site? For example, we saw the flaws in the M74 completion project.

Alyson Stafford:

Gateway, with its reviews and peer reviews, is our mechanism for that. When I described the make-up of the review team, I said some external people are always on the team. When I say "external", I do not mean simply someone from another part of the public sector in Scotland. Although we have trained reviewers from the universities and from the NHS, for example, we also get external people on the review team. That offers another check and another degree of independence.

Use of the gateway process has been mandatory since 2005. Several projects are still going through the various gateway stages. The gateway is one of our key mechanisms.

In life, we tend to hear of disasters rather than successes. Without breaching confidentiality, will you give an example of the system picking up and solving a problem?

Sir John Elvidge:

I have an example in mind, but the confines of confidentiality are a problem. I will think about what I can say. The example that was prompted by your question is of the system being given what was in effect false information about what was happening on a project.

Did the system pick that up? That is what I am after.

Sir John Elvidge:

The system picked up the situation and it worked. The project's management was changed and, at some cost, we got back on track. My difficulty is that, for reasons of confidentiality, I can tell you nothing about the identity of that project. That is not tremendously helpful for you, because you must trust me that it exists.

I do not know whether Sir John Elvidge has just encouraged people to think about freedom of information requests. He might have made a rod for his own back.

James Kelly (Glasgow Rutherglen) (Lab):

Post-project evaluation is critical. It looks back to decide whether a project has succeeded and allows lessons to be learned for future projects. Alyson Stafford spoke about the fifth gateway review, which was the benefits realisation process. What systems measure success in achieving the benefits of a project that are stated in its business case?

Sir John Elvidge:

Audit Scotland's report brings out the fact that the need to improve is strongest at that stage. I return to the distinction between having guidance and enforcing it. For some time, the guidance has said that post-project evaluation should be mandatory. It draws a distinction between two kinds of post-project evaluation. A self-contained process, which we call the post-project evaluation, evaluates how the process went and goes into issues such as how effectively the project was scoped and managed, which the report mentioned. A separate process, which we call post-occupancy evaluation, is about whether a project delivered the benefits that it was intended to deliver, never mind whether the most fantastic procurement job in the world was done.

A system exists, in that the framework is clear and the guidance makes it clear that those processes should be followed. However, the evidence tells us that compliance is not nearly as good as it should be. That takes us back to territory that Alyson Stafford has talked about.

Alyson Stafford:

That links into the infrastructure investment group and the gateway process overall. At the helm of the work on post-project evaluation and post-occupancy evaluation is the Government's construction advice and policy division. The procurement manual for construction schemes sets out how performance is measured in specific areas. That means that not just a subjective assessment, but a substantive assessment takes place. It is important to do such assessment and to have comparability with other projects.

James Kelly:

Where the business case states that there are particular cost benefits of going ahead with a project, will the benefits realisation process in the fifth gateway review look at the statement of those cost benefits and at whether they have been achieved, or are in the process of being achieved? Can you make that clear?

Alyson Stafford:

Yes. I will draw on the post-occupancy evaluation checklist that is used in reviews. As a minimum, it assesses the achievement of the business case objectives to date; the benefits to date against those that were forecast and the other benefits that were realised and expected; the extent to which there is continued alignment with the business strategy; the effectiveness of actual improved business operations, which may include function processes and staff numbers; the ways in which to maximise benefits and minimise whole-life costs; the risk assessment around that going forward; and business and user satisfaction. We also expect regular post-occupancy reviews to take place over the operational life of a facility. That chimes very well with gateway, which is not a single event process—we look to gateway 5 being achieved.

Therefore, depending on the life of a project or asset, we expect to see regular evaluation. If we expect a 20-year benefit, we expect gateway reviews to take place at intervals during that time to ensure that we get the benefits from the investment that was made; we also expect the evaluation to feed back into the process. I return to the point that we made earlier on the need for a continuous learning loop in our work going forward.

James Kelly:

Learning the lessons from projects and feeding those into future projects is important.

As Sir John mentioned, compliance in this area is obviously of concern. The report noted that in 21 of 43 cases, the project team conducted no post-project evaluation. What steps have you taken to ensure that compliance improves and that all project teams carry out post-project evaluations in future?

Alyson Stafford:

The change is that it has been made clear that the gateway process is now mandatory for all projects that are mission critical and/or high risk, with a budget of more than £5 million. That is the clear standard by which the Scottish Government must live and work.

Andrew Welsh:

There is no consistent approach to the provision of information on major projects and no regular publication is made available to the Parliament or the public to show how major projects across Government are performing. What plans are there for the Scottish Government to report publicly on projects?

Sir John Elvidge:

I will say something initially. We are on a journey. We now have two infrastructure investment plans, the first of which was published by the previous Administration in 2005, and the second by the present Government in 2008. The plans provide the first step towards a clear overall picture of investment activity. The second step is the database that the infrastructure investment group has constructed to provide a framework for tracking all projects.

When we think about the topic, we make a distinction between what we manage ourselves and what NDPBs are managing. That is an important ingredient in the complexity. The question is: what is the next step forward? Two issues are involved: the quality of data for individual projects; and how one moves forward with what is in public domain, starting with the infrastructure investment plans. The honest answer is that we have not reached conclusions about what the next step on that journey should be. This might be where Alyson Stafford comes in.

Before we bring Alyson in, is the journey one on which you are doomed to wander for eternity, or is there a specific timetable? If so, what is it?

Sir John Elvidge:

It is tempting to say that improvement is a journey that never ends. I am genuinely always hesitant to say, "Once we get there, we will have done everything that can possibly be done and that is it." This is not a "Maybe sometime" journey. We are looking to take regular steps and make progress. That is where the relevance of the work that Alyson Stafford is leading will help us to get a handle on the likely timescale.

Yes, but will you then report to Parliament and tell us what the target is for each step so that we can have some assurance that you are making progress?

Sir John Elvidge:

I am sure that we can give you an account of our ambitions for the steps on the journey. We can say quite clearly that the next step is to develop our database, and Alyson Stafford might be able to give us a sense of the timescale for that.

Andrew Welsh:

Infrastructure projects have been going on for a long time. You have just said that you have mechanisms for monitoring them, so you must know exactly what is going on. Earlier, I mentioned the reality gap. What information is available as the project progresses? Is the project on schedule? Are things being delivered? Surely all that information should be going through the monitoring structure that you already have. What is the problem?

Alyson Stafford:

I will respond to both those points.

The infrastructure investment group is focusing on having a database that charts all the information. On your questions, I have been considering how much of that information is in the public domain and at what stages. There are various elements to seeing a project through, as well as the interfaces with external contractors. I am concerned to ensure that we get all the value-for-money benefits that we have talked about by bringing in the life-cycle costing and getting the benefits of the individual projects as they go through. We have to have in our armoury the information that we need to continue to get the best arrangements with our contractors so that we can get the contracts and the facilities in place.

So, although it is about having the information, we have to think about commercial confidentiality so that we can still get the best deals possible as we go through any infrastructure project. We need to think carefully about getting value for money at the same time as reassuring you that we have the database to work those various issues through.

We have opportunities at intervals to take a snapshot of the project. The most obvious snapshot is our annual accounts, which contain our capital budget for the year. Obviously our programme of activity is in line with our capital phasing of investment. We have to have the budget there. We make the investments and we work that through. At the end of each financial year, in effect we draw a line under how much of our resources we have committed to specific projects and programmes of activity. At that point, we are clear about what we have delivered and where we are. We get a value for projects still under construction and we use that to explain any variances in individual rows of accounts.

One of the valuable things will be to think about how we use the information in the annual accounts. The annual accounts are part of our structure of reporting and are in the public domain. People can rely on them, because they go through an audit process. Those who were at the Finance Committee yesterday will be aware—

Andrew Welsh:

We are talking about informing the public and Parliament of progress on projects. We are talking about types of information. Everybody understands that some information will be confidential, but we want to know about the reality of a project as it progresses. We are also talking about clarity. It is important to give the public access to information and to state clearly what is happening. Projects have a start, a continuing process and an end. It would surely be appropriate from the start of such a process to let the public see simpler information and it could build up to greater complexity. The information that the committee would seek is probably different from what the general public would want. It becomes complex if you get all the information that is in the system.

We are not asking for Rome to be built in a day, but it would be welcome if we made a start and made fundamental information available to Parliament and to the public. Scotland performs could surely be a model for such information.

Alyson Stafford:

I am happy to look at the read-across from what we are talking about today to Scotland performs and to see how that links in. Scotland performs is about charting our progress on outcomes, and infrastructure is part of achieving those outcomes. I am happy to take that suggestion away and work on it with colleagues.

We are all interested in outcomes: the end-product is what is important.

Alyson Stafford:

Yes.

Can I move on?

Nicol Stephen would like to comment.

Nicol Stephen (Aberdeen South) (LD):

My question relates to that point.

Sir John, you mentioned the information that flows through to you as the accountable officer. We have talked about the information that is provided to Parliament and to the public. I am interested in the information that is provided to ministers as a result of the gateway process and in respect of the overall management of major capital projects. I would like to know how regularly such information is provided and whether it is provided consistently across different departments.

Obviously, the biggest set of projects at the moment is the M74 extension, the Aberdeen western peripheral route, the Forth road bridge replacement and the Borders railway. Those are big projects. I am interested to know how often the Minister for Transport, Infrastructure and Climate Change and John Swinney, the Cabinet Secretary for Finance and Sustainable Growth, get updated costings for those projects. Do they get such information monthly or quarterly? In what form is it provided? I do not want to know the detail, but I would like to know the frequency with which such information is provided and the shape and quality of what is provided to ministers to allow them to take appropriate action and to inform Parliament when that is necessary.

Sir John Elvidge:

We will have to come back to you on the detail. I know enough from my conversations with the ministers to know that they are happy with the information flow that they get, but I do not know enough to describe either its form or frequency. We will come back to you with precise information.

As Nicol Stephen knows, in this respect the system tends to mould itself around the working preferences of individual ministers. We have no reason to monitor centrally how the system works, provided that individual ministers are happy with it and provided that the information flow comes to us. There is a separate question about how the information that we gather through the processes that Alyson Stafford has talked about flows to ministers.

I promise to get back to you on your main question about how it works at the level of individual ministers. Perhaps Alyson can say a bit about the secondary question of how the aggregate information flows.

Alyson Stafford:

Yes. The aggregate information is drawn on each month when I pull together all the information that comes from the feeds of different parts of the Scottish Government on the financial performance of the Scottish Government. Alongside that, there is a feed of information that breaks down the capital figure of our budget into programmes of activity with a specific attention on programmes within each area of £50 million or more. There is a degree of aggregation when looking at the whole picture. That information comes through and I use the infrastructure investment group gathering to scrutinise that and test the confidence of the individual directors who lead on those areas in the robustness of the information.

It is not just about having a mechanical feed of figures that come through. A dialogue takes place in which I ask the directors, with their other sources of information and contacts with various people, whether the financial monitoring rings true with the delivery, to ensure that there is no gap between perception and delivery. There is testing at that point, and that is pulled together in the material that goes to the strategic board. There is then a chance for anything of an exceptional nature to be flagged up. Specific commentaries are provided in the briefest of terms, but are sufficient to say what is happening on each of the programmes.

Again, the whole idea is to maximise the use of our budget in any one year and to get the value that we want from it. That is our mechanism for pulling that together.

On maximising the use of budgets, what systems are there to ensure that priority is given to projects within the capital investment programme that will provide direct benefits?

Alyson Stafford:

That is an interesting question. The investment in individual capital projects is—as you would expect me, as finance director, to say—linked to budgetary decisions. It is fair to say that those budgetary decisions—the decisions about how much is allocated across individual portfolios and how those portfolios apply the funds—are very much ministerial decisions. Ultimately, it is for the Cabinet to decide on the mix across all the portfolios, and there are decisions and prioritisations within that. That is very much part of the whole area of ministerial decision making on prioritisation. The investment must be linked to the budgets, and that is where the conversation takes place.

Can you assure us that project proposals receive robust, independent challenge before they are accepted into the major capital programme?

Sir John Elvidge:

That depends on what the word "independent" means in that context. I think that we can assure you that there is an increasingly robust challenge through the mechanisms that Alyson Stafford leads. That is a robust function not just of the finance directorate, but of a wider circle of colleagues with expertise in overseeing capital projects. In that sense, the answer to your question is yes. If you asked me whether there is a routine external challenge, the answer would be no.

Andrew Welsh:

I would like assurances about such challenges. At the beginning of the M74 completion project, there was no clear plan for managing and controlling the project's total cost. The only allowance for risk was implicit within the range of cost estimates for the project—there was no explicit allowance for risk or bias. There was no agreed basis for accounting, controlling and managing the significant risk element in the estimate, nor any explicit strategy for doing so. There were also various other flaws. Can we be assured that that will not be repeated?

Sir John Elvidge:

Yes, I think that you can. Part of the answer is the development of Transport Scotland as a change that the previous Government made to the way in which transport projects are managed and the evolution of what that body of specialist expertise is able to bring to project management in the field of transport. The other part of the answer is the evolution of what we might call the challenge community, which Alyson Stafford leads through the infrastructure investment group.

So, there is a mechanism that has learned from past lessons.

Sir John Elvidge:

Yes.

Cathie Craigie:

The Audit Scotland report recommends that the Scottish Government strengthen strategic direction and investment planning through stronger, Government-wide co-ordination and more constructive challenging of projects to help to deliver them better. Both Sir John Elvidge and Alyson Stafford have spoken about having a database that can provide a snapshot of what is happening, but that does not give any real-time update and it is not a check across the portfolios on major capital projects and performance outcomes.

It seems to me that Audit Scotland has made a sensible recommendation that would make the situation much better if the Government would take it on board. From the answers that have been given to Andrew Welsh this morning, I am not satisfied that there really is a move to get that better flow of overall information and a better exchange of information between different departments. Can you say anything more about it that might satisfy me?

Sir John Elvidge:

We will do our best. I am disappointed that we have left you unconvinced about that. The work of the infrastructure investment group is, essentially, our response to that recommendation in the report, with which we agree strongly. My judgment—it is easier for me to say this than for Alyson—is that Alyson has driven forward our capacity in a marked way over the past year and a half using that structure.

We absolutely agree that there is scope to do more; however, it is a question of proportionality. One of the other threads of our work is the burdens that we place on organisations throughout the public sector—the information flows that we demand of them. There is an obligation on us to demonstrate that the information that we demand, in particular from NDPBs, is proportionate to the value that we get out of using it; otherwise, we could generate a lot of cost in the public sector without achieving a proportionate benefit.

In this sphere, that judgment must hinge on an assessment of how many projects go wrong that would be improved by our intervention in requiring a more regular information flow to us. That is a judgment that we have to make. I make no presumption about where that judgment would lie; that is simply the process that we must go through if we are thinking about a step change in the information that we require from public bodies. Requiring a shift towards real-time information flows, as opposed to regular snapshot reporting, would represent a significant shift in the demands that we place on public bodies. That is the issue that we must wrestle with.

Alyson Stafford:

It is fair to say that the infrastructure investment group has focused on ensuring that we get the maximum out of the budget. We can be judged by our outcomes, and in the past two financial years we used all the capital budget—which was in excess of £3 billion in each of the two years—to within a margin of less than £10 million. That evidence reinforces what we are saying about our work.

Some things are tangible now, but we know that we are moving into times when our financial position will be much more constrained. From the spending review, we know our settlement for the next three years. Not surprisingly, my emphasis with the infrastructure investment group has been to say, "Right, we need to make sure that we use the money effectively and efficiently. We need to get the benefit from the investments and from ministers' decisions." In the past two years, the evidence shows that we have achieved our aims and kept within fine margins. That has been done through careful interaction between directors on the various schemes that are under way, and it has been really important. If we generate any underspends, that money will not be available to us until the next spending review in 2011-12. That is a huge incentive for us.

As we have said, we are also shifting our attention towards life-cycle costs—a standard has been published this year—and towards project evaluation and outcome evaluation. We are moving the focus from getting the best from the budget and are now looking left and right to see what is in the pipeline. We have to consider how to bring all the projects that have been initiated since 2005 through the gateway process, taking into account the optimism bias and the risk. Budgets are tight, and we cannot afford to have anything going off track. We have to make the most of our investments.

Post-project work is where we learn lessons and evaluate, and such work is very much in with the bricks of the infrastructure investment group. However, we focus first on getting the best out of the budget that we have. Two years' worth of evidence shows that we have delivered on that. We are looking along the pipeline and looking out for events.

Skills development has been touched on, which is an important issue. We must also be aware of other strategic issues and policy initiatives, such as those relating to sustainability. Experts have been involved in giving us a steer on sustainability issues. We have also been considering the national planning framework. Time and cost issues are important in the early stages, and we do anything that we can to help to keep a project running smoothly and to minimise the disruption that external factors can cause.

Shall I move on, convener?

I am watching the time. If you want to ask one further question, that is fine; but if there is anything else, we can follow it up in writing.

How does the Government decide on its priorities for projects? Also, we have heard from the Government about the Scottish Futures Trust. What improvements in the procurement and project management of programmes will come from that?

Sir John Elvidge:

Those are two big questions. I will try to give some headline responses. We need to recognise that Audit Scotland's report describes project commissioning over a long period, in which the answer to your question about how prioritisation is done changed quite a lot. I will leap into the present. Now, prioritisation is achieved through the Government's structure of objectives—the single overarching priority of economic growth, the series of targets that relate to that and the five strategic objectives. Prioritisation is now handled in a way that tries to bring projects back to their contribution to those overarching objectives.

It is harder to do a headline on the Scottish Futures Trust, but I will try to draw out the main connections. One of the trust's objectives is simply to improve the efficiency of procurement. That takes us back to the territory of smaller public bodies commissioning capital projects, but it does not end there. The benefits of aggregating procurement activity are a key thrust for the trust to explore. We also expect it to interest itself increasingly, although not necessarily as its first priority, in working its way into other questions that we have discussed this morning. I cannot jump to the answer about how the trust will come up with fresh ideas to interact with those questions. Broadly, I expect the trust to start by considering the benefits of aggregation and of more co-ordinated procurement action, which are directly relevant to what we have discussed, and to move on as it develops as an organisation to consider wider questions.

The Convener:

We will reflect on whether we have covered all the issues. If we have not, we will write to you. I thank you and Alyson Stafford for a full session. Some of the evidence was technical and specific. We might well wish to return to issues that relate to capital projects or other matters. We all realise the significance of good management and of using scarce resources efficiently. As Sir John Elvidge said, Audit Scotland's report was exceptionally good. It should drive better services for the public.

I will allow a five-minute break for the changeover of witnesses.

Meeting suspended.

On resuming—