Which of the following is a key difference between a Request for Change and an Off-specification?
The axis of difference is intent: a Request for Change seeks approval to alter an already baselined product, whereas an Off-specification reports that a product has been delivered but fails to meet its agreed specification. Both are issue types.
Why this answer
In PRINCE2, a Request for Change (RFC) is a proposal to modify an already baselined product, while an Off-specification is a report that a product has been delivered but does not meet its agreed specification. Both are issue types recorded in the Issue Register, but their nature differs: RFCs are proactive change proposals, Off-specifications are reactive quality failures.
Exam trap
PRINCE2F often tests the confusion between Issue Register and Risk Register; candidates incorrectly assume Off-specifications go to the Risk Register because they sound like risks, but both RFCs and Off-specifications are issues, not risks.
How to eliminate wrong answers
Option B is wrong because neither an RFC nor an Off-specification inherently has or lacks cost and time impact; both can have impacts, and the distinction is not about impact presence. Option C is wrong because both RFCs and Off-specifications are recorded in the Issue Register, not the Risk Register; the Risk Register holds potential future risks. Option D is wrong because both RFCs and Off-specifications require authorization through the change control process; neither is exempt from approval.