Glossary
What Is Certificate Request Form?
In Verifycate, a certificate request form is a public application form for people who want your certificate: approved requests are issued, and the applicant's answers become the details printed on the copy.
Also called: request form, issue request, application form
What it's for
Half the people who should hold your certificate never appear on any list you were given: the attendee who registered under a different email, the employee who finished the training after the batch closed, the stranger who watched your webinar and wants proof. The usual options are a shared email address nobody watches, or a Google Form and a weekend of manual entry.
A certificate request form is the front door. Anyone with the link can apply for the certificate; you decide who gets in. It's recruitment and issuance in one motion.
How it works
The form is public — shared as a link or embedded wherever your audience already is. An applicant confirms who they are with a one-time code sent to their email; no account, no password. Then they answer the questions you chose.
The useful part is what happens to the answers: questions named to match a certificate's attributes fill those attributes directly. The applicant effectively types their own certificate — name, course, role, whatever you ask — and an approval issues a certificate that's already correct.
Which leaves the decision, same shape as every gate:
- Issue automatically. Approved by the rule, not by you. Right for open credentials where the bar is completion, not judgement.
- Review before issuing. Requests queue in an inbox — Issue Requests — and you accept or reject each one, with an optional reason. Accepting one issues the certificate and spends one credit.
How it differs from an unlock form
They point in opposite directions. A unlock form goes out to people already on the list and never creates a recipient. A request form comes in from people who aren't on the list yet, and approving it is what creates one. Feedback travels one way; applications travel the other.
Requests arrive from every certificate into one inbox, with the applicant's answers attached. Rejections record a reason and can be reopened. The journey analytics count request-form entries separately from CSV imports and manual adds, so you can see how much of your audience finds their own way in.
Everything on this page runs in Verifycate. The first 300 certificates are free, no card. Start for free
Common questions
- Do people applying need a Verifycate account?
- No. They confirm their email with a one-time code and submit. The account-less flow is deliberate — the easier the application, the more of the right people apply.
- What stops spam requests from costing me money?
- Nothing is issued until you approve it, and nothing pending costs anything. With review-before-issuing on, a hundred spam applications cost you zero credits; with automatic issuing, gate the form wherever your audience already trusts you.
- Can applicants upload files or pick from options?
- Yes — text, selections, uploads, ratings and more, depending on what the certificate needs from them. Field types match the form builder used elsewhere in the product.
- Where do I find the form to share?
- On the certificate, alongside the correction form and unlock form settings. One public link per certificate; it goes live when the certificate is published.
Related terms
- Certificate Unlock FormIn Verifycate, a certificate unlock form is a form a recipient must complete before their certificate is released — a survey, feedback or a testimonial — sent to each recipient as a private link.
- AttributeIn Verifycate, an attribute is a named piece of data — a recipient's name, a course title, a score — whose value gets printed onto each certificate through a placeholder in the template.
- Certificate RecipientIn Verifycate, a certificate recipient is one person on a certificate's list — the record carrying their name, contact details, attribute values and status from import through issue to verification.
- Bulk Certificate GenerationBulk certificate generation produces one personalised certificate per person from a single design and a list of recipients, instead of editing a file once per name.
Let the right people apply for your certificate.
One public link; approved applications are issued with the applicant's own answers already printed in. The first 300 certificates are free, no card.
“We issued 2,000+ certificates for InCTF — winners, participants, the lot.” — Aravind BL, Amrita InCTF
Start for free