Governing evidence and applicability rules (take precedence over aggregate bands): establish the document purpose, design, stage and available evidence before rating. A fit-for-purpose single-method design can earn the highest applicable rating; do not require complexity, mixed methods or two sources for every finding. Distinguish applicable, not applicable with reason, not evidenced, and observed inadequate. Report applicable coverage and the raw denominator. If any dimension is N/A or not evidenced, report the profile and gaps without a 25-point band or an unvalidated rescaled equivalent. Never interpret missing documentation as proof no activity occurred. Use source-linked historical facts only; keep proposed work and illustrative examples separate. Preserve unresolved source conflicts. Do not invent baseline values, quotations, fieldwork, pilots, validation, consent or approvals to improve a score. A serious consent, confidentiality, safeguarding, measurement-validity or unsupported-inference failure is a blocking issue regardless of the total, including 22/25. High document-quality scores do not establish legal compliance, instrument readiness, field authorization or donor approval. Accountable human review against the applicable protocol is separate. A well-documented failed pilot may score 25/25 for documentation while remaining not ready for fielding.
Use This Rubric
Bring: the proposed lessons, parent findings and source references, relevant context, contrary evidence, and intended decisions.
Stage: State whether this is a proposed design, a draft, or a report of completed work. Assess planned procedures as plans; require records before claiming they occurred. A complete submitted document can have an observed documentation defect even when the underlying activity is unknown.
Limits: Apply requirements to the stated purpose, methods, population, and risk. Do not impose extra methods or sensitive data collection solely to increase a score. These editorial anchors are provisionally checked, not practitioner-calibrated.
Scoring Criteria
Every lesson cites the specific finding, data point, or event it draws from. The reader can trace each lesson back to evidence in the report. Where multiple findings support a lesson, all are cited. Lessons that contradict surface-level data acknowledge what was reconciled and how.
At least 80 percent of lessons cite their source finding or evidence. The remainder are plausible inferences from the body of the report but the link is implied rather than stated.
Roughly half of lessons are traceable to findings. The rest read as the author's general impressions. Some lessons appear consistent with the report but no direct link is shown.
Most lessons appear to reflect author opinion without documented evidence. Citations to findings are rare or absent. The section reads as commentary detached from the analysis.
Lessons are untraceable to anything in the report. No evidence basis is shown.
Every lesson is specific to a context, mechanism, or condition. Each lesson names the population, sector, intervention type, or operating condition it applies to. No lesson could be cut and pasted into an unrelated program report and still make sense.
At least 80 percent of lessons are specific in this sense. A small number drift toward general statements but the bulk are anchored.
Roughly half of lessons are specific. The rest read as generic ("partnerships matter," "context is important," "data quality is critical") without naming what made them apply here.
Most lessons are generic platitudes that could be lifted into any program report. Specificity is rare.
All lessons are platitudes with no specificity at all.
Every lesson explicitly states its scope of applicability. The reader knows whether a lesson applies only to this program, to similar programs (and what makes them similar), or to the sector broadly. Boundary conditions are named where they matter.
At least 80 percent of lessons state their scope. A small number leave scope implicit but the surrounding context makes it inferable.
Some lessons name their scope; others do not. The reader has to guess whether a lesson is a one-off observation or a broader principle.
Scope is rarely addressed. Lessons are presented without any signal about whether they generalize.
No lesson states its scope. The reader cannot tell which lessons might apply elsewhere.
Learning is balanced against the supplied record. Documented failures, difficulties, unintended effects, and choices to retain or change practice are treated proportionately. Where no counter-lesson is supported, explain the evidence coverage rather than inventing a failure.
Relevant counter-lessons are meaningfully reported; a minor framing or evidence detail remains.
Some supported difficulties appear but their interpretation or implications are incomplete.
Documented difficulties are minimized, reframed without evidence, or detached from lessons.
Known failures or negative consequences are concealed or contradicted by the lesson account. There is no minimum count of counter-lessons.
Every lesson is framed so that a reader can derive an action or decision from it. Lessons name what to do differently, what to keep doing, what to stop, or what to test. Verbs and decisions are visible.
At least 80 percent of lessons are action-oriented. A small number remain observational but the bulk are decision-ready.
Roughly half of lessons are action-oriented. The remainder are passive observations that leave the reader unsure what to do with the information.
Most lessons are passive observations or descriptive statements. Few suggest action.
Lessons are descriptive only. No action framing is present.
Score Interpretation
Report blockers, the dimension profile, and evidence coverage first. Use these aggregate bands only when all five dimensions are applicable and sufficiently evidenced with no unresolved evidence conflict. Otherwise give no total, band, or rescaled equivalent. High documentation quality does not establish readiness, legal compliance, or approval.
| Total (out of 25) | Band | Next Step |
|---|---|---|
| 22-25 | Strong | Strong documentation profile only. Resolve blocking issues and obtain the applicable human review; this score does not authorize use. |
| 17-21 | Adequate | Prioritize source-linked revisions in the weakest dimensions. Request missing records before proposing additional activity; confirm the need for any new work from evidence. |
| 11-16 | Needs Revision | Use located findings as a revision brief. Distinguish reporting gaps from demonstrated design or implementation failures and label proposed work for confirmation. |
| 5-10 | Substantial Revision | Rework the evidence-backed weaknesses with accountable review. A low documentation profile alone does not establish that the underlying activity failed or must be repeated. |