Compliance

How to document and track PDUs for RBT supervision

Published April 9, 2026

The documentation side is where most organizations lose time. Not because the training isn’t happening, but because the paper trail is fragmented or lives in one person’s email. If a supervisor leaves and takes their records, the RBTs’ documentation goes too.

What should documentation include?

RBT name, topic, date, hours, trainer name. Ideally a signature or certificate. A platform auto-populates all of this.

Where to store records?

Centralized and accessible to the organization. Not one person’s email or personal drive.

How to track across multiple RBTs and supervisors?

Index by RBT and by training event. You should answer both “what has this RBT completed?” and “who completed this training?” in seconds.

How far before renewal to start checking?

At least 60 days. Time to identify gaps and schedule additional trainings.

Easiest way to generate documentation?

Issue a PDU certificate automatically every time an RBT completes a training assessment. The certificate is the documentation.

Good documentation is invisible when working. Set up the system before you need it.

About CEU Lab Certs

I'm an Org ACE Provider who spent years manually creating CEU certificates and stitching together clunky systems that weren't built for the BACB's changing requirements. I built CEU Lab Certs to be the tool I wished existed — BACB-compliant templates, shareable quiz links, automated certificate delivery, and audit-ready records in one place, so you can spend your time teaching instead of doing certificate admin on a Sunday.