Monitoring and Evaluation of Government Projects (MNG 0001 & PAd Studies) — Study Guide for South Africa

Monitoring and Evaluation (M&E) is the backbone of good governance in public-sector project delivery: it answers whether activities are happening as planned (monitoring) and whether they are creating meaningful change (evaluation). In South Africa, M&E is increasingly embedded in frameworks such as the Public Finance Management Act (PFMA), Treasury Regulations, and Performance Management expectations across national and provincial departments. This study guide is designed to support exam preparation for learners and students in Project Management for Public Administration (SA Government Focus), including modules commonly aligned with UPD/MNG-style public administration coursework (e.g., MNG 0001-level project management foundations) and related Unisa and CUT-style public administration and management learning outcomes.

The focus is not only on definitions, but on exam-relevant processes: designing results chains, building indicators, collecting data ethically, using evaluation designs correctly, and reporting findings so they actually influence decisions. You will find consistent terminology, step-by-step methods, and practical examples that reflect how government projects are structured and assessed in South Africa.

1. Foundations of Monitoring and Evaluation in South African Government Projects (PFMA, Performance, and Results)

1.1 Meaning of monitoring vs evaluation (and why exams always test it)

In government projects, monitoring and evaluation are related but distinct functions.

• Monitoring is the continuous or periodic tracking of project implementation. It checks:

  • Are activities being delivered on time?
  • Are outputs produced with expected quality?
  • Are budgets and procurement moving as planned?
  • Are risks and issues escalating or being contained?

• Evaluation is the systematic assessment of the project’s design, implementation, and outcomes. It asks:

  • Did the project achieve its intended outcomes?
  • Why did it succeed or fail?
  • What contribution did it make relative to what would have happened anyway?
  • Are results sustainable and scalable?

A common exam trap is confusing the two. If you are asked, for example, “Explain the difference between monitoring and evaluation,” a strong answer typically includes both:

1. Timing (monitoring often continuous; evaluation often mid-term/end-term/periodic), and
2. Purpose (monitoring ensures implementation; evaluation judges merit/value and causal contribution).

1.2 The results-based logic: inputs → activities → outputs → outcomes → impact

Most South African public-sector M&E rests on a results chain (also called the logic model). Understanding the chain is essential because indicators and data collection methods depend on where in the chain you are measuring.

A typical results chain for a government project might look like:

1. Inputs: budget, staff, equipment, training materials
2. Activities: workshops conducted, road resurfacing works executed, clinics supported
3. Outputs: number of roads resurfaced (km), number of learners trained, number of clinics equipped
4. Outcomes: improved access to services, reduced travel time, increased service utilisation
5. Impact: long-term societal benefits such as improved health outcomes or reduced poverty

Monitoring usually focuses heavily on inputs and outputs (and sometimes immediate outcomes).
Evaluation can cover outcomes, impact, relevance, effectiveness, efficiency, and sustainability.

1.3 Policy and governance drivers in South Africa

Although exam questions may not ask you to quote legislation verbatim, they often require you to link M&E to governance requirements. In South Africa, key drivers include:

• Public Finance Management Act (PFMA), 1999 (Act No. 1 of 1999): requires performance and accountability in public spending.
• Treasury Regulations and annual performance processes: encourage measurable objectives, indicator-based reporting, and consequence management.
• Government-wide planning and performance management expectations (including departmental strategic plans and annual performance plans): make monitoring and reporting part of normal operations.
• Service delivery oversight: parliamentary committee work, provincial legislature scrutiny, municipal oversight structures, and audit processes (e.g., AGSA) create pressure for evidence-based accountability.

A high-scoring exam answer shows you understand that M&E is not only a technical exercise; it is also a risk-control system for public resources.

1.4 Typical stakeholders and their roles

Government M&E involves many stakeholders. Exams may ask you to list stakeholders and match them to responsibilities.

Key stakeholders in South African government projects include:

• Project/Programme Management Unit (PMU) or implementing unit
  • Ensures implementation monitoring, routine data, and corrective actions.
• Line department officials
  • Uses monitoring and evaluation results for performance management and reporting to management.
• Treasury/finance units
  • Verify that spending aligns with planned outputs/outcomes.
• Internal audit and risk management units
  • Focus on systems integrity, compliance, and internal controls.
• Auditor-General of South Africa (AGSA)
  • Provides audit findings; while not “evaluation,” audits shape accountability and improvement needs.
• Beneficiaries and community structures
  • Provide feedback, especially for qualitative evaluation and participatory monitoring.
• Oversight bodies (e.g., parliamentary committees, MEC/municipal councils)
  • Use evidence to question performance, demand explanations, and approve remedial measures.
• Evaluators/consultants/research institutions
  • Conduct independent or semi-independent evaluations with methodological rigour.

A critical exam idea: M&E should be a shared accountability system, not only a compliance tool.

1.5 Unit-level vs project-level M&E: practical distinction

Government projects can be monitored at multiple levels:

• Department/Programme level: tracks strategic outcomes, portfolio indicators, and cross-cutting results.
• Project level: tracks specific deliverables and intermediate outcomes.
• Component level: tracks sub-activities and specific workstreams (e.g., training component, construction component).

For example, a rural water project may be monitored at:

• Programme level: % households with access to safe water in target districts
• Project level: km of pipelines installed, number of boreholes rehabilitated
• Component level: drilling completed, water quality testing performed per schedule

If exam questions ask you to “distinguish between monitoring at different levels,” this kind of hierarchical explanation scores well.

2. Designing Monitoring Systems for Government Projects (Indicators, Baselines, Data, and Reporting)

2.1 Building a monitoring framework: steps that exams reward

Designing an M&E system requires a clear structure from results to measurement. A common step-by-step approach:

1. Define project objectives and expected results
2. Develop a results chain (logic model)
3. Select indicators for each result level (output/outcome/impact)
4. Set baselines and targets
5. Define data sources (administrative records, surveys, registers, GIS, etc.)
6. Specify data collection methods and frequency
7. Assign responsibilities (who collects, who verifies, who reports)
8. Establish quality assurance procedures
9. Plan reporting formats and feedback loops
10. Budget for M&E costs within the overall project budget

If you memorise the sequence and apply it to an example, you can answer many different question styles.

2.2 Indicators: types, quality criteria, and common mistakes

Indicators can be:

• Output indicators: counts or completion measures
  • Example: “Number of community health workers trained”
• Outcome indicators: behavioural or service change measures
  • Example: “% of households reporting timely treatment within 24 hours”
• Impact indicators: long-term welfare measures
  • Example: “Reduction in incidence rate of a disease”

Indicator quality criteria commonly taught in public-sector M&E include:

• Specific (clear meaning)
• Measurable (can be quantified or reliably assessed)
• Achievable and relevant (connected to the project goal)
• Time-bound (measured within a defined period)
• Valid and reliable (captures what it claims; consistent measurement)
• Feasible (data can be collected at acceptable cost)

A frequent exam mistake: selecting indicators that are vague. For instance, “improve community participation” is not an indicator by itself. You need something like:

• “Number of community meetings held and attendance rates”
• “% of beneficiaries participating in decision-making sessions”

2.3 Baselines, targets, and the logic of change

A monitoring system needs a baseline (starting point) to interpret progress. Without baseline, targets become arbitrary.

Consider a hypothetical South African department project:
Project: “School Infrastructure Support for Safer Learning Spaces” (SIS-SLS)
Outcome: Improve safety perception and reduce classroom-related incidents.

You may set:

• Baseline: 35% of surveyed learners report unsafe classroom conditions (Year 0)
• Target: 60% report improved safety perception by Year 2
• Output targets: 120 classrooms renovated, 80 sanitation facilities upgraded

The monitoring question then becomes:

• Did renovations occur (outputs)?
• Did safety perception improve (outcomes)?
• Are incident reports decreasing (outcomes/impact depending on timeframe)?

2.4 Quantitative vs qualitative indicators (and why both matter)

Public-sector projects often over-rely on quantitative indicators. But many outcomes are best captured qualitatively, especially where governance, trust, or user satisfaction are central.

• Quantitative indicators:
  • counts, rates, percentages
  • e.g., “% waste collected within 48 hours”
• Qualitative indicators:
  • perceptions, reasons, experiences
  • e.g., “barriers reported by households to waste service access”

A strong monitoring plan often combines both:

• Routine administrative data for frequency and scale
• Periodic surveys, focus groups, or beneficiary feedback mechanisms for context

2.5 Data sources in government: administrative data, surveys, and citizen feedback

Data sources commonly used in South Africa government projects include:

1. Administrative data
   • health registers, attendance logs, procurement records, school enrolment systems
2. Routine monitoring systems
   • project management spreadsheets, dashboards, grant management tools
3. Audits and compliance reports
   • confirm whether processes followed (though not always effectiveness)
4. Surveys
   • baseline/endline household surveys, service user surveys
5. Direct observation
   • site visits, checklists, quality inspections
6. Geospatial data (GIS)
   • mapping service coverage or infrastructure locations
7. Community feedback mechanisms
   • suggestion boxes, hotline logs, community scorecards

Exams may ask: “Explain how you would ensure reliability of data.” You can answer by describing triangulation:

• Use at least two independent data sources (e.g., school attendance registers + learner surveys)
• Cross-check consistency (e.g., procurement quantities vs installed quantities)
• Implement data verification visits
• Train data capturers and standardise definitions

2.6 Monitoring frequency and workplanning

Different indicator types require different monitoring frequencies:

• Weekly/monthly: financial expenditure, procurement timelines, activity completion
• Quarterly: output delivery, service utilisation rates, progress against targets
• Biannual/annual: outcome indicators, service satisfaction surveys
• Special monitoring: whenever risk triggers occur (e.g., contractor underperformance)

A practical example:
If a project is building clinics, you might monitor construction progress monthly and service utilisation quarterly. But you might only measure certain outcomes (e.g., maternal health service access) annually or biannually due to limited recall periods and longer effects.

2.7 Quality assurance and data verification (avoiding “paper monitoring”)

“Paper monitoring” occurs when reported achievements are not validated in reality. Quality assurance methods include:

• Standard definitions: ensure “what counts” is consistent across districts and teams
• Data validation:
  • reconcile totals across sources
  • check outliers and missing values
• Supervision and field verification:
  • sample audits of beneficiary records
• Training and standard operating procedures (SOPs):
  • data collectors trained on consistent methods

In exam scenarios, if you are asked to propose a monitoring plan, always mention data quality steps—this is usually rewarded.

2.8 Reporting and feedback loops: using monitoring results for decisions

Monitoring outputs must lead to action. Reporting should not end with submission. A strong system has:

• Regular internal performance review meetings (e.g., monthly for programme leads)
• Action tracking: issues raised → corrective actions assigned → deadlines set → follow-up confirmed
• Escalation mechanisms when targets are at risk
• Communication with beneficiaries:
  • explain progress and address complaints

A useful way to structure an answer:

• Identify monitoring information needed by decision-makers
• Show how the information flows from field data → analysis → management → action

3. Evaluation of Government Projects (Designs, Methods, Ethics, and Interpretation)

3.1 When evaluation is needed: purposes and timing

Evaluations are conducted to answer deeper questions than monitoring. Common evaluation purposes include:

• Formative evaluation: improve design during early stages
• Summative evaluation: assess overall performance and results at mid-term/end-term
• Impact evaluation: estimate causal effects (what changed due to the project)
• Process evaluation: examine how implementation affects results
• Compliance/relevance evaluation: examine alignment to policy and whether resources were used as intended

Timing in government contexts is often constrained by budget cycles, procurement schedules, and reporting deadlines. Nonetheless, evaluation planning should start during design, not only at endline.

3.2 Evaluation criteria: relevance, effectiveness, efficiency, impact, sustainability

A standard set of evaluation criteria commonly used in public programmes includes:

• Relevance: Are project objectives aligned with real needs and policy priorities?
• Effectiveness: To what extent were objectives achieved?
• Efficiency: Were outputs/outcomes achieved with best possible use of resources?
• Impact: What long-term changes occurred, and for whom?
• Sustainability: Will benefits continue after funding ends?

In exam questions, if you see wording like “evaluate the project,” these criteria can be used as subheadings in your response.

3.3 Evaluation designs: experimental, quasi-experimental, and non-experimental

Evaluation designs determine how confidently you can claim causality.

1. Experimental (Randomised Controlled Trials—RCTs)

   • Random assignment reduces selection bias
   • Often difficult in government infrastructure contexts but possible for service delivery pilots.

2. Quasi-experimental designs

   • Use comparison groups without random assignment
   • Examples:
     • difference-in-differences
     • regression discontinuity
     • propensity score matching

3. Non-experimental designs

   • Use qualitative methods, case studies, or before-after comparisons
   • Strong for understanding mechanisms but weaker on causal claims

In public infrastructure projects (roads, buildings), evaluation may rely more on:

• Comparison of similar areas
• Statistical adjustment
• Qualitative exploration of implementation pathways

3.4 A concrete case example: evaluating an HIV prevention outreach project

Imagine a provincial department runs an outreach programme called “Community Health Link (CHL)” in selected districts. The project provides:

• peer educator training,
• door-to-door counselling,
• referral to testing and clinics.

Monitoring focus:

• number of sessions delivered,
• number of referrals made,
• testing attendance rates (short-term).

Evaluation focus (possible mid-term evaluation):

• Did knowledge and testing uptake improve compared to areas without CHL?
• What implementation factors drive success (e.g., peer educator commitment, stakeholder cooperation)?
• Are communities sustaining behaviour change?

A credible evaluation plan might use:

• A comparison group from similar districts not yet covered by CHL
• Baseline survey data (or retrospective baseline reconstruction if not collected)
• Follow-up surveys at six or twelve months

Interpretation challenge for exams:
If you see improved testing uptake in CHL districts, you must ask:

• Is it due to CHL or due to other campaigns during the same period?
• Are there confounders (clinic outreach, national media campaigns, stock availability)?

A strong evaluation answer will mention:

• threats to validity,
• how you mitigate them (matching, controls, triangulation).

3.5 Data collection methods for evaluation

Evaluation often uses mixed methods.

• Surveys: quantify outcomes, measure attitudes and service utilisation
• Key informant interviews: understand implementation barriers and institutional issues
• Focus group discussions (FGDs): capture community experiences and perceptions
• Document review: programme reports, budgets, implementation plans, procurement records
• Observation and site visits: verify outputs and service quality
• Administrative data: clinic records, education enrolment, crime statistics (where appropriate)

Exams often ask you to justify method choices:

• If the question is “Did outcomes change?” use surveys/admin data.
• If the question is “Why did it change?” use interviews/process tracing.

3.6 Sampling and comparability (how to avoid weak evaluation answers)

Sampling determines representativeness. Common evaluation approaches in government include:

• Cluster sampling: choose communities/districts then households/beneficiaries within clusters
• Stratified sampling: ensure representation across regions, genders, income categories
• Purposive sampling for qualitative case studies: select high-performing and low-performing sites

Comparability is critical:

• If you compare intervention and non-intervention districts, ensure similarity in baseline characteristics.
• If that cannot be guaranteed, mention adjustment methods and limitations.

A good exam response often includes:

• target population definition,
• inclusion/exclusion criteria,
• sample size rationale (even if not calculated precisely, discuss considerations),
• how you handle non-response.

3.7 Ethical considerations in evaluation

Ethics are central in social sector evaluation. Key ethical issues include:

• Informed consent: participants understand purpose, risks, and rights
• Confidentiality: protect personal data
• Do-no-harm: avoid harm during interviews or data collection
• Minimising power imbalance: participants may fear consequences in service-delivery contexts
• Data storage and security: secure databases, controlled access
• Use of findings: ensure evaluation results are used responsibly

Exams may ask: “Discuss ethical issues in evaluation.” Strong answers include not only consent and confidentiality, but also how evaluators handle sensitive information (e.g., health data) and ensure participants can refuse.

3.8 Validity, reliability, and triangulation

Evaluation must be credible. You can strengthen credibility by:

• Triangulation:
  • compare survey results with admin data and qualitative evidence
• Instrument piloting:
  • pre-test questionnaires/interview guides
• Quality control:
  • enumerator training
  • supervision and re-interview for consistency
• Documenting assumptions:
  • explain where data gaps exist and how they were handled

Exams often score higher when you explicitly link validity to decisions:

• If data are unreliable, policy decisions might be based on false signals.

3.9 From findings to conclusions: interpreting outcomes without overclaiming

A major exam skill is learning how to interpret results appropriately.

For example, if a project reports improved service coverage, but evaluation finds:

• outputs delivered,
• beneficiaries satisfied,
• yet outcomes did not change as expected,

Possible interpretations include:

• outcome indicators not measured correctly,
• duration insufficient for outcomes,
• external factors overshadowed project effects,
• beneficiaries not reached due to exclusion errors.

Your conclusion should be aligned to evidence strength:

• Use cautious language where causal attribution is limited.
• Explain alternative explanations and limitations.

4. Using M&E Findings for Management Decision-Making (Learning, Corrective Action, and Accountability)

4.1 The management use of M&E: performance, learning, and accountability

A common misconception is that M&E is only for accountability. In practice, M&E supports three linked functions:

1. Performance management: track progress and enforce accountability
2. Learning and adaptation: improve implementation based on evidence
3. Accountability and transparency: report results truthfully to oversight bodies and the public

In South Africa’s public sector environment, learning and accountability must coexist:

• if evidence suggests underperformance, systems must enable corrective action,
• if evidence shows success, results can guide scaling and replication.

4.2 Corrective action systems: from indicator signals to decisions

To move from data to decisions, projects need a structured approach to issue management:

1. Identify deviation:
   • target missed or quality concerns raised
2. Analyse root cause:
   • procurement delays? capacity constraints? beneficiary selection issues?
3. Select corrective action:
   • revise work plan, reallocate resources, train staff, adjust targeting
4. Assign responsibility:
   • who will do what and by when
5. Set verification checks:
   • how will you confirm corrected performance
6. Track follow-up outcomes:
   • did corrective actions improve output/outcome measures?

Exams often reward candidates who can describe both:

• “what to do when progress is off-track,” and
• “how to ensure the fix works.”

4.3 Performance reporting and the “evidence hierarchy”

Government reporting can become a box-ticking exercise unless it uses evidence appropriately.

A useful idea is an evidence hierarchy:

• Routine monitoring supports “implementation happened”
• Evaluation findings support “results occurred and why”
• Audits support “compliance and financial integrity”
• Independent evaluation supports stronger conclusions (especially for impact)

In writing exam answers, you can show how each evidence type contributes:

• Monitoring answers: Did we do it?
• Evaluation answers: Did it work and why?

4.4 Managing unintended consequences and risks

M&E should include monitoring and evaluation of risks and unintended effects.

Examples of unintended consequences in government projects:

• Construction projects that temporarily increase local unemployment but later lead to contractor layoffs
• A health campaign that improves testing uptake but strains clinic capacity due to referral spikes
• Training programmes that boost skills but fail to connect graduates to employment or deployment pathways

Risk monitoring indicators may include:

• stock-outs (for health projects),
• staffing turnover,
• delays in procurement,
• community complaints,
• service quality declines.

An exam-grade answer should mention:

• how risk information triggers changes in implementation,
• and how evaluation explores whether risks led to unintended outcomes.

4.5 Case study: using evaluation results to revise targeting in an education programme

Consider an education support initiative in a province: “Learner Access and Support (LAS)”. The project aims to reduce dropout rates by providing:

• learning materials,
• after-school support sessions,
• assistance for transport to school.

Initial monitoring signals:

• materials distributed to schools,
• attendance at after-school sessions reported.

Mid-term evaluation findings:

• dropout reduction did not occur as expected in the poorest wards.
• qualitative interviews revealed transport assistance was not reaching learners who needed it most because:
  • forms required documents learners could not access,
  • the application process was too slow relative to the dropout period,
  • parents were unaware of deadlines.

Corrective action might include:

• simplifying documentation requirements,
• introducing a fast-track application window,
• using school-based verification to reduce delays,
• targeted communication to parents/guardians.

Exams often ask candidates to explain “how evaluation results can be used.” This example shows:

• monitoring identifies a gap,
• evaluation reveals the mechanism,
• management adapts targeting and processes.

4.6 Building a learning culture: feedback loops across planning cycles

For learning to matter, M&E findings must reach:

• programme managers,
• senior leadership,
• implementation teams,
• and sometimes beneficiaries.

Common learning mechanisms in government projects include:

• quarterly learning reviews,
• dissemination workshops with districts/community structures,
• updating indicator definitions when measurement problems are discovered,
• revising standard operating procedures (SOPs) based on evidence.

A strong exam answer includes both formal (reporting, review meetings) and informal (lessons learned discussions) learning mechanisms.

4.7 Accountability and transparency: reporting to oversight bodies

Public projects must be transparent enough to allow oversight. Accountability includes:

• reporting progress against indicators,
• explaining budget variances,
• disclosing risks and remedial actions.

In South Africa, oversight may occur through:

• parliamentary portfolio committee engagements,
• provincial MEC-level reviews,
• municipal council reporting processes,
• audit and performance assessment processes.

The exam-ready takeaway:
Evidence must be understandable and actionable for oversight audiences, not only technical enough for specialists.

4.8 Common challenges in using M&E results (and how to address them)

Challenges include:

• Weak data quality: decisions based on incorrect numbers
• Indicator manipulation: reporting targets without real improvement
• Delayed reporting: learning arrives too late for corrective action
• Evaluation fatigue: too many assessments, low action on recommendations
• Lack of ownership: teams treat M&E as compliance rather than improvement
• Political and institutional pressures: results may be framed to defend decisions

Strategies to address these include:

• enforce data verification,
• link M&E findings to budget and workplan adjustments,
• build staff capacity for data use,
• establish consequences for persistent misreporting,
• ensure evaluation recommendations have responsible owners and timelines.

5. Exam-Style Frameworks and Practical Tools for Monitoring and Evaluation in Public Projects (Application, Templates, and Scenario Practice)

5.1 How to structure answers in exams (frameworks that consistently score)

Many exam questions in project management for public administration can be answered using repeatable frameworks. For instance:

• “Explain” questions: define → compare → give examples → mention implications
• “Design” questions: results chain → indicators → data sources → frequency → QA → reporting
• “Evaluate” questions: criteria → design choice → data collection → analysis → ethics → limitations
• “Discuss challenges” questions: identify challenge → explain consequence → propose mitigation

A key technique: write with headings and subheadings; marker-friendly structure improves the perceived clarity of your answer.

5.2 Practical template: monitoring matrix (indicator-by-indicator logic)

A monitoring matrix (sometimes called a logframe table) links results to measurement. Here is a sample structure (illustrative only; adapt to your project):

Results Level	Indicator	Baseline	Target	Data Source	Collection Frequency	Responsibility	Verification/QA
Output	Clinics equipped with essential supplies (count)	12 clinics	20 clinics	Procurement records + site checks	Monthly/Quarterly	PMU logistics officer	Sampling inspection
Outcome	% of targeted patients receiving timely medication	40%	65%	Clinic registers + patient exit surveys	Quarterly	M&E officer	Data validation and record checks

The point for exams: you don’t just list indicators—you justify them using baseline/target logic, and you show how data quality is ensured.

5.3 Practical template: evaluation terms of reference (TOR) essentials

Evaluation questions on exams often expect you to outline what should appear in TOR. TOR typically includes:

1. Background and context
2. Purpose of evaluation (formative/summative/impact/process)
3. Key evaluation questions mapped to evaluation criteria
4. Scope (geographical areas, time period, components)
5. Methodology (design, sampling, data sources, analysis approach)
6. Ethical considerations and data protection
7. Deliverables:
   • inception report,
   • draft report,
   • final report,
   • presentations/dissemination outputs
8. Roles and responsibilities:
   • steering committee,
   • evaluator,
   • programme management
9. Timeline and review process
10. Budget considerations

Even if your exam does not require a full TOR, demonstrating these items in a structured list is usually rewarded.

5.4 Scenario practice: designing an M&E plan for a municipal waste management project

Suppose a municipality implements a waste collection improvement project called “Clean Streets Initiative (CSI)”.

Project objectives:

• Improve waste collection reliability in selected wards.
• Increase landfill diversion through recycling partnerships.
• Reduce illegal dumping.

Possible results chain:

• Inputs: trucks, fuel, PPE, contractor management support
• Activities: route optimisation, community awareness, recycling linkage agreements
• Outputs: number of routes operational; number of households serviced; tonnage handled for recycling
• Outcomes: reduced illegal dumping incidents; increased waste collection compliance; higher recycling participation
• Impact: improved neighbourhood health and cleanliness

Monitoring plan examples:

• Output indicators:
  • % of scheduled collection runs completed
  • number of households serviced per ward
  • tonnes collected for recycling per month
• Outcome indicators:
  • average illegal dumping complaints per month per ward
  • % households reporting “waste collected as expected”
• Data sources:
  • route logs from contractor management,
  • service registers,
  • hotline complaint logs,
  • periodic household surveys,
  • site observation audits

Evaluation option (if asked in an exam):

• quasi-experimental comparison of similar wards not yet implementing CSI,
• difference-in-differences using pre/post data and complaint logs,
• process evaluation interviews with contractors and ward councillors to understand barriers.

This scenario demonstrates how to turn project goals into measurable indicators and evaluation questions.

5.5 Scenario practice: evaluating a health outreach programme with supply constraints

Consider a health outreach programme “Community Health Link (CHL)” described earlier. Evaluating it must account for supply constraints:

• if clinics run out of medication, increased referrals may not translate into health outcomes.
• if staff shortages exist, service quality declines.

Evaluation design implications:

• include clinic capacity measures as part of process evaluation,
• collect data on medicine stock levels,
• interview clinic managers about challenges.

A high-scoring answer would explicitly show:

• why process evaluation is necessary,
• how to distinguish between “project failed” and “system constraints limited outcomes.”

5.6 Common exam questions and strong answer skeletons

Below are representative exam question types and how to structure your response.

Question type A: “Define monitoring and evaluation and discuss differences.”

Skeleton:

1. Define monitoring (purpose + timing)
2. Define evaluation (purpose + timing)
3. Compare (inputs/outputs vs outcomes/impact; continuous vs periodic; implementation vs value/judgement)
4. Provide examples in government context
5. Conclude: both support accountability and learning

Question type B: “Explain how you would design an M&E framework for a government project.”

Skeleton:

1. Results chain
2. Indicator selection criteria
3. Baseline and target setting
4. Data sources and collection frequency
5. Responsibilities and data quality assurance
6. Reporting and feedback loop
7. Budget and feasibility

Question type C: “Discuss evaluation designs and when to use each.”

Skeleton:

1. Overview of RCT/quasi/non-experimental
2. Strength and limitations for causality
3. Suitability for different project types (services vs infrastructure)
4. How to strengthen non-experimental inference
5. Mention practical constraints in government

Question type D: “Discuss ethical issues in evaluation.”

Skeleton:

1. Consent and confidentiality
2. Do-no-harm
3. Power dynamics
4. Data protection and storage
5. Sensitive topics and referral pathways
6. Reporting responsibly

5.7 Integrating M&E with project management disciplines (schedule, cost, procurement, risk)

Because this study guide sits within Project Management for Public Administration (SA Government Focus), exams may connect M&E to other project management knowledge areas.

• Schedule control: monitoring activity timelines and completion rates; evaluation can assess whether schedule constraints affected outcomes.
• Cost control: monitoring expenditure against budget; evaluation can check efficiency (value for money).
• Procurement oversight: monitoring procurement milestones; evaluation can check whether procurement approaches affected delivery quality.
• Risk management:
  • monitoring tracks risk indicators,
  • evaluation examines whether risk mitigation worked.

A good integrated answer demonstrates that M&E is not isolated: it is part of controlling delivery and verifying results.

5.8 South Africa relevance: what markers look for in SA-focused answers

When answering exam questions in SA context, markers often reward:

• Reference to government accountability structures (departments, oversight bodies, reporting requirements)
• Use of results-based logic consistent with public programmes
• Awareness of data challenges (access, quality, capacity)
• Ethical sensitivity in social sector data collection
• Practical feasibility (what can be done with limited staff/time/budget)

Even without quoting legislation, your response should reflect public administration realities.

5.9 Quick revision checklists (for final days)

Use these checklists as “mental templates”:

Monitoring checklist

• Results chain defined
• Indicators chosen (output and outcome where relevant)
• Baseline and targets set
• Data sources identified
• Collection frequency planned
• Responsibilities assigned
• Data quality assurance included
• Reporting schedule set
• Feedback and corrective action mechanism described

Evaluation checklist

• Evaluation purpose and criteria stated
• Design chosen (experimental/quasi/non-experimental) with rationale
• Sampling and comparability addressed
• Data collection methods matched to questions
• Ethics and confidentiality addressed
• Validity and triangulation plan included
• Limitations acknowledged
• Findings translated into actionable recommendations

Final synthesis

Monitoring and Evaluation of Government Projects is both a technical discipline (indicators, baselines, designs, data quality, ethics) and a governance practice (accountability, transparency, and learning). In South Africa’s public administration environment, projects must demonstrate not only that activities were implemented, but also that they produced outcomes that matter and can be sustained. Exam success depends on your ability to move from abstract concepts to structured frameworks, use evidence responsibly, and propose realistic systems that lead to corrective action and improved service delivery.