How to Get Proof of Certification After Passing

"Please attach evidence of your certification." An HR system will not accept "it's on my LinkedIn", and a recruiter on a deadline will not chase your certification body for you. When that request lands, you need to know exactly which document to produce and where it lives — and the answer is almost never the score report you kept from exam day.

This guide walks through obtaining each one. How employers run verification on their side, and the etiquette of sharing badges publicly, are different subjects — here we deal only with getting the documents into your hands.

First, know which document the request actually needs

Requests for "proof" are vague, and sending the wrong artefact causes avoidable back-and-forth. A quick decoder:

Request	What to send
"Attach a copy of your certificate"	The official certificate PDF from your portal
"Provide your certification number"	The verification code / credential ID from your record
"We need to verify independently"	The verification code plus the provider's verification URL
"Evidence of all your credentials"	A transcript or consolidated record, where your provider offers one
"Proof you passed the exam" (rare)	Score report — the exam-day document, kept from your session

Note what is not on the list for most purposes: the score report. It evidences a session outcome, not a live credential, and it says nothing about whether the certification is still valid today. Certifications expire — Microsoft role-based credentials after 12 months, and CompTIA, AWS, Cisco, ISC2, ISACA and PMI credentials on three-year cycles — which is exactly why verification-based proof exists.

Step by step: collecting your proof documents

Step 1: log into the right portal

Your proof lives with the certification body, not with Pearson VUE or PSI. The delivery provider's account holds appointments and score reports; the credential record sits in the certification body's own system — your CompTIA account, Microsoft Learn profile, AWS Certification account, Cisco certification profile, ISC2 member area, or ISACA account. If you have never logged into that side, use the email address from your exam registration; the accounts are linked by your candidate record.

Step 2: download the certificate PDF

Inside the portal, find the area listing earned certifications and open the one you need. Providers place the certificate download alongside the credential record. Save the PDF with a sensible filename (name, certification, year), and store a copy somewhere durable — a personal drive, not only a work laptop you may hand back. If the portal offers a choice of certificate formats or languages, take the PDF: it is what upload forms expect.

Two checks before you send it anywhere:

• Name accuracy. The certificate shows the name on your certification record. If it is misspelt or outdated, correct it through the provider's support before distributing copies — a certificate that does not match your ID or CV invites questions.
• Dates. Confirm the issue and expiry dates match the portal record, especially if you have renewed before.

Step 3: locate your verification code

Somewhere on the same credential record is an identifier — variously labelled a verification code, certification number, credential ID or certificate number. This string, usually paired with the provider's public verification page, lets a third party confirm your status without trusting a PDF. Copy it into wherever you keep career records; it is the single most reusable piece of proof you own, because it stays valid as the credential renews while a downloaded certificate snapshot ages.

If a form asks for a "credential URL", the provider's verification page (or your badge's public link, below) is what belongs there.

Step 4: claim your digital badge

Many major programmes issue digital badges through third-party badging platforms — Credly is the one most candidates encounter. The flow is invitation-based:

1. After the credential is issued, an invitation email arrives from the badging platform.
2. Create or log into an account on that platform — use a personal email you will keep.
3. Accept the badge. It now has a public URL you can hand to anyone.

If no invitation arrives, check spam, then confirm which email address your certification account has on file — the invitation goes there, not necessarily to the address you check daily. Badge platforms also typically let you download the badge image and share the verification link; the link is the part that constitutes proof, since anyone can copy an image.

Step 5: pull a transcript if you hold several credentials

Where you hold multiple certifications with one body, look for a transcript or credential-history feature in the portal — one document listing everything with dates beats five separate certificates when an employer wants the full picture. Availability and naming vary by provider; if yours does not offer one, a set of verification codes covers the same ground.

Keep your proof from going stale

Proof of certification has a shelf life, because the underlying credential does. Three habits prevent an embarrassing moment where the certificate you attach is for a lapsed credential:

• Re-download after every renewal. A renewed credential means new dates; an old PDF now understates your status. Microsoft's free online renewal assessment, for instance, extends a role-based certification a year from its expiry date — after which the record, and the certificate worth sending, changes.
• Keep the portal email current. Badge invitations, renewal notices and expiry warnings all route through it.
• Store code, PDF and badge URL together in one place you control, per credential. Thirty seconds of filing beats a frantic portal search during a job application.

What happens to your proof once a credential actually lapses — and how recovery works — is covered in what happens when a certification expires, and the upkeep routine that stops it happening in how to keep your certifications current.