At a Glance
Standard vs Custom at a Glance
| Factor | Standard indicators | Custom indicators |
|---|---|---|
| Source | Established framework (SDGs, Sphere, sector handbooks, donor libraries) | Designed for this program, based on its theory of change |
| Definition | Fixed, inherited | Must be authored and validated |
| Data collection method | Typically specified by the framework | Must be designed and tested |
| Disaggregation | Often required by the framework | Decided by program |
| Comparability | Possible when definitions, methods, populations, periods, and source versions are comparable | Low by default; requires explicit alignment to achieve comparability |
| Donor acceptance | Confirm the applicable agreement and reporting instrument | Varies; requires justification and definition |
| Cost to deploy | Lower (tools and definitions exist) | Higher (authoring, testing, training) |
| Captures program-specific outcomes | Only if program aligns exactly to the framework | Yes, by design |
The choice is not binary. Most mature MEL plans use both deliberately and the ratio reflects the program's design. Neither a mixed portfolio nor a fixed ratio establishes quality; judge each measure by purpose, validity, comparability, and cost.
For the conceptual definition, see custom vs standard indicators. For the broader indicator design context, see indicator selection.
Common Standard Indicator Frameworks
Standard indicators are never just "standard." They come from a specific framework with its own conventions. Using one means inheriting that framework's measurement discipline.
| Framework | Scope | Strength | Common use |
|---|---|---|---|
| Sustainable Development Goals (SDG) | Global, cross-sector | Widely recognized, aggregated to national statistics | Population-level outcomes, national-policy linkage |
| SPHERE Standards | Humanitarian (WASH, shelter, food, health, protection) | Sector-specific, field-tested, minimum standards | Humanitarian programs, emergency response |
| Published funding-framework indicator sets | Scope varies by framework | Read the exact definitions and version | Use only where relevant; applicability comes from the actual agreement |
| JMP (Joint Monitoring Program, WHO-UNICEF) | WASH | Service ladders (surface water, unimproved, limited, basic, safely managed), comparable across countries | WASH programs, SDG 6 reporting |
| DHS / MICS | Population health + child welfare | National sample surveys; produces comparable estimates | Health and nutrition program benchmarking |
| INEE | Education in emergencies | Minimum standards, access and quality dimensions | Education in humanitarian contexts |
| HFIAS / FCS / rCSI / HHS | Food security | Validated household-level measures | Food security monitoring |
| Donor-specific indicator libraries | Agreement-specific | Applicability must be checked against the funding agreement | Proposal and reporting to that donor |
Two implications. First, "standard indicators" is not a single catalog; it is many frameworks with different assumptions and data collection requirements. Second, the framework you pick shapes your data collection budget as much as your indicator list does. Picking a SPHERE standard indicator commits you to SPHERE-aligned measurement; the required population, denominator, source, and precision must fit the reporting level. Some SDG methods can inform a local estimate, which must be labeled local and must not be reported as a national SDG estimate.
When to Use Each
When Standard Indicators Win
Use standard indicators when one or more of the following applies.
Compliance is non-negotiable. Your donor's indicator library is in the contract. You report their indicators whether they fit your program or not. This is the most common driver; identify applicable obligations from the actual funding agreement rather than assuming a percentage of the indicator portfolio.
Comparability is analytically important. You are running a program in a context where others have measured the same thing, and you want your results to be comparable. This matters for evaluation credibility, scale-up decisions, and evidence-base contributions.
The framework has validated methodology you would otherwise have to build. JMP service ladders, HFIAS food insecurity scales, and DHS-style household indicators come with tested questionnaires, pretested item wording, and known psychometric properties. Rebuilding these yourself is expensive and probably worse.
The program fits the framework's assumptions. If your WASH program is delivering household water access in a way JMP was designed to measure, use JMP indicators. If your food security program targets household-level consumption in a way HFIAS measures, use HFIAS.
External benchmark data exists. Standard indicators often come with reference values (national averages, SPHERE minimum standards, JMP coverage rates). These benchmarks are analytically useful and impossible to reproduce for a custom indicator without running parallel studies.
When Custom Indicators Win
Use custom indicators when the standard indicators do not capture what your program is actually doing.
Your program is outside the standard framework's scope. A social enterprise producing livelihoods through niche value chains, an innovative education delivery model, or a conflict-sensitive program in a new geography may have outcomes no standard framework measures well. Forcing these into the nearest standard indicator produces data that is technically collectable but substantively uninformative.
Your theory of change is pathway-specific. Standard indicators usually sit at the outcome or impact level. If your program's causal pathway includes intermediate changes (attitude shifts, skill acquisition, behavioral precursors) that standard indicators do not measure, you need custom indicators for those stages. See output vs outcome vs impact for the level-by-level logic.
The measurement cost of the standard indicator is disproportionate. If an indicator requires national inference, a survey in three program districts does not provide it. The same construct may still be measurable locally using an appropriate definition and design. Using a custom indicator at the program scale is defensible even when a standard indicator exists in principle.
The standard indicator's definition fails the local context. "Household" in one context means nuclear family; in another, extended compound. Under JMP, boreholes are an improved source technology; contamination risk alone does not change that technology category or establish safely managed service. If the standard definition does not match your program's operational reality, using it anyway produces invalid data. Better to build a custom indicator with a locally-appropriate definition and document the rationale.
You need higher resolution than the standard provides. Standard indicators often track binary outcomes (had access / did not, achieved / did not). A program whose theory of change requires graduated measurement (how much access, how consistently, across what subgroups) needs custom indicators at finer resolution.
The Hybrid Approach
The strongest MEL plans use both. The question is not "which" but "in what proportion and how mapped."
Typical structure:
- Compliance Layer: 5-15 standard indicators required by the donor or regulatory framework. Reported at the required intervals in the required format. Data collection effort proportionate to reporting requirement, not higher.
- Comparability Layer: 3-8 additional standard indicators chosen for external benchmark value (SDG, SPHERE, JMP, or sector norm). These are not compliance-required but anchor your results against recognizable reference points.
- Custom Layer: 8-20 program-specific indicators measuring what the program uniquely does. These track the theory of change at the levels standard indicators cannot reach.
The layer counts above are planning illustrations, not a portfolio target. A standard-only, custom-only, or mixed portfolio can be suitable when every indicator is justified and resourced.
See mistake too many indicators for why ratio alone does not save you from indicator bloat.
Alignment Mapping
Building an Alignment Map
For each custom indicator, document its relationship to the relevant standard indicator (if any). This is the alignment map, and it is the single most important artifact of the hybrid approach.
Structure:
| Custom indicator | Maps to (standard) | Relationship | Use |
|---|---|---|---|
| % women reporting participation in household decisions on child education | Local household decision-making measure | Different construct from SDG 5.5.1, which concerns women in parliamentary and local government seats | Report locally; do not aggregate this as SDG 5.5.1 |
| Functional water committee score (0-20) | JMP "safely managed drinking water" service ladder | Not a direct map; custom measures management capacity as a precursor to service sustainability | Report both; use custom as leading indicator, JMP as outcome measure |
| Households demonstrating IYCF practice (observed) | WHO IYCF indicators (self-report) | Related construct; observation and recall can differ in population, period, and behavior captured | Follow the exact applicable WHO instrument/version; report observational findings separately without assuming equivalence or superiority |
What the map accomplishes:
- Analysts and evaluators can reconstruct why each indicator exists
- Successor M&E staff understand the logic without starting from scratch
- Donors see how program-specific data complements compliance reporting
- Comparability is achieved deliberately, not accidentally
Keep the map in the MEL plan, not in a separate file that will be lost. Review and update at every MEL plan revision.
Handling Definitional Drift
Standard indicators can change. Record the exact edition and revision used, check the framework owner's current documentation before adoption, and document the effect of revisions on comparability.
Definitional drift creates two specific problems:
Historical comparison is broken. Your 2022 endline data using the old definition is not directly comparable to your 2026 endline using the new definition. Document the version of each standard indicator in your MEL plan ("SDG 3.8.1 as of 2024 revision") so analysts can flag comparability breaks.
Donor reporting shifts mid-program. A multi-year program may enter year 3 and discover the donor's mandatory indicator list changed. Build revision contingency into the MEL plan: a review of indicator currency at each annual work plan cycle.
Custom indicators do not drift unless you change them. This is an advantage for internal program management and a disadvantage for external comparability.
Sector Examples
Sector Examples
The scenarios below are illustrative. Their figures, costs, and review outcomes are teaching assumptions, not reported studies or evidence of donor approval.
Health: Balancing a Donor's Mandatory Indicator Set with Program-Specific Outcomes, East Africa
An HIV program operated under a donor's mandatory indicator set (reported quarterly), requiring 12 indicators for compliance reporting. The program's theory of change included client-centered care quality improvements that the mandatory indicator set did not measure. The MEL team added 8 custom indicators covering: perceived provider respect (3-item scale), continuity of care across service types (proxy: consecutive quarter visits), and stigma reduction in the broader community (household attitudinal survey). Mapping: the 12 standard indicators covered outputs and service-coverage outcomes; the 8 custom indicators covered process quality and community-level outcomes that standard indicators did not reach. Reports separated the two layers clearly so donor compliance was never in question.
WASH: JMP Ladder Alignment for a Rural Water Program, West Africa
A rural water access program reported JMP service ladder categories for SDG 6.1 alignment (safely managed, basic, limited, unimproved, and surface water). Program management needed higher resolution: the program's theory of change included water committee capacity as a precursor to service sustainability. The MEL plan added a custom Water Committee Capacity Score (0-20, 10 items) as a leading indicator. When JMP-basic service coverage plateaued in year 2, the capacity score was already flagging specific weak committees, giving the program time to intervene. Standard indicators were the outcome measure; custom was the leading indicator.
Education: INEE Standards + Custom Learning Indicators, South Asia
An education-in-emergencies program applied INEE Minimum Standards for compliance and comparability (access, quality, coordination). INEE standards did not measure specific learning outcomes at the grade level the program was targeting. The MEL plan added custom learning indicators: Grade 3 literacy assessment scores (adapted EGRA), Grade 5 numeracy (adapted EGMA), and school-level reading time allocation. The mix gave the donor INEE-aligned comparability against other education-in-emergencies programs and gave program management learning-outcome data at the classroom level.
Food Security: HFIAS for Compliance, Food Diversity for Program Management, Sahel
A food security program reported HFIAS scores quarterly for donor compliance and cross-program comparability. The program's pastoralist context included seasonal migration patterns that HFIAS captured only partially. The MEL team added two custom indicators: a Household Diet Diversity Score disaggregated by migration phase (transhumance vs settled) and a Household Asset Disposal Indicator (tracking distress sales as early warning). HFIAS stayed as the comparable standard; the custom indicators caught context-specific dynamics the standard could not.
Mistakes & Checklist
Common Mistakes
Mistake 1: Picking standard indicators without reading the definitions. The indicator name sounds right; the technical specification says something different. "Households with improved water access" in JMP has a specific definition (the service ladder runs from surface water through unimproved, limited, and basic to safely managed) that is not the same as the colloquial meaning. Read the full definition before committing.
Mistake 2: Modifying standard indicators silently. If your operational definition differs from the framework definition, you are not using the standard indicator anymore. Either use it unmodified or label it as a custom indicator with a clear note on the deviation. Using the standard indicator's name with a modified definition produces data that looks comparable and is not.
Mistake 3: Assuming custom indicators do not need validation. Custom indicators are not shortcuts. They need defined measurement methods, tested questionnaires, inter-rater reliability checks for complex measures, and a clear rationale documented in the MEL plan. "We made it up" is not a methodology.
Mistake 4: No alignment map between custom and standard. Without a map, custom and standard indicators drift into parallel tracks that nobody uses together. The map forces the question: why does the custom version exist if the standard one already measures this?
Mistake 5: Too many standard indicators without regard to program fit. A program operating in 3 districts does not need 15 national-level SDG indicators. Compliance is required; over-reporting is not. Push back on excess standard indicators when the compliance requirement does not mandate them.
Mistake 6: Too many custom indicators without regard to comparability. A largely custom portfolio may limit external comparison, but comparison remains possible where operational definitions and populations match. External evaluators struggle to contextualize results. Add 3-5 standard indicators for benchmark value even when not compliance-required.
Mistake 7: Ignoring donor framework updates mid-program. Standard indicators drift. Check the current version at every annual work plan revision. Report comparability breaks explicitly in the annual report.
Mistake 8: Running standard and custom data collection as parallel operations. Where the constructs overlap, integrate measurement into a single survey round or data collection visit. Running two separate quarterly surveys for standard and custom indicators doubles the cost for marginal quality gain.
Custom-vs-Standard Decision Checklist
Run through this during MEL plan development for each candidate indicator.
Is a standard indicator available?
- Checked donor's mandatory indicator list
- Checked sector-specific frameworks (SPHERE, SDG, sector-specific standards)
- Checked donor library for supplementary recommended indicators
- Reviewed the standard indicator's full definition, not just its name
Does the standard indicator fit the program?
- Construct matches program's theory of change at the right level
- Measurement method is feasible given program scale and budget
- Definition matches local context and operational reality
- Data collection frequency matches decision cycle
If you are using a custom indicator instead:
- Reason documented (standard unavailable, fit poor, cost prohibitive, resolution insufficient)
- Measurement method defined and tested (cognitive pretest + pilot)
- Alignment to the nearest standard indicator mapped
- Validation approach specified (inter-rater reliability, construct validity, or expert review)
Portfolio-level checks:
- Standard/custom mix is justified by decisions, construct fit, applicable obligations, and burden; no fixed ratio is required
- No duplicate measurement (same construct measured standard and custom without explicit reason)
- Alignment map complete in MEL plan
- Donor compliance requirements all met with unmodified standard indicators
For the full indicator design workflow, see SMART indicators deep-dive and indicator vs target vs milestone. For the proposal-writing application, see how to write the M&E proposal section. For current document workspaces, see the Playbooks catalog.