Evaluation frameworksEvaluation useStakeholder engagementIntended usersPatton

Utilization-Focused Evaluation

Utilization-Focused Evaluation
Also known as: UFE、Use-oriented 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
Content updated: 2026-10-07Source checked: 2026-09-13 (includes AI cross-checking)No documented human reviewIncludes fictional examples

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]

  1. Preparation: confirm whether evaluation will be used
  2. Identify intended users
  3. Identify intended uses
  4. Focus evaluation questions
  5. Choose methods and design
  6. Collect, analyze and interpret data
  7. Document use plans and support implementation
Sequence of implementation steps. See “Implementation steps” for details of each stage.

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

  1. Preparation: confirm whether evaluation will be used
    Check 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.
  2. Identify intended users
    Identify primary intended users by name. Designate specific people or a small group rather than the entire organization or stakeholders generally.
  3. Identify intended uses
    Specify 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.
  4. Focus evaluation questions
    Prioritize questions directly relevant to users’ decisions. Determine numbers according to decision scope and feasibility.
  5. Choose methods and design
    Explain options and limitations understandably and select credible, feasible methods suited to the questions. Do not sacrifice information quality for simplicity.
  6. Collect, analyze and interpret data
    Involve users in analysis and interpretation wherever possible. Discussing the meaning of numbers together creates ownership before they receive the report.
  7. Document use plans and support implementation
    Agree 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]
Fictional example; not actual results

Intake evaluation for the December budget meeting

The following fictional example evaluates intake so the manager can choose next year’s booking slots.

Primary user (name and role)Intended use (specific decision or action)Timing of use
Service manager A (fictional role)Decide whether to pilot evening slotsDecember 2026
Resident collaborator B (fictional role)Check ease of use of the pilot proposalNovember 2026

Common errors in judgment

Common mistake

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.

Common mistake

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

  1. Utilisation-focused evaluation
    BetterEvaluation
    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.
    Source checked: (includes AI cross-checking)

Editorial and checking information

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. “Utilization-Focused Evaluation”. EvalCompass, updated 2026-10-07. https://evalcompass.jun-nakatani.com/en/methods/utilization-focused/
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
  • — 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.