- A
A Request for Change always requires a change budget; an Off-specification does not
Why wrong: Both may require a change budget, but that is not the defining difference.
- B
A Request for Change proposes a modification to baselined products; an Off-specification identifies a failure to meet a specification
This is the correct distinction: RFC proposes a change, Off-specification identifies a deviation.
- C
A Request for Change is raised by the Project Board; an Off-specification is raised by the Project Manager
Why wrong: Both can be raised by anyone, but the key difference is the nature of the issue.
- D
A Request for Change is recorded in the Risk Register; an Off-specification is recorded in the Issue Register
Why wrong: Both are recorded in the Issue Register.
Quick Answer
The answer is that a Request for Change proposes a modification to baselined products, while an Off-specification identifies a failure to meet a specification. This distinction is rooted in the PRINCE2 change control approach: a Request for Change is a formal proposal to alter a product that has already been agreed or baselined, often triggered by a need for improvement or adaptation, whereas an Off-specification is a notification that something which should be provided is not—or is forecast not to be—provided, meaning a product has deviated from its agreed specification. On the PRINCE2 Foundation exam, this tests your grasp of issue types within the Change theme; a common trap is confusing the two because both can arise from the same problem, but remember that an Off-specification is about a gap or defect, while a Request for Change is about a deliberate alteration. A helpful memory tip is to think of “Off-spec” as “off the mark” (a failure to meet requirements) and “RFC” as “revision for completion” (a proposal to change what was already set).
PRINCE2F PRINCE2 Practices Practice Question
This PRINCE2F practice question tests your understanding of prince2 practices. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
What is the difference between a Request for Change and an Off-specification?
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
A Request for Change proposes a modification to baselined products; an Off-specification identifies a failure to meet a specification
A Request for Change is a proposal for a change to a product that has been agreed or baselined. An Off-specification is something that should be provided but is not (or is forecast not to be) provided.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A Request for Change always requires a change budget; an Off-specification does not
Why it's wrong here
Both may require a change budget, but that is not the defining difference.
- ✓
A Request for Change proposes a modification to baselined products; an Off-specification identifies a failure to meet a specification
Why this is correct
This is the correct distinction: RFC proposes a change, Off-specification identifies a deviation.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
A Request for Change is raised by the Project Board; an Off-specification is raised by the Project Manager
Why it's wrong here
Both can be raised by anyone, but the key difference is the nature of the issue.
- ✗
A Request for Change is recorded in the Risk Register; an Off-specification is recorded in the Issue Register
Why it's wrong here
Both are recorded in the Issue Register.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
- Use explanations to understand the rule behind the answer.
TExam Day Tips
- Underline the problem statement mentally.
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the PRINCE2F exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which PRINCE2F exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
- →
PRINCE2 Practices — study guide chapter
Learn the concepts, then practise the questions
- →
PRINCE2 Practices practice questions
Targeted practice on this topic area only
- →
All PRINCE2F questions
1,731 questions across all exam domains
- →
PRINCE2 Foundation study guide
Full concept coverage aligned to exam objectives
- →
PRINCE2F practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PRINCE2F practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Overview of PRINCE2 and Principles practice questions
Practise PRINCE2F questions linked to Overview of PRINCE2 and Principles.
Business Case and Organizing practice questions
Practise PRINCE2F questions linked to Business Case and Organizing.
Project Initiation and Stages practice questions
Practise PRINCE2F questions linked to Project Initiation and Stages.
Overview of PRINCE2 and the project environment practice questions
Practise PRINCE2F questions linked to Overview of PRINCE2 and the project environment.
People: organizations, teams, and leadership practice questions
Practise PRINCE2F questions linked to People: organizations, teams, and leadership.
PRINCE2 Practices practice questions
Practise PRINCE2F questions linked to PRINCE2 Practices.
PRINCE2 Processes practice questions
Practise PRINCE2F questions linked to PRINCE2 Processes.
PRINCE2F fundamentals practice questions
Practise PRINCE2F questions linked to PRINCE2F fundamentals.
PRINCE2F scenario practice questions
Practise PRINCE2F questions linked to PRINCE2F scenario.
PRINCE2F troubleshooting practice questions
Practise PRINCE2F questions linked to PRINCE2F troubleshooting.
Practice this exam
Start a free PRINCE2F practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this PRINCE2F question test?
PRINCE2 Practices — This question tests PRINCE2 Practices — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: A Request for Change proposes a modification to baselined products; an Off-specification identifies a failure to meet a specification — A Request for Change is a proposal for a change to a product that has been agreed or baselined. An Off-specification is something that should be provided but is not (or is forecast not to be) provided.
What should I do if I get this PRINCE2F question wrong?
Identify which PRINCE2F exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
8 more ways this is tested on PRINCE2F
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. What is the difference between a Request for Change (RFC) and an Off-specification?
hard- A.An RFC is raised by the Project Board, while an Off-specification is raised by the Project Manager.
- B.An RFC is always approved by the Change Authority, while an Off-specification is approved by the Project Board.
- ✓ C.An RFC is a change to an approved baseline, while an Off-specification is a deviation from a requirement.
- D.An Off-specification can be resolved by concession, while an RFC cannot.
Why C: An RFC is a proposal for a change that would deliver something not originally specified. An Off-specification is something that should have been provided but was not, i.e., a failure to meet a requirement.
Variation 2. What is the difference between a Request for Change and an Off-specification?
hard- A.A Request for Change is always raised by the Project Manager; an Off-specification is raised by the Team Manager
- B.There is no difference; they are synonyms
- C.A Request for Change requires a change budget; an Off-specification is always free
- ✓ D.A Request for Change proposes a change to an agreed product; an Off-specification identifies a product that does not meet its specification
Why D: A Request for Change is a proposal for a modification to a product that has been approved or baselined. An Off-specification is a situation where a product is not meeting its specification. Both are issue types.
Variation 3. What is the difference between a Request for Change and an Off-specification?
medium- ✓ A.A Request for Change is a proposal to modify a baseline; an Off-specification is a failure to meet the baseline
- B.A Request for Change is raised by the Project Manager; an Off-specification is raised by the team
- C.A Request for Change is always urgent; an Off-specification is not
- D.There is no difference; they are the same thing
Why A: A Request for Change proposes a modification to an approved baseline, while an Off-specification is something that should have been provided but was not, or that deviates from the baseline.
Variation 4. What is the difference between a Request for Change and an Off-specification?
hard- ✓ A.A Request for Change seeks to alter a product; an Off-specification is a failure to meet a requirement
- B.A Request for Change is raised by the Project Board; an Off-specification is raised by the Project Manager
- C.A Request for Change is always approved; an Off-specification is always rejected
- D.There is no difference; they are synonyms
Why A: A Request for Change is a proposal to change a product that has been approved, while an Off-specification is a deviation from what was specified. Both are issue types.
Variation 5. What is the difference between a Request for Change and an Off-specification?
medium- A.A Request for Change is an issue that cannot be resolved, whereas an Off-specification is a problem that can be resolved
- B.A Request for Change is a product that does not meet its specification, whereas an Off-specification is a proposal for a change
- ✓ C.A Request for Change is a proposal for a modification, whereas an Off-specification is a product that does not meet its specification
- D.A Request for Change is a proposal for a change, whereas an Off-specification is a product that should have been produced but was not
Why C: A Request for Change is a proposal for a modification, while an Off-specification is a product that does not meet its specification.
Variation 6. What is the difference between a Request for Change and an Off-specification?
hard- A.A Request for Change is always raised by the Project Board, while Off-specification is raised by the Project Manager
- B.A Request for Change requires a change budget, while Off-specification does not
- ✓ C.A Request for Change proposes a new or modified product, while an Off-specification records something that should have been provided but is missing
- D.Off-specification is a type of risk, while Request for Change is a type of issue
Why C: A Request for Change proposes a modification to an agreed baseline, whereas an Off-specification identifies something that was specified but not delivered.
Variation 7. What is the difference between a Request for Change and an Off-specification?
medium- A.A Request for Change is always approved; an Off-specification is always rejected
- ✓ B.A Request for Change proposes a new requirement; an Off-specification identifies a failure to deliver a required product
- C.An Off-specification must be escalated to the Project Board; a Request for Change can be handled by the Change Authority
- D.They are the same thing with different names
Why B: A Request for Change is a proposal for a change that is not required to meet the original specification; an Off-specification is something that should be there but is not.
Variation 8. What is the difference between a Request for Change (RFC) and an Off-specification?
hard- A.An RFC is a request for a new feature, while an Off-specification is a report of a defect
- ✓ B.An RFC seeks to change an approved baseline, while an Off-specification reports a failure to meet a specified requirement
- C.An RFC is used for threats, while an Off-specification is used for opportunities
- D.An RFC is raised by the Project Board, while an Off-specification is raised by the Project Manager
Why B: An RFC proposes a modification to an approved baseline, while an Off-specification indicates that something should have been provided but was not, or is not working as expected.
Last reviewed: Jun 21, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.