A recruiter reading "Sec+ certified (CompTIA)" and a recruiter reading "CompTIA Security+ (SY0-701) — CompTIA, issued March 2026, Credential ID COMP123456" are looking at the same achievement, but only one of those lines survives an applicant tracking system search, matches the job advert's wording, and can be verified in thirty seconds. Formatting is not decoration here — it is the difference between a credential that counts and one that gets missed.
This guide covers the mechanics only: what each certification entry should contain, how to word it, how to handle abbreviations, in-progress certifications and credential IDs. Where the section should sit on the page is a separate decision — our guide to where certifications go on a resume covers that — and if you are wondering whether to trim your list, see how many certifications to include.
One honesty note before the details: there is no official rulebook for resumes. Certification providers publish exam policies, not CV conventions, so everything below is editorial best practice built around two hard constraints that do exist — automated keyword matching and employer verification.
The anatomy of a correct certification entry
Every certification entry should carry four elements, in a consistent order:
- The full official name of the credential, exactly as the provider writes it — "AWS Certified Cloud Practitioner", not "AWS cert".
- The issuing organisation — Amazon Web Services, CompTIA, ISC2, ISACA. Certifications belong to providers, and naming the provider makes the credential checkable.
- The date earned, and the expiry or renewal status where the credential has one.
- A credential ID or verification link, where the provider issues one.
Put together, a clean plain-text entry looks like this:
CompTIA Security+ (SY0-701) — CompTIA | Issued Mar 2026 | Credential ID: COMP001234567
Or, in a slightly fuller two-line format:
AWS Certified Cloud Practitioner (CLF-C02) Amazon Web Services · Issued Jan 2026 · Valid to Jan 2029 · Verify: [credential URL]
Both formats work. What matters is that every entry in your section uses the same one.
Why the exam code is worth including
Where a certification has distinct versions, adding the exam code — SY0-701 for Security+, CLF-C02 for Cloud Practitioner, 220-1201/220-1202 for the current CompTIA A+ — quietly signals that your credential is current. As of 2026, Security+ means SY0-701 and A+ means the 220-1201/1202 series; a resume still describing an old code invites the question of whether the knowledge is current too. If you are unsure which version you hold, your score report or the provider's candidate portal will say. You can browse current exam codes across providers in the certification exams directory.
Codes are optional for credentials that do not version publicly (CISSP, for instance, is simply "CISSP — ISC2").
Use the official name — then handle abbreviations deliberately
Recruiters search resumes by keyword, and applicant tracking systems match text literally. That creates a simple rule: include both the full official name and the common abbreviation at least once, because you cannot know which one the search uses.
The tidy way to do it is name first, abbreviation in brackets:
- Certified Information Systems Security Professional (CISSP) — ISC2
- Certified Information Systems Auditor (CISA) — ISACA
- Project Management Professional (PMP) — Project Management Institute
After that first full mention, the abbreviation alone is fine elsewhere on the resume — in your summary or a job bullet. What to avoid:
- Invented shorthand. "Sec+", "SolArch", "Az Fund" match nothing a recruiter searches for.
- Wrong casing or spacing. It is "CompTIA A+", not "COMPTIA A +"; "ISC2", not "(ISC)²-style variants you half-remember". Copy the name from the provider's site or your certificate.
- Translating official names into British spellings. Official titles stay as issued, even where they use American spellings.
Dates, expiry and renewal status
Always include the issue date — an undated certification reads as either ancient or hidden. Beyond that, match the wording to how the credential actually behaves:
- Time-limited credentials. AWS certifications are valid for three years, so "Issued Jan 2026 · Valid to Jan 2029" is accurate and useful.
- Renewal-programme credentials. CompTIA runs a Continuing Education (CE) programme and ISACA requires ongoing CPE, so an actively maintained credential can say "Active — maintained via CompTIA CE" or simply carry a current validity date.
- Credentials with no stated expiry. Just the issue date is fine.
If a credential has lapsed, the wording rules change entirely — that case has its own traps, and we cover them in how to list an expired certification rather than here.
Credential IDs and verification links
Most major providers operate verification systems that let an employer confirm a credential, and many issue a credential ID, a verification URL or a digital badge. On a resume:
- Include the ID or link when you have one. It costs one line and pre-answers the verification question.
- Prefer a short "Credential ID: XXXX" over a long pasted URL on a printed or PDF resume; put the full verification link on your LinkedIn profile instead — here is how to add a certification to LinkedIn properly.
- Never approximate an ID. A wrong ID is worse than none, because it fails the check a correct one would have passed. How the checking actually happens on the employer's side is its own topic — see how employers verify certifications.
How to list an in-progress certification honestly
Listing a certification you have not yet earned is legitimate — if the wording makes the status unmistakable. The line between ambition and misrepresentation is the verb.
Safe, standard wordings:
- CompTIA Security+ (SY0-701) — in progress, exam scheduled November 2026
- AWS Certified Solutions Architect – Associate — candidate, expected Q1 2027
- Currently preparing for the CISA exam (registered with ISACA)
Wordings to avoid:
- Listing the bare credential name with no status, hoping nobody asks.
- "Pursuing CISSP" when you have not registered and do not yet meet ISC2's five-year experience requirement — anyone in security hiring knows that prerequisite exists.
- "Expected" dates you have no realistic plan behind.
Two practical rules keep this honest. First, only list an in-progress certification when you have taken a concrete step — booked the exam, registered with the provider, or completed the required training. Second, be interview-ready for the obvious follow-up: "how is the study going?" A useful way to make sure your stated timeline is real is to benchmark yourself against the exam objectives — working through free sample questions for your exam shows you quickly whether "exam scheduled November" is a claim you can stand behind.
Separate the statuses visually, too: a sub-heading such as "In progress" under your certifications section, or an italicised status note, prevents any accidental blending of earned and pending credentials.
Writing entries an applicant tracking system can read
Applicant tracking systems parse resumes into structured data before a human sees them, and ornate formatting is where certification entries go to die. Keep the section machine-readable:
- Use a clearly labelled heading — "Certifications" or "Licences & Certifications". Cute alternatives ("Badges of Honour") may not be recognised as a credentials section.
- Plain text beats graphics. Badge images, icons and logos are invisible to text parsing. If you earned a digital badge, link it; do not paste the picture in place of the words.
- Avoid tables and multi-column layouts for this section; parsers frequently scramble them.
- Mirror the job advert's terminology. If the advert says "Certified Information Systems Auditor (CISA)", your entry should contain both forms.
Keyword matching is a deeper game than formatting alone — the tactics for getting credentials past automated screens are covered in certifications and applicant tracking systems.
Worked example: a before and after
Before (real problems, condensed):
CERTS: Sec+, AWS, working on cissp
Three credentials, zero searchable names, no dates, no issuers, and an in-progress credential indistinguishable from earned ones.
After:
Certifications CompTIA Security+ (SY0-701) — CompTIA · Issued Feb 2026 · Credential ID: COMP00987 AWS Certified Cloud Practitioner (CLF-C02) — Amazon Web Services · Issued Sep 2025 · Valid to Sep 2028 In progress: Certified Information Systems Security Professional (CISSP) — ISC2 · exam scheduled Jan 2027
Same person, same achievements — but now every credential is searchable, dated, attributable and verifiable, and the pending one is honestly framed.
- Inconsistent entry formats — one line with dates, the next without; it reads as careless in a section that is meant to signal rigour.
- Burying certifications only in job bullets. Mentioning a credential inside a role description is good reinforcement, but recruiters scan for a dedicated section; use both.
- Listing training courses as certifications. A completion certificate for a video course is not a proctored credential; mixing them dilutes the real ones. If in doubt, a "Professional development" sub-section keeps them separate.
- Stale exam codes. Referencing a superseded version when you hold the current one undersells you.
- Overstuffing. Ten entries where three are relevant is a curation problem, not a formatting one — that judgement call belongs to how many certifications should be on your resume.
Frequently asked questions
Should I put letters after my name instead of a certifications section?
You can do both for genuinely senior credentials ("Jane Okafor, CISSP") — but the dedicated section should still exist, because that is where parsers and recruiters look for the full, dated, verifiable entry.
Do I list the training course and the certification separately?
List the certification. Add the course only if it is notable in its own right and clearly labelled as training, not as a credential.
How do I format a certification with two exams, like CompTIA A+?
List the credential once — "CompTIA A+ (220-1201/220-1202) — CompTIA, Issued 2026" — not as two separate entries. The credential is one certification earned through two exams.
Should I include scores?
No. Providers report scaled scores that employers are not equipped to compare, and passing is the credential. The exception is a formal distinction the provider itself awards.
A five-point check before you hit send
Run every entry through this: official name copied exactly, with the abbreviation; issuer named; issue date (and validity where relevant); credential ID or verification route; status honest for anything not yet earned. If all five hold and the whole section uses one consistent format, your certifications will survive both the software pass and the human one. And if writing the entry for a scheduled exam has reminded you the exam itself still needs passing, a timed practice test is a sensible way to check the date you printed is one you will keep.