5.12 - Develop SAP workplan and budget
To aid the development of a workplan, the key milestones introduced on the previous page are presented in a simple checklist below, together with an indication of who is likely to be the lead individual or organisation for the action, and who else is involved and approves the action.
Activity Checklist
|
Activity |
Project Manager |
Steering Committee |
SAP Development Team |
Expert/ Consultant |
Countries |
|
L |
X |
||||
|
L |
X |
X |
X |
||
|
X |
L |
X |
|||
|
X |
X |
L |
|||
|
Strategic thinking meeting 2: Ideas, Opportunities and Options |
X |
X |
L |
||
|
X |
X |
X |
L |
||
|
L |
X |
X |
|||
|
L |
X |
X |
|||
|
Adoption by steering committee |
X |
L |
X |
||
|
X |
X |
L |
L – Lead; X – involved
In addition, A generic Gantt chart showing key SAP Development milestones for a typical 5-country project is shown here.
Defining the timeframe for SAP development
As with the TDA development process, the time frame for the development of the SAP will vary from project to project. Some projects have completed the activity within a year whist other projects can take much longer. Again, much will depend on the number of participating countries, the complexity of the project and the budget available. Ideally SAP development should take about 12 to 18 months, although it might span more than one GEF intervention (e.g. the SAP document, or a technical draft of the SAP might be produced during one GEF project, along with the TDA, whilst further SAP development, endorsement and implementation might occur during subsequent projects). Examples of typical SAP development times are presented in the Table below.
|
Project |
TDA Development time (months) |
|
Black Sea |
12 (Technical draft only – not endorsed) |
|
Guinea Current LME |
24 |
|
Yellow Sea LME |
24 |
|
Nubian Aquifer |
12 (Technical draft only – not endorsed) |
|
Lake Chad |
12 (Technical draft only – not endorsed) |
|
Dnipro River Basin |
18 |
|
Rio de la Plata |
18 |
Finance and Budgeting
Good financing and budgeting is a challenge to most IW projects and consequently TDA/SAP development. The Project Implementation Plan will define the budget for the SAP component of any given project. Consequently, it is important to be aware of what is possible and what is not in terms of SAP ambition and have a good understanding of how the respective governments will use the SAP. For example, can the SAP be an outline or technical SAP such as those produced for the Prespa Lakes or the Black Sea? Or does it need to be a much more detailed with specific actions to implement (e.g. Dnipro River Basin)?
In other words, how the SAP is developed and how it will be used will have a significant effect on the budget needed. More information on Money Matters can be found in the GEF IW Project Management Manual.
