Definition
An inception report is the first formal deliverable from an evaluation team to the programme or donor. It is submitted after the evaluator has conducted initial document review, met with key stakeholders in an inception workshop, and refined the evaluation design. The inception report details the evaluation questions, refined methodology, data collection instruments (surveys, interview guides), sampling strategy, fieldwork timeline, roles and responsibilities, and any adjustments to the original Terms of Reference. It serves as the evaluation's working blueprint and is the client's opportunity to approve the methodology before field work begins.
Why It Matters
The inception report is a critical quality gate. Between the Terms of Reference and primary data collection, the evaluation team gains detailed understanding of the programme context, accessible data sources, and stakeholder expectations. Often, what seemed feasible in the ToR requires adjustment once the team is on the ground. The inception report surfaces these adjustments and requests client approval before the team invests in fieldwork.
Without this gate, evaluators sometimes discover partway through data collection that their sampling strategy is infeasible, their instruments are misaligned, or they are answering questions the client no longer cares about. The inception report prevents such costly course corrections mid-engagement.
What Does an Inception Report Include?
A standard inception report typically covers these sections, in roughly this order:
-
Programme overview. A concise summary of the programme being evaluated: its objectives, geographic scope, duration, implementing partners, and intended beneficiaries. This grounds the reader in the programme and signals that the evaluation team has understood the context before proposing methods.
-
Refined evaluation questions. The evaluation questions, revised based on initial document review and stakeholder input. The original Terms of Reference questions are usually retained, but they may be split, merged, or re-scoped to reflect what is actually answerable given the programme's design and available data.
-
Detailed methodology. The evaluation design (descriptive, theory-based, quasi-experimental, experimental), data sources used, sampling strategy including sample size and selection method, and analytical approach. This is the technical core of the report and the section clients scrutinize most carefully.
-
Data collection instruments. Draft or near-final survey questionnaires, interview guides, focus group discussion guides, observation checklists, and secondary data extraction templates. These are usually placed in annexes with a summary of the instrument logic in the main text.
-
Fieldwork timeline. A detailed schedule of data collection activities with key milestones: instrument finalization, enumerator training, pilot, primary data collection, data cleaning, and analysis. The timeline should identify dependencies and critical path items.
-
Analysis plan. How the data will be analyzed (quantitative methods, qualitative coding framework, mixed-methods integration strategy) and how findings will be structured in the final report. This section prevents the common problem of collecting data that cannot be analyzed to answer the evaluation questions.
-
Team roles and responsibilities. Who does what, including team leader, sector specialists, enumerators, data analysts, and quality assurance reviewers. Also describes the management structure, meeting cadence, and escalation paths.
-
Risks and mitigation strategies. Anticipated challenges, for example access constraints, data quality issues, respondent fatigue, political sensitivity, and a concrete plan for how the team will address each if it materializes.
-
Deviations from the ToR. Any changes from the original terms, with explanation and justification. This is often the most negotiated section and the one the client will want to approve explicitly.
The report typically runs 20-40 pages plus annexes, and concludes with a sign-off page where the client confirms that the methodology is acceptable before fieldwork begins.
Example Table of Contents
A well-structured inception report often follows this outline for a mid-sized evaluation (around 30 pages):
- Executive Summary (2 pages)
- Background and Context (3 pages)
- Evaluation Purpose, Objectives, and Questions (3 pages)
- Methodology (6 pages): design, data sources, sampling, analytical approach
- Data Collection Tools (2 pages summary, with full drafts in Annex)
- Fieldwork Plan and Timeline (3 pages including Gantt chart)
- Team Structure and Responsibilities (2 pages)
- Risk Assessment and Mitigation (2 pages)
- Ethical Considerations and Safeguarding (2 pages)
- Quality Assurance Arrangements (1 page)
- Deliverables and Reporting Schedule (1 page)
- Deviations from ToR with Rationale (1 page)
- Sign-off Page (1 page)
Annexes (usually 15-40 additional pages): full draft instruments, document review log, stakeholder map, bibliography, CVs of team members, and any preliminary findings from secondary data.
Common Mistakes
Treating it as a formality. Some teams copy-paste methodology language from their proposal without genuinely refining it. Clients catch this quickly, and it signals that the team has not engaged with the programme context.
Missing the sign-off. Without an explicit client sign-off, the inception report has no binding force. If issues arise during fieldwork, the team has no record that the client accepted the methodology. Always include a sign-off page and get it signed.
Not surfacing ToR deviations clearly. Deviations from the original Terms of Reference are common and usually justified, but burying them in methodology text instead of calling them out explicitly creates problems later. A separate section listing each deviation, the reason, and the client's response protects both sides.
Over-specifying too early. An inception report that locks every detail before pilot testing leaves no room to adjust. The better pattern is to propose a clear plan while identifying specific elements (sample size, instrument wording) that will be finalized after the pilot.
Skipping stakeholder consultation. Teams sometimes prepare inception reports based only on document review, without talking to implementers or beneficiary representatives. The report is usable, but the methodology often needs major revision once the team finally hears from the people who know the programme best.
Variation by Evaluation Type
Inception reports are not one-size-fits-all. Their emphasis shifts depending on what is being evaluated:
Impact evaluations. The methodology section is expanded to justify the identification strategy (randomisation, matching, difference-in-differences, synthetic controls), describe the counterfactual in detail, and explain how attribution claims will be supported. Sample size calculations with statistical power analysis are expected.
Process or implementation evaluations. The analytical framework (such as a process evaluation framework or fidelity assessment matrix) is usually featured prominently. The report explains how the team will distinguish between design failure, implementation failure, and measurement failure.
Real-time evaluations. The fieldwork timeline compresses and the feedback loop to programme managers is emphasized. These reports often include the format of interim briefings and the turnaround time between data collection and sharing findings.
Meta-evaluations. Document selection criteria, quality appraisal tools, and synthesis methodology take center stage. The instruments section is replaced by an extraction template and coding framework.
Formative or developmental evaluations. The report often describes how findings will be shared continuously rather than only in a final report, and includes a collaborative sense-making schedule with programme teams.
In every case, the report serves the same purpose: to confirm alignment between the evaluation team and the client before substantive work begins.
Related Topics
- Scope of Work - The detailed specification of what the evaluator will deliver
- Evaluation Questions - The overarching inquiries the evaluation will answer
- Terms of Reference - The formal document commissioning the evaluation
- Reporting Best Practices - Standards for evaluation report quality and use