How to run a CME-accredited conference

A CME conference is not a bigger version of a meetup. The difference is that it has to produce evidence: who presented, who attended, on which days, and a certificate a licensing body will accept afterwards.

Most of the pain comes from running those steps in separate systems — abstracts in email, registration in a form, attendance on a printed list, certificates in a word processor the night before. Here is the chain, in order, and what each step has to produce for the next one.

1. Call for abstracts

Submissions arrive with a title, an author, an affiliation and a body. What matters is that each one carries a status you can move through review, and that the author's details survive to the badge and the certificate. An abstract accepted in an inbox has to be retyped twice before the conference opens; an abstract accepted in the system does not.

2. Registration, with the questions your event actually needs

Every conference asks something unusual — council registration number, dietary requirement, workshop choice, institution. Those answers have to come back attached to the booking and export with it, or somebody rebuilds the delegate list by hand.

Two things worth deciding early:

• Ticket types are not just prices. They are what gets printed on the badge stripe and what the door uses to decide who may enter which session.
• Accompanying persons are real people. They need their own name on their own badge, and they usually pay a different amount. Treating them as a quantity on someone else's ticket means two people arrive holding the same badge.

3. Badges

Print them from the same attendee list you registered — never from a re-typed spreadsheet. A badge needs the name large enough to read across a handshake, the role or ticket type, the institution, and a scannable code.

That code should be the same reference the door scans and the attendee's ticket carries. If the badge QR encodes anything else, you have two identifiers for one person and the door will eventually reject someone who is holding a valid badge.

More on what belongs on a badge.

4. Attendance, per day

This is the step that quietly breaks three-day conferences. A single "used" flag on a ticket can record that somebody arrived — once. It cannot express that they came on Thursday and Saturday but not Friday, which is exactly what a CME claim rests on.

Attendance has to be recorded per person per day. Why day two is where it goes wrong.

5. Certificates that survive scrutiny

A certificate is only useful if somebody else can check it. That means three things:

• The right wording for the right person. A speaker did not "attend" — they delivered a presentation. A chairperson chaired. A delegate attended. One template that calls everyone an attendee devalues the document for exactly the people whose certificates matter most.
• The credit, stated on the face of it. "18 CME hours" printed on the certificate is what the council reads.
• A verification route. A certificate number and a public page that confirms it. On Eventio360 every certificate carries a QR that resolves to a verification page showing only what the printed document already says — enough to confirm it is genuine, nothing more.

6. The people who never registered

Speakers, chairpersons, the organising committee, volunteers. They were never delegates, they never paid, and they are usually handled with a separate spreadsheet and a panicked badge print on the morning.

They need the same two artefacts as everyone else — a badge to get in, a certificate afterwards — and they should come off the same machinery, so the cards match and their attendance is recorded like anyone else's.

The order matters

Each step feeds the next: abstracts name your speakers, registration names your delegates, both produce badges, badges produce attendance, attendance produces certificates. Break the chain anywhere and somebody is retyping a list at midnight. Keep it intact and the certificates are a print job rather than a project.