Utilization-Focused Evaluation
An approach that clarifies who will use evaluation, for which decisions and when, then selects questions and methods based on that use. It plans use beyond reporting. [1]
- Difficulty
- Intermediate
- Cost
- Medium
- Duration
- Illustrative estimate (adjust for scale and staffing): 1–4 weeks to identify users and focus the evaluation; total duration depends on scale
How it works at a glance
Utilization-focused evaluation identifies specific primary users and intended uses at the outset. Evaluation is designed with people who will make judgments or take action in response to findings, rather than abstract stakeholders. [1]
Questions, collection and reporting timing and formats are chosen for their usefulness. Allocate time and resources for interpretive discussion and support for actual use as well as analysis and reporting. [1]
- Preparation: confirm whether evaluation will be used
- Identify intended users
- Identify intended uses
- Focus evaluation questions
- Choose methods and design
- Collect, analyze and interpret data
- Document use plans and support implementation
When to use it and when it is unsuitable
When to use it
- Designing an evaluation that ensures use after earlier evaluations were shelved
- Linking findings directly to a specific decision, such as budget allocation or program continuation
- Clarifying whom the evaluation serves among diverse stakeholders
- When resources allow the evaluator to collaborate with users from the design stage
When it is unsuitable
- Where users cannot be identified or cannot participate in evaluation, such as when strictly external evaluation is required
- Where accountability takes priority over use and user involvement creates conflicts of interest
Participants, roles, and deliverables
Participants and roles
Evaluator as facilitator, identified primary users (around 1–5 people) and other stakeholders as needed
Main deliverables
- Document identifying users and intended uses
- Focused evaluation question list
- Evaluation report
- Evaluation use plan
Implementation steps
- Preparation: confirm whether evaluation will be usedCheck whether evaluation is truly needed and whether resources and willingness to use it exist. Reconsider conducting it if nobody can explain why it is needed now and by whom.
- Identify intended usersIdentify primary intended users by name. Designate specific people or a small group rather than the entire organization or stakeholders generally.
- Identify intended usesSpecify why identified users will use the evaluation. Identify concrete decisions or actions, such as renewing next year’s grant or redesigning training, rather than simply improvement.
- Focus evaluation questionsPrioritize questions directly relevant to users’ decisions. Determine numbers according to decision scope and feasibility.
- Choose methods and designExplain options and limitations understandably and select credible, feasible methods suited to the questions. Do not sacrifice information quality for simplicity.
- Collect, analyze and interpret dataInvolve users in analysis and interpretation wherever possible. Discussing the meaning of numbers together creates ownership before they receive the report.
- Document use plans and support implementationAgree before evaluation ends on a concrete plan stating who will do what by when. The evaluator follows up on use for a period after submitting the report.
Strengths and limitations
Strengths
- The only framework specifically dedicated to maximizing evaluation use and uptake
- Highly flexible design can be combined with any data collection or analysis method
- User participation additionally strengthens trust in evaluation and organizational evaluation capacity
Limitations
- Optimizing for particular users risks bias from other stakeholders’ perspectives
- Continuous communication with users requires evaluator time
- Restricting information for use can create tension with transparency and accountability
Common pitfalls
- Defining intended users as departments or organizations leaves nobody responsible; identifying individuals by name is the principle
- Users want to know everything and questions exceed 20; focus by asking what they would ask if limited to one question
- Evaluators become influenced by user preferences and self-censor critical analysis
Conditions of use and evidence
- Identify primary users and intended uses early and link subsequent evaluation decisions to them. [1]
Intake evaluation for the December budget meeting
The following fictional example evaluates intake so the manager can choose next year’s booking slots.
Scroll horizontally to view the table
| Primary user (name and role) | Intended use (specific decision or action) | Timing of use |
|---|---|---|
| Service manager A (fictional role) | Decide whether to pilot evening slots | December 2026 |
| Resident collaborator B (fictional role) | Check ease of use of the pilot proposal | November 2026 |
Common errors in judgment
Analyzing data to fit users’ preferred conclusions
How to revise
Provide evidence needed for decisions, including inconvenient findings
ReasonFocusing on use does not mean tailoring conclusions to please users.
Writing only “government” as the primary user
How to revise
Specify the responsible role, decision and deadline for use
ReasonThis enables concrete planning for use.
References and checked sections
- Utilisation-focused evaluationBetterEvaluation
- Section consulted
- Main text; two essential elements
- How it relates to the text
- Identify primary users and intended uses early and link subsequent evaluation decisions to them.
Editorial and checking information
How to cite this page
Change history
- — Corrected statements and procedures identified during content checks (U04). Preserved the order, number and labels of input fields and the section structure.
- — Updated explanations to correspond to the sources and added method-specific fictional completed examples, judgment examples and a change log.


