Document-based Program Evaluation
Also known as: documentary program evaluation, records-based evaluation, document review evaluation, archival program evaluation
Document-based program evaluation is a systematic approach to assessing a program's design, implementation, and outcomes using existing documentary evidence — such as policy statements, implementation reports, budgets, meeting minutes, and program artifacts — rather than primary data collection through interviews or observation. It is particularly suited to retrospective evaluations, accountability reviews, and contexts where direct fieldwork is impractical or infeasible.
Read the full method
Sign in with a free account to read this section.
Method map
The neighbourhood of related methods — select a node to explore.
When to use it
Use document-based program evaluation when primary data collection is impractical (the program has ended, key stakeholders are unavailable, or budget is limited), when an accountability or compliance audit is required, or when contemporaneous records are rich enough to answer the evaluation questions. It is especially valuable for retrospective evaluations of completed projects and for triangulating findings from interview- or survey-based evaluations. Do NOT use it as the sole method when the evaluation question requires understanding stakeholder experiences, perceptions, or unrecorded processes; documents capture formal outputs and decisions, not informal dynamics. Avoid it when the documentary record is sparse, incomplete, or heavily redacted, as evaluative conclusions will be unreliable.
Strengths & limitations
- Uses existing records, reducing the time and cost of primary data collection.
- Documents created during program operation are not subject to retrospective recall bias.
- Highly suitable for retrospective evaluations of programs that have concluded.
- Provides an auditable evidence trail — evaluative judgments are directly traceable to source documents.
- Can be combined with interviews or observations to triangulate and strengthen conclusions.
- Documentary records capture only what was formally recorded; informal decisions, interpersonal dynamics, and unintended processes leave no paper trail.
- Program documents are often written to satisfy funders or regulators, introducing a self-presentational bias that the evaluator must account for.
- Incomplete or inaccessible archives limit the scope and confidence of conclusions.
- Cannot assess participant experiences or subjective outcomes without supplementary primary data collection.
Frequently asked
What types of documents are typically used?
Funding proposals, logic models, implementation plans, progress and final reports, financial accounts, meeting minutes, correspondence, policy statements, program artifacts, and any records generated during program operation. The inventory should be comprehensive and systematically logged.
How do I handle missing or inaccessible documents?
Missing documents are a significant limitation and must be explicitly acknowledged. Note what is missing, why access was not possible, and how the gap affects the confidence of specific evaluative conclusions. Do not substitute inference for evidence.
Is document-based evaluation less rigorous than interview-based evaluation?
Not inherently — rigor depends on systematic document selection, authenticity appraisal, transparent coding, and clear linkage between evidence and conclusions. In some respects documents are more reliable than retrospective interviews because they were created at the time of program operation. The methods are complementary, not hierarchical.
Can I combine document analysis with interviews?
Yes, and doing so is strongly recommended when feasible. Documents establish the formal record; interviews can clarify ambiguities, reveal informal processes, and provide stakeholder perspectives. Mixed-method evaluation designs routinely triangulate documentary evidence with primary data.
How is this different from historical archival research?
Both use existing documents, but the purposes differ. Historical archival research aims to reconstruct or interpret past events and their meaning. Document-based program evaluation aims to judge program performance against stated objectives and criteria — it is inherently evaluative, not merely descriptive or interpretive.
Sources
- Stufflebeam, D. L., & Shinkfield, A. J. (2007). Evaluation Theory, Models, and Applications. Jossey-Bass. ISBN: 978-0787908331
- Rossi, P. H., Lipsey, M. W., & Freeman, H. E. (2004). Evaluation: A Systematic Approach (7th ed.). Sage. ISBN: 978-0761908944
How to cite this page
ScholarGate. (2026, June 3). Document-based Program Evaluation. ScholarGate. https://scholargate.app/en/field-methods/document-based-program-evaluation
Which method?
Set this method beside its closest kin and read them side by side — the library lays the books on the table; the choice is yours.
- Case Law AnalysisField Methods↔ compare
- Content AnalysisQualitative↔ compare
- Curriculum AnalysisField Methods↔ compare
- Document AnalysisQualitative Research↔ compare
- Historical Archival ResearchField Methods↔ compare
- Program EvaluationField Methods↔ compare