Formative, Process, and Outcome Evaluation Types

Key Takeaways

  • Formative evaluation informs program design and early improvement before and during initial implementation; process evaluation assesses whether the program is delivered as planned; outcome evaluation measures whether the program produced the intended changes.
  • Process evaluation tracks five dimensions: fidelity, dose, reach, delivery versus receipt, and implementation context; these dimensions determine whether implementation occurred as intended.
  • Common implementation challenges include resource shortages, staff turnover, lack of leadership support, and community resistance; facilitators include existing coalitions, organizational champions, aligned funding, and community readiness.
  • Outcome evaluation operates in three tiers: short-term outcomes (knowledge, attitudes), intermediate outcomes (behavior and policy change), and long-term outcomes or impact (morbidity, mortality, health status).
  • Threats to validity in outcome evaluation include history, maturation, testing, selection, and attrition; recognizing which threat applies to a given scenario is heavily tested.
Last updated: July 2026

Quick Answer: Formative evaluation informs program design and improvement before and during implementation; process evaluation assesses whether the program is delivered as planned (fidelity, dose, reach); outcome evaluation measures whether the program produced the intended changes in knowledge, behavior, and health status.

The Three Evaluation Types Defined

The NBPHE task to develop and conduct formative, process, and outcome evaluations requires distinguishing three evaluation types by purpose, timing, and the questions each answers.

Evaluation TypePrimary QuestionTimingExample Methods
FormativeIs the program design feasible and appropriate?Before and during early implementationPilot tests, focus groups, expert review, material pretesting
ProcessIs the program being delivered as planned?During implementationActivity logs, participant counts, fidelity checklists, observations
OutcomeDid the program produce the intended changes?After implementation (short and long term)Pre/post surveys, comparison group designs, longitudinal tracking

Formative evaluation occurs in two phases: pre-implementation (needs assessment, pilot testing, material pretesting) and implementation (early monitoring to refine delivery). Its purpose is improvement, not judgment. Process evaluation is continuous and tracks whether implementation matches the program design. Outcome evaluation is summative — it judges whether the program achieved its goals.

Process Evaluation: The Core of Implementation Fidelity

The NBPHE task to ensure that program implementation occurs as intended depends on process evaluation. The key dimensions are fidelity, dose, reach, delivery versus receipt, and implementation context.

Fidelity asks whether the program was delivered as designed — were core components preserved and was adaptation within acceptable limits? Dose asks how much of the program was delivered, measured by number of sessions, duration, and content covered. Reach asks what proportion of the intended audience participated, measured by coverage rate and representativeness of participants. Delivered versus receipt recognizes that what was delivered is not always what participants took in — attendance does not equal engagement. Implementation context examines what external factors affected delivery, such as staff turnover, funding cuts, or competing events.

Fidelity monitoring uses several tools: structured observation checklists against the program protocol, participant feedback surveys, facilitator self-reports (which are subject to social desirability bias), and audio or video review. The challenge is that perfect fidelity in real-world settings is rare — programs adapt to local context, and the question becomes whether adaptation preserved core components.

Implementation Challenges and Opportunities

The NBPHE task to identify challenges of and opportunities for program implementation expects you to recognize common implementation barriers and facilitators.

Common challenges include insufficient resources (staff, funding, materials), staff turnover and inadequate training, lack of organizational leadership support, resistance from the target community or gatekeepers, competing priorities within the organization, policy or regulatory changes mid-implementation, and inadequate communication across partners.

Common opportunities or facilitators include existing coalitions and partnerships, organizational champions, aligned funding cycles, community demand and readiness, a supportive policy environment, an evidence-based program with clear protocols, and an adaptive program model that allows local tailoring.

The challenge-and-opportunity analysis is not theoretical — it should be built into the planning phase. A program that ignores likely barriers (for example, assuming clinics will donate staff time indefinitely) will struggle to maintain fidelity. Conversely, identifying existing assets (for example, an active community coalition) can accelerate implementation and improve reach.

Outcome Evaluation: Short, Intermediate, and Long-Term

Outcome evaluation measures change in the target population. The three outcome tiers map to the logic model. Short-term outcomes appear within weeks to months and include knowledge, awareness, attitudes, and skills. Intermediate outcomes appear over months to years and include behavior change, policy adoption, and environmental change. Long-term outcomes or impact appear over years and include morbidity, mortality, health status, and health equity.

A critical design question is whether to use an experimental design (randomized controlled trial), a quasi-experimental design (comparison group without randomization), or an observational design (no comparison group). The choice depends on feasibility, ethics, and the strength of inference needed. RCTs provide the strongest causal evidence but are often impractical in community settings; quasi-experimental designs such as pre/post with a matched comparison community are more common in public health program evaluation.

Threats to validity in outcome evaluation include history (external events coinciding with the program produce change), maturation (natural changes over time as participants grow, learn, or age), testing (pre-test affects post-test responses), selection (differences between program participants and non-participants), and attrition (differential dropout distorts results). Recognizing which threat applies to a given scenario is heavily tested.

Linking Evaluation Types to Program Decisions

The three evaluation types serve different decision points. Formative evaluation answers whether to modify the program before scaling. Process evaluation answers whether the program is being delivered as planned and, if not, why. Outcome evaluation answers whether the program worked and whether to continue, expand, or end it.

A common exam trap is applying the wrong evaluation type to a given question. For example, asking whether participants are satisfied with the training is a formative or process question, not an outcome question. Asking whether participants' knowledge increased is a short-term outcome question. Asking whether diabetes hospitalizations declined is a long-term outcome or impact question. Knowing which evaluation type answers which question is essential for selecting appropriate methods and interpreting results correctly.

Test Your Knowledge

During early implementation of a smoking cessation program, staff conduct focus groups with participants to refine the curriculum and pretest educational materials. This activity is an example of which evaluation type?

A
B
C
D
Test Your Knowledge

A process evaluation finds that a parenting program was delivered to 40% of the intended audience, with 70% of sessions completed as designed. Which two process evaluation dimensions do these findings describe?

A
B
C
D
Test Your Knowledge

Which threat to validity occurs when external events coinciding with a program produce observed changes that are mistakenly attributed to the program itself?

A
B
C
D