Rapid evaluation design and implementation worksheet

Define what must be decided within the short period at the outset. Collect enough evidence for the next decision rather than investigating everything.

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

EvalCompass Worksheet

Rapid evaluation design and implementation worksheet

Method: Rapid Evaluation

Define what must be decided within the short period at the outset. Collect enough evidence for the next decision rather than investigating everything.

Basic information

Record the rapid evaluation's purpose and deadline.

Completed example for this section (fictional)

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

Program evaluated: Consultation desk (fictional)
Decision to be made: Whether to change staff assignments on Monday mornings
Evaluation period: 2 weeks (fictional)
Decision deadline: Next management meeting
Responsible person: Evaluator A

Reason for this entry: Limit intended use according to the deadline.

Program evaluated

Decision to be made

Evaluation period

Decision deadline

Responsible person

Writing tips and explanation for this section

About this section

Record the rapid evaluation's purpose and deadline.

Limit intended use according to the deadline.

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

Questions and evidence requirements

Define the minimum evidence needed for each question.

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

Evaluation question	Required sources	Minimum cases or documents	Conditions for use in decisions
Which processes stall on Monday mornings?	Reception records, observations and staff	Initial plan: records from the last 4 weeks and observation on 2 days	Treat conclusions as provisional if collection is insufficient.

Reason for this entry: Counts are initial values for this fictional plan, not universal minimums.

Scroll horizontally to view the table

Evaluation question	Required sources	Minimum cases or documents	Conditions for use in decisions

Writing tips and explanation for this section

About this section

Define the minimum evidence needed for each question.

Counts are initial values for this fictional plan, not universal minimums.

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

Collection plan

Assign data collection methods feasible within the short period.

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

Method	Population or subject	Date implemented	Responsible person	Hypothesis to check
Reception record review	4 weeks of records	Week 1	Staff member A	Concentration in data entry
Observation and interviews	Monday reception and responsible staff	Weeks 1–2	Staff member B	Scope to improve role allocation

Reason for this entry: Review records first to focus observations.

Scroll horizontally to view the table

Method	Population or subject	Date implemented	Responsible person	Hypothesis to check

Writing tips and explanation for this section

About this section

Assign data collection methods feasible within the short period.

Review records first to focus observations.

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

Confidence in conclusions

Separate higher-confidence findings from issues requiring further verification.

Completed example for this section (fictional)

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

Relatively certain: reviewed records show long waits on Monday mornings. Provisional: unclear data entry responsibility may contribute. Unchecked: impacts on service users and patterns outside busy periods.

Reason for this entry: Distinguish strengths of evidence.

Writing tips and explanation for this section

About this section

Separate higher-confidence findings from issues requiring further verification.

Distinguish strengths of evidence.

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

Completion check

Completed example for this section (fictional)

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

☑ Checked: Focused questions according to the decision deadline and evidence needs
☑ Checked: Checked main findings using multiple sources
☑ Checked: Specified limitations and further verification needs
☑ Checked: Defined the next improvement actions and responsible staff

Reason for this entry: This example focuses on 1 question needed for the next decision. Staff member A proposes a trial redistribution of roles.

Focused questions according to the decision deadline and evidence needs
Checked main findings using multiple sources
Specified limitations and further verification needs
Defined the next improvement actions and responsible staff

Writing tips and explanation for this section

About this section

This example focuses on 1 question needed for the next decision. Staff member A proposes a trial redistribution of roles.

View the method explanation

Writing tips

Read each item and check those you have confirmed. Do not use the fictional example’s checkbox states as findings about your own program.

Read the full fictional example

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

Rapid evaluation design and implementation worksheet is a worksheet for applying Rapid Evaluation in meetings or individual work. For the overall duration of the method, use “Planning example, not a universal standard duration: a few days–4 weeks in a short cycle with a focused scope” 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

When an improvement decision is needed within a few weeks
When understanding field conditions and key hypotheses before a large evaluation
When identifying what to change next in the early stages of a new program or pilot

Participants and preparation

1–2 evaluators, a field manager and several service users or stakeholders. Involvement of decision-makers able to act quickly is important.

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

Suggested order

1. Basic informationRecord the rapid evaluation's purpose and deadline.
2. Questions and evidence requirementsDefine the minimum evidence needed for each question.
3. Collection planAssign data collection methods feasible within the short period.
4. Confidence in conclusionsSeparate higher-confidence findings from issues requiring further verification.
5. Completion check

Signs the worksheet is ready for review

Rapid evaluation brief
Key findings and confidence levels
Next improvement actions

Cautions for review

Treating rapid evaluation as careless evaluation without defining questions, evidence requirements or limitations
Hearing only favorable views without seeking contrary views from service users or field staff
Presenting exploratory findings as conclusions from rigorous effect evaluation

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

Fictional example; not actual results

A fictional illustrative 2-week evaluation plan with observations created for explanation.

Basic information

Program evaluated: Consultation desk (fictional)
Decision to be made: Whether to change staff assignments on Monday mornings
Evaluation period: 2 weeks (fictional)
Decision deadline: Next management meeting
Responsible person: Evaluator A

Reason for this entry: Limit intended use according to the deadline.

Questions and evidence requirements

Scroll horizontally to view the table

Evaluation question	Required sources	Minimum cases or documents	Conditions for use in decisions
Which processes stall on Monday mornings?	Reception records, observations and staff	Initial plan: records from the last 4 weeks and observation on 2 days	Treat conclusions as provisional if collection is insufficient.

Reason for this entry: Counts are initial values for this fictional plan, not universal minimums.

Collection plan

Scroll horizontally to view the table

Method	Population or subject	Date implemented	Responsible person	Hypothesis to check
Reception record review	4 weeks of records	Week 1	Staff member A	Concentration in data entry
Observation and interviews	Monday reception and responsible staff	Weeks 1–2	Staff member B	Scope to improve role allocation

Reason for this entry: Review records first to focus observations.

Confidence in conclusions

Reason for this entry: Distinguish strengths of evidence.

Completion check

☑ Checked: Focused questions according to the decision deadline and evidence needs
☑ Checked: Checked main findings using multiple sources
☑ Checked: Specified limitations and further verification needs
☑ Checked: Defined the next improvement actions and responsible staff

Reason for this entry: This example focuses on 1 question needed for the next decision. Staff member A proposes a trial redistribution of roles.

Common errors in judgment

Drawing definitive conclusions even from a short study

How to revise: Separate provisional conclusions from additional checks.

Reason: Findings may be specific to a narrow period or population.

Trying to answer every evaluation question

How to revise: Focus on questions needed for the immediate decision.

Reason: An overly broad scope prevents supporting evidence being assembled by the deadline.

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

Rapid evaluation
Eleanor Williams／BetterEvaluation
Section consulted
Other common features across rapid models include
How it relates to the text
Use multiple sources and iterative analysis even within a short deadline, and report evidence limitations.
Source checked: 2026-09-13 (includes AI cross-checking)

How to cite this page

EvalCompass Editorial Team. “Rapid evaluation design and implementation worksheet”. EvalCompass, updated 2026-10-07. https://evalcompass.jun-nakatani.com/en/worksheets/rapid-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 through content checks (U11). Preserved field order, counts, labels and section structure.
2026-09-13 — Checked sources for definitions and applicability conditions, and added fictional examples, reasons for judgments and examples for every worksheet field. Revised unverified claims about history and adoption. Also reviewed existing procedures and cautions, and adjusted fixed participant counts and thresholds and generalizations about institutions. Preserved field positions, types and counts while revising fixed conditions and thresholds in the forms.