Practical evaluation guide

What is process evaluation? Examining implementation for program improvement

An explanation of process evaluation, differences from outcome evaluation, evaluation items, collection and use for improvement.

Examine implementation through five questions

This is the practical framework used in this guide. It is not a universal scale for every program; adapt it to the improvement questions you need to answer. Read the full explanation

Main takeaway

Process evaluation assesses whom a program served, how and with what quality. It identifies implementation successes and barriers invisible in outcomes alone and judges whether delivery matched expectations and where improvement is needed. [1]

When outcomes do not emerge, appropriate improvement requires distinguishing problems in the program's underlying approach from failure to deliver as planned. Process evaluation examines this distinction.

Even successful programs are difficult to replicate elsewhere or in another year without recording which delivery elements worked. Making implementation visible supports expansion as well as improvement.

Look for improvements in implementation

Distinguish implementation from outcomes, then examine implementation questions, routine records, and decisions for improvement.

Differences from outcome evaluation

Outcome evaluation examines target-group changes. Process evaluation examines whether the program intended to produce them was delivered to the intended group with the planned content, frequency and quality.

For low participation and unclear outcomes, process evaluation can identify problems in outreach, timing, registration or staff deployment. It prevents rejecting the whole program based solely on outcome figures.

Differences from outcome evaluation
PerspectiveProcess evaluationOutcome evaluation
Main questionWas delivery as planned while maintaining quality?What changed for the target group?
Main dataImplementation records, participation, observation and staff/user accountsIndicators, surveys, follow-up, comparisons and cases
Main useImprovement during implementation and checking replicabilityContinuation, expansion or termination decisions
What is missed if omittedReach and delivery qualityWhether change occurred and what it means
[1]

Five implementation questions

This guide organizes practical checks into reach, quantity, quality, participant responses and implementation conditions. These are not a fixed common scale. Select implementation elements relevant to outcome pathways and check what followed plans and what changed.

Distinguish reach from implementation quality: whether targets were reached differs from whether content was provided as intended. Even high participation can imply different outcome interpretations if necessary support was insufficient.

  • Reach: was the intended group reached?
  • Quantity: did counts, time and support volume follow plans?
  • Quality: were necessary content, procedures and expertise maintained?
  • Participant responses: how accessible and acceptable was delivery?
  • Conditions: what constraints concerned staffing, coordination, venue or institutions?
Practical framework or suggestion

Integrate data collection into routine work

Requiring many new frontline records is unsustainable. First inventory attendance lists, consultation records, meeting notes, inquiries and staff reflections, then add only missing information in brief forms.

Combine brief surveys, interviews and observations of delivery to check user experiences. Alongside numbers, retain examples of practical innovations and barriers to make improvements easier to develop.

  1. Select important implementation elements from the logic model
  2. Set evaluation items for reach, quantity, quality and conditions
  3. Check information available in existing records
  4. Create concise forms only for missing information
  5. Review numbers and examples in routine meetings
  6. Record improvements and implementation-condition changes
Practical framework or suggestion

Interpret results for improvement

Results inform where changes might improve outcomes as well as judgments of quality. Compare reach across target groups, sites with different conditions and cases with or without outcomes to develop hypotheses.

Avoid asserting conclusions from a few cases alone. Compare numbers, observations and staff/user accounts, design a small next improvement trial and check it again through monitoring.

  • Compare results by target group, site and period
  • Record implementation conditions in high-outcome cases
  • Do not attribute problems solely to insufficient staff effort
  • Avoid adding too many improvements at once
  • Check post-change results in subsequent monitoring
Practical framework or suggestion
Fictional example; not actual results

Use implementation records to explore why consultation does not reach people

A fictional example for illustration: an outreach program held 4 sessions but use was lower than expected.

CheckIllustrative observationChange to consider
Delivery volumeAll 4 planned sessions heldCheck reach before simply adding sessions
ReachFew employed people use the serviceAsk preferences for evenings or other weekdays
Implementation conditionsVenue available only on weekday daytimeCheck venue-change costs and consultation arrangements
QualityNecessary explanations and follow-up providedCheck whether quality can continue after time changes

What this example supports

Distinguish delivery of planned session counts from reaching people in need. Evening sessions are an improvement proposal, not a proven effective response.

Common errors in judgment

Assume implementation succeeded because the planned count was met

How to revise: Check those reached, those not reached and content provided

Reason: Counts alone do not establish appropriate implementation.

Assume the program's theory is wrong because outcomes did not occur

How to revise: Examine implementation as intended separately from theory validity

Reason: Implementation conditions may have interrupted the outcome pathway.

Put it into practice next

Record outcome-related delivery elements and checks in the observation worksheet

Frequently asked questions

Does process evaluation wait until outcomes occur?

Starting during implementation supports improvement. Set items and records at the beginning and review regularly.

Do participant numbers alone constitute process evaluation?

They are an important part, but do not establish delivery quality or reasons for non-reach. Check reach, quality and conditions too.

Are interviews necessary for process evaluation?

Not mandatory, but useful for barriers, innovations and experiences invisible in records and numbers alone.

References and checked sections

  1. Magenta Book: Central Government guidance on evaluation
    HM Treasury / Evaluation Task Force · 2026
    Section consulted
    1.7.1 Relationship between benefits management and evaluation / 1.8.1 Process evaluation
    How it relates to the text
    Complementarity of continuous tracking and evaluation; examining implementation, context and improvement
    Source checked: (includes AI cross-checking)
Content updated: Source checked: (includes AI cross-checking)No documented human reviewIncludes fictional examplesEditorial policy and scope of checkingCite this pageReport a correction

How to cite this page

EvalCompass Editorial Team. “What is process evaluation? Examining implementation for program improvement”. EvalCompass, updated 2026-10-07. https://evalcompass.jun-nakatani.com/en/guides/process-evaluation/
Add the date you accessed the page. Text created by this site is available under CC BY 4.0. Quotations, external materials, and bundled fonts have their own terms of use. When reusing content, credit the source, link to the license, and indicate any changes.

Suggest a correction or improvement to this page

Change history
  • — A cross-guide review clarified indicator formats, outcome classifications and causal judgments, interpretation of tables, and the scope of SVI2026 where relevant.
  • — Distinguished original methodological sources from practical guidance and added specific fictional examples, judgment examples and next actions. Revised categorical claims about classification and measurement conditions.