PRINCE2F Practice Question: Overview of PRINCE2 and the project environment
A project is using PRINCE2. The Senior User identifies a new requirement that was not in the original scope. What should the Project Manager do first?
⚠ Common exam trap
The trap is jumping to the change request or rejection step — candidates forget that PRINCE2 requires the Project Manager to first log and assess the issue before any decision or escalation, so they pick 'raise a change request' or 'reject' prematurely.
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
✓
Log it as an issue and assess the impact on the project
In PRINCE2, any new requirement or change that was not in the original scope is treated as an issue (specifically a change issue) and must be captured in the Issue Register and assessed for impact before any decision is made. The Project Manager's first action is to log the issue and evaluate its effect on the project's business case, plans, risks, and scope. Only after impact assessment should the Change Authority decide whether to approve, reject, or defer the change.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Immediately update the Project Plan to include the new requirement
Why it's wrong here
Updating the Project Plan directly bypasses PRINCE2 change control; the requirement must first be captured and assessed. The Project Manager should log it and evaluate impact via the Change Authority. Updating plans immediately suits minor, pre-authorised changes within tolerance, not new scope.
- ✗
Ask the Senior User to raise a change request with the Change Authority
Why it's wrong here
The Project Manager should first assess the change's impact on the project, since PRINCE2 requires evaluation before any formal submission. Directing the Senior User to the Change Authority bypasses this assessment and the Project Manager's own handling of issues and changes. Escalating straight to the Change Authority is tempting where authority is delegated, but impact analysis must precede it.
- ✓
Log it as an issue and assess the impact on the project
Why this is correct
Any new requirement is an issue under PRINCE2, so the Project Manager must first capture it in the Issue Register and assess its impact before deciding whether it needs a formal change. Only after impact analysis can the appropriate authority decide.
- ✗
Reject the requirement because it is out of scope
Why it's wrong here
Rejecting outright ignores PRINCE2's change control: every proposed change must be assessed and logged, then approved, rejected or deferred by the appropriate authority. The Project Manager cannot unilaterally dismiss it. Rejection is tempting because the requirement sits outside the agreed scope, but that decision belongs to the Change Authority after impact evaluation, not to the Project Manager.
Go deeper
Related to this question
About these practice questions
This PRINCE2F question is part of Courseiva's 1,189-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.