Policy evaluation vs programme evaluation, political economy awareness in design, implementation tracking and regulatory impact, and welfare-effect estimation approaches. Walk out with a policy evaluation design brief.
Walk in with a public policy or government scheme. Walk out with an evaluation design brief covering the policy-programme distinction, political economy mapping, implementation tracking, and welfare estimation approach.
A programme is a bounded intervention with defined beneficiaries, a budget, and a start/end date. A policy is a rule, incentive structure, or institutional arrangement that shapes behaviour across an entire population. Evaluating the two requires different logics.
| Dimension | Programme evaluation | Policy evaluation |
|---|---|---|
| Scope | Bounded: specific geographies, beneficiaries | Universal or near-universal: affects entire populations |
| Counterfactual | Non-participants or comparison group | Often no untreated group (universal policies); use pre-post, cross-state, or regression discontinuity |
| Implementation | Controlled by implementing agency | Mediated through bureaucracy, politics, and state capacity |
| Timeline | 2-5 years typical | Effects unfold over decades; political cycles interrupt |
| Data | Primary collection usually feasible | Often relies on administrative data (NSSO, PLFS, Census, SECC) |
India has a growing culture of policy evaluation but it remains patchy. NITI Aayog's Development Monitoring and Evaluation Office (DMEO) commissions evaluations of centrally sponsored schemes. The Programme Evaluation Organisation (PEO) has been folded into DMEO. State-level evaluation capacity varies enormously -- Kerala and Tamil Nadu have strong traditions; many states have none.
PM-KISAN (Rs 6,000/year cash transfer to farmer families) was implemented nationally in February 2019. No randomisation was possible because it is a universal entitlement. Evaluations have used: (a) PLFS panel data comparing pre/post implementation periods, (b) regression discontinuity at the 2-hectare cutoff (in the initial design which had a landholding cap), and (c) difference-in-differences across states with faster vs slower DBT rollout. Each design answers a different question and has different limitations.
Fill these for your policy/scheme. Answers flow into the capstone.
Policy evaluation is never politically neutral. The findings will be used, misused, or ignored depending on who commissioned the evaluation, when in the political cycle it is released, and which stakeholders benefit from the current policy.
DMEO guidelines require evaluations to be conducted by "independent" agencies. In practice, agencies that produce unfavourable findings are less likely to receive future contracts. This structural incentive biases towards positive findings. Document your quality assurance process explicitly: peer review by named experts, pre-registered analysis plan, data deposited in a public repository.
Map the political economy. These flow into your capstone.
Most policies fail not because the design is wrong but because implementation breaks down. Lant Pritchett's concept of "capability traps" explains why: India announces ambitious policies that exceed the implementation capacity of the state machinery. Implementation tracking is therefore the most useful form of policy evaluation for improving outcomes.
MGNREGA implementation tracking: The most informative evaluations of MGNREGA focus not on "did it reduce poverty?" (too distal, too many confounders) but on implementation quality: days provided vs days demanded (demand gap), wage payment delays (measured in days between muster roll closing and DBT credit), social audit coverage, and material-labour ratio. These process metrics directly diagnose implementation health and are actionable at the block level.
Design the implementation analysis. These flow into your capstone.
When you need to estimate the causal effect of a policy on welfare outcomes, you need a credible identification strategy. India's policy landscape offers several natural experiment opportunities.
| Strategy | When it works | Indian example |
|---|---|---|
| Regression discontinuity | Eligibility has a sharp cutoff (BPL score, age, income) | PMAY-G eligibility based on SECC deprivation score |
| Difference-in-differences | Policy rolled out at different times across states/districts | MGNREGA phased rollout (2006-2008) across districts |
| Instrumental variables | An instrument affects policy exposure but not outcomes directly | Rainfall as instrument for MGNREGA take-up (demand rises after drought) |
| Synthetic control | A single treated unit (one state) with many potential comparison units | Gujarat's industrial policy effect compared to synthetic Gujarat |
India's administrative data ecosystem has expanded enormously: NSSO/PLFS (labour), NFHS (health/nutrition), AIDIS (debt/assets), ASI (industry), UDISE+ (education). These datasets are free, nationally representative, and increasingly available as microdata. Use them.
Large-scale policies create general equilibrium effects that programme evaluations miss. MGNREGA raises rural wages even for non-participants. GST changes relative prices across sectors. PM-KISAN may affect land prices. These spillover effects can be larger than direct effects and require macro-level analysis, not household surveys.
Design the estimation strategy. These flow into your capstone.
Click Build my brief to compile everything.
Click "Build my brief" -- your module answers will be pulled into the artefact.
Share this brief with a policy researcher before circulating. The most common blind spot is ignoring implementation quality when interpreting impact estimates.
Help us improve: feedback form.