Skip to contentVerifycate
ImprovedIssuingNo. 038

Issue to late additions after the event

Add a recipient to an already-published certificate and issue their certificate without rebuilding the original batch or reissuing everyone else.

By Ashwin Shenoy · Founder and engineer

The certificate is published, the batch has gone out, and then someone arrives with a legitimate late claim: a speaker confirmed at the last minute, a volunteer joined on the day, a student registered after the export.

A published certificate can accept late additions.

Two ways in

Add the recipient directly from the certificate's Recipients tab, or let them submit the Issue Request Form if the form is open. Both paths create a recipient record against the existing certificate. Issue that record individually; the original batch is untouched.

The new recipient gets the same design, the same public page, and their own QR code. Their email is sent at issue time, like any other recipient.

What not to do

Do not re-import the whole list to add one person. It creates duplicate-checking work and risks reissuing people who already have a certificate. Do not reissue the batch either; the late addition is a separate recipient record.

Adding a recipient does not spend a credit. Issuing their certificate does. If the certificate is part of a Pro workflow with forms, the request path can capture the details and apply the matching Attributes automatically.

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.