Certificate issued to the wrong person: review and correction checklist
If a certificate was issued to the wrong person, first identify the exact award and the approved recipient. Do not start by replacing the displayed name: that can turn a record of one person’s achievement into another person’s certificate without resolving the issuing error.
This checklist is a suggested review process for training teams. It separates the program owner’s decision from the platform action, so a problem with one award does not become an unintended change to a whole campaign.
Find out what is actually wrong
- The right person has a spelling error: use the certificate name-correction process after confirming the approved spelling.
- The award is correct but an email went to the wrong address: review the contact and delivery records. Do not assume that the award itself must be deleted.
- The credential names someone who did not earn that award: ask the program owner to review eligibility and authorize the specific correction.
- The evidence is unclear: keep the case open. A similar name or a forwarded certificate is not enough to decide who should receive the award.
Check the credential identifier, campaign, original roster and completion evidence together. Keep the investigation in your private support system; avoid placing participant details or the reason for a disputed award on a public certificate.
Write down the decision before changing the record
Use a short case record containing the affected credential link, reported error, approved source record, reviewer, proposed action and records that must remain unchanged. Record whether a replacement is authorized and for whom. A correction request is not automatic permission to issue a new award.
If the error may affect other rows, pause further sends from the affected input while the owner checks its scope. Do not delete a whole campaign simply because one record is wrong. Preserve the before-state needed for the review in your approved storage, following your organization’s data-handling rules.
Check the difference between one credential and a campaign
Sertifier’s sent-credential deletion guide describes two different scopes: removing a selected credential from a recipient’s record, and deleting a campaign, which removes all credentials issued under that campaign. Confirm the selected object and its scope before taking either action.
The certificate removal guide states that a removed credential is no longer accessible to its recipient. Do not assume deletion provides a public revocation notice, preserves a usable verification page, or offers an undo action. Resolve any required recovery or record-retention questions with the responsible administrator before deletion.
Editing a shared campaign is a separate operation. Sertifier documents that campaign edits affect its issued credentials. A broad design or content edit is therefore not a substitute for resolving the recipient of one award. For spreadsheet changes, review the recipient import scope guide before uploading another file.
Fictional example: one incorrect award in an otherwise valid cohort
Suppose a sample completion roster was mapped incorrectly: Sample B received the award intended for Sample A. The program owner confirms that Sample A met the requirements and Sample B did not. This is a fictional operating example, not a customer result.
Review the affected award
Match Sample B’s credential identifier to the incorrect roster entry. Record the owner’s decision about that specific award.
Protect the rest of the cohort
Keep correctly issued awards outside the change scope. A campaign-wide deletion is not the approved action in this example.
Prepare only the approved replacement
Check Sample A’s eligibility, name, address and award details. Check whether an appropriate credential already exists before issuing another.
The useful distinction is between correcting the error and repeating the original batch. Before continuing issuance, repair the input or mapping that produced the mismatch and review it with a synthetic test record.
Verify the outcome and communicate clearly
- Inspect the original credential link. Record what a recipient can actually see after the supported change. Do not call an unavailable page a visible revocation notice.
- Check any authorized replacement. Confirm its recipient, achievement, dates and verification link against the approved source.
- Check an unaffected award. Confirm that the action did not change another credential in the campaign.
- Tell each affected recipient what to use. Use your approved communication process and share only the information relevant to that person. Do not assume a previously downloaded file or forwarded email has changed.
- Close the case with evidence. Record the operator, action time, observed result and any unresolved delivery or access issue.
Frequently asked questions
Can I just change the name to another person?
First establish whether the award belongs to that person. A name edit does not establish eligibility or resolve an incorrectly issued achievement.
Should I resend the whole campaign?
Only issue the awards the program owner has approved. Check existing credentials first; replaying a cohort is not a reliable way to isolate one correction.
Is deleting a credential the same as publishing a revocation status?
Do not treat them as interchangeable. The Sertifier removal documentation describes removing access. Confirm the actual recipient-facing result rather than promising a particular status label.
Build a review step into your next certificate campaign
Agree who approves eligibility, which roster is authoritative and who checks the recipient view before issuing. Create a Sertifier workspace to prepare your certificate workflow, and test it with synthetic recipients before using a real cohort.
