Skip to main content

Fix a mistake on a certificate you've sent

Issue a reviewed replacement for incorrect details, preserve the history and check delivery of the corrected version.

Certificates can't be edited after they're sent. That's what makes them trustworthy. Instead, you issue a correction.

  1. Open the certificate from the list.
  2. Under Correct Recipient Details, fix the name or detail and give a reason.
  3. Choose Issue Corrected Credential. The recipient gets the new certificate.

Anyone who checks the old one sees "A newer credential replaces this one", with a link to the new version, so a mistaken copy can't be passed off as current.

Recipients can ask you for a correction from their Passport. You'll find their requests under Corrections.

Choose correction, resend or withdrawal

Correct a certificate when its signed details are wrong. Resend when the certificate is correct but the email is missing. Withdraw when the award should no longer be relied on. These actions have different consequences; changing the design for future recipients does not repair certificates already issued.

Review a correction carefully

  1. Open the issued certificate or the holder's request under Corrections. Confirm you are working on the latest version for the right person.
  2. Inspect the existing details and the requested changes. Ask for clarification if a name or email change could identify a different person.
  3. Enter the corrected values and a useful reason. Review the replacement preview, including the printed wording, not just the form fields.
  4. Confirm the correction once. It creates a replacement and records the relationship to the old certificate.
  5. Open both records: the old version should show that it was replaced, and the new version should show the intended details. Check email delivery separately.

What remains historical

The old certificate remains part of the record. A recipient's previously downloaded PDF does not rewrite itself. Give them the corrected version and its current verification link. Expiry handling preserves the original end date; a correction is not an automatic renewal.

If correction fails or a request looks stale

Refresh the request and inspect the current certificate before submitting again. Another teammate may have completed a correction, or the review may no longer match the current details. If issuance succeeded but delivery failed, resolve delivery rather than replacing the replacement. Keep the request and error reference for support.

Certificates transferred from another system can have a separate correction preview and review process. Use that certificate's available controls; a native bulk correction is not a universal way to rewrite imported history.

Still stuck? A person will help.

Contact us