Prediction as a scientific goal

Prediction identifies covariation

Two events covary when changes in one reliably accompany changes in another. A school transition may often precede a help request. A particular prompt may be followed by quicker starts. Repeated, representative observations can make those relations useful for forecasting.

The BACB BCBA Test Content Outline, 6th edition names description, prediction, and control as goals of behavior analysis. It also covers measurement, graphing, experimental design, validity, assessment, and data interpretation.

A prediction must be prospective

State the forecast before observing the outcome. Define:

• the event that serves as the predictor
• the response or outcome forecast
• the eligible settings and opportunities
• the time window between events
• the expected direction or probability
• the comparison when the predictor is absent
• the rule for missing and excluded observations

Retrospective storytelling can fit almost any result. Prospective statements expose the relation to a fairer test.

A fictional transition example

Nia is a fictional student who wants more warning before schedule changes. The team records twelve unexpected classroom transitions. A visual preview is available before five transitions and absent before seven.

Nia uses an accessible clarification request in 4 of 5 previewed transitions and 2 of 7 transitions without a preview. She reports that the preview helps her understand what is changing. The pattern predicts a higher chance of clarification under the previewed condition in this small sample.

It cannot show that the preview caused the difference. Activities, staff, urgency, and time of day varied. The team can use the association to improve support while collecting a more balanced sample or arranging a safe comparison.

Conditional probabilities add clarity

Report how often the outcome occurs when the predictor is present and when it is absent. A predictor that appears before most responses can still be uninformative if it is present almost all day.

Use equal observation windows and representative opportunities. Preserve zero-event periods. A ratio built only from episodes where the response occurred cannot estimate prediction accuracy.

Prediction can serve prevention

A reliable forecast can support earlier communication access, staffing, materials, medical review, or environmental adjustment. The goal is to improve support, rather than to label the person as risky.

Use the least intrusive response consistent with safety. A prediction should never become a reason to restrict someone automatically. Define who reviews it, what evidence triggers action, and how false alarms and missed events are examined.

Calibrate the forecast

Track true positives, false positives, true negatives, and false negatives when those categories fit. Report base rates because a rare event can make a seemingly accurate rule misleading.

Review performance across people, settings, and time. A rule developed during weekday clinic sessions may fail on weekends or in the community. Recalibrate after schedule, health, staffing, or measurement changes.

Prediction differs from control

Prediction rests on dependable covariation. Control requires experimental evidence that changing a variable produces a change in behavior. Rain predicts umbrella use in some settings; changing the forecast display may or may not change actual use.

Clinical teams can act on useful prediction while stating causal uncertainty. Ethical or practical limits may prevent an experimental test. The record should match the claim to the design.

Avoid overconfidence

Small samples, changing definitions, observer expectations, selected opportunities, concurrent events, and measurement gaps can inflate apparent predictiveness. Use confidence language that fits the evidence.

Separate group-level forecasts from person-specific ones. A population association cannot determine what will happen for one individual. Invite the person’s account of variables that the data system cannot see.

Make predictions actionable

Attach each forecast to a safe response and review rule. State who needs the information, how soon, and what support becomes available. Measure whether the response occurred and whether it helped.

Retire prediction rules that add burden without improving decisions. A useful forecast should clarify action, preserve rights, and remain open to revision.

Evaluate value as well as accuracy

An accurate forecast can still have little value if staff receive it after the decision or lack an appropriate response. A less frequent alert may be more useful when it gives enough time to make communication, space, or medical support available.

For each rule, track alerts issued, required responses completed, outcomes, false alarms, missed events, and client experience. Review whether the intervention following the alert helped. Keep forecast performance separate from response performance.

Set an expiration or revalidation date. A prediction developed before a move, medication change, new communication system, or staffing change may need rebuilding rather than routine reuse.