Certificate issuance request form: a brief for training teams

A request to “send certificates for the workshop” leaves several decisions unresolved: what the award means, which list is approved and who can authorize delivery. Give the issuing coordinator one clear request record before they start building the campaign.

The template below is a suggested internal process for training teams that ask a central coordinator to issue credentials. Keep it in your approved form, ticket or document system. It is not a built-in Sertifier approval form, and submitting it does not authorize a send.

Separate the request from approval to issue

The requester supplies the course information and proposed delivery date. The program owner confirms the award criteria and eligible recipients. The coordinator prepares the credential and checks the approved materials. Name the person who gives the final release approval; do not infer approval from a deadline or a completed form.

Institutional requirements can differ. For example, the University of Dayton’s non-credit certificate request service distinguishes attendance or completion certificates from official continuing education units and academic credit. Follow your organization’s actual policy rather than treating a generic form as authority to award a regulated qualification.

A certificate issuance request form you can adapt

Copy the following fields into your team’s existing request system. Store recipient data in an access-controlled file and link to it, instead of pasting the roster into a broadly visible ticket.

Request and program

Request reference; requester and department; course or event name; cohort reference; program owner.

Meaning of the award

Exact credential title; proposed description; attendance, completion or assessed achievement; approved earning criteria and the record that supports eligibility.

Recipient list

Controlled roster location; file version; person responsible for confirming names and delivery addresses; approval state; excluded or unresolved records.

Dates and delivery

Course dates; intended issue date; any applicable expiry rule; requested send date, time and timezone. Explain any difference between completion and delivery dates.

Approved materials

Design reference; issuer name; authorized signature material where used; credential description; notification email; support contact.

Existing records

New cohort, additional recipients or correction; existing campaign reference if applicable; whether any recipients already hold this award.

Review and release

Preview reviewer; outstanding decisions; final approver; approval date and exact roster/material version approved; coordinator responsible for sending.

Leave a field marked “pending” when the answer is unknown. A blank expiry field, for example, should not silently become a decision that the award never expires.

Use a hold record when a request is incomplete

Return a specific question to the person who owns the missing decision. The coordinator should not invent assessment criteria, infer attendance from registration or include an unresolved recipient just to match a requested total.

Fictional request example
Program: Customer onboarding workshop, October cohort.
Requested action: Prepare completion certificates.
Roster: Approved file version B; one record remains held.
Open question: The course owner has not confirmed completion for that record.
Next action: Prepare the approved subset for preview; keep the held record out of the release list until the owner decides.
Release approval: Pending review of the credential and notification.

This example separates permission to prepare a draft from permission to send it. A later approval should identify the exact materials reviewed. If the roster changes after approval, check whether the change needs another review under your team’s process.

Turn the approved brief into a credential campaign

In Sertifier, the credential details guide documents a title, description and skills, with optional fields including earning criteria and supporting documents. Use the approved brief to supply those details. Do not turn a participation award into an assessed skill claim merely because a field is available.

Check the request type before importing a list. Sertifier’s recipient upload guide distinguishes account-level and campaign-level imports and documents different effects for existing recipient emails. Some options update existing records; others create a new credential. Choose deliberately rather than treating every request as a fresh batch.

If the request is for extra recipients after an earlier send, use the separate additional-recipient checklist. For delivery at a future time, review the scheduled certificate delivery guide after the roster and release approval are settled.

Approve the recipient experience, then close the request

Review the credential and notification together. Sertifier’s preview documentation explains how to review both and send a test certificate to yourself. Use an authorized test recipient and your approved testing process. Check the displayed title, names, dates, links and notification copy against the request.

Record the reviewed version and approval before sending. After the authorized issuance, add the campaign reference, actual send time and observed result to the request. Keep any exceptions open with an owner. “Sent” is not proof that every recipient opened the email or viewed their credential.

If you already use Sertifier, adapt this request form to your next approved cohort and follow the linked setup guides. If you are evaluating a shared issuing workflow, create a Sertifier account and prepare a sample credential with fictional recipient data before working on your approved live cohort.