Certificate of attendance checklist for conference organizers

Use one issuance and exception register

Download the editable certificate issuance register (Markdown, English)

Copy the worksheet for this event. It records eligibility rule, evidence source, specimen approval, batch status, delivery route, correction reference and owner. Keep full contact data in the restricted delivery system; use a recipient reference in the shared register.

Define the statement before the recipient list

Write the exact event name, date or session, issuer and statement the certificate will carry. Decide whether it confirms registration, check-in or another documented participation condition. These are different claims: an Eventbrite Check-ins report contains checked-in tickets, while its status glossary separates “Attending” from “Checked In.” Check what your own event records actually show. Do not turn attendance into a claim of course completion, professional credit or competency unless the responsible program owner has separately approved that claim. Record who approves the wording.[1][2]

Reconcile recipients against the agreed evidence

Start with the event or session roster and the evidence named in the rule. Use a stable recipient reference to join records; confirm the display name from the appropriate attendee record rather than guessing from the purchaser name. Set aside duplicates, canceled entries, group bookings, manual admissions and unclear session attendance for review. Mark each row eligible, pending or excluded with a reason and reviewer. A ticket sale or invitation by itself should not silently become proof of attendance. Do not email an unreviewed export.

Approve a specimen before the batch

Make sample certificates with short and long names, accented characters and every wording variant. Check event title, date, issuer, spelling, line breaks, file name, delivery message and recipient-to-file match. A decorative certificate can still include real selectable text; W3C advises against putting readable text only inside an image when real text can be used. Have a second reviewer open the actual output and sign off on the specimen. If the certificate will be printed, also check a print proof with the chosen printer.[3]

Release, then close the exceptions

Agree the batch cutoff, delivery method and sender with the communications owner. Send a small test to approved internal addresses, then release the approved recipient set. Record the batch reference, send time and owner; do not mark a certificate delivered solely because a file was generated. Give recipients a correction route. For a wrong name, missing recipient, bounced message or disputed eligibility, log the case, verify against the source record and approve a replacement before sending it. Mark the earlier version superseded where your process permits, and hand unresolved cases to a named owner. Keep the final register under the event’s access and retention rules.