How to count non-overlapping months of PMP experience

Last updated November 16, 2026. Checked against PMI's July 2026 rules.

PMI counts calendar months, not projects, and counts each month once. Worked examples of overlapping projects, gaps, and the 10-year window.

PMI measures experience in months. It does not matter how many projects you led or how many hours you worked. What matters is the number of distinct calendar months, inside the last 10 years, in which you were leading at least one project.

That sounds simple, and it trips up a surprising number of applicants.

The rule

Every project is recorded separately on the application, with its own start and end date. PMI then counts the months those projects cover, and a month covered by more than one project is counted once.

PMI's own example:

Adding the two durations gives seven. The correct answer is five.

A longer worked example

Suppose you have a bachelor's degree, so you need 36 months, and these are your projects:

Project Start End Months on its own
A. Warehouse system rollout March 2021 February 2022 12
B. Site relocation November 2021 June 2022 8
C. Training program build September 2022 August 2023 12
D. Vendor transition June 2023 January 2024 8

Added up, that is 40 months, which looks like enough.

Now count calendar months:

The real total is 16 + 17 = 33 months. This applicant is three months short and needs another project, or a later application date once more experience has built up.

The experience calculator on this site does this count for you.

The 10-year window

Only months within the 10 years before you submit the application count.

If you submit in the middle of November 2026, the window reaches back to the middle of November 2016. A project that ran from June 2016 to May 2017 contributes only its last six months or so.

Two practical consequences:

Which dates to use

Use the dates of your involvement in leading the project.

If you joined a three-year program for its final year, you have twelve months, not thirty-six.

If you list a project that is still in progress, count only the months completed up to the date you submit.

Common mistakes

Adding durations. This is the mistake in the worked example above. Always count calendar months on a timeline.

Counting gaps. Time between projects is not project experience, even if you were employed as a project manager throughout.

Rounding up. A project that ran from the 20th of one month to the 5th of the next did not take two months of your leadership. Be conservative with partial months at the edges. If an audit compares your dates with what a verifier remembers, generous rounding is what stands out.

Listing everything. You do not get extra credit for exceeding the requirement by years. Choose the projects that are easiest to describe and verify, clear the requirement with a margin of a few months, and stop.

Forgetting the window. A project counted in full that began eleven years ago is the easiest error for a reviewer to spot.

A quick method

  1. Draw a line of months covering the last 10 years.
  2. For each project, shade the months from your start to your end.
  3. Count the shaded months. A month shaded twice still counts once.
  4. Compare the count with your requirement: 60, 48, 36, or 24 months depending on your education.

If the count is short by a small number, look again at your list for real projects you overlooked. Short assignments such as a system migration, an office move, or a one-time audit preparation are often left off because they did not feel like "project management" at the time. The guide on what counts as project experience can help you spot them.