What Counts Here
The tool focuses on events after the target behavior. Events before behavior belong in antecedent or setting-event analysis.
Consequence Analysis
Consequence Analysis is a practitioner-only FBA configuration for practitioners and FBA team members. It helps them link target-behavior episodes to reported post-behavior events, review recurring consequence patterns, and confirm candidate maintaining consequences when supported by the entered data.
Map sample post-behavior events to fictional episodes and review candidate consequence patterns.
Interested in using Consequence Analysis with clients? Request access now.
Request access
Request access to Consequence Analysis. Enter your email below.
Tool guide
Learn more about this tool
Use this background section to understand when the tool fits, how practitioners use it, and what to consider before sharing it with clients.
Interpretation Boundary
Maintaining consequence labels are practitioner-confirmed candidate interpretations, not automatic function determinations.
Partial Evidence
Sparse, conflicting, or unlinked reports remain visible and should not be presented as confident maintaining-consequence claims.
Does the tool automatically identify behavioral function?
No. It summarizes reported consequences and lets the practitioner confirm candidate maintaining consequences.
Can informants use the tool?
Only to report what happened after observed episodes if that workflow exists; they are not asked to determine function.
What happens to events that occurred before the behavior?
Events before the behavior are out of scope for this tool and should be flagged or moved to antecedent analysis.
Can labels like access or escape be used?
Yes, as practitioner-selected candidate interpretations tied to supporting data, not as automatic conclusions.