PMP Eligibility Requirements 2026: Experience, Education & Hours

When candidates first approach me about the PMP, the conversation almost never starts with the exam. It starts with eligibility. They want to know if their seven years of mixed contributor-and-lead work counts. They want to know if their diploma from a polytechnic disqualifies them. They want to know whether the project they ran for a non-profit in 2017 still falls inside PMI's rolling window. I get it - the application is the first real gate, and it is also where most rejected applications go wrong.

I have walked dozens of candidates through this process, and the pattern is consistent: the eligibility rules sound simple on the PMI website but the edges are sharp. Overlap rules, definition of "leading and directing", the 10-year experience window, the difference between a contact hour and a billable hour - these are where applications stall or trigger an audit. In this guide I will go through every requirement in detail, explain how I tell PMs to interpret each clause, and give you a workable approach to documenting your experience so that the application sails through on the first attempt.

This article focuses strictly on 2026 eligibility, including the rules that PMI has carried forward from the most recent handbook revisions. If you are starting from zero and just want to know whether you qualify today, read the next section first and circle back to the documentation guidance at the end.

PMI offers two routes to PMP eligibility. The path you take depends on your highest completed qualification, and the requirements scale inversely - less formal education means more hands-on experience. Both routes require the same 35 contact hours of project management education and the same exam.

In my experience, roughly four out of five Indian and Western European candidates qualify through Path A because higher education completion rates are high in those markets. Path B is common in the United States skilled trades, in operations roles in manufacturing, and among self-taught professionals who moved into project management from technical specialisms.

A practical note - PMI does not require your bachelor's degree to be in a project management or business field. An engineering degree, a humanities degree or a sciences degree all qualify equally. The same is true for postgraduate degrees, although PMI does not currently offer a third reduced-experience tier for master's holders.

PMI uses the phrase "four-year degree" but accepts global equivalents. This matters because degree structures vary widely. A three-year UK undergraduate degree is accepted as a global equivalent of a four-year US degree provided it is conferred by a recognised institution. An Indian B.E. or B.Tech of four years qualifies clearly. A three-year Bachelor of Commerce from an Indian university generally qualifies as a global equivalent under PMI's rules, although I have seen audits where additional verification was requested.

What I tell PMs is to take the most defensible position. If you have a three-year bachelor's plus a recognised postgraduate qualification, list the postgraduate qualification as your highest. If you only have a three-year degree, list it and be ready to provide the transcripts and the institution's accreditation details if audited.

The secondary diploma route is unambiguous - a US high school diploma, a UK A-level certificate, an Indian Class 12 board certificate, or any equivalent secondary leaving certificate all qualify. Associate degrees from two-year US community colleges also fall under Path B, which sometimes confuses Indian candidates who assume an associate degree puts them on Path A. It does not.

A few qualifications I have seen rejected or pushed for clarification: incomplete bachelor's degrees, vocational diplomas without a formal academic component, online "degrees" from unaccredited mills, and bachelor's-equivalent titles from professional bodies. If in doubt, contact PMI's Customer Care before paying for the application.

The hours requirement is where most candidates get tangled up. PMI requires you to record actual hours spent leading and directing projects, not the calendar months you held a job title. This distinction matters because it forces an honest accounting.

Take a project manager who held the title for 36 months but spent 50% of her time on operational support work. Her relevant project hours are not 36 months times 160 hours - they are closer to 36 times 80 hours, or roughly 2,880 hours. That number is well below the 4,500 threshold for Path A and would force her to extend her experience window backwards or pick up additional project work.

For Path A you need 4,500 hours of leading and directing across at least 36 months. For Path B you need 7,500 hours across at least 60 months. PMI counts a typical full-time work month as roughly 160 hours, although they accept hour totals that reflect part-time work, consulting engagements with variable utilisation, and contractor billing patterns.

I recommend building a simple spreadsheet during your application prep. Columns for project name, your role, start date, end date, total hours, and an estimated split across the five process groups. You will reuse this directly in the application form.

The months requirement runs alongside the hours requirement. Even if you accumulate 4,500 hours of project work in 18 calendar months by working sixty-hour weeks across three concurrent projects, PMI still wants you to have spanned at least 36 unique calendar months under Path A or 60 under Path B.

The reason is straightforward - PMI is testing for breadth of experience as well as depth. A PM who only worked through two project lifecycles will not have seen the same variety of risks, stakeholder dynamics and procurement patterns as one who worked through five or six lifecycles. The months gate enforces that breadth.

The months are counted as unique calendar months. Two overlapping projects in March 2024 still count as one month of experience. This is the single most common misunderstanding I see. Candidates list every project they have run with full date ranges, then submit an application showing 96 months of "experience" when the unique-calendar-months total is actually 41. PMI's system catches this and either auto-flags or triggers a manual review.

Plan your project list so the unique calendar months total at least matches the requirement. If you are sitting at 33 unique months under Path A, you have a problem to solve before submitting - either find another qualifying project to add or wait three more months.

PMI requires all qualifying experience to fall within the last eight years from the date of your application. Earlier handbooks used a 10-year window. As of the most recent handbook revisions in force for 2026, the window is eight rolling years measured back from your submission date.

I have seen PMs make the mistake of including a flagship project they ran 11 years ago because it was their most impressive engagement. If it falls outside the window, it does not count. Period. Listing it anyway risks an audit and almost always results in PMI deducting the hours and pushing the applicant back to the drawing board.

The rolling nature of this window also means timing matters. If you have a critical project ending in three months that would tip you over the threshold, wait. If you have a project rolling out of the window in two months, submit now. Calendars matter.

This phrase is the most-debated clause in the PMP application handbook. PMI defines it as performing the activities of a project manager - planning, scheduling, leading the team, managing risk, controlling change, reporting status, managing stakeholders, closing out deliverables.

What does not count:

• Being a team member on a project, even a senior team member, unless you were also accountable for an end-to-end work package
• Pure subject matter expertise contribution, such as writing code or designing a circuit, without any     planning or coordination responsibility
• Operations or business-as-usual work that is repetitive and lacks a defined end state
• Programme oversight that consisted only of approvals and reporting without active project-level     leadership

What does count even when the title was not "Project Manager":

• Scrum Master, Iteration Manager, Delivery Lead, Engagement Manager, Solution Lead, Workstream Lead,  Programme Coordinator
• Technical leadership of a defined deliverable inside a larger programme, where you owned the planning, execution and closure
• Functional team leadership during a clearly time-boxed initiative such as a migration or product launch
• Volunteer project leadership for non-profits, provided you can demonstrate full project lifecycle    responsibility

In my experience, the line is whether you owned outcomes against a plan. If you did, claim the hours. If you only contributed to outcomes that someone else owned, do not claim them.

Concurrent projects are normal in consulting, in IT services and increasingly in agile delivery organisations. PMI allows you to claim hours from overlapping projects, but the rules require careful application.

Example - During Q2 2024 I led Project Alpha (ERP rollout, 60% of my time, 96 hours per month) and Project Beta (customer portal, 40% of my time, 64 hours per month). For the three-month overlap, I claim 288 hours on Alpha and 192 hours on Beta. The calendar months Apr-May-Jun count once each toward the 36-month gate.

The two principles to remember are these. First, hours are additive across projects in the same period, provided your time split is honest and adds up to no more than full-time effort. Second, calendar months are unique across all projects - you cannot triple-count the same March because three projects were active.

A subtle point - PMI does not require you to itemise exact percentages in the application form for every project. They require you to record the project hours and the start and end dates. The auditor, if you are picked, will reconstruct your utilisation from your project descriptions and dates. Keep the underlying spreadsheet so you can defend the numbers.

Separate from experience, PMI requires 35 contact hours of formal project management education. This requirement is identical across Path A and Path B. The hours must focus on project management content - generic leadership courses or technical skills courses do not count.

What counts:

• A structured PMP exam prep course from a PMI Authorised Training Partner
• University courses in project management completed any time before the application
• Non-PMI training courses from established providers, provided the content maps to project management knowledge
• Employer-led internal training programmes if they cover project management topics and you can document hours

What does not count:

• Self-study from books, even PMI publications
• Conference attendance without structured instruction
• Free YouTube content
• Webinars under one hour each that do not aggregate into a structured course

A few practical points. The 35 hours do not expire - a course you completed in 2018 still counts in 2026. You can stack multiple courses to reach 35 hours. The course must produce a certificate of completion with your name, the provider's name, the course title and the hour count. Save these PDFs in a dedicated folder before applying.

PMI accepts contact hours from a wide range of providers. The safest bet is an Authorised Training Partner (ATP) because PMI vouches for ATP-issued certificates. Outside the ATP network, accredited universities, professional bodies and established corporate training providers are also widely accepted.

I generally tell PMs to choose a provider based on three criteria. First, the course must produce a clean certificate with the required information. Second, the content must align with the current PMP examination content outline - if the course is built around PMBOK 5, walk away. Third, the format must fit your study style. Live cohorts force discipline. Self-paced on-demand suits experienced PMs revising fundamentals.

Cost ranges widely. A self-paced online ATP course typically costs between USD 200 and USD 600. Instructor-led virtual cohorts run USD 800 to USD 2,000. Classroom programmes can exceed USD 3,000 in major markets. If you are budget-constrained, look at quality self-paced ATPs and supplement with practice question banks.

The application form asks you to list projects with the following fields for each: project title, organisation, your role, start and end dates, project hours, a description of the project objective and outcome, and your specific contribution. The description field has a character limit (currently around 500 characters) so concision matters.

What I recommend in the description:

• One sentence stating the project objective in business terms
• One sentence stating your role and accountability
• One or two sentences describing the work you led across initiation, planning, execution, monitoring and closing
• A closing sentence stating the outcome and any measurable result

Example description - Led the migration of 14 retail branches from legacy POS to a cloud platform. As project manager I owned planning, vendor coordination, stakeholder communication and rollout sequencing. Coordinated a cross-functional team of 11 across IT, store operations and finance through pilot, staged rollout and stabilisation. Delivered on plan with zero unplanned downtime during peak season.

Avoid jargon, abbreviations the auditor will not recognise, and any language that suggests you were a contributor rather than a leader. Use active verbs - led, planned, coordinated, managed, closed.

PMI audits a random subset of applications - the rate is not published but my estimate based on the candidates I have worked with sits around 8-12%. If you are audited, PMI gives you 90 days to respond with three things: signed verification from your education institution, signed verification from someone who can confirm your project experience for each project listed, and copies of your 35 contact hours certificates.

The experience verification is the hardest part. Each project requires a signature from a manager, sponsor or colleague who can attest that you held the role and hours you claimed. If your former managers have moved on, peers who worked alongside you on the project can sign. The form is short. The verifier does not need to be a PMP.

My advice - prepare for an audit as if you will be audited. Compile a folder per project containing the project description, your time records if available, and a short note identifying the verifier with current contact details. If you reach the audit step with this folder ready, you can respond in days rather than weeks. Most audit-driven application failures come from candidates who cannot locate verifiers in time.

For a deeper treatment of the audit step itself see PMP audit

A few candidate profiles deserve specific notes.

Career changers from non-PM roles. If you ran a clearly defined initiative inside an engineering, marketing or operations role and have documentation of your accountability, those hours count. The application does not require you to have held a PM job title. What it requires is that you led projects.

Consultants and contractors. Your projects often overlap and your utilisation varies. Document each engagement separately and reconstruct hours honestly. Do not round up. PMI auditors recognise consulting patterns and look favourably on accurate, conservative estimates.

Agile practitioners. Scrum Masters and Product Owners are PMI-qualifying roles when the underlying work is project-shaped (defined start, defined end, defined deliverables). A long-running product team with no end state is operations and does not qualify. A six-month feature programme led by a Product Owner inside a product team does qualify.

PMOs and Programme Coordinators. The line here is sharper. If you ran a portfolio dashboard, your role likely does not qualify. If you owned project plans, ran status meetings, managed risk logs and drove decisions, you likely do qualify. Frame the role accordingly in the application.

A list I have built up over the years of conversations with candidates whose applications stalled:

• Listing projects from outside the eight-year window
• Padding hours to hit the threshold instead of finding more projects to add
• Using the same generic project description for multiple engagements
• Failing to tally calendar months for uniqueness
• Listing contributor-level work as leadership
• Claiming contact hours from informal learning that lacks a certificate
• Submitting without verifying that bachelor's-equivalent claims will hold up
• Missing the 90-day audit response window

Every one of these is avoidable. The fix is process. Build the spreadsheet, build the audit folder, get your verifiers warm, and only then start the online application.

Here is the checklist I share with candidates the week before they start the application:

• Education evidence: degree certificate scan, transcripts if available, institution accreditation details
• Project list spreadsheet: project, role, dates, hours, process group split, verifier name and contact
• 35 contact hours: certificate(s) totalling at least 35 hours from an acceptable provider
• Calendar months total: unique months across all qualifying projects, verified to meet the path threshold
• Hours total: leading-and-directing hours summed across all projects, verified to meet the path threshold
• Window check: every project end date inside the eight-year window
• Verifier confirmation: each verifier contacted in advance and willing to confirm
• PMI account: created, profile complete
• Membership decision: PMI membership active if you want the lower exam fee
• Payment method: ready for the application fee

Once these items are green, the application form itself takes around two hours to fill in.

For the next step in the journey see PMP application process 2026 and pmp-certification-cost-2026.