Data-Based Supervision Decisions, Documentation, and Fieldwork Exam Traps
Key Takeaways
- Supervision decisions integrate multiple data streams, supervisee performance, treatment integrity, client outcomes, documentation, and context, because no single stream answers every question.
- Always separate implementation failure from intervention failure by comparing treatment-integrity data against client-outcome data before changing a plan.
- Current fieldwork facts: 2,000 Supervised Fieldwork hours OR 1,500 Concentrated Supervised Fieldwork hours, with monthly supervisory periods and differing contact and supervision-percentage requirements.
- Group and individual supervision both count, but at least 50% of supervised hours must be individual, and at least 60% of total fieldwork must be unrestricted activities.
- High-probability traps include averaging across months, counting undocumented activities, blaming an intervention before checking integrity, and choosing punishment before function-based staff support.
Use Data Before Deciding
Sound supervision decisions combine several data streams. A supervisor may review client graphs, procedural integrity, supervisee work products, observation notes, contact records, and progress toward supervision goals. No single stream answers every question, the art is integrating them.
| Data pattern | Stronger supervisory decision |
|---|---|
| Low integrity AND poor client progress | Retrain (BST), simplify, prompt, and monitor implementation before touching the plan |
| High integrity AND poor client progress | Reconsider the assessment, goals, or intervention selection, the plan, not the staff |
| Good meeting attendance BUT weak skill data | Add direct observation and measurable supervision goals; attendance is not competence |
| Missing fieldwork records | Do not rely on memory; correct the documentation system going forward |
The second row is the heavily tested implementation-vs-intervention distinction. If integrity is high and the client still is not improving, the intervention is the suspect. If integrity is low, you cannot yet conclude the intervention failed, you have not really tested it.
Implementation Failure vs. Intervention Failure
This is one of the most important supervisory judgments. Before declaring a treatment ineffective, the supervisor must verify it was implemented as designed, measured by treatment integrity (also called procedural fidelity).
- If integrity is low and the client is not progressing, the most likely cause is implementation failure. Changing the intervention now would be premature, you would abandon a possibly good plan based on a bad test. The fix is to retrain the staff to integrity and re-measure.
- If integrity is high and the client is still not progressing, the implementation is sound, so the intervention or its assessment is the suspect. Now it is appropriate to revisit the FBA, goals, or procedure.
The exam trap reverses this: an item shows a struggling client and offers "change the intervention" without mentioning integrity. The keyed answer first checks integrity, because you cannot evaluate a plan that was never run correctly.
Fieldwork Requirements: The Numbers
Fieldwork details are reliable exam traps. The current BACB framework distinguishes two pathways by total hours, and a supervisory period is one calendar month.
| Requirement | Supervised Fieldwork | Concentrated Supervised Fieldwork |
|---|---|---|
| Total hours | 2,000 | 1,500 |
| Supervisory period | 1 calendar month | 1 calendar month |
| Minimum contacts per period | 4 | 6 |
| Minimum % of hours supervised | 5% | 10% |
Additional rules cut across both pathways: at least 50% of supervised hours must be individual supervision (the rest may be small-group), and at least 60% of total fieldwork hours must be unrestricted activities (direct behavior-analytic work) rather than restricted activities (e.g., direct implementation that is more technician-level). Front-load unrestricted activities so you do not discover a shortfall at the end.
Group vs. Individual Supervision and Documentation
Individual supervision is one supervisor with one supervisee (or a very small, defined arrangement per current BACB rules). Group supervision involves a supervisor with a small group of supervisees and is capped, no more than the allowed group size, and it cannot replace the required individual portion.
Documentation is not optional paperwork; it is part of the service. For each supervisory period, records should capture:
- Dates and number of supervision contacts in the period.
- Hours accrued and the percentage supervised.
- The split of individual vs. group supervision.
- The balance of unrestricted vs. restricted activities.
- What was observed and what feedback/goals were addressed.
Missing or reconstructed-from-memory documentation is a red flag. The keyed answer never fabricates records to fill a gap; it corrects the system so future periods are documented accurately, and it does not pretend an undocumented activity counts.
The Averaging Trap and Other Shortcuts
Because each supervisory period is evaluated on its own, you cannot average across months. A strong May does not rescue a deficient April; if April fell below the required contacts or supervision percentage, those April hours are jeopardized regardless of how good May was. Track each month independently as hours accrue.
- Averaging trap: assuming a good month offsets a bad month, each period must independently meet requirements.
- Undocumented-activity trap: counting an activity that was real but never recorded, if it is not documented appropriately, do not count it.
- Hours-as-competence trap: treating accumulated hours as proof of skill, hours measure exposure, not mastery.
- Punishment-first trap: disciplining staff before analyzing function, analyze, then choose training or performance support.
Fast Trap-Sort Summary
When a Domain I item appears, classify it quickly:
- Hours question → check activity type (restricted/unrestricted), dates, contacts per period, supervision percentage, individual-vs-group split, and documentation. Never average months.
- Staff-behavior question → define and pinpoint the behavior, assess function (can't-do vs. won't-do), then choose BST or performance support, not punishment first.
- Client-progress question → compare client-outcome data against treatment-integrity data before changing the plan.
- Equity question → use objective criteria and opportunity data, not the supervisor's impression of fairness.
- Documentation question → fix the system and document accurately; do not fabricate or count undocumented activities.
A client's challenging behavior has not decreased over four weeks. The supervisor's first instinct is to change the intervention. Before doing so, what should the supervisor examine?
A trainee on the Supervised Fieldwork pathway met all requirements in three months but, in one month, had only 3 supervision contacts instead of the required 4. The next month they had 6 contacts. How should those hours be treated?
Which statement about individual versus group supervision is accurate under current BACB fieldwork rules?
A supervisor cannot find documentation for several fieldwork activities the supervisee insists they completed. What is the appropriate response?