How to collect missing attendee details after an event

Before sharing the Issue Request Form link, decide what counts as eligible: registered attendees, people who completed a workshop, team members, or another group. The form confirms control of an email address with a one-time code; it does not verify event attendance.

If you need to check attendance or eligibility against another record, choose Review Before Issuing and do that check in Issue Requests. Issue Automatically sends a certificate to anyone who submits the form, so use it only when access to the link is enough to qualify.

Request the recipient's name and any details the certificate needs. The applicant confirms their email address with a one-time code before submitting. Add only extra fields your certificate or review process requires, such as a team name, institution, or session.

Tell people how to spell the name that should appear and when to expect the certificate: immediately with Issue Automatically, or after review with Review Before Issuing.

Review Before Issuing is useful when you need to check event attendance or match submitted details against another record. You can accept and issue, reject, or reopen submissions in Issue Requests.

Issue Automatically sends the certificate to anyone who submits the form. It removes the review step; the form does not apply additional eligibility rules for you.

Share the Issue Request Form link in the event follow-up email, community space, or event page. Include a deadline and a contact path for people who cannot submit the form.

After the request window closes, review pending submissions in Issue Requests if you selected Review Before Issuing. Resolve duplicates, then let recipients know where to find their certificate page.