LGCDP M&E Framework
LGCDP M&E Framework
LGCDP M&E Framework
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>LGCDP</strong> Sample Surveys do complement the MC/PM assessments and<br />
administrative data in two important ways: First, sample surveys can directly address<br />
the citizens. Second, sample surveys can provide – at least initially – administrative<br />
data from VDCs on a sample basis before the MLD is able to set up a comprehensive<br />
data collection system.<br />
Recommendation:<br />
⇒ conduct a sample survey every 2 years: more often will not add much<br />
value to the information gathered, less often is too late to inform decisionmaking<br />
for <strong>LGCDP</strong>; include the questions from the <strong>LGCDP</strong> M&E framework<br />
in all surveys (see Annex 3)<br />
⇒ make use of external quality control for sample surveys; sample<br />
surveys are expensive and methodologically challenging; if the sampling<br />
methodology is not sound (and not perceived as being sound), the<br />
credibility of <strong>LGCDP</strong>’s entire monitoring system is at stake<br />
⇒ even if more administrative data is collected from DDCs and municipalities,<br />
continue using sample surveys for at least 6 more years to provide quality<br />
control and triangulation to data obtained through administrative<br />
channels<br />
Indicator tracking combines key data from the MC/PM Assessment, the sample<br />
surveys and additional data from the MLD and other external resources. The<br />
indicator data will be updated on a trimesterely basis, since monthly data collection<br />
would be cumbersome without adding much value. Performance indicator tracking<br />
will be done using the indicator tracking sheets described in Annex 2.<br />
Recommendation:<br />
⇒ update indicator tracking sheets described in Annex 2<br />
trimesterely as simple key tool for tracking indicators<br />
The <strong>LGCDP</strong> programme document does currently not define risks at any level, with<br />
the only exception of fiduciary risks. Before a system can be set up to monitor risks,<br />
these risks need to be clearly defined.<br />
Recommendation:<br />
⇒ clearly define risks for <strong>LGCDP</strong> at at least two levels (output to<br />
outcome, outcome to purpose) as a first step to monitor risks<br />
23