Inception Report: What It Is and What to Include

What Is an Inception Report

Definition

An inception report is the first formal deliverable an evaluation team gives the program or donor. It is written at the start of the work, after the contract is signed, an opening meeting with the client and some early desk review. It presents the team's complete plan for the evaluation, or for another assignment: the questions it will answer, the methods and samples, the tools, the ethics safeguards and the deliverables. The client reads it and approves the plan before fieldwork begins.

Why It Matters

The inception report is a quality gate between the Terms of Reference and primary data collection. The Terms say what the client wants to know. The inception report shows how the team will find out, and gives the client a chance to confirm that the plan fits what it needs before anyone is sent to the field.

Without this gate, teams sometimes find partway through data collection that the sampling is not feasible, the tools do not match the questions, or the client now cares about different questions. The inception report settles these points early, in writing, when changing course costs almost nothing.

Where It Fits

• Terms of Reference. Written by the client before the contract. It sets what the client wants to learn, the scope, the budget and the deliverables.
• Proposal. Written by the evaluation team before the contract. It offers an approach, a team and a price.
• Inception Report. Written by the evaluation team at the start of the work and approved by the client. It fixes the final questions, methods, samples, tools, plan and deliverables.
• Evaluation Matrix. Usually part of the inception report. It links each question to the evidence that will answer it.
• Final Evaluation Report. Written by the evaluation team at the end of the work. It gives the findings, conclusions and recommendations.

What It Includes

The outline below follows the downloadable template, in order. Each part says what it should do. A writer can read that as what to write, and a reviewer can read it as what to look for. A mid-sized evaluation usually runs 20 to 30 pages. To draft or score a report against this outline, use the inception report prompts and rubric. For a Word version with a filled example of deliverables, changes from the Terms and limitations, see the inception report template.

Executive Summary

One page that lets a busy reader approve the plan: what the program is, why the evaluation is happening, the design, the dates that matter and what the client is asked to approve. It is written last and placed first, and its numbers and dates match the rest of the report.

Background

• Context. The setting that shapes the evaluation: the population, geography, policy changes, and anything that affects access. Each point connects to a choice made later in the plan.
• Program Overview. The program's objectives, location, duration, participants, budget and targets, and how it is meant to work, using the program's own figures.

Evaluation Framework

• Purpose and Objectives. Who will use the findings and for what decision, followed by three to five objectives.
• Scope. What the evaluation covers and what it does not, so the client plans for exactly the work being delivered.
• Understanding of the Assignment. Shows the client that the team understands what is being asked and why, including how the team reads each question.

Example, from a Made-Up Program: Dovecrest and the funder want an independent, honest view of the program at its halfway point that they can act on. The Terms of Reference ask what is working, for whom and why, and they ask for practical recommendations for the rest of the program rather than a final verdict. The team reads effectiveness as progress against the outcome targets in the results framework, and equity as whether the poorest women, the youngest, women living with disability and women farthest from a facility are being reached as well as everyone else. The team will confirm this reading with the client before fieldwork begins.

• Evaluation Questions. The final questions, usually three to five main questions, traceable to the Terms of Reference, with any change explained.
• Evaluation Matrix. Each question linked to the evidence that will answer it: its sub-questions, the tool that will collect the answer, the sample it draws on and the limitations that apply. Every method in the plan appears at least once.

Methodology

• Design. The overall design, such as descriptive, theory-based, quasi-experimental or experimental, and why it fits the questions, the budget and the stage of the program.
• Desk Review. The documents to be reviewed, why each matters, who is responsible and when the review will be complete.
• Quantitative Methods. Each method, such as a survey or an analysis of monitoring data: its purpose, how many people or records, from whom, where, who carries it out and which question it answers.
• Qualitative Methods. Each method, such as key informant interviews, focus group discussions or observation: its purpose, how many, with whom, where, who carries it out and the main topics.
• Sampling. For each data source, the population, the sample size and how units are selected, with the calculation shown in a line or two.

Example, from a Made-Up Program: The survey sample is sized to estimate the facility birth rate across the three program districts with a margin of error of plus or minus 4 percentage points at 95 percent confidence. With a design effect of 1.8 for clustering and a 10 percent allowance for non-response, this needs 1,200 women. Results for each district (400 women) will carry a margin of about plus or minus 7 points and will be reported as indicative.

• Ethics. How participants are protected: ethical review, safeguarding and do-no-harm steps. It includes informed consent (how it is obtained, in what language and form), accessibility (how everyone selected can take part) and data protection (how data is stored, who sees it and when it is deleted).
• Data Tools. The instruments, who each is used with, how they will be tested and when they will be finalized, usually after a pilot.
• Limitations. What could limit the evidence, the effect on the findings and how each limit will be handled.

Deliverables

Every product the client will receive, with its format and due date. Working products such as tools and progress notes appear alongside the final report.

Common Mistakes

These are also the first things a client reviewer looks for.

Treating It as a Formality. Some teams copy the method from their proposal without refining it. Clients notice quickly, and it signals the team has not engaged with the program.

Over-Specifying Too Early. A plan that locks every detail before the pilot leaves no room to adjust. Propose a clear plan, and name the elements, such as sample size and instrument wording, that will be finalized after the pilot.

Skipping Stakeholder Consultation. A report built only from documents, without talking to implementers or the people the program serves, often needs major revision once the team hears from them. Consult them first.

Hiding Changes from the Terms. Changes from the Terms of Reference are common and usually justified, but burying them in the method text creates problems later. List each change in one place with its reason, so the client can agree to it.

A Matrix That Stops at the Question. A matrix that lists questions without sub-questions, tools, samples and limitations does not show how the evidence will be gathered. Complete every column for every question.

A Sample with No Logic. Writing 'we will interview stakeholders' without numbers, selection rules or a sample size leaves the client unable to judge feasibility. Show the calculation and the selection method.

Fieldwork Dates That Ignore Approval. Fieldwork scheduled to start before ethical review and client approval can be finished cannot go ahead as planned. Build in the time for both.

How It Varies

Often Added

Many clients and funders also ask for a fieldwork timeline with dates and dependencies, team roles and days, risks and how they will be handled, quality assurance arrangements, a list of any changes from the Terms of Reference with reasons, a sign-off page for the client's written approval, and annexes such as full instruments, a document review log, a stakeholder map and team CVs. Add whichever your client asks for.

Length by Size

• Small. A few weeks and one main method: 8 to 15 pages, with a shorter background and tools and methods sharing a section.
• Mid-Sized. Several methods in one country: 20 to 30 pages, following the full outline above.
• Large. Several countries or methods: 40 pages or more plus attachments, with a section for each country or method and fuller ethics and quality assurance.

Assignment Types

Inception reports are not one-size-fits-all. The emphasis shifts with what is being done.

• Impact Evaluation. The identification strategy (randomization, matching, difference-in-differences, synthetic controls), the counterfactual and how attribution claims will be supported, with sample size calculations and power analysis.
• Process or Implementation Evaluation. The analytical framework, such as a fidelity assessment, and how the team will tell design failure, implementation failure and measurement failure apart.
• Real-Time Evaluation. A compressed timeline and the feedback loop to program managers, including interim briefings and the turnaround between data collection and sharing findings.
• Meta-Evaluation. Document selection criteria, quality appraisal tools and the synthesis method, with an extraction template and coding framework in place of instruments.
• Formative or Developmental Evaluation. How findings are shared continuously rather than only at the end, and a collaborative sense-making schedule with the program team.
• Research Study. The research questions, literature review, ethical review and a dissemination plan.
• Assessment or Baseline. The indicator framework, sampling, tools and how the results will be reported.
• Technical Assistance or Training. The work plan, the starting capacity of those being supported, the schedule of deliverables and the handover.

In every case the report serves the same purpose: to confirm alignment between the team and the client before substantive work begins.

Client Formats

Some clients and agencies publish their own inception report format or quality checklist. United Nations agencies often follow the United Nations Evaluation Group quality checklist for Terms of Reference and inception reports, and many funders ask for the OECD DAC evaluation criteria: relevance, coherence, effectiveness, efficiency, impact and sustainability. Ask for the client's format at the first meeting. Where it differs from the template, follow the client's headings and keep the content.

Common Questions

Can fieldwork start before the report is approved? Usually not. Fieldwork waits for written approval, because the approval confirms the method, the sample and the tools. Desk review and logistics can continue.

Can the questions change after approval? Yes, with the client's written agreement. Small changes to wording do not need it. Changes to questions, sample, dates or budget do.

What if the Terms of Reference are unclear? Raise it early. Note the problem at the opening meeting, propose a clear reading in your statement of understanding, and record the client's answer in the report. If a change affects cost, schedule or scope, ask for written agreement.

Can I reuse my proposal? Reuse the team and roles, the overall design and its reasons, and the ethical safeguards. Rewrite the method with what you have learned, the questions if the client's priorities have shifted, and the sample, tools and timeline with real numbers and dates.

What happens after I submit it? The client reviews it, usually in one to two weeks, and sends one consolidated set of comments. The team revises, with a short note on how each comment was handled, and the client gives written approval before fieldwork begins.

Who approves it? The commissioner, usually the client focal point together with whoever holds budget authority. A funder may also need to approve.

What is an inception meeting? The first meeting between the evaluation team and the client after the contract is signed, often called a kickoff meeting. The team confirms the scope, the questions, the key contacts, the documents it needs and the timeline. What is agreed there goes into the inception report.

Does a small assignment need one? Yes, in a shorter form. Even a few pages confirm that the team understands the work and that the client agrees to the plan.