Operations

How to handle CEU certificate re-issue requests without losing your mind

Published April 9, 2026

Nobody warns you about this part. Issue 200 certificates and three months later: “I can’t find mine.” “Wrong email.” “Typo in my name.” “The BACB is asking and I don’t have it.” At scale, this is a genuinely significant admin chunk — unless your system makes re-issuance trivial.

How common are re-issue requests?

5–10% of learners will contact you eventually. Triggers: changed email, deleted the original, need it for audit, typo in name.

Fastest way to handle one?

Look up by name or email, find the original, re-send. Under a minute with a searchable platform. Much longer from your email sent folder.

What about corrections?

Verify, re-issue with correct info, log both versions. Unique certificate IDs keep the audit trail clean.

Should I charge for re-issues?

I wouldn’t. If re-issuing takes 30 seconds, it’s not worth the friction.

How do I reduce the volume?

Send certificates immediately after quiz completion, and give learners a way to re-download without contacting you.

Re-issues are a systems problem, not a people problem. Learners will lose certificates. The question is whether your response is a 30-second lookup or a 30-minute dig.

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.