A completion certificate people trust: what to put on it

A certificate attached to a CV is not read. It is glanced at. In that glance the reader asks exactly two questions: who issued this, and what did the holder do to earn it? A certificate that answers neither drops straight into the decorative pile, however handsome the border and however shiny the seal.

Most certificates I see are designed as pictures rather than as statements. The effort goes into the gold trim and the placement of the logo, and nothing is left over for the fields that actually carry the trust. This article is about those fields: what belongs on an online course completion certificate, what to delete from it, and how to make it checkable instead of merely assertive.

The certificate is written for a third party, not for your learner

This is the mental switch that changes every decision after it. You are not writing for the learner, who knows perfectly well what they studied and how hard it was. You are writing for three readers, and each arrives with a different question.

The learner wants something they can show: their name exactly as it appears on their official ID, and a title that someone outside your field can understand. The checker, a hiring manager or a training committee or a client choosing between freelancers, wants one fast answer: did this really come from the body it names? They will not call you to ask. They will move on. And you, two years from now, when a question arrives about a cohort whose details only the record still remembers.

Write for the third party and most of the ornament falls away on its own. The line you are proudest of is usually the one nobody can check, and the line that strikes you as painfully plain is the one that settles the matter: completed these modules and passed their quiz on this date.

The six fields that carry the trust

A useful certificate says six things without ambiguity. Two of them the platform prepares for you, three are decisions you make once in the template, and the sixth is the whole difference between a document and a picture.

Field	Why the reader cares	Where it comes from
The learner's name as recorded	One wrong letter and it no longer matches their official ID	Filled automatically from the learner record at issue time
The issuing body and its visual identity	The reader attributes it to an organisation they can look up, not to an anonymous file	Your logo and colours in a template you design once
A specific title for what was achieved	"A marketing course" says nothing; "Paid search advertising" says something	Your wording in the template
The issue date	It dates the skill, and in fast-moving fields that is half its value	Filled automatically at issue time
One line describing what earned it	It turns a claim into a description someone can believe	Your wording, provided it matches the rule you actually set
A verification link	The difference between a document you can check and a picture you either believe or do not	A public link and a verification page anyone can open

Notice that the name and the date are never typed by you. The template holds the learner fields and they fill from the record at issue time, which by itself kills the classic failure of hand-made certificates: a misspelled name on a document claiming to be official. The rest of the look is the identity your learner already sees on every page of your academy, and the template is built once from your logo and colours and then forgotten.

And what to delete

• Signatures from people the reader has never heard of and cannot verify.
• Phrases like "internationally accredited" with no named accrediting body. That line tells a professional reader precisely one thing: there is no accreditation.
• Invented serial numbers with no record behind them. A number nobody can look up is ornament dressed as data.
• Logos of organisations that never gave you permission to use them.

Each of these buys the appearance of officialdom and pays for it out of credibility. A professional reader spots the difference faster than you would expect, because certificates cross their desk in bulk and the eye learns quickly which parts can be checked and which cannot.

The rule before the template: attended, completed, passed

The real content of any certificate is not its wording but the rule that granted it. That is why the work starts with deciding what "completed" means in your course, precisely, and not with choosing a typeface. The biggest drafting mistake that follows is reaching for the strongest available phrase instead of the truest one. The working rule: write the sentence you could defend if someone asked how you verified it. Three claims are available to you, and each rests on different evidence.

1. Attended: evidenced by attendance actually recorded in the live session. Session and program certificates on Dwrrah rest on exactly this. Someone who booked a slot and then failed to show up earns nothing, even if they paid. A booking is not attendance, and that distinction alone is what keeps the certificate from being a payment receipt in disguise.
2. Completed: evidenced by finishing the course content as you arranged it. Here is why building the content comes before designing the certificate: the order of the modules is the working definition of the word "completed". If your material is a pile of files in no particular order, you have no definition to defend.
3. Passed: evidenced by a quiz whose passing mark is the condition for issuing. This is the strongest of the three, because it is the only one that speaks about understanding rather than mere exposure.

Running both kinds side by side in one academy is perfectly reasonable: a session or program certificate resting on recorded attendance, and a course certificate resting on completed content and a passed quiz. The only real problem is writing "passed" when you measured nothing, because the first learner who tells an employer there was never a test brings down every certificate you have ever issued.

Once the rule is set, let certificate issuance run automatically for whoever meets it, so the certificate goes out the moment the condition is satisfied, with no work from you and no waiting for the cohort to finish. Manual issuance exists for the case a rule does not cover, and it stays healthy only as a named exception you could explain. Every time you issue one by hand because the rule felt "a bit strict", you are not doing one learner a favour. You are lowering the value of every certificate you issued before it and every one you will issue after.

Test your rule with a single question: if you handed this certificate to everyone who paid, would the list change? If the answer is no, the rule is doing no work and your certificate describes a payment rather than a piece of learning.

A certificate is a page to be checked, not a file to be circulated

Here is the decision that surprises some trainers the first time: on Dwrrah there is no stored PDF to download. The certificate is a single page rendered from one source at its own link, printed straight from the browser, or kept as a copy through your device's print option.

The reason is simple. A file in circulation cannot be verified. Anyone can open an image and change the name and the date on it in two minutes, and the reader has nothing to compare it against. A certificate that lives at its link is a different object, because the verification page reads the source itself, and a doctored copy fails the first check. Keeping the certificate on one source is what makes verification possible in the first place.

There is a cost to that, so let us name it: some job portals and application forms want an attachment, not a link. In that case your learner prints the page and uploads the printout, and the link remains the original that anyone who wants certainty can return to. Teach your learners that small habit: on LinkedIn and on a CV, the link beats the image, because an image ends at an impression and a link ends at certainty.

What a digital certificate cannot do, plainly

• It is not accreditation. The verification page proves that your academy issued this certificate to this person. It does not prove that your programme is accredited by any educational or professional body. That reputation is yours to build through outcomes; the platform only keeps the record straight.
• It does not stop anyone designing a lookalike image. What it stops is that image surviving a check, because verification reads the source rather than the file in the reader's hands.
• It cannot repair a weak eligibility rule. If the rule is "opened the course page", the certificate is perfectly truthful about something worthless.
• It cannot force anyone to accept it. The most it can do is make acceptance an easy decision: a clear issuer, a specific claim, and a link that checks out in seconds.

We say this out loud because a trainer who sells an "accredited certificate" without holding any accreditation loses twice: once with the learner who eventually finds out, and once with a market that grows more sceptical of every certificate issued after it, including the certificates of people who were telling the truth.

Five mistakes that hollow out a certificate, and where to start

One: issuing it to everyone who paid. A certificate everybody receives distinguishes nobody. Its value comes from the existence of people who did not receive one.

Two: typing the name by hand for every learner. Tedious work that repeats with every cohort and eventually misspells a name on a document claiming to be official. Fields that fill from the record close that door for good.

Three: a generic title that says nothing. "Training course" or "development programme" gives the reader nothing to act on. Write the name of the skill the way a hiring manager searches for it, not the way you like to label your material.

Four: sending an image instead of the link. The image travels through chat and email and nobody can check it. The link is the product; the printout is a copy of it, not a replacement.

Five: designing the template before setting the rule. Two hours on a typeface and a border, then the discovery that you do not know who deserves the thing. Reverse the order.

Start with the sentence rather than the design: write in one line what your certificate will say about its holder, then ask whether the learner's record actually holds evidence for it. If it does, the rest is a short setup. If it does not, the work waiting for you is inside the course, not inside the template. Certificates are on the Premium plan, and you can try them in full during the 14-day free trial, which needs no card: issue one to yourself and open its verification link the way the first employer will.