How to Calculate Your PMP Experience Hours: The 36-Month Non-Overlapping Rule Explained

To calculate your PMP experience hours, PMI requires either 36 non-overlapping months and 4,500 hours of leading and directing projects if you hold a bachelor's degree, or 60 non-overlapping months and 7,500 hours if your highest qualification is a high school diploma or associate degree, with all experience earned within the eight years before you apply. The word non-overlapping is the part most candidates miscalculate: if two projects ran during the same calendar month, that month can only be counted once toward your total, not once per project. Getting this calculation wrong is one of the most common reasons PMP applications are delayed, flagged for audit, or rejected outright.

Key Highlights: How to Calculate Your PMP Experience Hours?

• Bachelor's degree holders need 36 unique months and 4,500 hours; those without a bachelor's degree need 60 unique months and 7,500 hours, both within the last eight years.
• Overlapping months across simultaneous projects are counted only once, never added together, which is the single most miscalculated part of the application.
• Experience must involve leading and directing projects, not simply participating in them as a team member or performing routine operational work.
• Each project you list must include tasks from at least one of the five PMBOK process groups: initiating, planning, executing, monitoring and controlling, and closing.
• PMI's application audit is random and can affect any submission, so accurate hour calculation matters even if you are never selected for review.
• Self-employed applicants, career-break candidates, and those with part-time or volunteer project work need to document experience slightly differently to withstand scrutiny.
• A simple worksheet approach, listing every project's start and end month before totalling hours, catches most overlap errors before submission.

The Two Experience Paths: 4,500 Hours vs 7,500 Hours

PMI sets two eligibility tracks based on education, and confusing them is a common first mistake. The table below lays out both paths exactly as PMI's certification handbook defines them.

A candidate does not need to hold a project management degree specifically, only a bachelor's degree or recognised global equivalent in any field, to qualify for the shorter 36-month, 4,500-hour path. This distinction alone changes a candidate's required experience by 3,000 hours and two full years, so confirming which path applies to you should be the very first step before calculating anything else, and it is worth double-checking against Simpliaxis's PMP certification eligibility requirements guide or the PMI eligibility page directly. The same eligibility check also confirms the 35 contact hours of formal project management education requirement, which most candidates satisfy through an accredited course such as Simpliaxis's PMP certification training rather than a standalone workshop.

What Actually Counts as Leading and Directing Projects

PMI's language is specific: your experience must show that you led and directed project tasks, not merely that you contributed to a project team or performed repeatable operational work. Reviewers look for evidence spanning PMBOK's five process groups, so a project description should ideally touch at least one of the following:

• Initiating: defining project objectives, identifying stakeholders, or authorising the project to proceed.
• Planning: developing schedules, budgets, scope statements, or risk registers.
• Executing: directing and managing the work, coordinating resources, or managing stakeholder engagement.
• Monitoring and Controlling: tracking performance against baselines, managing changes, or reporting status.
• Closing: formalising acceptance of deliverables or closing out contracts and lessons learned.

Work that is purely repetitive, such as ongoing operational support with no defined start, end, or unique objective, does not qualify, even if it consumed significant hours. This is why a long tenure in a role is not, by itself, proof of eligible experience; PMI is assessing the nature of the work performed within that tenure.

The Non-Overlapping Rule: How to Handle Simultaneous Projects

The rule that catches the most candidates off guard is straightforward once illustrated with numbers, but easy to miscalculate mentally. Consider a candidate who managed two projects at the same time for part of their career, as shown below.

A practical way to apply this rule is to work backward from your most recent project and assign each calendar month to only one project, marking any month already claimed by a later project as unavailable to an earlier one. This produces an accurate, non-duplicated month count that matches how PMI's application system and any subsequent audit will assess your submission.

A Step-by-Step Worksheet for Calculating Your Hours

Before opening PMI's application form, working through your experience on a simple worksheet, even a basic spreadsheet, prevents most calculation errors.

1. List every project you intend to include, with its exact start and end month.
2. Sort the list chronologically and highlight any months where two or more projects overlap.
3. Assign each overlapping month to a single project, typically the more recent one, and remove it from the others.
4. Total your unique months and confirm it meets or exceeds 36 (with a bachelor's degree) or 60 (without one).
5. Estimate hours per month based on your actual time spent leading and directing that project, not your full working hours in the role, and total these against the 4,500 or 7,500-hour threshold.
6. Map each project to at least one process group so your written description can demonstrate leadership activity rather than pure participation.
7. Confirm your experience window falls within the eight years preceding your application date.

Common Mistakes That Trigger Audit Flags or Rejections

Several recurring errors show up across forum discussions and PMI application guidance, and most are avoidable with careful preparation rather than requiring additional experience.

A Full Worked Example: Calculating One Candidate's Eligibility From Scratch

Seeing the process applied to a complete career history makes the worksheet method easier to replicate. Consider a candidate with a bachelor's degree who needs 36 unique months and 4,500 hours, and who has held four roles involving project work over the past six years.

Adding the unique months gives 12 plus 18 plus 3 plus 24, which totals 57 unique months, comfortably above the 36-month threshold, and the hours total 1,000 plus 1,700 plus 250 plus 2,600, which is 5,550 hours, above the 4,500-hour minimum. Notice that the volunteer initiative could not contribute its full six months because three of them overlapped with the Project Beta role; only the non-overlapping portion counts. This is exactly the kind of calculation that a spreadsheet-based worksheet catches immediately but that a candidate estimating from memory is likely to inflate.

How to Turn Your Hour Calculation Into a Project Description PMI Approves

Once your months and hours are calculated accurately, the next risk is writing a project description that fails to demonstrate leadership even though the underlying experience genuinely qualifies. PMI reviewers are looking for evidence that you directed the work, not just that you were present for it, and the clearest way to show this is the STAR structure: Situation, Task, Action, Result.

A weak description might read simply "Involved in a system migration project and helped coordinate testing," which tells a reviewer nothing about leadership or process-group coverage. A stronger version of the same experience, written against the same underlying facts, reads closer to "Led a 6-person cross-functional team through a system migration project; developed the project schedule and risk register during planning, directed user acceptance testing across 25 end users during execution, and formally closed the engagement with a documented lessons-learned session."

The second version explicitly touches planning, executing and closing, uses PMI's own terminology, and states a measurable scope, all of which help a reviewer map the description to eligible experience rather than leaving it ambiguous.

Each project description should stay within roughly 200 to 500 words and should avoid organisation-specific jargon that a reviewer unfamiliar with your industry would not recognise. Simpliaxis's PMP application examples guide includes several worked before-and-after descriptions if you want additional templates to model your own writing on.

Special Cases: Self-Employed, Career Breaks, Part-Time and Volunteer PM Work

Not every candidate's career fits neatly into a single employer's project list, and PMI's application does accommodate several common variations, provided they are documented carefully. Self-employed applicants and consultants can count client engagements as valid project experience, but because there is no internal supervisor to list as a verification contact, it is worth identifying a client-side stakeholder who can confirm the engagement if selected for audit.

Candidates with career breaks should simply exclude those months from their total rather than attempting to stretch surrounding projects to cover the gap, since PMI's eight-year window is measured from the application date backward regardless of breaks within it.

Part-time project work counts, but hours should reflect actual time spent leading the project rather than a full-time equivalent, and volunteer project leadership, such as directing a non-profit initiative or community project, is accepted as long as it meets the same leading-and-directing standard and process-group coverage as paid work.

Candidates who changed employers mid-career sometimes worry that a short gap between roles disqualifies surrounding experience, but PMI does not require continuous, unbroken employment, only that the total non-overlapping months across all listed projects reach the required threshold within the eight-year window. Similarly, candidates who moved between industries, for example from construction into IT, can combine project leadership experience from both sectors on a single application, since PMI's eligibility criteria concern the nature of the work performed rather than the industry it occurred in.

What matters in every one of these variations is that each project description can still independently demonstrate a defined objective, leadership role, and at least one process group, regardless of how the roles are otherwise structured around employment gaps, industry changes, or paid versus unpaid status.

What to Track in Your Worksheet Columns

A worksheet built specifically for this calculation is more useful than a general resume-style project list, because it needs to answer PMI's eligibility questions directly rather than simply describing your career. At minimum, each row should capture the project name, exact start and end month, your role and title at the time, a one-line objective statement, the process groups your work touched, an estimate of hours per month spent specifically on leading and directing tasks, and the name and contact details of a supervisor or stakeholder who could verify the work if selected for audit.

Keeping this worksheet updated throughout your career, rather than reconstructing it from memory immediately before applying, is one of the most effective ways to avoid both accidental overlap errors and the scramble to track down a former supervisor's current contact details months or years after a project ended.

How Employers and L&D Teams Can Help Multiple Candidates Document Experience Correctly

When an organisation is sponsoring several employees through PMP certification at once, inconsistent experience documentation across the group is a common and avoidable source of delay. A PMO or learning and development manager coordinating a cohort can standardise this by having each candidate use the same worksheet approach above before submission, and by pairing the group with a coach who reviews draft project descriptions for process-group coverage and non-overlapping accuracy before anyone applies.

This kind of coordinated preparation is one of the practical benefits organisations get from booking Simpliaxis's corporate and group training programme rather than leaving each employee to interpret PMI's eligibility rules independently, since a shared cohort timeline also makes it easier to schedule application reviews and mock audits together rather than one at a time.

What Happens After You Submit: Audit Odds and Timeline

PMI states plainly in its certification handbook that all applications are subject to audit and that selection is random, so accurate experience calculation matters regardless of whether you expect to be audited. Independent estimates from exam-prep sources place the audit rate anywhere from roughly 5% to 20% of applications, though PMI does not publish an official figure, and this uncertainty is itself a reason to prepare every project description as though it will be checked.

If selected, candidates are typically given a 90-day window to submit supporting documentation, which can include signed verification forms from supervisors or client contacts confirming the dates and nature of the project work claimed. A well-documented, accurately calculated application, built from the worksheet process above, is the most effective way to move through this stage without delay, and Simpliaxis's PMP audit process guide walks through what documentation to have ready in advance.

Conclusion

Calculating PMP experience hours correctly comes down to two disciplines: knowing which eligibility path applies to your education background, and rigorously avoiding double-counted months when projects overlap. The 36-month, 4,500-hour and 60-month, 7,500-hour thresholds are fixed by PMI, but how accurately a candidate maps their career onto those thresholds is entirely within their control, and a simple worksheet listing every project's start and end date is usually enough to catch the errors that most often cause delays or rejections.

Whether you are applying independently or as part of an employer-sponsored cohort, treating experience documentation with the same rigor as the exam itself is what separates a smooth application from one that stalls in audit.