Compliance

What are PDUs for RBTs and how are they documented?

Published April 6, 2026

BCBA CEUs get most of the attention, but RBT PDUs are required too — and the population of RBTs is much larger than the population of BCBAs. If you train RBTs (whether your own staff or a broader audience), having a clean way to issue and document PDUs is a competitive advantage.

What are PDUs for RBTs?

PDUs are Professional Development Units that RBTs are expected to engage with as part of maintaining their RBT credential and growing in the role. They're the RBT equivalent of CEUs in concept, but the structure and expectations are managed differently from BCBA CEUs.

Who is responsible for tracking an RBT's PDUs?

The RBT and their supervisor are jointly responsible for ensuring the RBT receives appropriate ongoing training. The employing organization typically maintains the documentation. Clean certificates issued at the time of training make this dramatically easier.

What should a PDU certificate include?

The same fields you'd expect on any training certificate: learner name, training title, date, hours, and the issuing organization. The certificate should be clearly labeled as PDUs (not CEUs) so there's no confusion later about what credential it applies to.

Can the same training event issue both CEUs and PDUs?

Yes, when the content is appropriate for both audiences. The cleanest way is to issue two separate certificates from the same underlying course — one labeled as CEUs (for BCBAs) and one labeled as PDUs (for RBTs). A platform that supports multiple certificate templates per course makes this trivial.

Do I need to be an ACE provider to issue PDUs?

PDUs are not gated by the ACE provider system in the way that CEUs are. However, structured training delivered by qualified instructors with proper documentation is still the gold standard for supporting an RBT's development.

CEU Lab Certs treats PDU certificates as a first-class format alongside CEU certificates so you can serve RBTs and BCBAs from the same platform without juggling separate systems.

See pricing