In the context of the PRINCE2 7 'Controlling a Stage' process, the activity 'Take corrective action' represents the practical application of the Project Manager's authority to keep the stage within agreed limits. This activity is triggered when monitoring reveals a deviation from the Stage Plan—suc…In the context of the PRINCE2 7 'Controlling a Stage' process, the activity 'Take corrective action' represents the practical application of the Project Manager's authority to keep the stage within agreed limits. This activity is triggered when monitoring reveals a deviation from the Stage Plan—such as a delay reported in a Checkpoint Report or a newly identified issue—that requires intervention but is currently forecast to remain within stage tolerances.
The Project Manager analyzes the deviation to determine the most effective response. The goal is to solve the problem at the stage level without burdening the Project Board, adhering to the principle of 'Management by Exception.' Corrective actions might include rescheduling tasks, adjusting resource allocations within the team, or addressing a small scope change if a change budget is available and authorized.
If the Project Manager determines that the corrective action will resolve the issue while keeping the stage within its time, cost, quality, scope, benefit, risk, and sustainability tolerances, they proceed to update the Stage Plan and Issue Register and issue new Work Packages if necessary. This autonomy is crucial for efficient project flow.
However, this activity is strictly bounded by tolerance. If the analysis shows that the necessary corrective action would cause a breach of stage tolerances, the Project Manager cannot simply 'take action.' Instead, they must immediately escalate the situation by raising an Exception Report for the Project Board to consider. Thus, 'Take corrective action' is the mechanism for solving day-to-day problems, ensuring the stage remains viable and aligned with the business case.
PRINCE2 Practitioner v7 Guide: Controlling a Stage - Take Corrective Action
Overview In the PRINCE2 method, Take Corrective Action is a critical activity within the Controlling a Stage process. It serves as the mechanism by which the Project Manager (PM) acts on deviations, issues, and risks to ensure the stage remains on track regarding time, cost, quality, scope, benefits, and risk.
Why is it Important? Projects rarely go exactly according to the initial plan. Without this activity, small deviations would accumulate, inevitably causing the stage to breach its tolerances. This activity empowers the Project Manager to solve problems proactively without constantly interrupting the Project Board, provided the solution fits within the agreed limits. It is the practical application of the principle Manage by Exception.
What is it? It is the execution phase of issue and risk management. Once the Project Manager has gathered information (Review Work Status) and analyzed the impact (Capture and Examine Issues and Risks), they must act. Take Corrective Action is the implementation of the chosen solution to resolve the issue or mitigate the risk.
How it Works The workflow depends entirely on Tolerances: 1. Assess the Deviation: The PM identifies that an issue has arisen or a risk has materialized. 2. Compare against Stage Tolerance: The PM calculates if the solution will push the stage beyond its agreed time, cost, or scope limits. 3. Select the Path: - Within Tolerance: If the PM can solve the issue without exceeding stage tolerances, they implement the corrective action immediately. This involves updating the Stage Plan and potentially issuing new or modified Work Packages to the Team Managers. - Exceeds Tolerance (Forecast): If the issue creates a forecast that stage tolerances will be breached, the PM cannot take corrective action locally. They must trigger the escalation procedure by creating an Exception Report and submitting it to the Project Board.
How to Answer Questions on 'Take Corrective Action' In the Practitioner exam, scenario-based questions will describe a problem occurring during a stage. To select the right answer, follow this logic:
1. Determine Authority (Tolerance): Calculate or look for clues regarding whether the fix is expensive or time-consuming. Does it fit in the tolerance? 2. Identify the Action: - If Inside Tolerance: The answer usually involves "Updating the Stage Plan" or "Issuing a Work Package." - If Outside Tolerance: The answer involves "Creating an Exception Report" or "Escalating to the Project Board." 3. Check for Change Authority: If the corrective action involves a Request for Change (RFC), check if the PM has a delegated Change Budget. If not, the PM must seek approval from the Change Authority before taking action.
Exam Tips: Answering Questions on Take Corrective Action Tip 1: Forecast vs. Actual PRINCE2 is proactive. You do not wait for the stage to actually go over budget. If you forecast a breach of stage tolerance, you stop and escalate immediately. Avoid answers that suggest "waiting to see" or "trying to fix it anyway."
Tip 2: The Exception Report Trigger If the scenario states the PM is taking corrective action but realizes the stage will be delayed beyond the limit, the only valid output is the Exception Report. Distinguish this from an Issue Report (which is used to analyze the problem initially) or an End Stage Report (used for routine closure).
Tip 3: Don't Confuse with Directing a Project Take Corrective Action is a PM task. If an answer option suggests the PM "approves the exception plan," this is wrong. The PM creates the Exception Plan (in the Managing a Stage Boundary process) only after the Project Board has reviewed the Exception Report and requested a plan.