How to write your PMP experience descriptions, with before and after examples

Most PMP applications that go wrong were not written by people without experience. They were written by people who described real work in words nobody could check.

What PMI wants from each project

PMI asks you to list each project separately, with your role and the work you led. Its own guidance on the PMP page adds two rules that shape everything else: count only time you spent managing projects in a professional setting within the last 10 years, and do not double-count projects that overlapped.

So a description has a job to do. It must show that you led the work, not merely took part in it, and it must be specific enough that a supervisor can confirm it. If you are chosen for an audit, that supervisor signs for every project you claimed, and PMI gives you 90 days to collect the signatures.

Think of each description as a short statement that three people will read: the PMI reviewer, your supervisor and you, a year from now, when you try to remember what you wrote.

Four parts, in this order

Write four short parts, in this order.

1. The objective. What the project had to deliver, and for whom.
2. Your responsibilities. What you personally led. Use "I", not "the team".
3. The team. Who you led and roughly how many people.
4. The result. What was delivered, with a number only if it is true and you can show where it came from.

Use the language of project work, such as scope, schedule, budget, risk and stakeholders, but only where the word describes something you did. A description that is full of vocabulary and short on events reads as copied.

Three rewrites, before and after

Here are three rewrites. The projects are invented, but the pattern is the one that causes trouble in real applications.

Example 1: a building site.

Before: "Managed construction of a residential block. Responsible for delivery, coordination and quality. Project completed successfully."

After: "Delivered a six-storey residential block of 24 flats for a private developer. I led the site programme and weekly coordination between the structural, mechanical and finishing subcontractors, controlled the monthly cost report against the approved budget and raised two change requests when the client altered the lift specification. I led a site team of nine and coordinated four subcontractors. The block was handed over two weeks after the original date, with the change requests approved and priced."

The first version has no number, no event and nothing a supervisor could confirm or deny. The second contains things that happened.

Example 2: an IT migration.

Before: "Led the migration of company systems to the cloud. Worked with stakeholders and managed risks."

After: "Moved the finance and HR systems of a 300-person company from two on-site servers to a hosted platform. I wrote the migration plan, ran the fortnightly steering meeting with the finance director and HR manager, kept the risk register and decided to split cut-over into two weekends after a rehearsal exposed data-mapping errors. I led three IT staff and one external consultant. Both systems went live on the revised dates with no data loss reported."

Example 3: a campaign that nobody called a project.

Before: "Responsible for the annual conference."

After: "Organised a two-day conference for 400 delegates, a one-off piece of work with a fixed date and a set budget. I defined the scope with the sponsor, built the schedule and vendor plan, led a team of five and managed eight suppliers. I tracked spend weekly against the budget and moved the registration deadline once to protect catering numbers. The event ran on the planned dates within the approved budget."

This one matters for people whose job title is not "project manager". PMI counts the work you led, not your title, so a conference, a product launch or a plant shutdown can count when you led it as a defined piece of work with a start, an end and a result.

The supervisor test

Before you submit, take each description and ask four questions.

• Could the person named as supervisor read this and say "yes, that is what happened"?
• Is every sentence about something I did, not something the department did?
• Is every number one I could show on request, from a report, a plan or an invoice?
• Does the date range match the dates in my own project list?

If the answer to any of them is no, rewrite the sentence. A modest, true description is safer than an impressive one that a supervisor hesitates over. A supervisor who hesitates is the most common reason an audit becomes slow.

Where applications usually go wrong

Describing the team's work as your own. "The team delivered" tells the reviewer nothing about what you led.

Counting overlapping projects twice. If two projects ran from January to June, you claim six months, not twelve.

Claiming a project nobody can confirm. A project from six years ago, led under a manager who has since left the company, is a risk. Find a replacement signer who saw your work before you rely on it. Someone who never saw it will not sign.

Padding the vocabulary. If you did not run a change control board, do not write that you did.

Leaving the result blank. "Completed" is not a result. What was handed over, and when?

Before you write a word

Build one folder first. For every project, record the dates, your role and a supervisor's current contact details. Add your diploma and your training certificates. Then contact each supervisor and ask whether they would sign if you are audited.

Only after that do you write. It takes an afternoon, and it removes the part of an audit that costs time: searching for people and papers while the 90 days run down.

When a description is ready to submit

Read all of them in one sitting. They should sound like a person describing different jobs, not one paragraph copied with the nouns changed. The projects should add up, without overlap, to at least the months your education level requires: 36 for a bachelor's degree or higher, 60 for a secondary diploma, with the shorter routes in between.

If they do, submit, and start studying while PMI reviews. If they do not, use the gap to lead something you can document rather than stretching the records you have.