Skip to contentVerifycate
ImprovedRecipient formsNo. 085

See exactly what changed before approving a correction

Correction requests now show the old and new values side by side, and a rejection can carry the reason the recipient needs to resubmit.

By Ashwin Shenoy · Founder and engineer

A correction request that says "change my name" is not enough to approve safely. The reviewer needs to see what is on the certificate now and what the recipient wants it to say.

The correction review has been rebuilt around those two values.

Old and new

The request drawer shows the current value and the requested value for each field. Approving updates the existing certificate and public page; it does not create a second certificate or spend a credit.

Reject with a reason

A rejection includes a note that goes to the recipient, so they know what to fix before resubmitting. A rejected request can be reopened or replaced by a fresh one.

Name and college corrections are the most common post-event request. Reviewing them should take seconds and leave a clear trail. Showing both values removes the guesswork; a reason turns a rejection into a fixable next step. Approved corrections keep the certificate ID and public URL.

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.