How to collect event feedback before releasing certificates

Decide what you need to learn: session quality, speaker feedback, project links, a testimonial, or a suggestion for the next event. Avoid turning the form into a general-purpose survey if a few focused questions will do.

For a hackathon, a project link or short reflection may be useful. For a workshop, ask about the material or the next topic participants need.

Use plain language and avoid asking for information you already have. Tell recipients whether answers are optional, who will read them, and whether you may publish a testimonial or project link.

Ask separately for permission before using someone’s response publicly. Submitting feedback should not be treated as consent to publish it unless your process clearly says so.

With Review Before Release, the organiser checks each response before releasing that recipient's certificate. Release Automatically After Submission is faster when any completed response is enough. Make the choice when configuring the Unlock Form.

In Verifycate, publish the certificate with an Unlock Form enabled. Waiting recipients receive a private link when it is published, and recipients added later receive their link by email. Select Release Automatically After Submission or Review Before Release.

Tell recipients what happens after they submit and how long it may take. Monitor submissions in Unlock Responses, follow up on stuck responses, and provide a way to contact the organiser if someone cannot complete the form.

Use the Issue Request Form for people who need to ask for a certificate. Use the Unlock Form for recipients you have already added when you need a response before releasing their certificate.