You did the teaching. Now your participants want certificates — something they can show an employer, a client, or a licensing board. That sounds simple until you are staring at a list of forty names, three spelled in ways you are not sure about. This guide covers what a certificate needs to carry, the practical ways to issue one, and how to fix the mistakes that happen.
A certificate is a claim: this person completed this program, run by this organization, on this date. It has to carry enough detail for someone else to check that claim later:
Optional but often useful: training hours, topics covered, a signature or seal. They add credibility, but the five items above are the core — without a way to verify, the rest is decoration.
By hand. Design a template in a tool like Canva or Word, fill in each name, export a PDF, email it. For five people, this is fine. For fifty, it eats an afternoon, and every manual step is a chance to misspell a name or send the wrong file to the wrong person. And there is no record afterward — confirming a certificate months later means searching your sent folder.
With PDF and mail-merge tools. A spreadsheet plus a merge tool generates many PDFs at once and scales better, but you still keep your own list of who got what, and the PDFs still prove nothing on their own.
With a certificate service. You enter or upload the recipient list once, and the service generates each certificate, emails it to the recipient, and keeps the issuance record. Every certificate carries its own verification page and QR code. This removes the repetitive work and gives you a record you can check — and a way to fix mistakes, covered below.
It is tempting to think verification is the recipient's problem. It is yours too: your organization's name is on every certificate you issue. A bare PDF can be copied, edited, or faked outright — a stranger can put their name on your workshop's certificate, no employer can tell the difference, and your program's reputation takes the hit.
A QR code and verification page change that. Anyone checking lands on a page showing the details from your issuance record: the name, the program, the date, and whether the certificate is still valid. A fake has no matching record. It also helps your real participants: a certificate an employer can confirm in seconds is worth more than one that triggers a phone call to you.
Names get misspelled. Someone registers under one name and wants another on the certificate. A certificate goes to the wrong person, or a participant's completion is later found not to count.
With hand-made PDFs, a correction means editing, re-exporting, and re-sending — and the wrong version is still out there, indistinguishable from the right one. With a certificate service, you revoke the bad certificate: its verification page then shows it is no longer valid, and you issue a corrected one. Revocation is also your answer if a certificate was obtained improperly.
CertLaurel is a certificate service built for issuers who do not run a learning management system. You can issue one at a time from the dashboard, upload a CSV list, or use the API, which is included on every plan, even the free one. If a row in your CSV has a problem, the error message explains it in plain English. Plans run from a free tier (25 certificates a month) to $19, $49, and $99 a month, each with a hard monthly cap and no overage charges — and verification pages for certificates you have already issued never go dark if you stop paying. CertLaurel is run by The R Thompson Group Inc. Details at certlaurel.com.