Certificates of attendance get treated as the last job of a congress: a mail merge, a batch of PDFs, and a week of answering people who spelled their own name differently on the registration form. That framing is why they hurt. A certificate is not a document you produce at the end. It is the output of data you either captured during the event or did not, and once the delegates have flown home, the second option is permanent.<\/p>\n\n\n\n
If your congress carries accreditation, this is not a matter of house style. It is written down.<\/p>\n\n\n\n
The European Accreditation Council for Continuing Medical Education, run by the European Union of Medical Specialists, accredits live educational events across Europe. Its criteria for those events are blunt: “Simple registration of attendance at the event is not sufficient” [1]. To award credits that reflect real attendance, providers must “monitor the presence of each participant for each session of the event”, by attendance list, scanning system or similar, and for virtual events attendance “must also be monitored through a tracking system” [1].<\/p>\n\n\n\n
Per session. Not per congress. Everything else follows from that.<\/p>\n\n\n\n
Coffee and lunch breaks, commercial sessions, non-scientific opening and closing ceremonies and assessments earn no European CME credits [1]. A four-day congress therefore does not produce four days of credit. The European Society of Cardiology’s 2026 congress, accredited by the same body, was allocated a maximum of 29 credits across its four days \u2014 seven, eight, eight and six \u2014 and told online delegates they would “receive one credit for each full hour you have spent online” [2].<\/p>\n\n\n\n
Three further rules catch organisers out. A participant cannot receive the certificate until they have completed the feedback form, and a provider “cannot deliver a higher number of certificates than the number of feedback forms received” [1]. Certificates may be distributed up to six months after the event [1], which is generous only if you still hold the data six months later. And you may not charge a fee to issue one [1], so every manual hour spent on certificates is paid for by the society.<\/p>\n\n\n\n
That is the European medical position, and it is worth saying plainly that it is not the rule everywhere. A UK professional body, an Australian college or a US accreditor each sets its own requirements, and you should read yours rather than assume this one transfers. The shape tends to hold, though: attendance evidenced at session level, credit tied to actual hours, and a record you can produce long after the venue has been handed back.<\/p>\n\n\n\n
A registration list tells you who paid. It does not tell you who was in the room for the Thursday afternoon parallel session, and it cannot be made to tell you afterwards. The gap between those two facts is where the volunteer hours go \u2014 the treasurer cross-referencing a badge-scan export against a delegate list, the secretary answering forty emails in December from people who need a certificate for an appraisal in January.<\/p>\n\n\n\n
The remedy is dull, and almost all of it happens before the congress opens.<\/p>\n\n\n\n
The second job of a certificate is not issuing it. It is standing behind it years later, when a delegate’s employer or regulator wants to know the PDF is real. Most societies answer that by having a volunteer look someone up and reply by email, which is a verification system in roughly the way a shoebox is an accounting system.<\/p>\n\n\n\n
The standards work here has moved. 1EdTech’s Open Badges specification reached version 3.0, with the current document issued on 29 June 2026, and restructures each badge as a credential that “aligns with the conventions of the Verifiable Credentials Data Model v2.0” [3][4]. That data model became a W3C Recommendation on 15 May 2025 [5]. In plain terms, the credential carries its own proof and can be checked cryptographically by whoever receives it, with nobody contacting your office.<\/p>\n\n\n\n
What travels inside one is the part worth thinking about now, because it is the same information your paper certificate should already carry. Jisc describes a digital credential as holding details of the issuing organisation, what the individual did to earn it, the criteria assessed against, confirmation that it was issued to the expected recipient, and when it was issued and whether it expires [6].<\/p>\n\n\n\n
Two honest caveats. Adoption is uneven, and plenty of employers will want a PDF for years yet, so treat this as an addition to your certificate rather than a replacement. And a verifiable credential proves that the society issued it. It does not prove your attendance data was any good.<\/p>\n\n\n\n
If you intend to reissue certificates for six months, or answer verification requests for five years, you are committing to keep attendance records for that long. In the UK, that is a decision you have to be able to defend. The UK GDPR requires personal data to be kept in identifiable form no longer than is necessary for the purposes for which it is processed [7]. The Information Commissioner’s Office puts the practical duty directly: you must be “able to justify” how long you keep it, and “You need a policy setting standard retention periods wherever possible” [8]. That is the UK position. Societies with members in the EU, Australia or Canada are working to their own regimes alongside it.<\/p>\n\n\n\n
This is a line in a retention schedule, not a project. Attendance and credit records kept for a stated number of years, because accreditation reissue and professional verification require it, disclosed to delegates at registration. Defensible, and done.<\/p>\n\n\n\n
What does our accreditation body require in writing, and has anyone read it this year? Could we evidence session-level attendance for last year’s congress today, without asking a volunteer to reconstruct it from memory? And if the person who made last year’s certificates stepped down tomorrow, could their successor produce this year’s from the documentation alone?<\/p>\n\n\n\n
Membersites issues certificates from the same system that holds the registration, the programme and the membership record, so the name on the certificate comes from the record the delegate already owns and the document sits in their account rather than in an inbox. Because a society’s conference sites and its membership site share one login, a delegate returning for next year’s congress is recognised as the same person rather than entered again.<\/p>\n\n\n\n
If you would like to talk through what your accreditation body requires and what your current setup can actually evidence, we are glad to have that conversation.<\/p>\n\n\n\n
Accreditation bodies do not accept a registration list as evidence of attendance, which makes a certificate the output of data you either captured during your congress or did not. Here is what the rules actually require, and what to fix before the next one.<\/p>","protected":false},"author":1,"featured_media":7777,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"slim_seo":{"title":"The certificate is the easy part. Proving who was in the room is not. - Membersites","description":"Accreditation bodies do not accept a registration list as evidence of attendance, which makes a certificate the output of data you either captured during your c"},"_slim_seo_primary_term_category":0,"_slim_seo_primary_term_post_tag":0,"footnotes":""},"categories":[37,44],"tags":[],"class_list":["post-7769","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-conference-management","category-global-operations"],"_links":{"self":[{"href":"https:\/\/membersites.co\/ar\/wp-json\/wp\/v2\/posts\/7769","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/membersites.co\/ar\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/membersites.co\/ar\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/membersites.co\/ar\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/membersites.co\/ar\/wp-json\/wp\/v2\/comments?post=7769"}],"version-history":[{"count":0,"href":"https:\/\/membersites.co\/ar\/wp-json\/wp\/v2\/posts\/7769\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/membersites.co\/ar\/wp-json\/wp\/v2\/media\/7777"}],"wp:attachment":[{"href":"https:\/\/membersites.co\/ar\/wp-json\/wp\/v2\/media?parent=7769"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/membersites.co\/ar\/wp-json\/wp\/v2\/categories?post=7769"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/membersites.co\/ar\/wp-json\/wp\/v2\/tags?post=7769"}],"curies":[{"name":"\u062f\u0628\u0644\u064a\u0648 \u0628\u064a","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}