To measure client exposure to an ABA procedure, separate scheduled time, attendance, available opportunities, eligible opportunities, procedure offers, correctly implemented opportunities, client participation, and meaningful contact with the active component. Record access, assent or withdrawal, health, cancellations, and setting constraints. A billed hour or attended session is not automatically a dose of the procedure being evaluated.
Build an exposure funnel
Count scheduled sessions, attended sessions, relevant opportunities, eligible opportunities, procedure offers, correct implementations, and client contacts as distinct states.
Define each transition and prevent a single event from entering incompatible categories. Show the raw count and denominator at every step, along with cancellations, missing contexts, invalid opportunities, and client decline. The funnel should reveal where exposure was lost. Attendance may support service-delivery reporting, but it cannot substitute for contact with the active procedural component.
Define the active component
State what contact is expected to influence the outcome. Materials being present or staff being assigned may support delivery without constituting exposure.
Identify the cue, implementer action, client opportunity, partner consequence, timing, and minimum contact necessary for the proposed mechanism. Separate partial, prompted, incorrect, and unavailable delivery according to the clinical question. Qualified review should establish the definition for the current procedure version. Avoid retrofitting exposure criteria after seeing the outcome.
Preserve access and withdrawal
Record when AAC, health support, mobility, sensory access, consent, assent, or a safe setting was absent. Do not convert protected withdrawal into a treatment failure.
Keep recognizable communication, breaks, medical needs, and emergency pathways available throughout the routine. Record whether the person accepted, paused, changed, or declined participation and how partners responded. An inaccessible or unsafe opportunity may be invalid for exposure analysis and still require immediate system repair. Client withdrawal remains important experience evidence even when it does not enter the treatment denominator.
Link exposure to the right outcome window
Align the exposure period with the outcome measure and plausible timing. Avoid comparing a cumulative outcome with a single-session integrity value.
Use dates, procedure versions, settings, and expected latency to create a mature cohort. Track concurrent changes, baseline comparability, missing outcome data, and whether exposure occurred often enough to support the intended inference. Display exposure and outcome as separate series. A temporal association can inform review without establishing that the procedure caused the observed change.
Use the exposure analysis to decide what can be interpreted, not to create a dose claim automatically. If contact is sparse or uneven, first investigate opportunity availability, access, implementation, scheduling, and plan fit. Qualified clinicians should determine whether to collect more evidence, repair delivery, revise the procedure, change the goal, or use another assessment while preserving client choice and burden.
Put the client-exposure measure into practice
Dev attends six after-school sessions, yet the selected choice routine occurs only four times. The procedure is offered in three eligible opportunities and implemented correctly in two. Dev's participation and experience remain separate. The analysis reports each funnel count instead of calling six sessions the treatment dose.
Compare measurement options for Dev
Dev's team compares direct observation, component scoring, opportunity sampling, duration, permanent product, structured interview, system record, and direct client feedback only when each option can answer the procedure-exposure analysis's decision. Record validity, visibility, reactivity, effort, privacy, access, timeliness, and what each source cannot establish.
Pilot Dev's procedure-exposure analysis
Test the definition, form, observer instructions, technology, access, timing, missing-data states, and review workflow in representative conditions. Ask Dev and the implementer whether the process changes the routine or adds burden. Revise the measurement system before using it for coaching, treatment change, supervision, or performance decisions.
Protect access and clinical responsibility for Dev
Dev's review keeps AAC, interpreters, mobility, food, water, bathroom use, prescribed care, health support, rest, relationships, and emergency help available. Obtain required consent and assent when applicable and follow the governing response to withdrawal or distress. A qualified clinician retains responsibility for clinical interpretation and treatment decisions; a fidelity score does not transfer that responsibility.
Keep procedure versions and evidence states separate
For Dev, record the active procedure version, date, author, authorized adaptations, temporary responses, observed deviations, missing evidence, and unresolved classifications. Preserve the original record. Add a dated explanation whenever a correction or later review changes the procedure version used to judge an observation.
Ask six integrity questions for Dev
Use these questions in the procedure-exposure analysis:
- Which decision, procedure version, component, cue, and eligible opportunity apply?
- Which client, implementer, setting, time, and observation conditions were sampled?
- Which access, safety, health, consent, assent, and communication supports were present?
- Which integrity, exposure, outcome, experience, adverse-effect, and agreement series stay separate?
- Which missing evidence, adaptation, drift, burden, reactivity, or concurrent change limits interpretation?
- Which owner, repair, stop rule, next evidence step, and review date follow?
Keep every unresolved item visible with a state, owner, age, and next action.
A fictional integrity example for Dev
Dev is fictional and involved in an after-school choice routine with changing attendance and opportunity counts. Reviewers freeze 36 scheduled, available, eligible, offered, implemented, correct, participation, access, health, and outcome fields and complete 26 of 36 by the checkpoint. Every missing, unobservable, inapplicable, adapted, drifted, failed, or pending field keeps its defined state.
The procedure-exposure analysis measures evidence completeness. It does not establish effectiveness, safety, acceptability, medical necessity, authorization, payment, compliance, generalization, maintenance, or causation. Report the applicable raw counts and conditions before a percentage.
Use current sources within their scope for Dev
For Dev's procedure-exposure analysis, the CASP public summary supplies high-level individualized assessment, implementation, and evaluation scope for ABA treatment of autistic people. The BACB Ethics Code addresses competence, client involvement, consent and assent when applicable, risk, documentation, supervision, and evaluation for covered behavior analysts. The BCBA Test Content Outline includes procedural fidelity as examination content; it is not a case protocol or universal threshold.
For Dev's procedure-exposure analysis, the Ferguson practitioner guide supports observable component and eligible-opportunity design. The Essig, Rotta, and Poling review supports caution about the consistency and interpretation of fidelity reporting in the literature it examined. ASHA's AAC guidance says AAC users should always have access to their communication tools or devices. None of these sources makes one sampling rate, percentage, or repair rule valid for every case.
Close Dev's review
Ask Dev and each implementer to review the procedure-exposure analysis through accessible communication. Record the selected decision, raw evidence, procedure version, direct feedback, limitations, responsible role, repair, next observation, and review date. Reopen the analysis when the goal, procedure, client preference, access, health, setting, implementer, risk, or outcome changes.
Related resources
- How to Distinguish Planned Adaptation From Treatment Drift
- How to Plan Representative Treatment-Integrity Sampling
- How to Calculate Component-Level Treatment Integrity
- How to Define Treatment-Integrity Components and Opportunities
Sources
- Council of Autism Service Providers, ABA Practice Guidelines Version 3.0 public summary
- Behavior Analyst Certification Board, Ethics Code for Behavior Analysts
- Behavior Analyst Certification Board, BCBA Test Content Outline, 6th edition
- Ferguson and colleagues, A Practitioner's Guide to Assessing Procedural Fidelity
- Essig, Rotta, and Poling, Procedural Fidelity and Interobserver Agreement in Applied Behavior Analysis Research
- American Speech-Language-Hearing Association, Augmentative and Alternative Communication