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 study questions, design, data inventory, proposed analysis steps, and method-specific quality procedures.
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
All 4 elements: Each research or evaluation question has a defined analytical approach (no orphan questions). The approach is appropriate to the question type (descriptive, inferential, exploratory, explanatory, normative). The order of analytical steps is logical and the sequence is clear. A mapping table or equivalent makes the question-method link visible to a reader.
Three of four elements adequately specified; the remaining element incomplete: Question-method mapping covers most questions; ordering or visible mapping table partial.
Mapping is implicit. Some questions have approaches; others left undefined. Order of analysis loosely described.
Methods listed without clear mapping to questions. Order absent.
No mapping between questions and analysis. Questions and methods sit in unrelated sections.
All 4 elements: Specific methods are named (e.g., "logistic regression with the four covariates listed and clustered standard errors at facility level," not "regression analysis"). For qualitative work, the specific approach is named (thematic, framework, grounded theory, content analysis) with a coding strategy described. Software or tools are named where relevant (Stata, R, NVivo, Dedoose, Excel). Method choice is justified (why this method, not another).
Three of four elements adequately specified; the remaining element incomplete: Methods specific and tools named; justification or coding strategy partial.
Methods named at category level only. Tools mentioned. Coding strategy and justification thin.
Generic method labels ("we will analyze qualitatively"). No tools. No justification.
No methods named or methods incompatible with the data described.
All 4 elements: Handling of missing data is specified (rules, thresholds, imputation approach if any, or documented exclusion logic). Outlier or anomaly handling is defined with rules for inclusion or exclusion. Data integration logic is clear when combining sources (how survey and admin data merge, how qualitative and quantitative findings connect). Data transformations are documented (recoding, scaling, derived variables).
Three of four elements adequately specified; the remaining element incomplete: Missing data and outliers handled; integration or transformations partial.
Generic statement of "we will handle missingness." Outliers mentioned. Integration vague. Transformations undocumented.
No missingness rules. No outlier rules. Integration assumed.
No data preparation plan.
The evidence strategy fits the questions and justified method or methods. Necessary checks and handling of contradictions are explicit. Integration or weighting is specified where relevant. A single-method analysis can meet this anchor.
The strategy is appropriate and operational; one nonmaterial check or synthesis detail is incomplete.
The strategy is partly described, but important contradictions or the evidence-to-claim link need clarification.
Necessary checks or synthesis are absent, or integration is asserted without an operational method.
The strategy cannot support the claims or falsely presents unsupported checks as validation.
Quality checks fit the analytic tradition and risks, with responsibilities and timing. Sensitivity or alternative-interpretation checks are specified where meaningful or nonapplicability explained. Decisions have an audit trail, and limitations state what cannot be answered. Reflexive qualitative work need not use inter-rater reliability.
Appropriate checks, audit trail, and limitations are substantially specified; one minor operational detail remains.
Some appropriate checks are specified but responsibilities, audit trail, or material limitations are incomplete.
Quality assurance is generic or method-inappropriate; material analytical risks lack a response.
No appropriate checking is specified, or validation is claimed beyond what the procedures can establish.
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. |