PRINCE2 7 Foundation · Study lesson 25
Recognise a changed situation
Capture issues without assuming that every issue requires a baseline change.
9 minute study lesson · Practices · Original learning material
What you will understand
- Distinguish issues from uncertain future events.
- Recognise requests for change, off-specifications, problems and opportunities.
- Explain why approved baselines support meaningful control.
The idea
A stakeholder’s concern, an unexpected offer and a failed product check can all need attention. They do not all justify changing the project. The issues practice makes it safe to surface relevant events and concerns, assess what they mean and control any resulting change. Welcoming information and protecting authorised baselines are complementary responsibilities.
An issue is a relevant situation or unplanned event requiring management attention. It may concern an immediate problem, a concern whose timing or effect needs assessment, an external event, a business opportunity, a request for change or an off-specification. Version 7 deliberately treats issue management more broadly than changing documents. Capture what has been raised and assess it rather than dismissing it because no change request form exists.
A request for change proposes an alteration to an approved baseline. For example, users may request an additional reporting function after the agreed product scope has been authorised. The request is not approved merely because it is sensible, inexpensive or raised by a senior person. Its effects and the decision authority still need consideration. A question about an existing requirement may need clarification without changing a baseline at all.
An off-specification identifies that something required is not, or is forecast not to be, provided as agreed. A data export missing a mandatory field is an example. This differs from asking for a new field that was never required. Assessment may lead to correction, a proposed change or an authorised concession where permitted. The classification describes the deviation; it does not settle the decision or excuse the unmet requirement.
A business opportunity can arise from an unexpected positive development, such as a partner offering access to a useful facility. A problem may already have an immediate negative effect, while a concern needs assessment before its consequences are clear. An uncertain future event belongs in risk management; a realised event needs issue attention and may create new risks. These distinctions help select useful actions rather than force every situation into one rigid label.
A baseline is an approved reference used for comparison and control, such as an authorised plan or product description. Approval does not make it permanently unchangeable. It means that changes require the agreed authority and a traceable record. The issue management approach defines procedures and responsibilities. The issue register records issues being managed formally, while an issue report provides the analysis needed for a particular significant issue. Minor matters can be handled proportionately using agreed arrangements rather than escalating every observation to the board.
An issue needs assessment
| Issue | What to examine |
|---|---|
| A request for change | The proposed alteration to an approved baseline. |
| An off-specification | A product that fails, or is forecast to fail, its agreed specification. |
| A problem or concern | The situation and its possible implications. |
| A business opportunity | The advantage available and the effect on the project. |
| All issues | Who needs to decide and whether the baseline actually changes. |
An original fictional example
Fictional example: a neighbourhood printing studio
A studio’s new booking tool is required to issue accessible confirmations. Testing shows it cannot. Separately, a nearby college unexpectedly offers shared training space, and a volunteer asks whether an existing confirmation can be resent. The team initially labels all three matters as requests for change.
The decision
Assess the unmet confirmation requirement as an off-specification, the college offer as a possible business opportunity and the resending question first as a clarification or operational matter.
Why it makes sense
Each matter needs a response matched to its effect. None becomes an approved baseline change simply by being raised.
A common confusion
The mistaken idea: Every issue is a request to change the project.
The distinction: Issues include different types of situations requiring attention. Assessment determines whether a baseline change is appropriate or whether another response resolves the matter.
Capture the issue; determine the change.
Points to remember
- A missing agreed requirement differs from a request for something additional.
- A baseline is approved and controlled, rather than permanently frozen.
- Positive developments can require issue management too.
Your takeaway
Capture issues openly and classify them carefully. Use approved baselines to distinguish a missing commitment from a proposed addition, then assess the consequences before deciding whether any change should occur.
This independently written explanation is supplementary study material. It is not official examination content. Read about our content and its limitations.