Scoring Criteria
Every MoV entry names a specific document, dataset, or record (e.g., "training attendance register form TR-02", "DHIS2 monthly health facility report", "end-line household survey dataset"). No generic categories.
At least 80 percent of entries name a specific source. No more than 20 percent use generic phrases such as "project reports" or "M&E records".
Half or more entries are specific. The remainder use generic categories such as "monitoring data" or "field reports" that do not identify the actual document.
Half or fewer entries name a specific source. Most use generic categories such as "project records" or "internal reports".
No specific sources named. The column lists only category labels (e.g., "primary data", "secondary data") or is blank.
The method named for each MoV is appropriate for the indicator. Quantitative indicators have quantitative methods (surveys, administrative records); qualitative indicators have qualitative methods (interviews, focus groups, observation). Mixed indicators have a mixed-method MoV.
At least 80 percent of methods are appropriate. No more than 20 percent show a mismatch (e.g., a perception indicator measured only through administrative records), and these are clearly minor.
Half or more methods are appropriate. The remainder show a recognizable mismatch but the indicator could still be approximated with the named method.
Half or fewer methods are appropriate. The majority of indicators are paired with methods unable to produce the required data type or unit of measurement.
No relationship between methods and indicators. Methods are either generic (e.g., "reports") or systematically mismatched.
A specific data collection frequency is stated for every indicator (e.g., "monthly", "quarterly", "annually", "baseline and end-line"). No frequency is left implicit.
At least 80 percent of indicators have a stated frequency. No more than 20 percent are missing a frequency, and these are at minor output levels.
Half or more indicators have a stated frequency. The remainder are missing a frequency or use vague terms such as "regular" or "ongoing".
Half or fewer indicators have a stated frequency. Most use vague terms or omit frequency entirely.
No frequencies stated. The column treats frequency as implicit or covered elsewhere without cross-reference.
A specific position responsible for data collection is named for every indicator in the MoV column itself, or each entry cross-references a row in the roles and responsibilities matrix. No ambiguity.
At least 80 percent of indicators have responsibility named or cross-referenced. No more than 20 percent are silent on responsibility.
Half or more indicators have responsibility named. The remainder rely on a general statement such as "the M&E team" with no individual position attached.
Half or fewer indicators have responsibility named. The column mostly uses unit-level labels or omits responsibility.
No responsibility named or cross-referenced anywhere in the MoV column.
Every MoV is realistic given existing data systems, staffing levels, geography, and budget. Methods named are within the program's documented capacity to execute at the stated frequency.
At least 80 percent of MoV entries are feasible. No more than 20 percent appear stretched (e.g., quarterly household survey across multiple districts) but could be executed with adjustment.
Half or more entries are feasible. The remainder require resources or systems not clearly documented in the program plan.
Half or fewer entries are feasible. The majority assume data systems, staffing, or budget that the program does not have.
The MoV column is systematically unrealistic. Methods named cannot be executed at the stated frequency with the program's resources.
Score Interpretation
| Total (out of 25) | Band | Next Step |
|---|---|---|
| 22-25 | Strong | Minor refinements only |
| 17-21 | Adequate | Address flagged dimensions before submission |
| 11-16 | Needs Revision | Return to MEL team with AI output as revision brief |
| 5-10 | Substantial Revision | Redesign the MoV column with the data manager before proceeding |