PMP Application 2026: Step-by-Step with Project Description Samples

I have walked candidates through the PMP application form more times than I can count, and I will tell you the truth: the application is harder than most people realise. Not technically harder. The PMI portal is straightforward. But the project description section is where 30% of applicants get rejected or audited, and almost always because they wrote their experience the way they would write a CV bullet point instead of the way PMI wants to read it.

The application is a gatekeeper. PMI is checking whether you have actually led projects, whether you understand the language of project management, and whether you can articulate the problem, your approach, your role, and the deliverable in PMI's preferred verbs. If you write "I managed a team to deliver a website," you are likely to be audited. If you write "I led a cross-functional team of 8 in initiating, planning, and executing the redesign of a customer-facing e-commerce platform to address declining conversion rates, resulting in a 22% lift in checkout completion within 60 days of go-live," you are likely to be approved without question.

This guide walks you through every step of the 2026 application portal, the rules of writing PMI-compliant project descriptions, four full sample descriptions across industries, what triggers an audit, and a 90-day timeline from your first portal click to your scheduled exam date.

Before you touch the portal, confirm you actually qualify. As of 2026, PMI requires:

Path A: Four-year degree (bachelor's or equivalent)

•  36 months of project leadership experience within the last 8 years
•  35 hours of project management education

Path B: High school diploma, associate degree, or equivalent

• 60 months of project leadership experience within the last 8 years
• 35 hours of project management education

The 35 contact hours can come from any PMI-authorised training provider, an accredited university programme, or company training programmes that map to PMI's learning objectives. Free YouTube content does not count.

"Project leadership experience" means you were leading and directing projects, not assisting on them. You do not need to have held a "Project Manager" title. You do need to have made initiation, planning, execution, monitoring, controlling, or closing decisions. I have signed off on applications for engineers, marketing leads, operations managers, and HR business partners. Title does not matter; demonstrated leadership does.

In my experience, candidates who prepare these materials before opening the application save themselves about 8-10 hours of confused rework:

• A complete list of every project you might claim, including:
• Project title and short description
• Start and end dates (month and year)
• Your role
• Project deliverable
• Contact person willing to verify (usually a manager or sponsor)
• Your 35 contact hours certificate(s) - PDF or screenshots
• Your degree certificate or transcript
• A clean version of your CV for cross-referencing
• A working email address linked to your PMI account (use a personal one, not a corporate one - corporate inboxes are unreliable)

The biggest mistake I see: candidates open the portal cold and try to type their experience from memory. They miss projects, write inconsistent dates, and trigger audits. Spend an evening getting your materials together before you start.

If you do not already have a PMI account, create one at pmi.org. You will need:

• Full legal name (this MUST match your government-issued ID)
• Email and password
• Country and language preference

I tell candidates to also become a PMI member at this stage. Membership is GBP 110 for the first year (plus a one-time GBP 8 application fee), but it saves you GBP 130 on the exam fee. Membership pays for itself with one exam attempt. Plus you get free access to PMBOK guides, the Agile Practice Guide, and a steady stream of PDU opportunities for renewal later.

Once your profile is set up, log in and click "Apply for PMP."

The education section asks for:

• Highest degree completed
• Institution name
• Country
• Programme/major
• Dates attended

For the 35 contact hours, you list the training provider, course name, dates, and hours. If you took an online course from a PMI Authorised Training Partner (ATP), you should have received a certificate with the course code and hours breakdown. Upload that or have it ready for the audit step.

Common mistake: candidates list hours from multiple courses but the total falls short. Double-check that your hours add to 35 or more. If you fall short, you cannot proceed.

Another mistake: listing a degree you have not yet received. PMI accepts in-progress degrees only with documentation. If you are mid-degree, list your current education status and check the relevant box.

This is the section that takes 80% of the application time and causes 90% of the audits.

You will be asked to add projects one at a time. For each project, you provide:

• Project title
• Organisation (you can mark this private if needed)
• Your role
• Project dates (start and end)
• Hours led on this project
• Contact person (name, email, phone) for verification
• A project description (200-500 characters)

PMI calculates your total project leadership hours and months from these entries. You need 4,500 hours (path A) or 7,500 hours (path B) of leadership experience, accumulated across 36 or 60 months respectively. Critical: the same calendar months across multiple projects only count once. If you led two projects in parallel in March 2024, that is still one month, not two.

The portal does the month math for you. The hours math also gets calculated; you do not need to specifically hit 4,500. Just enter accurate hours per project.

PMI suggests selecting projects that span the five process groups (initiating, planning, executing, monitoring/controlling, closing). You do not need every project to cover all five, but your portfolio of projects together should.

Once you have entered enough experience, you submit and pay.

2026 fees:
 

Pay by card. PMI then takes 5-10 business days to review your application. Most non-audit applications are approved within 5 days. If you are audited, the review can take 4-6 weeks (more on this below).

You will receive an email confirming approval. That email contains your authorisation to test (eligibility ID), which is what you use to schedule the exam.

Once approved, you have 12 months to schedule and sit the exam, with up to three attempts in that window. You schedule via Pearson VUE, which is integrated into the PMI portal.

Options:

• In-person at a Pearson VUE test centre. I recommend this for most candidates. Stable environment, fewer technical surprises.
• Online proctored at home. Convenient but requires a quiet room, a clear desk, a working webcam and microphone, and patience with the proctor process. Failures of online attempts (technical, not academic) are higher than they should be.

Book at least 2-4 weeks ahead. Some test centres in busy cities book out 6 weeks in advance.

I tell candidates: schedule the exam as soon as you are approved, even if you are not feeling ready. Having a date on the calendar focuses the mind. You can reschedule once for free up to 30 days before the exam.

This is where most candidates lose points. PMI's reviewers read thousands of applications per month. They are scanning for a specific structure:

1. Problem or business need - What was the project trying to solve?
2. Approach - How did you tackle it (predictive, adaptive, hybrid)?
3. Your role - What did you lead and direct?
4. Deliverable - What did the project produce or achieve?

If you cover all four, in PMI language, you sail through. If you skip one, you are at audit risk. If you write in fluffy CV language ("collaborated with stakeholders to drive success"), you are nearly guaranteed an audit.

Word count matters. PMI gives you 200-500 characters per project. That is roughly 30-80 words. Tight, dense, action-led writing wins.

The reviewer is asking two questions: "Did this person actually lead a project?" and "Do they know what project management vocabulary sounds like?" Answer both with your description.

PMI has a preferred verb vocabulary. Use it. Reviewers recognise it instantly.

A good description weaves three or four of these verbs into a single tight sentence. Use the five process groups (initiating, planning, executing, monitoring/controlling, closing) explicitly where they apply.

Also: use specific, quantified outcomes. "Resulting in a 22% lift in checkout completion" is stronger than "improving the customer experience." Quantification signals real project work.

Project Title: E-Commerce Platform Redesign
Role: Senior Project Manager (Lead)
Dates: March 2023 - November 2023
Hours: 1,200

Description (478 characters):

Led the initiation, planning, execution, monitoring, and closing of a six-month redesign of the company's e-commerce platform to address a 14% decline in checkout completion. Directed a cross-functional team of 8 across engineering, design, and analytics using a hybrid Scrum-Waterfall approach. Managed scope, schedule, and a GBP 480,000 budget. Facilitated stakeholder alignment across marketing and product. Delivered a redesigned checkout flow that increased completion by 22% within 60 days of release.

Why this works:

• Four of five process groups named
• Hybrid approach explicitly identified
• Team size and budget quantified
• Outcome quantified with specific business metric
• PMI verbs throughout (led, directed, managed, facilitated, delivered)

Project Title: Office Refurbishment - 3-Floor HQ
Role: Construction Project Manager
Dates: January 2024 - August 2024
Hours: 1,400

Description (492 characters):

Initiated, planned, executed, and closed the refurbishment of three floors (4,800 sq m) of the corporate HQ to support a 35% headcount expansion. Directed a team of 14 across architecture, MEP engineering, and trade contractors. Managed a GBP 2.1M budget under predictive delivery with weekly earned value reporting. Coordinated procurement of long-lead furniture and AV systems. Resolved scope conflicts between facilities and IT stakeholders. Delivered the space three days ahead of schedule and 1.4% under budget.

Why this works:

• Clear scope (3 floors, 4,800 sq m)
• Predictive approach explicitly named
• Budget and team quantified
• EVM mentioned, signalling PM literacy
• Stakeholder conflict resolution called out
• Outcome quantified against schedule and budget

Project Title: Global Brand Campaign Launch
Role: Programme Manager
Dates: September 2023 - February 2024
Hours: 900

Description (484 characters):

Led the planning, execution, and closing of a six-month integrated brand campaign across 12 markets to support the launch of a new product line. Directed a virtual team of 18 across creative agencies, media buyers, regional marketing leads, and PR. Managed a GBP 1.8M budget and tailored an adaptive approach to allow rapid creative iteration. Facilitated weekly cross-market stand-ups and risk reviews. Resolved escalations across two underperforming markets. Delivered campaigns on time across all 12 markets, generating a 31% increase in qualified leads.

Why this works:

• Programme-scale leadership signalled
• Distributed/virtual team explicit
• Adaptive approach named with tailoring
• Risk management language present
• Outcome quantified with business metric

Project Title: Electronic Health Record Rollout - Regional Hospital
Role: Project Manager (Clinical Systems)
Dates: April 2022 - May 2023
Hours: 2,100

Description (495 characters):

Led the initiation, planning, execution, monitoring, and closing of a 13-month rollout of a new EHR system across a 380-bed regional hospital, replacing four legacy systems. Directed a team of 22 across clinical informatics, IT, training, and change management. Managed a GBP 3.6M budget under hybrid delivery, with predictive infrastructure workstreams and adaptive clinical configuration workstreams. Facilitated weekly governance with the medical director and CIO. Resolved data migration risks and clinician workflow concerns. Delivered go-live on schedule with 96% clinician sign-off in week one.

Why this works:

• Scale of organisation specified (380 beds)
• Replacing-legacy-systems context shows complexity
• Hybrid approach with explicit workstream split
• Governance and stakeholder management specific
• Outcome quantified with adoption metric
   

PMI audits about 10-15% of applications randomly, plus a higher rate for applications that flag certain red flags. Triggers I have observed:

• Vague project descriptions ("worked on multiple projects")
• Round-number hours (1,000, 2,000 on every project)
• Identical contact person across many projects
• Hours that exceed reasonable working capacity (over 2,500 per year)
• Mismatched dates (overlapping projects with overlapping hour totals)
• Job title that does not obviously include project leadership

If audited, you have 90 days to provide:

• Signed verification from each project's contact person
• Your degree certificate (original or attested copy)
• Your 35 contact hours certificate

PMI sends a form to each of your project contacts asking them to confirm your role and dates. If a contact does not respond, that project may be disqualified.

How to survive an audit:

1. Warn your contacts in advance. Send them a friendly note saying you are applying for PMP and they may receive a verification request. Include the dates and your role to refresh their memory.
2. Keep your project descriptions truthful and aligned with what the contact will remember.
3. Have your documents ready as PDFs, named clearly.
4. Respond fast. Do not waste the 90-day window.

Audits are not punitive. PMI is verifying, not accusing. If your application is accurate, you will be approved at the end of the audit.

In my coaching, the most common rejection reasons:

1. Insufficient leadership hours. Candidate counted assistant or support-role work as leadership. PMI rejects.
2. Project descriptions are CV bullets, not PMI descriptions."Managed the website project" without process group language.
3. Contact hours short of 35.Counted a 20-hour course twice or included non-qualifying training.
4. Education credentials unverifiable. No transcript, foreign degree without translation.
5. Overlapping hours that exceed plausibility. Claimed 2,000 hours in a year where also reporting full-time non-PM employment.
6. Misrepresented role. Listed as "project manager" but contact says "team member."

If rejected, PMI tells you why and gives you a chance to revise. Read the feedback carefully and submit a corrected application within the window.

Here is the timeline I give to candidates from first portal click to scheduled exam date:

This is a moderate, realistic timeline for a working professional. You can compress to 60 days if you are between roles or have intensive evenings, but I have rarely seen candidates pass who compressed below 45 days. The application alone, with audit risk, can take 4 weeks.