Skip to contentVerifycate
NewRecipient formsNo. 047

Collect feedback before releasing a certificate

Ask recipients for feedback, a testimonial, a link, or a file before release. Choose automatic release or review each response.

By Ashwin Shenoy · Founder and engineer

Some certificates should not be handed over until something is handed back: workshop feedback, a testimonial, a project link, proof the course was finished.

The Certificate Unlock Form is now available on Pro.

The form

Each recipient on the list gets a unique private link. No login, no shared link to forward. Start from event feedback, course feedback, testimonial, NPS, project submission, or a custom form, then add text, ratings, numbers, links, dates, or file uploads.

The release decision

Release automatically after submission, or review every response in Unlock Responses before releasing. With review on, accept and release, reject with a reason, or reopen. Reminders go to people who have not responded, and a certificate can be released without waiting.

One boundary

An unlock form goes to people already on the list. It never creates a new recipient. For people who are not on the list yet, the Issue Request Form is the other workflow.

A response accepted and released spends one credit, the same as any other issue. The form itself does not spend credits.

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.