How to write a PMP project description
An eight-part structure for the project description on the PMP application, with what each part should show, a worked example, and how to keep it honest and within the length limit.
For each project on your application, PMI gives you one box to describe it. In a few hundred words a reviewer needs to see that this was a real project, that you led it, and that you did the things project leaders do.
PMI does not prescribe a format. What follows is a structure that covers everything PMI says a description should explain, in an order that is easy to read.
What PMI wants to learn
In its guidance on the application, PMI says to be ready to explain, for each project:
- what the project aimed to accomplish
- when it started and ended
- how you led or directed the work
- who you worked with or influenced
- which project activities you led or directed
- what value, output, or outcome it delivered
The dates go in their own fields. Everything else goes in the description.
The eight-part structure
Answer these eight prompts in order. Each one is a sentence starter, and together they form a single description.
1. "The overall objective of the project was to..."
One sentence that says what the project was for. Include something countable: how many users, sites, items, dollars, or weeks.
A reviewer who reads only this sentence should understand the project.
2. "As the project manager, I was responsible for..."
Two or three sentences on the scope of your role. Say that you led the effort from start to finish, or say which part you led. If your formal title was something else, this is where you make clear that you were the person leading the project.
3. "The key deliverables of the project were..."
One sentence listing concrete outputs as nouns. Include both what the project produced for its users and the management documents you created to run it.
Good: "a requirements document, a project schedule, a risk register, the configured system, a training guide, and a transition plan".
Weak: "all the things needed for a successful rollout".
4. "While working with stakeholders, I..."
Two or three sentences about people outside your team: sponsors, customers, approvers, other departments. Show that you identified who they were, understood what they expected, kept them informed, and brought them into agreement.
5. "While working with my team, I..."
Two or three sentences about leading the people doing the work. Setting roles and expectations, removing whatever blocked them, resolving disagreements, and passing on knowledge all belong here.
6. "While working on the project, I..."
Two or three sentences about running the project itself. This is where planning, scope, schedule, budget, resources, quality, procurement, and tracking progress go. Name the approach you used, whether predictive, agile, or hybrid.
7. "Throughout the project, I..."
Two or three sentences about the things that surround the work: governance, compliance, risk, issues, change control, and lessons learned. After the 2026 update these topics carry much more weight in PMI's outline, so do not skip this part.
8. "The project resulted in..."
Two sentences. State whether the project succeeded, then give the measurable result and tie it back to the objective in part 1.
A project that was cancelled or only partly successful can still be listed. Say so plainly and describe what was delivered or learned.
How the parts map to PMI's outline
PMI's Exam Content Outline groups the work of a project manager into three domains: People, Process, and Business Environment. Parts 4 and 5 show People. Part 6 shows Process. Part 7 shows Business Environment.
You do not need to name the domains or quote the outline. A description that covers all eight parts will show all three naturally. The guide to the 2026 Exam Content Outline lists the tasks in each domain if you want to check your wording against them.
A worked example
Here is a set of raw notes, the way most people would jot them down:
Clinic had 3 sites still on paper scheduling. Got asked to move them to the online booking system the main hospital uses. 14 weeks, me plus 5 people (2 IT, 2 front desk leads, 1 trainer). Had to work around the regional privacy audit in week 9. One site manager hated the idea. Went live on time, no-shows dropped from 18% to 11% in the first quarter.
And the description built from them:
The overall objective of the project was to move three outpatient clinics from paper scheduling to the hospital's online booking system within 14 weeks. As the project manager, I was responsible for leading the effort from initiation through handover to clinic operations. I planned the work, coordinated a team of five, and reported progress to the director of outpatient services. The key deliverables of the project were a project charter, a site-by-site cutover schedule, a risk register, the configured booking system at three sites, staff training materials, and a support handover document. While working with stakeholders, I identified the clinic managers, front desk staff, and privacy office as key groups and met each to understand their concerns. I addressed one manager's objections by piloting the system at that site first and sharing the results. While working with my team, I set clear roles for the IT, front desk, and training leads, held short weekly check-ins, and removed obstacles such as delayed access approvals. While working on the project, I used a predictive approach with a phased rollout, tracked progress against the cutover schedule, and re-sequenced one site to avoid a regional privacy audit. Throughout the project, I confirmed privacy requirements with the compliance officer, maintained the risk register, managed two approved scope changes, and recorded lessons learned after each site. The overall outcome of the project was a success. The project resulted in all three clinics going live on schedule, and missed appointments fell from 18 percent to 11 percent in the first quarter.
That is about 255 words. Every claim in it can be traced to something in the notes or to an ordinary part of running the project that the applicant could talk about if asked.
Length
PMI's form limits the length of each description and shows a counter as you type. Applicants commonly report a limit of a few hundred words. Aiming for 250 to 350 words gives you room for all eight parts and keeps you safely inside it. Check the counter in the form itself, because PMI can change the limit.
Rules for wording
- Write in the first person and the past tense. "I planned", "I led", "I resolved".
- Use verbs that show leadership. Planned, led, coordinated, negotiated, resolved, tracked, reported, approved. Avoid "assisted with", "supported", and "participated in" unless that is truly all you did.
- Describe the project, not the technology. A reviewer does not need to know which database you used.
- Remove jargon. Spell out or replace every acronym a stranger would not know. For military terms, see the glossary.
- Do not repeat yourself. Each part should add something new.
- Do not inflate. If you led a workstream, say so. An honest description of a smaller role is far safer than an impressive description of a role you did not have.
Using the drafting tool
The drafting tool on this site asks for your notes and produces a first draft in this structure. It is a starting point. Read each sentence and ask whether you could explain it to someone who was there. If not, change it or remove it.
For more finished descriptions in different industries, see the examples.