Certificate of Attendance vs Appreciation: who gets which

Most conferences issue one certificate template with one sentence, and change the name at the top. It is the fastest way to produce four hundred documents, and it quietly insults the twenty people who did the most work.

The distinction is not cosmetic

A delegate attended. That is a claim about presence, and for CME purposes it is the claim that matters — it is backed by the attendance record.

A speaker delivered a presentation. A chairperson chaired a session. A member of the organising committee served on the committee. These are claims about contribution, and they are what those people will actually put in front of a promotion committee or an academic file.

Handing a speaker a "Certificate of Attendance" tells them the conference did not notice what they did.

The heading has to agree with the body

The most common version of this mistake is subtler than the wrong name: it is a certificate whose heading and body contradict each other.

Certificate of Attendance

This is to certify that Dr Rita Shrestha delivered a presentation at…

Both halves were written by sensible people. The heading came from the template; the sentence came from someone who knew what actually happened. Printed together they read as carelessness, and the reader trusts the whole document less.

Pick the pairing and keep them consistent:

• Attendance — for delegates, and for invited guests who came to listen.
• Appreciation — for speakers, chairpersons, faculty, the organising committee, volunteers and staff.

Wording that works

Keep it to one sentence, in the register the reader expects:

• This is to certify that {name} delivered a presentation at {event}.
• This is to certify that {name} chaired a session at {event}.
• This is to certify that {name} served on the organising committee of {event}.
• This is to certify that {name} volunteered at {event}.
• This is to certify that {name} attended {event}.

The pattern is the same each time, so the documents look like a set rather than six unrelated designs.

What else has to be on it

The credit, if there is any. "18 CME hours" on the face of the certificate is what a council reads. It is not a footnote.

A certificate number. Unique, and stored — not generated fresh each time the PDF is opened, or the number on the copy in someone's file will not match the one in your records.

A way to check it. A QR that resolves to a page showing what the printed certificate already says. That is the difference between a document somebody can verify and a nicely-set image anyone could reproduce in an afternoon. It should reveal nothing beyond what is on the paper — enough to confirm it is genuine, and no more.

Release them deliberately

Certificates should be a switch you throw, not something that exists from the moment the event is created. An attendee who can download a certificate before the closing session has a certificate that proves nothing.

The useful arrangement: the organiser can print and check them while preparing, and attendees can reach theirs only once the event is over and the organiser has released them.