One of the most consistent sources of lost marks on the PRINCE2 Practitioner exam is confusing issues with change requests. They are related concepts - but they are not the same thing  and the exam exploits that confusion deliberately.

The PRINCE2 7th Edition introduced terminology changes that catch candidates off guard, particularly those familiar with the 6th Edition or everyday project management language. Scenario questions regularly hinge on correct classification, so understanding the distinction is not optional - it is essential.



## **What Is an Issue in PRINCE2 7?**

In PRINCE2 7, an issue is defined as any event that has happened, was not planned  and requires management action. The scope of this definition is deliberately broad - it captures far more than traditional change requests alone.

PRINCE2 7 replaced the Change theme with the Issues practice, expanding its coverage to include four distinct issue types. A Request for Change is a proposal to modify a project baseline. An Off-Specification covers something required but missing or failing to meet standards. A Problem or Concern captures anything worrying the team that requires attention. A General Issue handles ambiguous cases where full facts are not yet available.

Candidates who reinforce these distinctions through quality [PRINCE2 Practitioner Exam Dumps](https://www.certshero.com/prince2/prince2-practitioner)  find that scenario classification questions become far more manageable. Well-structured dumps present issue-type scenarios in the same framing the real exam uses, building the pattern recognition that matters under time pressure.



## **What Is a Change Request?**

A Change Request is not a standalone concept in PRINCE2 7 - it is one specific type of issue. Precisely, it is a proposal to alter an agreed project baseline, whether that baseline relates to scope, cost, schedule, quality criteria, or benefits.

The timing distinction is critical. Before a change request receives formal approval, it remains an issue logged in the Issue Register. A change only truly exists after the appropriate authority has approved the Request for Change and the relevant baselines have been updated.

The change control process follows four steps: capture the issue, assess its impact on project objectives, decide through the correct authority level  and implement by updating plans and baselines accordingly. The exam frequently tests which step applies next in a given scenario.



## **Common Practitioner Exam Pitfalls**

The most frequent mistake is treating every issue as a change request. Not every issue requires change control - some only need to be captured, monitored  and reviewed. Applying change control unnecessarily is just as wrong as failing to apply it when needed.

Misclassifying off-specifications is equally common. When a deliverable fails to meet required quality criteria, that is an Off-Specification - an issue type - not automatically a change request. It only becomes a change if the Project Board approves a formal deviation from the original specification.

Ignoring change authority levels is another costly error. Small Requests for Change may fall within the Project Manager's tolerance and can be approved without escalation. Larger or higher-impact RFCs must go to the Project Board. The exam tests whether candidates know the escalation logic, not just the definitions.



## **Quick Classification Cheat Sheet**

When facing a scenario question, ask three questions in sequence. First: did something unplanned happen that requires management attention? If yes, it is an issue. Second: is someone proposing a modification to an agreed baseline? If yes, it is a Request for Change - still an issue type. Third: has that RFC been formally approved? Only then does a change exist in PRINCE2 terms.

If the scenario describes a failing deliverable, think Off-Specification first. If it describes a general concern without enough facts, think General Issue. Reserve change control for scenarios where a baseline is explicitly being altered through formal approval.

Before your exam date, practicing these classification decisions through scenario-based resources on [Certshero](https://www.certshero.com) exposes you to the exact framing the Practitioner exam uses - making the logic feel instinctive rather than effortful on the day.



## **Conclusion**

The distinction between issues and change requests in PRINCE2 7 is precise, testable  and frequently misunderstood. Issues are broad - any unplanned event requiring action. Change requests are a specific issue type that triggers formal control only after approval. Off-specifications, problems  and concerns are all issues too, but they follow different handling paths.

Master the four issue types, understand when change control is triggered  and know which authority level applies at each decision point. That clarity translates directly into correct answers on scenario questions that trip up underprepared candidates.


**Frequently Asked Questions**

**Q1: What is the difference between an issue and a change request in PRINCE2 7?** 
An issue is any unplanned event that requires management action - it is the broader category. A change request, formally called a Request for Change, is one specific type of issue where someone proposes modifying an agreed project baseline. All change requests start as issues, but not all issues become change requests. The Practitioner exam tests this hierarchy regularly through scenario questions that ask candidates to classify events correctly before selecting the appropriate response.

**Q2: When does a Request for Change become an actual change in PRINCE2 7?** 
A Request for Change only becomes a formal change after it has been reviewed, assessed for impact  and approved by the appropriate authority - either the Project Manager within tolerance or the Project Board for larger modifications. Before approval, it remains an issue logged in the Issue Register. This timing distinction is one of the most commonly tested concepts in PRINCE2 Practitioner scenario questions and one of the most frequent sources of incorrect answers.

**Q3: What is an Off-Specification in PRINCE2 7 and how does it differ from a change request?** 
An Off-Specification describes a situation where a product or deliverable fails to meet its agreed quality criteria or specification. It is an issue type - not a change request - because it reflects something missing or failing rather than a proposal to modify a baseline. If the Project Board approves a formal deviation from the original specification to resolve the off-specification, that approval then triggers change control. The exam tests candidates on recognizing this two-stage process rather than treating the off-specification as an automatic change.



Issues vs Change Requests in PRINCE2 7 for Practitioner Exam