Developmental evaluation embedded-support worksheet

This worksheet enables the evaluator and team to establish an agreement for embedded support. Clarify the evaluator’s involvement and learning arrangements beforehand.

When to use this worksheet and what completion involves Fictional completed example

EvalCompass Worksheet

Developmental evaluation embedded-support worksheet

Method: Developmental Evaluation

This worksheet enables the evaluator and team to establish an agreement for embedded support. Clarify the evaluator’s involvement and learning arrangements beforehand.

Basic information

Enter the program’s characteristics and reasons for selecting DE

Completed example for this section (fictional)

This fictional example is for explanation. Adapt it to your own program. Your entries will not change.

Program name: Youth community space pilot (fictional)
Program phase (exploration / development / expansion / transition): Exploration and development
Evaluator name: Embedded evaluation officer
Embedded-support period: September–December 2026

Reason for this entry: Do not yet fix the final operating model.

Program name

Program phase (exploration / development / expansion / transition)

Evaluator name

Embedded-support period

Writing tips and explanation for this section

About this section

Enter the program’s characteristics and reasons for selecting DE

Do not yet fix the final operating model.

View the method explanation

Writing tips

Follow each field’s heading to record the program name, focus, period, and other details. Leave undecided matters clearly marked as unresolved.

Read the full fictional example

Assess complexity

Identify which program aspects are complex and emergent

Completed example for this section (fictional)

This fictional example is for explanation. Adapt it to your own program. Your entries will not change.

Scroll horizontally to view the table

Element of complexity	Specific manifestation in this program	Implications for evaluation
Diverse motivations for use	Some want conversation; others want quiet	Ask separately about different experiences, rather than only average attendance
Changing operating conditions	Intake capacity varies with volunteer numbers	Always record staffing on pilot days

Reason for this entry: Turn uncertainty into matters to examine in evaluation.

Scroll horizontally to view the table

Element of complexity	Specific manifestation in this program	Implications for evaluation

Writing tips and explanation for this section

About this section

Identify which program aspects are complex and emergent

Turn uncertainty into matters to examine in evaluation.

View the method explanation

Writing tips

Keep the information in each row aligned. Scroll wide tables horizontally to see every column.

Read the full fictional example

Define evaluator roles and boundaries

Agree on team involvement and boundaries maintaining independence

Completed example for this section (fictional)

This fictional example is for explanation. Adapt it to your own program. Your entries will not change.

Scroll horizontally to view the table

Setting for involvement (meetings / processes)	Evaluator role (observation / participation / facilitation)	Boundaries maintaining independence
Fortnightly operational reflection	Organize records and propose questions	The operating manager decides what to adopt. Record contrary evidence in minutes too

Reason for this entry: Clarify responsibility for judgments while providing ongoing support.

Scroll horizontally to view the table

Setting for involvement (meetings / processes)	Evaluator role (observation / participation / facilitation)	Boundaries maintaining independence

Writing tips and explanation for this section

About this section

Agree on team involvement and boundaries maintaining independence

Clarify responsibility for judgments while providing ongoing support.

View the method explanation

Writing tips

Keep the information in each row aligned. Scroll wide tables horizontally to see every column.

Read the full fictional example

Ongoing learning arrangements

Design regular reflection sessions (frequency, participants, questions and outputs)

Completed example for this section (fictional)

This fictional example is for explanation. Adapt it to your own program. Your entries will not change.

Scroll horizontally to view the table

Type of reflection	Frequency	Participants	Central question
Pilot reflection	Every 2 weeks	Operators, voluntarily participating young people and evaluation officer	Who found participation easy and who had difficulties? / What single change should be tried next?

Reason for this entry: Use questions enabling comparisons even over short cycles.

Scroll horizontally to view the table

Type of reflection	Frequency	Participants	Central question

Writing tips and explanation for this section

About this section

Design regular reflection sessions (frequency, participants, questions and outputs)

Use questions enabling comparisons even over short cycles.

View the method explanation

Writing tips

Keep the information in each row aligned. Scroll wide tables horizontally to see every column.

Read the full fictional example

Current program hypotheses and uncertainties

Describe current, potentially changing program logic hypotheses and the greatest uncertainty

Completed example for this section (fictional)

This fictional example is for explanation. Adapt it to your own program. Your entries will not change.

Drop-in participation broadens access, but crowding may reduce feelings of safety. Combine booked and drop-in places and examine experiences during visits and reasons for giving up.

Reason for this entry: Consider hypotheses about both positive and negative effects.

Writing tips and explanation for this section

About this section

Describe current, potentially changing program logic hypotheses and the greatest uncertainty

Consider hypotheses about both positive and negative effects.

View the method explanation

Writing tips

Use the example as a reference and record what you have established about your own program. Distinguish assumptions and unchecked matters from confirmed facts.

Read the full fictional example

Before writing, check when to use the worksheet and what completion involves

Developmental evaluation embedded-support worksheet is a worksheet for applying Developmental Evaluation in meetings or individual work. For the overall duration of the method, use “Illustrative estimate (adjust for scale and staffing): embedded support throughout the program (several months to years), with monthly to quarterly reflection sessions” as a reference, adjusting for scale and resources. Fill in what you know provisionally and leave unresolved matters as questions to check next.

When this worksheet is useful

Evaluating social innovation or new models where objectives themselves may change
Multi-agency programs addressing complex social issues such as homelessness or climate adaptation
Pilot programs built around experimentation and pivots that need learning and real-time decision support

Participants and preparation

An evaluator with complexity and evaluation expertise joins the core team. Outside experts are often involved in periodic reviews.

Bring the materials used for decisions, existing data, and differing stakeholder views to help complete the worksheet.

Suggested order

1. Basic informationEnter the program’s characteristics and reasons for selecting DE
2. Assess complexityIdentify which program aspects are complex and emergent
3. Define evaluator roles and boundariesAgree on team involvement and boundaries maintaining independence
4. Ongoing learning arrangementsDesign regular reflection sessions (frequency, participants, questions and outputs)
5. Current program hypotheses and uncertaintiesDescribe current, potentially changing program logic hypotheses and the greatest uncertainty

Signs the worksheet is ready for review

Program hypothesis map (systems map)
Periodic reflection reports
Learning summary by phase

Cautions for review

Abandoning all indicators and logic because the program is complex, leaving only informal conversation and reflection
Evaluators become assimilated into the team and lose critical perspective (going native)
Failing to document learning from embedded evaluation allows it to disappear when staff change

Guides to read before starting

Read a completed fictional example (your entries will not change)

Fictional example; not actual results

The following fictional example explores whether bookings or drop-in participation are more accessible in a new youth community space.

Basic information

Program name: Youth community space pilot (fictional)
Program phase (exploration / development / expansion / transition): Exploration and development
Evaluator name: Embedded evaluation officer
Embedded-support period: September–December 2026

Reason for this entry: Do not yet fix the final operating model.

Assess complexity

Scroll horizontally to view the table

Element of complexity	Specific manifestation in this program	Implications for evaluation
Diverse motivations for use	Some want conversation; others want quiet	Ask separately about different experiences, rather than only average attendance
Changing operating conditions	Intake capacity varies with volunteer numbers	Always record staffing on pilot days

Reason for this entry: Turn uncertainty into matters to examine in evaluation.

Define evaluator roles and boundaries

Scroll horizontally to view the table

Setting for involvement (meetings / processes)	Evaluator role (observation / participation / facilitation)	Boundaries maintaining independence
Fortnightly operational reflection	Organize records and propose questions	The operating manager decides what to adopt. Record contrary evidence in minutes too

Reason for this entry: Clarify responsibility for judgments while providing ongoing support.

Ongoing learning arrangements

Scroll horizontally to view the table

Type of reflection	Frequency	Participants	Central question
Pilot reflection	Every 2 weeks	Operators, voluntarily participating young people and evaluation officer	Who found participation easy and who had difficulties? / What single change should be tried next?

Reason for this entry: Use questions enabling comparisons even over short cycles.

Current program hypotheses and uncertainties

Drop-in participation broadens access, but crowding may reduce feelings of safety. Combine booked and drop-in places and examine experiences during visits and reasons for giving up.

Reason for this entry: Consider hypotheses about both positive and negative effects.

Common errors in judgment

Assuming that changing policy every time constitutes developmental evaluation

How to revise: Record reasons for changes, trial conditions and findings

Reason: Evidence enabling learning from trials is necessary.

Having the evaluator take all operational decisions

How to revise: Separate analytical advice from decision-making roles

Reason: This maintains responsibility and critical examination despite close involvement.

Editorial and checking information

Content updated: 2026-10-07Source checked: 2026-09-13 (includes AI cross-checking)No documented human reviewIncludes fictional examplesEditorial policy and scope of checking Cite this page Report a correction

References and checked sections

Developmental evaluation
BetterEvaluation
Section consulted
Main text; Purpose; Complexity & uncertainty
How it relates to the text
Its main purpose is supporting adaptation and program development under uncertainty, rather than applying to every evaluation.
Source checked: 2026-09-13 (includes AI cross-checking)

How to cite this page

EvalCompass Editorial Team. “Developmental evaluation embedded-support worksheet”. EvalCompass, updated 2026-10-07. https://evalcompass.jun-nakatani.com/en/worksheets/developmental-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

2026-10-07 — Corrected statements and procedures identified during content checks (U08). Preserved the order, number and labels of input fields and the section structure.
2026-09-13 — Updated explanations to correspond to the sources and added method-specific fictional completed examples, judgment examples and a change log.