{"id":20054,"date":"2026-10-25T10:40:03","date_gmt":"2026-10-25T10:40:03","guid":{"rendered":"https:\/\/sertifier.com\/blog\/?p=20054"},"modified":"2026-10-25T10:40:03","modified_gmt":"2026-10-25T10:40:03","slug":"adding-certificate-recipients-after-first-batch","status":"publish","type":"post","link":"https:\/\/sertifier.com\/blog\/adding-certificate-recipients-after-first-batch\/","title":{"rendered":"Adding certificate recipients after the first batch: a coordinator\u2019s checklist"},"content":{"rendered":"<p>The first certificate batch has gone out, then another approved participant appears on the roster. Before sending anything, establish whether that person needs a new credential or already has one. A missing email, a name correction and a newly confirmed completion call for different actions.<\/p>\n<p><strong>Short answer:<\/strong> Build a small list containing only the newly approved recipients, compare it with existing credential records, and decide whether to extend the original campaign or create a separate campaign from it. Preview the result and reconcile the new records after sending. Keep unresolved eligibility cases outside the release.<\/p>\n<h2>Identify what actually changed<\/h2>\n<p>Start with the program&#8217;s completion evidence, not the latest spreadsheet alone. A late registration does not establish that someone earned the certificate. Ask the program owner to confirm the achievement, recipient identity and applicable dates before adding a person to the approved list.<\/p>\n<p>Use this fictional example to separate the work. These sample labels represent different situations, not real learner records or measured outcomes.<\/p>\n<table>\n<thead>\n<tr>\n<th>Request<\/th>\n<th>Existing record<\/th>\n<th>Next action<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Sample A did not receive an email<\/td>\n<td>A correct credential already exists<\/td>\n<td>Inspect notification delivery; do not add another award<\/td>\n<\/tr>\n<tr>\n<td>Sample B completed the requirements after the first release<\/td>\n<td>No credential for this achievement<\/td>\n<td>Add to the newly approved recipient list<\/td>\n<\/tr>\n<tr>\n<td>Sample C asks for a spelling correction<\/td>\n<td>A credential exists with an incorrect name<\/td>\n<td>Use the correction process for that record<\/td>\n<\/tr>\n<tr>\n<td>Sample D is awaiting an assessment decision<\/td>\n<td>Eligibility is unresolved<\/td>\n<td>Hold until the program owner confirms the result<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Sertifier documents <a href=\"https:\/\/help.sertifier.com\/resend-a-credential-email-to-my-recipient\">Send Again for an existing credential email<\/a>. If the credential is already correct, follow the <a href=\"https:\/\/sertifier.com\/blog\/digital-credential-email-delivery\/\">email delivery guide<\/a> instead of adding the person to another issuance batch.<\/p>\n<h2>Build the additional-recipient list<\/h2>\n<p>Keep the original approved roster and release record. Create a separate working list for additions, recording why each person belongs in it. This is a recommended operating practice; it is not a claim that the product automatically reconciles eligibility.<\/p>\n<ul>\n<li><strong>Match the achievement.<\/strong> Check the program, cohort or completion event, not just the person&#8217;s name. The same person may legitimately earn different credentials.<\/li>\n<li><strong>Check existing issuance.<\/strong> Search for the recipient and the relevant credential before assuming that a missing spreadsheet row means no credential exists.<\/li>\n<li><strong>Confirm recipient values.<\/strong> Review the delivery address, display name and any attributes used by this design.<\/li>\n<li><strong>Keep dates meaningful.<\/strong> Confirm the achievement, issue and expiry dates under your program&#8217;s rules. A later administrative send should not silently redefine when an achievement occurred.<\/li>\n<li><strong>Separate unresolved requests.<\/strong> Keep unapproved additions and corrections out of the ready-to-send list.<\/li>\n<\/ul>\n<p>Sertifier&#8217;s <a href=\"https:\/\/help.sertifier.com\/what-are-credential-reports\">credential reports guide<\/a> describes records including recipient, campaign, status, credential ID, page URL and send date. Use the relevant records to investigate the original batch and capture the result. Do not treat an email status as proof that the learner earned the award.<\/p>\n<h2>Choose whether to extend or copy the campaign<\/h2>\n<p>There are two documented routes in Sertifier. <strong>Send to New Recipients<\/strong> duplicates the selected campaign and opens a new campaign for additional recipients. To add people without copying the campaign, the help guide describes editing the sent campaign and choosing <strong>Edit Recipients<\/strong>, then <strong>Add Recipients<\/strong>. See the current <a href=\"https:\/\/help.sertifier.com\/how-do-i-add-recipients\">recipient instructions<\/a> for the interface steps.<\/p>\n<p>Choose based on how your team needs to review and account for the work:<\/p>\n<ul>\n<li><strong>Extend the existing campaign<\/strong> when the additional people belong to the same approved release context and your team wants to manage their records there.<\/li>\n<li><strong>Use a separate campaign<\/strong> when the later group needs its own review, notification or operational record. Treat the copied setup as a starting point that still needs checking.<\/li>\n<\/ul>\n<p>Those are workflow recommendations, not automatic product rules. A copied campaign is not evidence that every inherited field is suitable for the new group. Review the credential title, design, dates, recipient attributes and email before issuing.<\/p>\n<p>If importing the additions presents update choices for existing recipients or credentials, pause and identify the affected records. The <a href=\"https:\/\/sertifier.com\/blog\/recipient-import-change-scope\/\">recipient import guide<\/a> covers that separate decision. Do not choose an update option merely to make a spreadsheet upload finish.<\/p>\n<h2>Review only the intended additions before sending<\/h2>\n<p>Compare the final recipient list with the approved additions. Check that already-issued recipients have not been included by mistake and that held cases remain excluded. Record which campaign will receive the additions and who reviewed the list.<\/p>\n<p>Then review the actual credential and message. Sertifier&#8217;s <a href=\"https:\/\/help.sertifier.com\/what-is-the-preview\">preview instructions<\/a> describe checking the credential and email and sending a test. Use a controlled internal address and fictional recipient values for that test. A successful test checks the prepared experience; it does not prove the live recipient list is correct.<\/p>\n<p>For a later release, follow the <a href=\"https:\/\/sertifier.com\/blog\/scheduled-certificate-delivery\/\">scheduled delivery checklist<\/a>. Recheck the additional list if eligibility changes before the scheduled time.<\/p>\n<h2>Reconcile the result without replaying the batch<\/h2>\n<p>After issuing, compare the intended additions with the resulting credential records. For each approved recipient, retain a private reference to the corresponding credential and record any unresolved result. Check notification delivery separately.<\/p>\n<p>If an action times out or its result is unclear, inspect the current campaign and credential records before trying again. Repeating the same send without checking can make it harder to distinguish a missing result from a duplicate action. For integrations that must handle repeated events, use the broader <a href=\"https:\/\/sertifier.com\/blog\/credentialing-automation-workflow\/\">credentialing automation guide<\/a>.<\/p>\n<p>Close the additional batch when the approved people and their credential results reconcile. Keep held requests visible for a later decision; do not mark them complete because the rest of the batch was sent. Keep learner names, addresses and internal notes in your private system, not in public examples.<\/p>\n<h2>Prepare the next approved group<\/h2>\n<p>A reliable additional batch starts with a verified list and a deliberate campaign choice. <a href=\"https:\/\/app.sertifier.com\/signup\">Create a Sertifier account<\/a> to prepare your credential workflow, or follow the <a href=\"https:\/\/help.sertifier.com\/how-do-i-add-recipients\">recipient instructions<\/a> in your existing account.<\/p>\n<h2>Frequently asked questions<\/h2>\n<h3>Should I upload the entire original roster again?<\/h3>\n<p>First identify the newly approved people and compare them with existing records. Reusing a full roster without that comparison does not establish who needs a new credential.<\/p>\n<h3>Does Send to New Recipients keep the same campaign?<\/h3>\n<p>The documented action duplicates the selected campaign. The recipient guide describes editing the sent campaign as the alternative when you want to add people without making a copy.<\/p>\n<h3>What if the participant already has the certificate but cannot find the email?<\/h3>\n<p>Inspect the existing credential and delivery record. If the credential is correct, use the notification workflow rather than treating the request as a new award.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The first certificate batch has gone out, then another approved participant appears on the roster. Before sending anything, establish whether that person needs a new credential or already has one. A missing email, a name correction and a newly confirmed completion call for different actions. Short answer: Build a small list containing only the newly &hellip;<\/p>\n","protected":false},"author":3,"featured_media":20053,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"","rank_math_description":"Add newly approved certificate recipients after the first batch. Compare existing records, choose the campaign route and verify the result.","rank_math_focus_keyword":"","rank_math_canonical_url":"","footnotes":""},"categories":[939],"tags":[],"class_list":["post-20054","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-digital-credentials"],"_links":{"self":[{"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/posts\/20054","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/comments?post=20054"}],"version-history":[{"count":1,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/posts\/20054\/revisions"}],"predecessor-version":[{"id":20055,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/posts\/20054\/revisions\/20055"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/media\/20053"}],"wp:attachment":[{"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/media?parent=20054"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/categories?post=20054"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/tags?post=20054"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}