SPICED Indicators

SPICED is a participatory indicator framework used alongside SMART in development evaluation. The expansion below follows UNESCO/UNICEF's 2014 technical guidance, box 23; an origin claim is not established here. The six criteria favor community voice, interpretation, and learning over standardized, donor-facing measurement.

What Does SPICED Stand For?

SPICED indicators meet six criteria, each pushing against a weakness in purely technical indicator design.

Subjective. Beneficiaries decide what counts as progress. An indicator that matters to the community is more useful than one imposed by an external analyst, even if it is harder to benchmark.

Participatory. Indicators are co-designed with the people whose lives the program affects. Design is a workshop, not a desk exercise.

Interpreted and Communicable. Meaning is negotiated across stakeholders. The same data point can mean different things to a farmer, a field officer, and a funder, and SPICED treats that interpretation as part of the measurement. Explain local meanings to external audiences so the evidence can be understood and used.

Cross-checked. Compare information across informants, methods, and other indicators of progress. Examine disagreements and seek independent corroboration rather than assuming a shared interpretation verifies the claim.

Empowering. The act of measuring strengthens participant agency. Data collection becomes a reflection tool for the community, not just an extraction exercise.

Diverse and Disaggregated. The framework captures variation across groups rather than averaging differences away. Gender, age, disability, ethnicity, and geography are treated as analytical categories, not footnotes.

When Does SPICED Work Better Than SMART?

SPICED earns its place in the following conditions:

• Empowerment, voice, dignity, or social cohesion outcomes where the point of the program is the thing hardest to count.
• Learning-focused evaluation, where understanding what happened matters more than comparing to a target.
• Strong community participation mandate, especially in localization-led or indigenous-led programming.
• Qualitative-primary evaluation designs using most significant change, outcome harvesting, or participatory rubrics.
• Contexts where standardized indicators erase exactly the variation the program is trying to surface.

How Are SPICED and SMART Used Together?

A program can combine useful features of both frameworks according to its measurement purpose. SMART can help specify measures and timing, including comparable metrics where appropriate. SPICED indicators capture the participant-voiced, learning-focused evidence that tells the program team what is actually changing and why. A livelihoods program in rural Southeast Asia might track SMART income and yield metrics alongside SPICED indicators co-designed with women's cooperatives about confidence, bargaining power with traders, and time poverty. Both sets feed the same report. They answer different questions.

Proposal Context

Cite SPICED in a proposal when the design is genuinely participatory or learning-led. Explain how community voice shapes measurement and how information will be interpreted and cross-checked. Follow the applicable proposal instructions rather than assuming that a SPICED label earns approval. Empowerment, social cohesion, and governance proposals benefit from SPICED alongside SMART because SMART alone misses the point of the program. The common pitfall: using SPICED as a get-out-of-SMART excuse for vague, unverifiable indicators. SPICED indicators still need a definition, a measurement method, a data source, and validity discipline. The framework changes which dimensions you prioritize, not whether you do the work. Reviewers will see through a SPICED label pasted over sloppy design.

Common Mistakes

Using SPICED to justify vagueness. "Community members feel more empowered" is not a SPICED indicator; it is an unmeasured claim. SPICED still requires definition, method, and evidence.

Treating the frameworks as exclusive. Combine their useful features where they fit the purpose. Community voice and cross-checking can strengthen clearly specified measures; neither label establishes validity by itself.

Method Source

UNESCO/UNICEF, Towards a Learning Culture of Safety and Resilience (2014), box 23, printed p. 117. This is methodological guidance, not a funding requirement.