A scheduled certificate campaign is useful when an approved cohort should receive its credentials at a planned time. The practical risk is that the list, message or achievement record changes between preparation and release. Treat the schedule as a commitment to send a reviewed version, with someone responsible for changes before it runs.<\/p>\n
Short answer:<\/strong> Confirm who has earned the credential, what will be sent, which time the schedule represents and who can stop it. After the planned time, check the credential result and notification separately. A saved schedule does not prove that a recipient received an email.<\/p>\n Use a scheduled campaign when the recipients and approved achievement are known, but delivery should happen later. If eligibility depends on an event that has not happened yet, do not substitute a date for that decision. Keep those recipients out of the approved batch until their results are confirmed.<\/p>\n Sertifier documents scheduled campaigns, external application triggers and credential pathways as different automation methods. Its automation overview<\/a> explains the supported patterns. For broader integration design and duplicate handling, continue with the credentialing automation guide<\/a>.<\/p>\n Write down the meaning of each date before selecting a send time. This is an operating recommendation, not a claim that all programs or platforms use identical date fields.<\/p>\n Do not change an achievement date merely because the notification is delayed. Check how the selected issue date appears on both the certificate and credential page. If validity is part of your program, review shared and individual expiry dates<\/a> as a separate decision.<\/p>\n Keep a private release note that identifies the campaign, approved roster version, design, credential details, email template and operator. A colleague should be able to tell which version was reviewed without comparing screenshots by eye.<\/p>\n The current campaign creation guide<\/a> documents reviewing credential pages and emails, sending a test credential, and using Schedule for Later. Use a controlled internal address and fictional values for a test. The guide also describes a test banner; do not treat a test credential as evidence that the live campaign has run.<\/p>\n \u201cFriday morning\u201d is not a complete release instruction when the team works across timezones. Record a named timezone and a calendar date, then compare the saved schedule with that instruction. Where a local clock change could affect the date, confirm the intended offset for that specific day.<\/p>\n The public scheduling documentation reviewed for this guide does not establish recipient-local delivery, timezone conversion rules or an exact-to-the-second delivery guarantee. Verify the behavior shown in your account or with support before relying on any of those assumptions. Do not borrow timezone settings from a different feature and assume they control campaign scheduling.<\/p>\n Choose an internal review cutoff that leaves your team time to respond. This is your operational deadline, not a documented product cancellation limit. If an important correction arrives before release, inspect the current scheduled campaign and decide whether it can be corrected safely or should be cancelled while the issue is resolved.<\/p>\n Sertifier’s scheduled credentials guide<\/a> documents viewing scheduled credentials, editing or cancelling them, and using Cancel Issue from the scheduled list. Confirm the resulting state after an action. A click alone is not evidence that a send was stopped.<\/p>\n A training coordinator prepares the approved cohort for a Friday release. Before the scheduled time, the program owner reports that Sample B’s assessment is still under review. The coordinator checks the current campaign, holds the affected release, and reconciles the roster with the program owner. They review the revised batch before saving its next schedule.<\/p>\n If the send time has already passed, the next step changes: inspect whether a credential was created or sent before trying to schedule again. If Sample B already received an incorrect credential, use the program’s correction process. Do not create a second campaign to conceal the original result.<\/p>\n Compare the approved batch with the actual credential records. Then check notifications and recipient access separately. Keep unresolved results visible until there is evidence to close them.<\/p>\n Keep these records in your private operating system. Public examples and screenshots should contain no learner addresses, internal identifiers or customer data.<\/p>\n Start with one approved cohort and a clear review owner. Prepare the credential, check the recipient experience, confirm the schedule and verify the result. Create a Sertifier account<\/a> to prepare your credential campaign, or use the scheduling instructions<\/a> if your account is already set up.<\/p>\n No. The program’s eligibility decision must come first. Scheduling controls a planned action; it does not replace approval of the achievement.<\/p>\n Sertifier documents cancellation from the Scheduled view. Check the current state before acting and verify the result, especially close to the planned time.<\/p>\n First inspect the existing campaign and credential records. An email problem does not by itself justify creating another credential.<\/p>\n","protected":false},"excerpt":{"rendered":" A scheduled certificate campaign is useful when an approved cohort should receive its credentials at a planned time. The practical risk is that the list, message or achievement record changes between preparation and release. Treat the schedule as a commitment to send a reviewed version, with someone responsible for changes before it runs. Short answer: …<\/p>\n","protected":false},"author":3,"featured_media":20050,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"","rank_math_description":"Check the approved roster, dates, notification settings and cancellation state before a scheduled certificate campaign runs.","rank_math_focus_keyword":"","rank_math_canonical_url":"","footnotes":""},"categories":[939],"tags":[],"class_list":["post-20051","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\/20051","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=20051"}],"version-history":[{"count":1,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/posts\/20051\/revisions"}],"predecessor-version":[{"id":20052,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/posts\/20051\/revisions\/20052"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/media\/20050"}],"wp:attachment":[{"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/media?parent=20051"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/categories?post=20051"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/tags?post=20051"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Choose a schedule for a ready cohort<\/h2>\n
Keep the dates separate<\/h2>\n
\n
Review the exact batch before scheduling<\/h2>\n
\n
Check the time without guessing<\/h2>\n
Use a stop rule for last-minute changes<\/h2>\n
A fictional cohort example<\/h3>\n
Reconcile after the planned send<\/h2>\n
\n
Prepare your first scheduled campaign<\/h2>\n
Frequently asked questions<\/h2>\n
Does scheduling confirm that a certificate has been earned?<\/h3>\n
Can a scheduled campaign be cancelled?<\/h3>\n
Should I schedule the same batch again if an email is missing?<\/h3>\n