The PgMP panel review is the stage most candidates fail. Unlike the PMP application review (which is essentially administrative), the PgMP panel review is a peer evaluation by 12 certified PgMPs of your written programme narratives. This guide walks through what they actually evaluate and how to prepare.
What the panel is looking for
Panel reviewers are experienced programme leaders reading your narratives with three questions in mind:
- Did this person actually run a programme, or a large project?
- Do the narratives show strategic alignment and benefits realisation — or just project execution?
- Is the level of decision-making described genuinely at a portfolio level?
Many rejections happen because candidates describe large projects as if they were programmes. A programme is a coordinated set of related projects delivering benefits that would not be achieved if managed separately. If your programme could have been done as one big project without losing value, it probably was not a programme.
Structuring each programme narrative
For each programme you claim, PMI wants:
- Business objective the programme delivered
- Multiple component projects and how they related
- Programme governance structure
- Stakeholder complexity handled
- Benefits realised (measurable outcomes)
- Programme lifecycle actions (initiation, planning, execution, closure)
Weak narrative (reads like a project):
"Managed the refinery expansion. Coordinated engineering, procurement, and construction contractors. Delivered on time."
Strong narrative (reads like a programme):
"Led a 3-year refinery capacity-expansion programme (USD 480M, 4 concurrent EPC contracts, 6 stakeholder groups) chartered to deliver a 40% throughput increase while maintaining certification for European product exports. Established programme governance with monthly Board review, integrated four contract schedules into a master programme baseline, and managed benefits realisation against the throughput and export-certification KPIs. Programme delivered 42% throughput uplift and preserved certification without a single day of production loss during commissioning."
The 5 things most rejected candidates got wrong
- Narratives read like large projects, not programmes. No mention of multi-project coordination, benefits realisation, or programme governance.
- Insufficient strategic framing. Programmes exist to deliver strategic outcomes. If your narrative sounds tactical, that is a red flag.
- Timeline math does not add up. Overlapping programmes claimed across the same period at implausible workloads.
- Stakeholder complexity understated. A programme with only 1–2 stakeholder groups is rare. If you describe simple stakeholder engagement, it dilutes the "senior leader" positioning.
- No mention of benefits realisation. The PgMP body of knowledge is explicit about benefits management as a distinct discipline. If your narrative does not mention it, it looks like you have not read the standard.
How we prepare candidates
Our PgMP programme includes:
- 1:1 narrative review for every claimed programme, iterated until it reads as programme-level, not project-level
- Mock panel simulation where a practitioner reviews your narratives with the same lens the actual panel uses
- Terminology drills to ensure PMI programme-management vocabulary is used correctly
- Follow-up support if you are selected for the actual panel review
Reference: PMI publishes the Standard for Program Management. Read it before you write your narratives — not after.