How to Document Experience for Certification Applications

The most common reason a qualified candidate struggles with a certification application is not a shortage of experience — it is that eight years of real work exists nowhere on paper in the shape the form demands. PMI wants your history sliced into projects with month counts; ISC2 wants it mapped onto exam domains and vouched for by another certified professional. The work of documentation is translation: turning what you actually did into the structure the certification body reads.

This guide covers exactly that — how to record and evidence experience on the application itself, assuming you already know your experience qualifies. If you are still working out whether your background meets the bar in the first place, start with how professional experience counts toward certification, which explains how bodies define and measure qualifying experience.

Start from records, not memory

Before typing anything into a portal, rebuild your history from artefacts. Memory compresses and rounds; application reviewers and auditors want dates, durations and named organisations that survive checking.

Assemble, for each role you intend to cite:

1. Employment dates — from contracts, offer letters, payslips or your HR system, not from your CV (CVs round to years; applications usually want months).
2. Project or engagement dates — from project charters, tickets, release notes, statements of work or old calendars.
3. Named contacts — a manager, sponsor or client per project who could confirm your involvement if the certification body asks.
4. Your actual responsibilities — pull real language from performance reviews, job descriptions and project documents rather than inventing it retrospectively.

This evidence file never gets uploaded with most applications — PMI's and ISC2's forms are self-declared — but it is what you draw every entry from, and it is what saves you if your application is selected for verification. A fuller pre-submission checklist of documents and decisions sits in how to prepare a certification application.

Writing PMP experience descriptions that hold up

PMI's Project Management Professional (PMP) application asks you to evidence months of experience leading projects — 36 months alongside a four-year degree, or 60 months with a secondary diploma or associate degree, plus 35 contact hours of project management education (a Certified Associate in Project Management, CAPM, satisfies the education requirement). You document this as a series of project entries.

Structure each project entry

For every project, the form expects the basics — organisation, your role, dates, and a description of what you did. A description format that reviewers can process quickly:

• One sentence of context: the project's objective and rough scale ("Led a 9-month CRM migration for a 40-person sales organisation").
• Your responsibilities across the project's life, phrased as project-leadership work: initiating, planning, executing, monitoring and closing activities. Use active verbs — led, planned, managed, coordinated, delivered — attached to concrete work.
• One sentence on the outcome: delivered scope, dates met, or the state at handover.

Keep each description tight and factual. Padding with generic methodology language ("utilised best-practice frameworks to synergise stakeholder value") reads as evasive; specific, plain statements of what you personally directed read as credible.

Handle the traps

• You do not need the title "project manager". Leading and directing project work counts regardless of what your business card said; describe the leadership work, and let your actual job title stand as it was. Never inflate a title — your named contact may be asked about it.
• Count months honestly. Follow PMI's current counting rules on overlapping projects as stated in the application itself rather than assuming parallel projects each count in full — and when in doubt, cite more calendar span than you strictly need so an interpretation difference cannot sink you.
• Stay inside the experience window. PMI's eligibility paths look at recent experience; anchor your entries in your most recent qualifying years rather than reaching back to your oldest projects.
• Match the education line to a real certificate. The 35 contact hours must correspond to a course you can evidence with a completion certificate naming the provider, dates and hours.

A realistic example: a service-delivery lead with a four-year degree needs 36 months. Rather than one sprawling entry ("various IT projects, 2021–2025"), she documents four entries — an office relocation (7 months), two system rollouts (11 and 9 months) and a vendor transition (10 months) — each with organisation, sponsor contact, dates and a three-part description. Thirty-seven documented months, four checkable references, no rounding.

Documenting experience for CISSP endorsement

ISC2 sequences things differently: for the Certified Information Systems Security Professional (CISSP), the full experience documentation happens at endorsement, after you pass the exam. You have nine months from passing to submit an endorsement application vouched for by an ISC2-certified professional in good standing — or by ISC2 itself, with employment verification, if you do not know one.

What you are evidencing: five years of cumulative, paid, full-time work experience in at least two of the eight CISSP domains. Document it with the same discipline as a PMP entry, plus three ISC2-specific angles:

• Map roles to domains explicitly. For each position, note which of the eight domains your work touched — a security operations role might map to Security Operations plus Identity and Access Management. Your endorser is attesting to a domain-shaped claim, so hand them a domain-shaped record.
• Count part-time and internships correctly. ISC2 counts part-time work pro rata (for 20–34 hours per week, 1,040 hours equates to six months and 2,080 hours to twelve) and accepts documented internships, paid or unpaid. If you rely on either, keep the hours arithmetic and any internship documentation in your evidence file.
• Record any waiver you claim. A maximum of one year can be waived via a relevant degree or an approved credential (CompTIA Security+, Certified Information Security Manager and others on ISC2's list) — one waiver only. Note which you used and keep the certificate or transcript.

Give your endorser everything they need to attest confidently: a dated role history with domain mappings and employer names. ISC2 conducts random audits of applications, so every claim should trace back to something a former employer could confirm. Candidates short of the five years can still pass the exam and become an Associate of ISC2, with six years to accumulate the experience — the documentation habits above apply just as well while you accrue it.