Putting military experience on the PMP application
How service members and veterans can find qualifying projects in their careers, describe them in civilian terms, protect sensitive details, and line up people to verify them.
Military careers are full of project management. Very little of it is called that. An officer or NCO who has fielded equipment, planned an exercise, or stood up a new capability has done exactly the work the PMP recognizes, and has usually described it in language no civilian reviewer can follow.
This guide is about closing that gap.
Does military experience count?
Yes. PMI requires professional experience leading and directing projects. It does not require a particular industry or the title "project manager", and its application form lists the armed forces among the choices for an organization's primary focus.
What PMI does require is that the work was a project, that you led it, and that it falls within the last 10 years. Those are the same tests everyone faces.
Finding the projects in your career
Most military time is operations: running a section, maintaining readiness, executing the daily and weekly rhythm of a unit. That does not count, however well you did it.
The projects are the one-time efforts with a start, an end, and a defined result. Common ones include:
- Fielding new equipment or systems, from notification through training and turn-in of the old gear.
- Planning and running a major exercise or a training center rotation, as the lead planner or officer in charge.
- Deployment and redeployment, treated as a defined effort to move people and equipment and establish operations.
- Standing up or closing down a unit, a site, a capability, or a program.
- Facility projects: building, renovating, or relocating a headquarters, motor pool, clinic, or network.
- Building a new course or training program and delivering it for the first time.
- System migrations and software development, including locally built tools.
- Process changes with a clear before and after, such as redesigning how a section tracks maintenance or property.
- Major events with a one-time plan and budget.
A useful test: if there was a concept, a plan, an execution phase, and an after-action review, and it would not have happened again the same way, it was probably a project.
What usually does not count
- Holding a leadership position. "Platoon leader for 14 months" is a job, not a project. The projects are the specific efforts you led during those months.
- Routine training events run from a standing calendar.
- Recurring inspections, inventories, and reports.
- Day-to-day supervision, administration, and duty rosters.
See what counts as project experience for the general rule.
You did not need to be the commander
Qualifying experience means you led and directed the project. On most military projects that person is not the commander, who approves and resources the effort much as an executive sponsor does. It is the officer in charge, the NCO in charge, the lead planner, or the action officer who built the plan, coordinated the sections, tracked progress, and briefed the boss.
If that was you, it is your project. In the description, the commander becomes "the senior leader" or "the executive sponsor", and you are the project manager.
Translating the language
A civilian reviewer cannot give you credit for something they cannot understand. Before any description goes in the form:
- Replace every acronym with what it means, or with a civilian equivalent.
- Replace ranks and duty positions with functions: "senior leader", "operations manager", "team supervisor".
- Replace unit names with sizes: "a 600-person organization", "five subordinate teams".
- Replace doctrine terms with their plain meaning. An operations order is a project plan. An after-action review is a lessons-learned session.
The military to civilian glossary lists common terms and what to write instead. The drafting tool applies the same translations automatically, and the examples page includes a translated fielding description.
Filling in the short fields
Organization. Use the name of the command or agency at a level you are comfortable disclosing. The branch of service, or a major command, is normally enough.
Job title. Give your actual duty title. The description is where you explain what it meant.
Budget. The form offers ranges. Estimate the value of what you managed, such as the equipment fielded or the funds you controlled. If you managed no money directly, choose the range that honestly reflects the resources involved.
Team size. Count the people whose work you coordinated for this project, not the size of your whole unit.
Protecting sensitive information
You are submitting to a civilian organization, and if you use any online tool to help write the description, the text passes through that tool's servers as well. Treat the description as public.
- Never include classified information or controlled unclassified information.
- Leave out specific locations, dates of movement, capabilities, frequencies, vulnerabilities, and unit identifiers where they would be sensitive.
- Describe the management of the project, which is rarely sensitive, and generalize the subject matter: "a communications system", "an overseas location", "a 400-person organization".
- If you are unsure, ask your security manager or supervisor before you submit.
A good description does not need the sensitive details. The reviewer is assessing how you led the project, not what the equipment could do.
Lining up people to verify your projects
If PMI audits your application, it asks someone who knew each project to confirm your role. Military moves make this harder than it is for most applicants.
- Choose a verifier for each project now: a supervisor, a commander, or a senior peer who saw your role first hand.
- Get a personal email address and phone number. Official addresses stop working when people move or leave the service.
- Tell them you are applying and what you plan to say about the project.
- Keep your own records: evaluation reports, award citations, orders, and briefing slides that show your role and the dates. These also help you remember the facts accurately years later.
The audit guide covers the rest.
Training hours
You still need 35 hours of project management training. Check what you already have. Some military and government courses include project management instruction, and PMI accepts employer-sponsored programs as long as the content covers the topics in its outline and you can document the hours. Only the hours spent on project management count.
If you plan to take a live prep course after 1 December 2026, confirm that the provider is a PMI Authorized Training Partner. The eligibility guide explains that change. Many service members can use tuition assistance, credentialing assistance, or veterans' education benefits toward training and exam fees. Those programs change often, so check with your education office or the relevant agency for current rules.