Implementation Fidelity Assessment
Checks how far an intervention was delivered as planned in content, frequency, duration and reach. Delivery quality and participant responses also inform outcome interpretation. [1]
- Difficulty
- Intermediate
- Cost
- Low
- Duration
- Planning example, not a universal standard duration: half a day–2 days for design; ongoing observation throughout the program
How it works at a glance
Implementation fidelity compares planned interventions with actual delivery. Define core elements and record content, dose, reach and implementation changes to examine departures from the plan. [1]
Intervention complexity, support arrangements, delivery quality and participant responses relate to fidelity. Do not treat every change as failure: distinguish deviations undermining the core from adaptations preserving the purpose, and explain the conditions under which outcomes occurred. [1]
- Define core elements
- Design fidelity indicators
- Standardize implementation records
- Combine observations, logs and interviews
- Classify field adaptations
- Interpret relationships with outcomes
When to use it and when it is unsuitable
When to use it
- When distinguishing design problems from implementation problems as reasons outcomes did not occur
- When examining quality variation across sites or staff delivering the same program
- When checking whether training or ongoing support was provided with planned frequency, content and quality
- When recording actual intervention reach alongside an RCT or effect evaluation
When it is unsuitable
- For emergent or developmental programs where following the design itself is not emphasized
- When the purpose is mechanical auditing of manual compliance without recording field adaptations
Participants, roles, and deliverables
Participants and roles
Program staff, field implementers, evaluators and third-party observers where needed. Checking field recording burdens is essential when designing records.
Main deliverables
- Implementation fidelity checklist
- Implementation logs and observation records
- Notes interpreting fidelity and outcomes
Implementation steps
- Define core elementsIdentify content, frequency, population and quality essential to outcomes. Distinguish core elements to preserve from peripheral elements adaptable in the field.
- Design fidelity indicatorsDevelop observation items and records addressing adherence, dose, delivery quality, participant response and differentiation.
- Standardize implementation recordsPrepare manageable checklists, implementation logs and observation forms. Avoid excessive detail.
- Combine observations, logs and interviewsDo not rely solely on self-reports. Use third-party observation, participant surveys or interviews where needed.
- Classify field adaptationsRecord departures as adaptations for improvement, omissions due to constraints or deviations. Retain reasons for adaptations.
- Interpret relationships with outcomesCompare outcomes between higher- and lower-fidelity sites, reflecting findings in improvement recommendations and limitations of outcome evaluation.
Strengths and limitations
Strengths
- Explains absent outcomes through implementation processes.
- Identifies quality variation across sites and informs improvement support.
- Strengthens interpretation of effect evaluations and helps identify failures of intervention reach.
- Recording field adaptations preserves knowledge for future improvement.
Limitations
- High recording burdens prevent adoption in the field.
- Overemphasis on fidelity can suppress necessary adaptations.
- Simple checklists cannot readily capture delivery quality or participant responses.
Common pitfalls
- Treating session counts alone as fidelity without examining delivery quality or participant responses
- Treating every departure as failure without recording useful field adaptations
- Considering fidelity only after outcome evaluation when implementation records are absent
Conditions of use and evidence
- Check content and reach as well as dose, and use delivery quality and field changes to interpret outcomes. [1]
Record learning support session counts separately from core activities
A fictional illustrative record of a program with 6 planned sessions.
Scroll horizontally to view the table
| Item | Plan | Fictional delivery |
|---|---|---|
| Session count | 6 sessions | 5 sessions = 83.3% |
| Core activity | Participants choose their learning goals each time. | Confirmed in 4 of 5 sessions |
| Adaptation | Learning materials may be changed. | Changed to easier-to-read materials. |
Common errors in judgment
Judging delivery faithful solely because the planned number of sessions occurred
How to revise
Also check core content, reach and delivery quality.
ReasonActual interventions may differ even with the same session counts.
Treating every field change as inappropriate
How to revise
Examine whether it preserves the purpose or departs from the core.
ReasonAdaptation to circumstances may be necessary.
References and checked sections
- A conceptual framework for implementation fidelityChristopher Carroll et al. · 2007
- Section consulted
- A conceptual framework: Background and Rationale; Measurement
- How it relates to the text
- Check content and reach as well as dose, and use delivery quality and field changes to interpret outcomes.
Editorial and checking information
How to cite this page
Change history
- — 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.


