Certificate campaign naming: a practical convention for training teams
A useful certificate campaign name tells an administrator which program, cohort and release they are about to open. Keep it distinct from the achievement title that a recipient should see. A clear internal label helps a reviewer choose the intended record, but it does not establish eligibility or approve a send.
In Sertifier, the campaign title is hidden from recipients, according to the campaign creation guide. Use that internal field for operational context. Write the credential title and notification subject for the person receiving the award.
This guide offers a naming convention and a small review worksheet. They are suggested working practices, not built-in validation rules or a promise that a name prevents mistakes.
Separate the three names
An internal campaign name answers “Which issuance job is this?” A credential title answers “What did this person earn?” An email subject helps the recipient recognize the notification. Do not assume that changing one updates the others.
For a fictional project-planning workshop, those fields could read:
| Field | Example | Purpose |
|---|---|---|
| Internal campaign name | PP101 / 2026-11 / Cohort B / Initial | Find the intended issuance job |
| Credential title | Introduction to project planning | Describe the achievement |
| Email subject | Your project planning certificate is ready | Identify the notification |
These are invented examples, not actual learner or customer records. Before sending, inspect the configured fields and the resulting preview rather than relying on the campaign list alone.
Choose a small set of stable parts
Start with Program / Cohort / Release. Add another component only when it resolves a real ambiguity in your workflow.
Program is a short identifier your team can interpret consistently. Keep a private reference that maps an abbreviation such as PP101 to the approved program definition. Do not create an abbreviation that incoming staff must guess.
Cohort identifies the learning group or completion event. Decide whether a date in this component means the start month, completion month or cohort label. Use the same meaning across the program. It should not silently change because an administrator sends the certificates later.
Release distinguishes the original batch from an approved additional batch or another operationally separate job. Choose plain terms such as Initial or Additions A, then define what they mean in the team’s working record.
For example, PP101 / 2026-11 / Cohort B / Additions A identifies a later batch for the same fictional cohort. It does not prove that its recipients were absent from the initial batch. That requires checking the actual records.
Avoid packing the whole approval history into the name. Keep eligibility decisions, source files and review notes in a controlled record associated with the campaign.
Keep changing status outside the permanent name
Words such as “final,” “approved” and “sent” can become stale. A draft called Final may still contain an unresolved recipient list. A label containing Sent does not prove that issuance succeeded.
Use the system’s current state and the recorded release decision to answer those questions. Sertifier’s API documentation distinguishes campaign states including Draft, Scheduled and Sent. A naming convention is not a replacement for that state or for checking the resulting credentials.
If your team uses a temporary working label during preparation, document how it is retired. Do not create successive names such as Final, Final new and Final latest as the only record of which version was reviewed.
Name an additional batch deliberately
When more approved recipients arrive, decide whether they belong in the existing campaign or a separate one before assigning a label. Sertifier’s recipient instructions describe Send to New Recipients as creating a duplicate campaign. They also describe adding recipients by editing the existing campaign.
If you choose a separate campaign, review its inherited details and give the new record a name that explains its relationship to the original. Keep references to both records in your release worksheet. A renamed copy is not proof that its dates, notification or recipient list suit the new group.
Use the additional-recipient checklist for the roster and issuance decision. The naming task here is narrower: make the chosen campaign identifiable after that decision is made.
Use a short campaign index
Maintain an index in your organization’s approved workspace when several administrators share a program. The following is a suggested structure, not a Sertifier export format.
| Record | What to enter |
|---|---|
| Internal name | The agreed program, cohort and release label |
| Campaign reference | A stable record ID or authorized link |
| Approved achievement | The credential title and program definition |
| Cohort meaning | What the date or group code represents |
| Related release | Original campaign or additional-batch reference, if applicable |
| Review owner | The person responsible for the release decision |
| Open question | The unresolved issue and its next action |
Keep personal details and sensitive learner information out of the label. Store supporting records where access matches the people who need them. A short internal identifier is easier to reference in an operational conversation than a list of learner names.
Test the convention with a handover task
Ask another authorized administrator to find a prepared campaign using the index. They should be able to identify the intended cohort, distinguish it from an earlier release and locate any open question without sending anything.
If two campaigns still look interchangeable, identify the missing distinction. Add the smallest useful component rather than expanding every name into a sentence. If the problem is an unclear program definition, resolve that definition instead of hiding it behind a longer code.
Then check the recipient-facing experience separately. Use the test certificate workflow to inspect the message and credential with controlled sample values. An intelligible internal name does not establish that the recipient sees the correct achievement.
Adopt the convention without rewriting history
Apply the agreed format to the next prepared campaign first. For older campaigns, start by mapping existing names to stable references in the index. Do not resend credentials or create replacement campaigns simply to make historical labels consistent.
If you decide an existing campaign needs renaming, inspect its current state and use the supported interface for that record. Preserve its reference and the reason for the administrative change. Review any downstream process that relies on the name before changing it; do not assume every integration uses a stable ID.
For the next release, confirm the campaign reference, cohort meaning, achievement title and approval record together. If you are starting a credential workflow, create a Sertifier account and establish a naming convention while preparing your first campaign.
