Program Evaluation Data Readiness Checklist | EVALCORP

What to Gather Before Scoping a Program Evaluation: A Data Readiness Checklist

An organization does not need perfect data before speaking with an evaluator. It does need a clear account of what information exists, who can access it, and what decisions the evaluation is meant to support.

Preparing that account can make early scoping discussions more productive. It helps distinguish questions that may be answered with existing records from questions that require new collection, a different design or more time.

Begin with the decision the findings must inform

Write one or two sentences describing the decision ahead. Is leadership considering a program expansion, reviewing implementation, or deciding how to improve access? Add the date by which findings would be useful and identify the intended decision-makers.

Keep this statement separate from a preferred method. Specifying a survey before agreeing on the question may narrow the work prematurely. EVALCORP’s guidance on asking good evaluation questions offers a useful starting point for this discussion.

Create a simple inventory of existing information

List each potentially relevant source, such as enrollment records, service logs, participant feedback, prior reports or budget records. For each source, record:

  • Its owner and the person who understands how it is collected.
  • The population, program and dates it covers.
  • How frequently it is updated.
  • Key definitions, including what counts as a participant or completed service.
  • Known missing fields, changes in collection methods or other limitations.

The inventory is a map, not a request to email confidential records. Start with descriptions and approved, nonidentifying examples. Decide how any sensitive information can be shared only after appropriate permissions and safeguards are established.

Explain the program behind the records

Gather available program descriptions, intended outcomes and documentation of important changes. If eligibility, staffing or service delivery changed during the reporting period, note when that happened. Otherwise, apparently comparable totals may describe different activities.

Ask frontline staff what the records fail to capture. A database may show that someone attended, but not explain a transportation barrier or an unexpected benefit. Community and participant perspectives can help identify which missing information matters.

Make constraints visible before fixing the scope

Record expected approval steps, data-sharing restrictions, staff availability and reporting deadlines. Distinguish a hard requirement from a preference. If a partner controls a needed dataset, name that dependency without promising access that has not been granted.

Be clear about the conclusions you hope to draw. Counts of services delivered and changes observed among participants do not, by themselves, establish that a program caused an outcome. The evaluation design must support the claims leadership intends to make.

Use the inventory to choose the next step

The initial conversation may identify a feasible evaluation, a targeted data-quality improvement, or a preliminary phase to clarify what can be answered. Each can be useful when it is connected to a real decision.

EVALCORP offers program evaluation and Data Utility Assessment & Planning services. Discuss your program and decision timeline with EVALCORP to explore a scope that reflects both the questions and the available evidence.

“If you can’t measure it, you can’t improve it.“

– Peter Drucker

Let’s Connect