You passed. The provisional result is on the screen, the confirmation email will follow, and now there is a question nobody's study guide covered: who at work do you actually tell, and how? Handled well, this conversation converts a certificate into assignments, review-cycle evidence and, sometimes, money. Handled as a one-line Slack message — or not at all — the credential sits in a drawer.
This guide covers the private channels only: your manager, HR, and hiring managers when you are interviewing. Posting the public announcement is a different exercise with its own etiquette, covered in how to announce a certification professionally, and updating your profiles is mapped in adding certifications to your professional profile.
Wait for the official confirmation before you tell anyone
Some programmes show a provisional result at the test centre before the formal confirmation arrives; only when the credential is officially issued do you have something verifiable — a credential ID, often a digital badge. Share after that point, not before. Two reasons:
- Employers can and do verify. Most major providers run verification systems, and a claim your employer cannot yet confirm starts the conversation on the wrong foot. (The mechanics of the employer side are explained in how employers verify professional certifications.)
- The badge or ID is your attachment. The message you send is stronger when it carries proof rather than a promise of proof.
The one exception: if your employer funded the exam or gave you study time, a same-day "passed — official confirmation to follow" note is courteous and expected.
Telling your manager: a conversation, not a notification
Your manager is the person who decides whether this credential changes your work, so the goal is not "FYI, I passed" — it is a short conversation that connects the credential to something your team needs.
Structure the message in three moves:
- The fact. Credential name, issuer, date. One sentence.
- The relevance. One or two sentences linking what the certification covers to a live problem, project or gap on your team.
- The ask. What you would like to happen next: a chance to apply it, a stretch assignment, inclusion in a project, or simply that it is noted for your development plan.
A workable email:
Subject: Passed the AWS Certified Cloud Practitioner
>
Hi Dana,
>
Quick note that I passed the AWS Certified Cloud Practitioner exam on Tuesday — official confirmation and badge attached.
>
The exam covers cloud concepts, billing and the core AWS services, which is directly relevant to the cost-review work the team has coming up. I'd like to put it to use — could we find fifteen minutes to talk about where that would help most?
>
Thanks, Sam
Notice what the email does not do: apologise ("just a small thing…"), inflate ("I'm now a cloud expert"), or demand ("I expect this to be reflected in my compensation"). The relevance-plus-ask structure lets your manager say yes to something concrete.
If your employer paid for the exam, lead with acknowledgement — "thanks for supporting this" — and close the loop on any paperwork the funding required. Sponsored training usually comes with an implicit expectation of a report-back; meet it before it is asked for.
If the certification is unrelated to your current role, be straightforward about why you pursued it. Framed as initiative and direction ("I'm building towards X; wanted you to know where I'm heading"), it reads well. Concealed and discovered later, it reads like a flight risk.
Getting it into HR records — the step almost everyone skips
Telling your manager does not update your employment record. File the credential with HR (or your HRIS self-service portal) separately, because the official record is what feeds:
- Capability and compliance audits. Teams bidding for work or maintaining partner statuses often need to evidence certified staff; an unrecorded credential is invisible to that count.
- Internal mobility. Internal recruiters search HR systems, not your memory.
- Training-budget justification. A recorded pass makes the next funding request — yours or a colleague's — easier to approve.
Send HR the credential name, issuer, issue and expiry dates, and the credential ID or verification link. Where the credential requires renewal, diarise the renewal date yourself; HR systems rarely remind you.
A certification mentioned for the first time during a review lands flat. The stronger sequence runs across the cycle:
- When you earn it: the manager conversation above, so it enters your development plan.
- In the months after: collect two or three instances where you applied what the certification covers — a decision you got right, a problem you handled, a task you took that you previously could not.
- At the review: present the credential plus the instances. "I earned X in March and used it to do Y and Z" is evidence; "I earned X" is a line item.
Whether a credential should move your pay is a market question that varies by role and employer — no honest general figure exists — but the review conversation is the legitimate place to raise scope, and scope is what moves pay. If certification was part of an agreed development goal, say so explicitly and mark the goal met.
Sharing with hiring managers when you are interviewing
The second employer audience is the one considering hiring you, and the channel etiquette differs:
- Earned before you applied: it belongs on your CV and profiles — no separate message needed. How recruiters and hiring managers actually weigh it is its own subject; see how employers view certifications.
- Earned mid-process: this is a genuinely good reason to email your recruiter or hiring manager. A two-line update — "Since we spoke, I've passed [credential]; badge attached — relevant to the [topic] part of the role" — keeps you visible and signals momentum. Send it once; do not manufacture repeat contact.
- In the interview itself: expect the credential to be probed, not admired. Prepare to explain why you earned it and what it proves — there is a dedicated guide to explaining a certification during a job interview.
Common mistakes when telling an employer
- Announcing before official confirmation. A provisional pass is not yet verifiable; wait for the issued credential.
- Making the message about the exam, not the work. Your manager needs a reason to care; the domains you now cover are that reason, the score is not.
- Skipping HR. The most consequential audience for audits, mobility and budgets is a form you never filled in.
- Leading with a pay demand. Compensation follows demonstrated scope. Ask for the work first, log the evidence, raise pay at the review with the evidence in hand.
- Overstating what the credential means. A foundational credential presented as expertise sets you up to disappoint. Present it as exactly what it is — verified coverage of a defined body of knowledge — and let your subsequent work do the inflating.
- Telling no one. The silent-modesty strategy has a 100% failure rate: credentials nobody knows about influence nothing.
From certificate to assignment: the week-one plan
If you want a simple sequence, this is it. Day one: official confirmation arrives; save the badge and credential ID. Day two: three-part email to your manager (fact, relevance, ask). Same week: file with HR, diarise the renewal date, and start the applied-evidence list for review season. If you are job-hunting, send the two-line update to any live processes. Then go get the assignment you asked for — the conversation you just had is only as good as the work that follows it. And if the pass has given you appetite for the next credential, browsing the certification exams directory while the momentum is fresh is a better use of the week than most.