The PMP Application Checklist

Why this checklist exists

The PMP exam is hard. Most candidates assume the exam is the only obstacle. It isn't.

The application itself is where most candidates get stuck:

• PMI typically reviews submitted applications in 1–2 weeks (5–10 business days). Add 2–4 weeks if you're randomly selected for audit. Either way, the application must clear before you can schedule the exam.
• PMI doesn't publish its audit rate; prep-provider estimates put it at roughly 5–10%, with random selection being the dominant mechanism
• Many prep experts who review applications commercially report that the most common rejection isn't lack of experience, it's how the application was written. PMI does not publish a breakdown of rejection reasons.

If you're trying to test before the July 9, 2026 exam change, the application is the bottleneck, not your study time. This checklist walks you through it.

Part 2: The 35 contact-hour requirement

The most-misunderstood part of the application.

PMI requires 35 hours of formal project management education before you apply. This is not the same as your work experience.

What counts

What does NOT count

How to document

PMI doesn't ask for proof when you submit, but if you're audited, they'll request:

• Certificate of completion for each course
• Course title, date completed, total hours
• Provider name (must be a real entity)

Action item: before applying, list every PM-related training you've completed in the last 5 years with dates and hours. If you're under 35, take a class to fill the gap.

Part 3: The 8-step application process

Step 1: Create your PMI account

Go to pmi.org/certifications/become-a-project-management-professional-pmp and click "Apply Now." Free to create the account; payment comes later.

Tip: Use a personal email, not work. Your PMI account is yours forever and outlives any one job.

Step 2: Fill your contact + education info

Straightforward. Use your legal name (it appears on your cert).

Step 3: Document your experience

This is the section that takes the most time and rejects the most applications. We'll cover the writing approach in Part 4.

You'll list each "project" you led, with:

• Project title and brief description
• Your role (Project Manager, Scrum Master, Lead, etc.)
• Start and end dates
• Total hours by knowledge area (Initiating, Planning, Executing, Monitoring & Controlling, Closing)
• Project verifier (someone who can confirm your role if PMI calls)

Critical: the experience descriptions are what reviewers actually read. See Part 4.

Step 4: Document your 35 contact hours

List each course, conference, or training you've completed. You'll provide:

• Course/training name
• Provider
• Date completed
• Hours

Step 5: Submit the application

Click submit. You'll see a confirmation. Now you wait.

Step 6: PMI review (1–2 weeks)

PMI typically reviews applications within 1–2 weeks (5–10 business days). You'll get one of three responses:

• Approved. Proceed to Step 7.
• Audited (random selection). See Part 5 below.
• Application clarification needed. Usually fixable; address the request and resubmit.

Step 7: Pay the exam fee

• PMI member: $425
• Non-member: $595 (increases to $675 on 2026-08-06)
• PMI membership: $154/year ongoing renewal, $164 for first-year new members (includes a one-time $10 application fee). Membership saves you $170 on the exam fee, so it pays for itself the first time you take the exam.

Most candidates join PMI to get the member rate.

Step 8: Schedule the exam

Once paid, you have 1 year to take the exam. You can attempt the exam up to 3 times total within that 1-year window. The first attempt is included in your application/exam fee; retake fees apply for attempts 2 and 3. Most testing is done online via Pearson VUE (or in-person at a testing center).

Pro tip: schedule the exam immediately after paying, even if the date is months out. Having a date locked in motivates study.

Part 4: Writing experience descriptions that get approved

This is the #1 reason applications get rejected or held up.

Reviewers spend ~10 minutes reading your descriptions. They're looking for specific signals.

What reviewers WANT to see

A good experience entry covers three things:

1. Project context. What was the project, what was the goal, what was at stake?
2. Your specific role. What did YOU do? Not what the team did. What were you accountable for?
3. Concrete deliverables. What did you produce, decide, deliver, or own?

Bad description (gets pulled for review)

"Managed a software development project for a financial services company. Worked with team to deliver on time and on budget. Used Agile methodology."

Problems: No specifics, no your-role detail, no deliverables, no scope.

Good description (gets approved)

"Led a 6-month software development project for a regional bank's customer onboarding portal. $1.2M budget, team of 8 (6 developers, 1 designer, 1 QA). Owned project planning, sprint cadence, stakeholder communication, and risk management. Delivered the portal 3 weeks early; reduced customer onboarding time from 5 days to 4 hours. Coordinated weekly with VP Operations and the bank's compliance team. Used hybrid Scrum + Waterfall approach (Scrum for development, milestone-based for compliance review)."

Why it works:

• Specific scope (budget, team size, duration)
• Concrete deliverable (the portal) and outcome (5 days → 4 hours)
• Clear ownership (your role explicitly named)
• Stakeholder visibility (named who you worked with)
• Methodology grounded in real process

Template structure to follow

Led [project name]. [scope: budget, team size, duration].
Owned [3–5 specific responsibilities].
Delivered [concrete output] resulting in [measurable outcome].
Coordinated with [stakeholders/sponsors].
Used [methodology] with [adaptations for the context].

Knowledge-area hour allocation

For each project, you allocate hours to PMI's knowledge areas (Initiating, Planning, Executing, Monitoring & Controlling, Closing). Two rules:

1. The math has to work: total hours per project should approximately equal months × ~160 hours/month (assuming part-time PM work). If your numbers are wildly off, you'll get audited.
2. Distribution should be realistic: Planning + Executing usually dominate. Initiating + Closing are smaller. Monitoring & Controlling runs alongside Executing.

Typical realistic distribution for a 6-month project:

• Initiating: ~5%
• Planning: ~25%
• Executing: ~40%
• Monitoring & Controlling: ~25%
• Closing: ~5%