Demonstrating PM competence convincingly: IPMA® Level C and B

“How do I demonstrate my PM competence convincingly?” Experienced project managers often ask me this when they are thinking about Level C or B. They have led projects for years, but feel unsure how to make this experience visible on paper and in conversation. As a trainer and textbook author, I have been supporting candidates along this path for many years. Here are the most important points.

Why Level C and B differ from Level D

Level D is the entry point to the four-level IPMA® system. There you show in an examination that you have mastered the knowledge of project management. Foundation credentials such as the Basic Certificate in Project Management (GPM)® come before it; they are not a separate level of the system.

From Level C onwards, a second question is added: alongside “What do you know?” comes “How do you apply it?”. Using real projects, you demonstrate that you lead projects successfully: in the environment of your company, with people and with the right methods. These are exactly the three areas described by the IPMA® competence standard, the ICB, as Perspective, People and Practice.

The requirements at a glance

The following guide values apply to the project management domain:

Level	For whom	Experience as a guide value (project management domain)
Level C	Managers of projects of medium complexity	at least three years of responsible project management; responsible sub-project management in complex projects can also be recognised
Level B	Managers of complex projects	at least five years of project management, including three years leading complex projects

Duration, period under review and required responsibility depend on the level, domain and certification body. At PM-ZERT, the regular period under review is six years for Level C and eight years for Level B; justified extensions are possible. The current rules of your certification body always apply: in Germany PM-ZERT of the GPM®, in Switzerland VZPM, in Greece IPMA® Greece. Check them before you apply, as the details change from time to time.

The procedure

As a guide, certification usually follows these steps:

1. Application: CV, an overview of your projects and a self-assessment of your competencies.
2. Written part: an examination, depending on level and certification body.
3. Report: a description of one of your own projects, in which you show your competence.
4. Interview: a conversation with assessors, who ask targeted questions.

Depending on the certification body and certification path, further examination elements, such as an assessment centre or an extended interview, may be required. Sequence and scope depend on the respective procedure.

Allow several weeks for the report and preparation. Anyone who wants to finish alongside everyday project work in two weekends almost always underestimates the effort.

Choosing the right project

The project in the report is your most important evidence. A good project meets these conditions:

• You held responsible leadership, not just a sub-task.
• The complexity matches the level you are aiming for.
• It was not too long ago, so that you can talk about it vividly.
• It did not run smoothly. Competence shows particularly in crises, conflicts and course corrections.
• You may speak openly about it without revealing confidential details.

Writing the report so that competence becomes visible

“I” instead of “we”. Assessors want to know what you yourself decided and did. “We held a risk workshop” says little. “I called the risk workshop because two suppliers were blocking each other, and then redistributed the responsibilities” says a lot.

Situation, action, result, reflection. For each topic, briefly describe the situation, your action, what came of it and what you learned from it. This pattern keeps the report clear and makes it verifiable.

Cover all three areas. Many reports confine themselves to planning and methods. Show equally how you dealt with the project’s environment, such as strategy, governance and stakeholders, and how you led, negotiated and resolved conflicts.

Evidence, not assertion. Figures, dates, concrete decisions and results are more convincing than adjectives.

Reflect honestly. What would you do differently today? Good reflection is not an admission of weakness but a sign of maturity.

Convincing in the interview

In the interview, the assessors check whether the picture from the report holds true, and go deeper into individual topics. The most common question is essentially: “What specifically did you do in this situation?”

Prepare six to eight short stories from your practice that show different competencies: a conflict in the team, a difficult negotiation, a crisis in the project, a decision under uncertainty. Speak openly about mistakes and what you made of them. Textbook answers learned by heart, on the other hand, rarely convince.

Typical pitfalls

• The chosen project is too small for the level you are aiming for, or your own role was not responsible enough.
• The report reads like a catalogue of methods, not like the story of a project.
• Personal reflection is missing or stays on the surface.
• The time required is underestimated.

Conclusion

Level C and B do not reward learning by heart, but good project work that you make understandable. If you choose the right project, describe your own contribution clearly and reflect openly, you will go into certification well prepared.

I prepare candidates for all four levels, from Level D to Level A. For getting started with Level D, you will find the learning material in my textbook on IPMA® Level D, in English, German and Greek.