PRINCE2F People: organizations, teams, and leadership Practice Question
How often should the Project Board meet during a PRINCE2 project?
⚠ Common exam trap
The trap is assuming a fixed meeting schedule (monthly, weekly) based on common project management practice, rather than recognizing PRINCE2's event-driven approach tied to stage boundaries and exceptions.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
At the end of each stage and when exceptions occur
In PRINCE2, the Project Board should meet at the end of each stage and when exceptions occur. This is because the Board is responsible for stage boundary decisions and for handling exceptions that threaten the project's tolerances. Regular meetings are not prescribed; the frequency is driven by stage boundaries and exception events.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Only at the end of the project
Why it's wrong here
Meeting only at the end removes the Project Board's authority at each stage boundary, where it must authorise the next stage and review the End Stage Report. It is tempting because boards do convene for a final project closure review, but PRINCE2 requires decision points throughout, not a single terminal gathering.
- ✗
Monthly
Why it's wrong here
PRINCE2 sets no fixed monthly cadence; meeting frequency is defined by the project's tolerances and information needs, documented in the Communication Management Approach. Monthly would suit a low-risk project with generous stage tolerances and minimal exception activity.
- ✗
Weekly
Why it's wrong here
PRINCE2 sets no fixed cadence; meeting frequency is defined in the Communication Management Approach and driven by tolerance thresholds and stage boundaries. Weekly meetings impose unnecessary overhead on a small project, yet would suit a high-risk stage needing frequent progress reviews against tight tolerances.
- ✓
At the end of each stage and when exceptions occur
Why this is correct
PRINCE2 sets no fixed meeting cadence; the Project Board convenes at each stage boundary to authorise the next stage, and additionally whenever an exception is escalated. This satisfies the stem by tying meetings to stage-end assurance and exception handling rather than a calendar schedule.
Go deeper
Related to this question
About these practice questions
One of 1,189 original PRINCE2F practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official PeopleCert exam blueprint
This PRINCE2F practice question is part of Courseiva's free PeopleCert certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PRINCE2F exam.