Study PRINCE2 Foundation v7 Issues, Baselines, and Authority: key concepts, common traps, and exam decision cues.
The Issues practice covers current problems, requested changes, and situations where actual products differ from what was agreed. Foundation questions often test whether you can classify the issue correctly before deciding who should act.
PRINCE2 commonly distinguishes these issue types:
| Issue type | Strongest reading |
|---|---|
| Request for change | A proposal to alter an agreed baseline |
| Off-specification | Something should have been delivered one way but is or will be different |
| Problem or concern | A current difficulty needing attention |
The stronger answer usually starts by asking what baseline or expectation is affected. That is why issue control links closely to authority and tolerances. Some decisions may be delegated to a change authority, while others need escalation.
Foundation questions may also test whether an item belongs in issue control rather than risk control. If the matter already exists, the issue path is usually stronger than the risk path.
flowchart TD
A["Something affects delivery or the baseline"] --> B{"Already happening or only uncertain?"}
B -->|Only uncertain| C["Think risk first"]
B -->|Already happening| D{"Is there a proposal to change the baseline?"}
D -->|Yes| E["Request for change"]
D -->|No| F{"Does delivered or forecast output differ from what was agreed?"}
F -->|Yes| G["Off-specification"]
F -->|No| H["Problem or concern"]
| If the scenario says… | The stronger response usually… |
|---|---|
| the matter has already happened | uses issue control rather than leaving it in risk language |
| someone wants to alter an approved requirement | classifies it as a request for change |
| the delivered or forecast output differs from what was agreed | classifies it as an off-specification |
| the change sounds small | still checks authority and does not approve it informally |
A user asks for an additional reporting feature that was not in the approved baseline. That is not automatically “good stakeholder engagement.” It is a request for change and should be handled through the issue and change-control path.
A product has already been delivered with a shortfall against an approved requirement, and the team suggests accepting the difference quietly because the project is busy. The stronger Foundation answer does not blur this into risk language or casual discussion. It classifies the situation correctly and keeps authority and baseline control visible.
A completed product does not fully match an agreed requirement in its approved description. Which PRINCE2 issue type best fits this?
A. Opportunity B. Off-specification C. Benefit review D. Team plan update
Best answer: B
Why: An off-specification is used when the delivered or forecast product differs from what was agreed.
Why the others are weaker: A is a type of positive risk, C is not an issue classification, and D is not the issue type being tested.