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.<\/p>\n
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.<\/p>\n
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.<\/p>\n
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.<\/p>\n
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.<\/p>\n
Sertifier’s sent-credential deletion guide<\/a> 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.<\/p>\n The certificate removal guide<\/a> 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.<\/p>\n Editing a shared campaign is a separate operation. Sertifier documents that campaign edits affect its issued credentials<\/a>. 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<\/a> before uploading another file.<\/p>\n 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.<\/p>\n Review the affected award<\/strong> Protect the rest of the cohort<\/strong> Prepare only the approved replacement<\/strong> 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.<\/p>\n First establish whether the award belongs to that person. A name edit does not establish eligibility or resolve an incorrectly issued achievement.<\/p>\n 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.<\/p>\n 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.<\/p>\nFictional example: one incorrect award in an otherwise valid cohort<\/h2>\n
Match Sample B’s credential identifier to the incorrect roster entry. Record the owner’s decision about that specific award.<\/p>\n
Keep correctly issued awards outside the change scope. A campaign-wide deletion is not the approved action in this example.<\/p>\n
Check Sample A’s eligibility, name, address and award details. Check whether an appropriate credential already exists before issuing another.<\/p>\n<\/div>\nVerify the outcome and communicate clearly<\/h2>\n
\n
Frequently asked questions<\/h2>\n
Can I just change the name to another person?<\/h3>\n
Should I resend the whole campaign?<\/h3>\n
Is deleting a credential the same as publishing a revocation status?<\/h3>\n
Build a review step into your next certificate campaign<\/h2>\n