PMP Certification Experience Requirements

You do not need "project manager" printed on a business card to qualify for the Project Management Professional (PMP) certification. The Project Management Institute (PMI) asks for months spent leading projects, not months spent holding a particular job title — and that distinction is the single biggest source of confusion, under-claiming and over-claiming on PMP applications.

One caveat before you start counting: PMI announced "expanded eligibility pathways" alongside the exam refresh that went live on 9 July 2026, so treat the two classic paths above as the baseline and confirm the current wording on pmi.org before you submit.

What actually counts as project management experience?

Experience counts when you were leading and directing project work — planning it, coordinating the people doing it, managing its risks, budget or schedule, or closing it out — on an initiative with a defined start, end and outcome. You did not need to own the whole project, and you did not need the title. A team lead who ran a system migration, a nurse who coordinated a ward accreditation effort, or an engineer who managed a product launch workstream can all have qualifying months.

A project, for PMI's purposes, is temporary work that produces a unique result. That's the test to apply to your own history:

• Likely counts: leading a software rollout, coordinating an office relocation, managing a marketing campaign launch, running a construction phase, directing a compliance remediation effort, managing a curriculum redesign.
• Doesn't count: business-as-usual operations — routine support tickets, ongoing maintenance, repeating monthly reporting, day-to-day people management with no defined deliverable or end date.

The grey zone is roles that mix both. If 30% of your operations job was spent leading a defined improvement project, the months you spent on that project can count — describe the project, not the job.

Do internal, unpaid or part-time projects count?

Professional experience is what PMI is assessing, and it does not have to come from a role labelled "project management". What matters is that you can honestly describe project leadership responsibilities within a defined initiative. If you are unsure whether a specific engagement qualifies — volunteer work, academic projects, part-time roles — check PMI's current certification handbook and application guidance on pmi.org rather than guessing, because the safe applications are the ones built on work you can document and a supervisor can corroborate.

How PMI counts your months

Two mechanics trip people up more than anything else.

1. Months are counted per calendar month, non-overlapping. If you led two projects simultaneously from January to June, that is six months of experience, not twelve. You cannot double-count a month no matter how many projects it contained.
2. You count months in which you performed project leadership work, not the total elapsed duration of your employment. A three-year job where you led projects for roughly half the time contributes the project months, not 36.

A worked example. A business analyst with a bachelor's degree has this history:

• Project A: CRM implementation, Jan 2023 – Oct 2023 (10 months)
• Project B: data migration, Jul 2023 – Mar 2024 (9 months)
• Project C: reporting platform build, Jun 2024 – Aug 2025 (15 months)

Projects A and B overlap from July to October 2023. Counting each calendar month once: Jan 2023 – Mar 2024 is 15 months, plus Jun 2024 – Aug 2025 is another 15. Total: 30 non-overlapping months. With a four-year degree the target is 36, so this candidate needs roughly six more months of project work before applying — useful to know before paying the exam fee, not after.

Build this tally in a spreadsheet first: one row per project, with start month, end month, your role, and the overlaps struck out. It takes an hour and it is the difference between an application you're confident in and one you're hoping about.

How to describe each project on the application

The application asks you to summarise each project you're claiming. Strong descriptions share three traits.

Lead with your responsibilities, not the project's. "The project delivered a new warehouse system" says nothing about you. "Led a team of six to deliver a new warehouse system: built the schedule, managed vendor risk, ran stakeholder reviews and closed out lessons learned" claims specific project leadership work.

Cover the life cycle where you genuinely touched it. PMI wants to see experience leading project work across initiating, planning, executing, monitoring and closing — not necessarily all five on every project, but across your portfolio as a whole. Spread your descriptions so that, taken together, they show the full arc.

Write in first-person, active, plain language. "Developed the project plan and budget; coordinated three delivery teams; managed scope changes through a formal change process; delivered the platform and handed over to operations." No jargon inflation, no borrowed accomplishments.

Experience description examples

Weak: "Worked on a large ERP programme for a retail client. The programme was very complex with many stakeholders."

Stronger: "Managed the finance workstream of an ERP implementation (8 team members, 11 months). Planned the workstream schedule and milestones; ran weekly risk reviews; managed UAT defect triage with the vendor; led cutover planning and post-go-live stabilisation."

The stronger version would let a reviewer — or your named supervisor — recognise the work immediately, which matters if your application is selected for audit.