Application

PMP® Application Professional Experience: What Changed and What Applicants Need to Know

By Alegria RegachoUpdated 17 July 20267 min read

A practical comparison based on forms observed on 9 July 2026. This article focuses specifically on Section 2: Professional Experience of the PMP® application — how to fill it out correctly. It does not cover the Education or Exam Details sections.

Important: The new experience form looks easier because it contains fewer fields. However, it may also be confusing — especially for applicants who assume they should enter their full employment period and copy their job description. Neither is correct, as explained below.

While supporting a PMP® aspirant on 9 July 2026, I noticed a significant change — not merely in the form's appearance, but particularly in how experience is entered. The previous form asked applicants to provide detailed project information through several separate fields. The new form is shorter and more streamlined.

What Changed?

The comparison below highlights the most visible differences between the previous and new PMP® application forms for the Professional Experience section.

New PMP application Professional Experience form showing Organization, Job Title, Experience Start and End Date, and Role Summary fields — The current Professional Experience form — Organization, Job Title, Experience Start/End Date, and a Role Summary (min. 100 / max. 500 words).

Previous PMP application Experience form showing Project Title, Organization, Job Title, Functional Reporting Area, Organization Primary Focus, Approach or Methodology, Project Team Size, Project Budget, Project Dates, and Project Description fields — The previous Experience form — included fields such as Project Title, Functional Reporting Area, Organization Primary Focus, Approach/Methodology, Project Team Size, and Project Budget.

Table 1 — Professional Experience Form: Previous vs. Current
Field	Previous Form	Current Form
Project Title	Required	Removed
Organization	Required	Required
Job Title	Required	Required
Functional Reporting Area	Required	Removed
Organization Primary Focus	Required	Removed
Approach / Methodology	Required	Removed
Project Team Size	Required	Removed
Project Budget	Required	Removed
Project / Experience Dates	Required (Start–Finish, non-overlapping)	Required (Start–End, non-overlapping)
"Currently in this role" option	Not present	Available
Description / Summary	Project Description (200–500 words: objective, outcome, role, responsibilities, deliverables)	Role Summary (100–500 words: role, contributions, outcomes)
Total experience required	36 months, non-overlapping, within past 10 years	36 months, non-overlapping, within past 10 years

Bottom line: The new form dropped six fields (Project Title, Functional Reporting Area, Organization Primary Focus, Approach/Methodology, Project Team Size, Project Budget) and merged the old “Project Description” into a shorter, more focused “Role Summary.” The 36-month, non-overlapping, 10-year eligibility rule has not changed.

What Aspirants Should Note — Field by Field

Here is what each field on the current Professional Experience form is actually asking for.

Field 1: Organization

Enter the name of the organization where you gained the project experience.

Field 2: Job Title

Enter your actual job title. It does not have to be “Project Manager” — it may be Project Engineer, Site Engineer, Construction Manager, Planning Engineer, Project Coordinator, Technical Manager, Design Manager, Operations Manager, IT Manager, Business Analyst, Team Leader, Department Manager, Consultant, or another relevant position.

What matters is not the title itself, but whether your experience demonstrates that you led and managed the project.

Field 3: Experience Dates

Enter the start and end dates of the relevant project experience being claimed. These dates should reflect the actual project period — not automatically your full period of employment with the organization.

A Simple Example: An applicant may have worked for an organization for five years but led a qualifying project for only eight months. In this situation, the full five-year employment period should not automatically be treated as five years of project leadership experience.

If one project does not provide enough qualifying months of project management experience, you may add other projects until you meet the required duration:

5 years of experience for diploma holders
3 years of experience for bachelor's, master's, or doctoral degree holders

These projects do not need to be from the same organization — they may include projects completed with previous employers, provided the experience was gained within the past 10 years.

However, as a bachelor's degree holder, if you have one project from your current organization that provides at least 36 months of qualifying experience, that project alone is sufficient. There is no need to add more projects.

Important: The project duration alone is not enough. The experience must meet PMI®'s eligibility requirements and demonstrate that you led and managed project activities.

Overlapping project periods can also be entered, but they cannot be counted twice — so it's better to select the longest one to report. Any of your projects from the last 10 years can be reported, but I always suggest selecting the most recent one. The form does not ask for the project name — just the start and end dates.

Field 4: Experience Summary

Previously, applicants were specifically asked to describe the project objective, description, leadership role, and key deliverables across the project life cycle — from initiating through closing — including the outcome based on project status.

The new form now asks for only three areas: your role, your contributions, and the project outcomes. Although the format is shorter, your summary must still provide convincing evidence that you led and managed a project. It should demonstrate project leadership — not merely describe your technical duties, routine operational responsibilities, or general job description.

Your Role

Describe your position within the project and the project leadership responsibilities you held. Explain your level of authority, accountability, and involvement in decision-making.

Tip: Emphasize how you led and coordinated activities across the following areas:

People: How you guided team members, managed stakeholders, resolved conflicts, communicated expectations, and supported collaboration.
Process: How you planned, executed, monitored, controlled, and closed project activities while managing risks, issues, changes, quality, schedule, and budget.
Business Environment: How you ensured the project aligned with organizational objectives, delivered business value, addressed compliance requirements, and responded to internal or external changes.

Your Contributions

Describe what you personally led, planned, managed, coordinated, monitored, resolved, or delivered. Focus on your individual actions and responsibilities — not only the work completed by the organization or project team.

Table 2 — Weak vs. Strong Contribution Statement
Instead of…	Write something like…
“The project delivered a new ERP system for the organization.”	“I identified key stakeholders, helped define the project objectives and requirements, developed and monitored the implementation plan, coordinated the technical and operational teams, managed risks and change requests, resolved issues affecting the schedule, oversaw user testing and training, and coordinated final acceptance and project closure.”

The Outcomes

Explain what the project achieved through your involvement and how the results benefited the end user, customer, or organization — improvements, benefits, or measurable results. State whether the project objectives and requirements were successfully achieved within the approved scope, budget, schedule, and quality expectations. If the project is ongoing, describe the results achieved so far and the expected outcomes.

Tip: Keep the summary of role, contributions, and outcomes clear and concise, with a maximum of 500 words. It should not simply repeat a general job description.

Ready to start your PMP journey?

PMI Authorized Training Partner · Live Online · 5 Sundays · 35-Hour Certificate

Enroll Now

Need Help Reviewing Your PMP® Application?

A well-prepared application can help avoid unnecessary confusion, delays, or possible rejection. Professional guidance can help you:

✔ Identify the correct qualifying project periods
✔ Organize multiple projects properly
✔ Avoid double-counting overlapping months
✔ Write a clear summary of your role, contributions, and outcomes
✔ Review the application before submission

Before submitting your PMP® application, make sure your experience is presented clearly, accurately, and in line with the information requested in the new form.

3FOLD Training FZE Supports You Beyond the Training

At 3FOLD Training FZE, we assist our students with their PMP® exam application, including:

✔ Reviewing eligibility and experience periods
✔ Guiding the correct presentation of project experience
✔ Helping organize multiple project entries
✔ Reviewing the role, contributions, and outcomes summary
✔ Supporting application submission and audit preparation

Our goal is not only to prepare students for the PMP® exam, but also to guide them through the application process with greater confidence and clarity.

Related Resources

PMP Certification Training PMP Application SupportStep-by-step guidance on completing the PMI application.PMP Application Process 2026Related article PMP Eligibility Requirements 2026Related article How to Get PMP Certified in 2026Related article

Ready to get PMP certified?

Start Your PMP Journey with 3FOLD Training

Live online · Every Sunday · PMI ATP certified · 35 contact hours · Full application support

PMI Authorized Training Partner5 Sundays — Fits Work ScheduleApplication Help IncludedNo Prior PM Knowledge Required

USD $390· all-inclusive, no hidden fees

Enroll Now

Next batch filling fast · Seats limited per session