Skip to contentVerifycate
NewRecipient formsNo. 014

Let missing attendees request their certificate

Share a public Issue Request Form so people who missed the original list can confirm their email and apply, with automatic or reviewed issuing.

By Ashwin Shenoy · Founder and engineer

The attendee list is almost never complete. Someone registered late, walked in without registering, or attended a session that used a different spreadsheet. The certificate exists, but the person is not on the list.

The Issue Request Form gives those people a path in.

How it works

Enable the form on a certificate, choose the fields applicants should provide, and share the public link through the event channels. Applicants confirm their email with a one-time code, then submit their details. The submission lands in Issue Requests, where you can accept and issue, reject with a reason, or reopen it.

Choose Issue Automatically if the form is open to anyone who can confirm an email. Choose Review Before Issuing if someone needs to check attendance, eligibility, or a duplicate.

The fields

Collect the details the certificate needs: name, email, institution, roll number, team, session, or a LinkedIn profile. Matching field keys can fill the certificate's Attributes when the request is issued, so the certificate is not a second manual data entry.

Where it helps

A workshop can share the form after the event for people whose registration did not make the export. A hackathon can collect team details from walk-ins. A university department can let students request a certificate for a programme that used a separate registration system.

The form is a Pro feature. Issuing through a request spends one credit, like any other issue.

Related

← Back to all updates

Start issuing

Certificates people can prove.

Design once, issue in bulk or from your LMS, and give every recipient a public page anyone can verify.