Use Data and Checklists as a Coaching Tool, Not Surveillance

When a technician goes quiet or stiff the moment a competency form appears, that reaction usually points to how the data are being used rather than to the technician. Framed well, competency data are a feedback safety net and a coaching tool, not a trap, and saying so explicitly from the very first supervision sets the tone — making clear the forms exist to help the technician do the job well, not to catch mistakes. Competency data actually serve three protective jobs at once: they protect the client by supporting safe, correct implementation, they protect the technician by documenting that training and support were provided, and they protect the supervisor and organization by showing that supervision met standards. Technicians tend to feel policed when no one explains the forms, when data only appear after something goes wrong, or when feedback feels like blame. Naming the purpose up front removes most of that anxiety before it starts.

A good checklist is built to be fair, clear, and coachable. Every item should map to a competency and be observable and behavior-based — for example, "across ten opportunities, the technician follows the behavior plan steps in order when aggression occurs" rather than the vague "handles the behavior plan well." Keeping the list short, in plain language, grouped by phase (set-up, instruction, response to behavior, and data collection), and scored simply as met or not-yet keeps it usable in the moment. Just as important is rolling the checklist out with the technician rather than at them, sharing what will be observed so it functions as a shared coaching tracker rather than a hidden test. Collecting the data unobtrusively also matters: quick tally marks or small symbols while staying present with the client, or short observe-then-jot time blocks, keep attention on the session, and if the data collection makes the technician more nervous than supported, the supervisor adjusts their own behavior before changing the tool.

How the data are discussed afterward determines whether checklists become allies or enemies. A supportive debrief starts with the pattern rather than the person, connects it to the client's learning, asks for the technician's perspective on what made a step hard, and turns it into a short, focused practice plan with support offered for next time. Closing each observation with a trend rather than a single moment keeps the focus on growth — for instance, noting that a step went from three out of ten opportunities last month to eight out of ten this week — and that trend then drives a quick decision about whether the technician needs more practice or better support. It helps to remember, and to say, that these forms ultimately protect the technician by proving they were trained and supported, and they help the supervisor meet professional and payor expectations. The bottom line is to use data to adjust the system rather than to blame the person. Approached this way, checklists and competency data become a shared coaching tool that builds consistency and confidence (Parsons, Rollyson, & Reid, 2012; Sellers, Valentino, & LeBlanc, 2016).

References

Garza, K. L., McGee, H. M., Schenk, Y. A., & Wiskirchen, R. R. (2018). Some tools for carrying out a proposed process for supervising experience hours for aspiring Board Certified Behavior Analysts. Behavior Analysis in Practice, 11(1), 62–70. https://doi.org/10.1007/s40617-017-0186-8

Parsons, M. B., Rollyson, J. H., & Reid, D. H. (2012). Evidence-based staff training: A guide for practitioners. Behavior Analysis in Practice, 5(2), 2–11. https://doi.org/10.1007/BF03391819

Sellers, T. P., Valentino, A. L., & LeBlanc, L. A. (2016). Recommended practices for individual supervision of aspiring behavior analysts. Behavior Analysis in Practice, 9(4), 274–286. https://doi.org/10.1007/s40617-016-0110-7