|
1
|
- ACTORS, ROLES
- AND OUTPUTS
|
|
2
|
- Identify major actors and explain the relationship between each of them
- Explain the dynamics between local and international actors
- Identify major mechanisms for communication, reporting, reviewing
approval
- Identify and discuss where are the ’centres of gravity’ for
decision-making
|
|
3
|
- Identify specific roles undertaken by different actors during each phase
of the GEF project cycle
- Explain the complementarities between different roles, both at each
phase, and between different phases
- Discuss their own roles within the GEF project cycle
|
|
4
|
- Identify and describe the sequence and relationship between each of the
major outputs
- Review the pre-requisites involved for the progressive and successive
development of the TDA/SAP
- Discuss and reflect upon the
integrated nature of the GEF project cycle, from preliminary project
request to full project implementation
|
|
5
|
|
|
6
|
|
|
7
|
|
|
8
|
- The PC is used as the technical core for a (concurrent or subsequent)
funding submission to the GEF (usually PDF-B)
- The PC should be approximately 10 - 20 pages long
- The PC must follow the requirements of the GEF Project Review Criteria
and comply with the GEF Strategic Priorities
- Check with the harmonised guidelines and template documents for drafting
a concept paper/PDF-B proposal
|
|
9
|
- The project's global and transboundary benefits
- Linkage between the project and GEF focal areas, Operational and/or
strategic priorities
- The national/regional baseline
- The region’s transboundary concerns/problems, root causes of the
problems, and the activities that will eventually address these causes
at their source.
- Focal points in each of the countries involved
- All key stakeholders
- The proposed work-plan (on the basis of a tentative budget which is not
included in the PC)
- Indicators on which monitoring and evaluation can be based
|
|
10
|
|
|
11
|
|
|
12
|
- Concept agreement review and pipeline entry is a requirement for all
projects that require approval by the Council
- The concept agreement review is the first GEF decision point prior to
the project proposal entering the GEF pipeline
- A project must be listed in the GEF pipeline document circulated to the
Council, prior to the work programme in which the project is included
for Council approval
- Pipeline documents are published quarterly
|
|
13
|
|
|
14
|
|
|
15
|
- The FP Brief is the primary vehicle for presenting the project proposal
for approval to the GEF Council
- The FP Brief evolves from the project concept. It should be developed in close
consultation with the GEF Coordination Office.
- The FP Brief should be consistent with the GEF Instrument, the
Operational Strategy and the relevant Operational Programmes
- Written government endorsement from participating countries is necessary
- The project executive summary should be submitted following the template
distributed by the GEF Secretariat
|
|
16
|
- Project executive summary
- Incremental cost analysis
- The STAP Roster review
- The country operational focal point endorsement
- A work plan for the TDA/SAP implementation phase including budgets
- Public involvement plan
|
|
17
|
|
|
18
|
|
|
19
|
|
|
20
|
|
|
21
|
|
|
22
|
|
|
23
|
|
|
24
|
|
|
25
|
|
|
26
|
|
|
27
|
|
|
28
|
|