OpenCEU
Log in
Live day

How attendance codes work

OpenCEU shows attendees a short code during your event. Here is how the timing works, and why you should never read a code out loud.

1

Codes prove attendees are paying attention

OpenCEU shows attendees a short code during your event. They type it in to prove they were paying attention. This meets BACB's active responding requirement.

2

Codes fire on their own

Codes fire automatically on a timer. You do not press any button to send one.

3

Four codes per CEU hour

Your event gets 4 codes for every CEU hour.

4

Codes finish early in the hour

Every code finishes firing within the first 50 minutes of each CEU hour. Codes never land right at the very end of your event.

5

Attendees need most of the codes correct

By default an attendee needs at least 75% of the codes fired live during your event correct, rounded up, to earn their certificate. For an event with 4 codes, that's 3. See Offer a make-up quiz for attendees who fall short, and How attendees get their certificates for the fuller picture.

A recording's codes work differently

An attendee who earns their certificate by watching the recording instead needs every code in that recording correct. OpenCEU treats the live broadcast and the recording as two separate gates, each with its own bar.

Never read the code out loud

Viewers watch your stream on a delay of about 11 seconds. A code that just appeared on your screen has not appeared on theirs yet. Reading a code out loud does not help attendees. It can confuse them if it does not match what they see. Let the system fire codes on its own timer instead.
← Host a panel with co-speakersNext: Live captions →

Still stuck? Contact support and we'll help.