If you do not know how to manage the day-to-day work of a project, you will end up with a chaotic mess where no one knows what they should be doing or if they are on track. The Controlling a Stage process is the Project Manager's toolkit for supervising the work, handling problems as they come up, and reporting progress so the project doesn't go off the rails. It is the heartbeat of project delivery, turning the detailed Stage Plan into reality.
Jump to a section
A head chef in a busy restaurant kitchen. Their job is not to cook every dish themselves, but to make sure the evening service runs smoothly and successfully. They have a detailed plan for the evening's menu, broken down into courses (the stages of the project).
As the service begins, the head chef focuses on one stage: the main course service. Their control involves continuously monitoring the pass (the point where plates are finished). They check each plate before it goes out to the dining room. Is the steak cooked to the right temperature? Is the sauce drizzled correctly? Is the plate clean? This is the equivalent of the Project Manager checking the quality of completed work packages.
The head chef also manages the team of line cooks, each assigned specific dishes (work packages). The chef gives clear instructions (authorising work) and checks they have the right ingredients (resources). When a cook runs out of a key ingredient, like truffle oil, the chef must decide immediately: send a runner to the store (escalate an issue), adjust another dish, or remove a menu item (approve a corrective action). This is the day-to-day management and problem-solving of the stage.
Crucially, the head chef is constantly looking at the clock and the ticket orders. Can they get all 80 main courses out within 45 minutes without sacrificing quality? If not, they must take corrective action, like asking a cook to switch tasks. They are balancing the plan with the messy reality of the kitchen. At the end of the service, the head chef reports to the restaurant manager (the Project Board), summarising what was served, what challenges arose, and whether they are on track for the dessert course. This mirrors the regular Highlight Reports sent to the Project Board to keep them informed and in control.
The Controlling a Stage process is the Project Manager's main job from the moment a stage starts until it is completed. It is the day-to-day management of the work. While the Initiating a Project process gets everything set up, and the Managing a Stage Boundary process plans the next stage, Controlling a Stage is where the actual work gets done and monitored.
Think of the Stage Plan as your recipe for that stage. It tells you what work needs to be done, who will do it, how much it should cost, and when it should be finished. The purpose of Controlling a Stage is to make sure that the work is being carried out according to that plan. It involves authorising work to be done, monitoring that work, handling any problems, and reporting progress to the Project Board (the people ultimately responsible for the project).
The process has several key objectives that define what the Project Manager is trying to achieve:
Focus on delivery of the stage's products.
Keep the Project Board informed of progress.
Identify and manage issues and risks as they arise.
Take corrective action when things go wrong to keep the stage on track.
Escalate critical problems to the Project Board for a decision.
To achieve these objectives, the Project Manager performs a set of core activities. The first is to authorise work. This means officially giving a Team Manager or team member permission to start working on a specific piece of work called a Work Package. A Work Package is a set of instructions for one or more products to be created. It describes what needs to be built, when it needs to be done, how much it can cost, and what quality checks are needed.
Next, the Project Manager monitors the work. They review Checkpoint Reports from the team, which are short, regular reports on progress. They also look at other data like time recording systems or task boards. The goal is to constantly compare actual progress against the Stage Plan. Are they on time? On budget? Are the products being built correctly?
Another key activity is reviewing the situation. The Project Manager looks at the bigger picture: what issues have come up? What risks are about to happen? Are there any new risks or changes in the business environment? This review determines if any action needs to be taken.
When something goes wrong, the Project Manager must take corrective action. This could be something small, like re-assigning a person to a different task, or something bigger, like requesting a budget increase from the Project Board. If the problem is too big for the Project Manager to handle within their authority limits, they must escalate it to the Project Board. This escalation is often done through an Exception Report, which describes the problem, the options for fixing it, and the Project Manager's recommendation.
A huge part of this process is reporting. The Project Manager sends a regular Highlight Report to the Project Board. This report summarises the achievements since the last report, the next period's plan, and any issues or risks. It keeps the Project Board in control without them needing to ask for updates constantly.
Finally, the process includes receiving and reviewing completed Work Packages. The Project Manager checks that the finished products meet the agreed quality criteria. If they do, the products are approved and the work is formally closed. If not, the team must fix the issues.
In summary, Controlling a Stage is a continuous cycle of authorising work, monitoring it, reviewing the situation, reporting, and taking action. It ensures the stage stays within its tolerances (the permitted deviation from the plan) and that the Project Board can step in before a small problem becomes a disaster. It replaces a hands-off management style where a Project Manager simply gives out work at the start of the stage and waits for the end result, which is a recipe for failure.
Authorise Work Packages
The Project Manager gives formal permission to the Team Manager to start a specific piece of work. This is done by creating and agreeing on a Work Package document that defines what must be produced, to what quality, by when, and for how much.
Review Work Package Status
The Project Manager regularly checks how the work is progressing by reviewing Checkpoint Reports (from the team) and other monitoring data. This is how they compare actual progress against the Stage Plan.
Review the Situation
The Project Manager looks at the whole stage—issues logged, risks that are starting to happen, any changes in the business environment—to decide if any action is needed. This is a periodic check of the health of the stage.
Take Corrective Action
If the Project Manager identifies a problem, they decide what to do. This might be a small adjustment (like reassigning a person) or a major escalation (sending an Exception Report to the Project Board) if the issue exceeds their tolerance.
Report Progress to Project Board
The Project Manager sends a Highlight Report to the Project Board at regular intervals (e.g., weekly). This report summarises achievements, next steps, and any issues or risks, keeping the board in the loop without overwhelming them with detail.
Review and Close Work Packages
When the team finishes a Work Package, the Project Manager checks the completed products against the quality criteria from the Work Package. If it passes, the Work Package is formally accepted and closed. If not, the team must correct any defects.
An IT professional acting as a Project Manager on a software development project would use the Controlling a Stage process constantly. Let's walk through a realistic scenario.
Imagine the project is to build a new mobile banking app for a regional bank. The current stage is the 'Development and Unit Testing' stage. The Stage Plan says it will take 6 weeks, cost £50,000, and produce the core login, balance check, and transaction history modules.
The Project Manager starts the week by calling a quick stand-up meeting with the two development teams. They authorise two Work Packages:
- Work Package 1: 'Build Login Module' (assigned to Team A). - Work Package 2: 'Build Balance Check Module' (assigned to Team B). Each Work Package documents the specific requirements, the quality criteria (e.g., all code must pass static analysis, must handle 1000 concurrent users), and the deadline (2 weeks). The teams agree and start work.
Mid-week, the Project Manager receives a Checkpoint Report from Team A's Team Manager. The report says they are on time but have hit a technical hurdle: a new security rule from the bank means the login must use multi-factor authentication (MFA), which was not originally planned. The team estimates this will add 3 days to their work.
The Project Manager now needs to review the situation. They check the Stage Plan's tolerances. The plan allows for a 5% time overrun (about 1.5 days) and a 10% cost overrun (£5,000). The 3-day delay exceeds the time tolerance. The Project Manager cannot approve this change themselves.
The Project Manager then takes corrective action. They calculate the impact: the delay will push the end of the stage from week 6 to week 6.5, which is outside tolerance. They must escalate to the Project Board. They write an Exception Report detailing the problem (the MFA requirement), the cause (new bank security policy), the options (option A: accept the delay, option B: cut a less important feature from this stage, option C: add extra developer resource to the login team). The Project Manager recommends Option A and explains why. They submit the Exception Report to the Project Board.
Later in the same week, the Project Manager reviews the weekly Highlight Report. They note that Team B is ahead of schedule on the Balance Check module, so they ask if they can start on the 'Transaction History' Work Package a week early. The Project Board approves this forward planning in their next meeting.
At the end of the stage, Team A completes the Login Module with MFA. The Project Manager reviews the completed Work Package. They run the quality checks specified in the Work Package: code review passes, security scan passes, performance test passes. The product is formally accepted. The Project Manager then closes the Work Package, records the actual time and cost, and prepares for the Managing a Stage Boundary process to plan the next stage.
Throughout this example, the Project Manager is constantly:
Authorising work via Work Packages.
Monitoring progress via Checkpoint Reports.
Reviewing the situation (the MFA issue).
Taking corrective action (escalating via Exception Report).
Reporting to the Project Board via Highlight Reports.
Reviewing completed Work Packages.
The PRINCE2F exam will test your understanding of the Controlling a Stage process quite directly. Expect questions that ask you to identify its purpose, its objectives, and its key activities. The exam loves to see if you can distinguish this process from the others, especially Managing a Stage Boundary and Directing a Project.
Here are the specific things you need to know for the exam:
Key concepts you must memorise:
The purpose: To monitor and control the work of a stage, handle issues, and report to the Project Board.
The objectives: Focus on delivery, keep the board informed, manage issues/risks, take corrective action, escalate.
The key activities: Authorise work packages, monitor work, review the situation, report progress, take corrective action, review completed work packages.
Trap patterns the exam uses:
Confusing 'Controlling a Stage' with 'Managing Product Delivery'. The latter is the Team Manager's process of actually doing the work and reporting completion. The former is the Project Manager's process of managing the stage. Practice questions often mix up management processes versus delivery processes.
Mixing up 'Issue' and 'Risk'. In this process, issues are problems that have already happened (e.g., a developer is sick). Risks are potential future problems (e.g., a key supplier might go bankrupt). The Controlling a Stage process handles both, but the exam may ask which one requires an Exception Report if it exceeds tolerance.
The 'Exception Report' trap: The exam might ask who prepares it (the Project Manager) and who receives it (the Project Board). The purpose is to escalate a situation that is beyond the Project Manager's tolerance limits. It is not a regular report; it is only used when things go wrong.
The 'Highlight Report' trap: This is a regular, periodic report from the Project Manager to the Project Board. It summarises progress. The exam might ask how often it is sent (the answer: as often as defined in the Communication Management Strategy, not daily or monthly by default).
Exam topics they love to test:
Work Packages: What do they contain? (Product description, quality criteria, budget, time). Who can update them? (Only the Project Manager, with the Team Manager's input).
The sequence of activities: Authorise work -> monitor -> review -> report -> take corrective action -> complete work packages.
Tolerances: The Project Manager operates within the tolerances set by the Project Board. If an issue goes over tolerance, the Project Manager must escalate. This is a common exam question.
Inputs and Outputs: Know that the Stage Plan is an input, and outputs include Highlight Reports, Exception Reports, and completed Work Packages.
A typical exam question might be: 'What is the first activity the Project Manager performs at the beginning of a stage?' The correct answer is to 'Authorise Work Packages'.
Another common question: 'Which report does the Project Manager use to escalate a problem that cannot be solved within tolerance?' The answer is the Exception Report.
Controlling a Stage is the Project Manager's process for monitoring and managing the work within a stage, not doing the work themselves.
The first activity in Controlling a Stage is to authorise Work Packages to the team.
The Project Manager must escalate to the Project Board using an Exception Report when an issue or risk exceeds the stage's tolerances.
Highlight Reports are regular updates from the Project Manager to the Project Board to keep them informed of progress.
Work Packages contain the product descriptions, quality criteria, budget, and time for a specific piece of work.
The Project Manager reviews completed Work Packages to ensure quality criteria are met before accepting the products.
Controlling a Stage handles both issues (problems that have happened) and risks (potential future problems).
The process is a continuous cycle: authorise, monitor, review, report, take corrective action, complete work packages.
These come up on the exam all the time. Here's how to tell them apart.
Controlling a Stage
Focuses on the current stage's day-to-day work.
Involves reporting progress and handling issues.
Happens during the stage execution.
Managing a Stage Boundary
Focuses on planning the next stage and reviewing the current stage.
Involves producing an End Stage Report and a Stage Plan for the next stage.
Happens at the end of a stage, just before moving to the next.
Highlight Report
Sent regularly (e.g., weekly) to keep the board informed.
Covers routine progress, achievements, and minor issues.
Does not require a change in stage plan.
Exception Report
Sent only when a problem exceeds stage tolerances.
Describes a serious issue and options for recovery.
Requires a decision from the Project Board to proceed.
Work Package
A formal instruction to a team to produce one or more products.
Includes budget, time, quality criteria, and reporting requirements.
Is agreed between Project Manager and Team Manager.
Product Description
Describes the detailed characteristics of a single product.
Is part of a Work Package, not the whole package itself.
Is used to define what needs to be built, not how to manage the work.
Issue (in PRINCE2)
A problem that has already occurred (e.g., a team member is ill).
Requires immediate corrective action.
Can lead to an Exception Report if it exceeds tolerance.
Risk (in PRINCE2)
A potential future problem (e.g., a key supplier might go bankrupt).
Requires proactive management to reduce probability or impact.
Is logged and reviewed in the Risk Register, not an Exception Report.
Mistake
The Project Manager does all the work themselves during Controlling a Stage.
Correct
The Project Manager manages the work; they authorise, monitor, and report. The actual building or creation is done by the team (Team Manager) via the Managing Product Delivery process.
Beginners often think 'management' means hands-on work. In PRINCE2, management and delivery are separate roles.
Mistake
Controlling a Stage is only about fixing problems.
Correct
It is also about monitoring progress, authorising work, and reporting success. The process is proactive and continuous, not just reactive.
People focus on the dramatic 'issue handling' part and forget the routine monitoring and reporting that prevents issues.
Mistake
The Project Board gets involved in day-to-day work during this process.
Correct
The Project Board is not involved in daily management. They are kept informed via Highlight Reports and only step in when an Exception Report is raised or a decision is needed.
The name 'Controlling a Stage' sounds like the board controls it, but really the Project Manager controls it within set tolerances.
Mistake
Work Packages are only created at the start of a stage.
Correct
Work Packages can be authorised throughout the stage as work is needed, depending on the stage plan. They are not necessarily all created on day one.
Beginners assume a fixed, one-time assignment, but projects often authorise work in sequence as team capacity becomes available.
Mistake
The Highlight Report is sent after every stage.
Correct
Highlight Reports are sent periodically during the stage (e.g., weekly), not just at the end. The end-of-stage report is the End Stage Report.
The word 'report' is generic, so learners confuse the different types of reports. The exam tests the distinction.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Controlling a Stage is the Project Manager's process of managing the overall stage. Managing Product Delivery is the Team Manager's process of actually doing the work and reporting completion. The Project Manager does not do the building.
The Project Manager writes the Exception Report. It is sent to the Project Board when a problem exceeds the stage's tolerances and the Project Manager cannot fix it alone.
A Work Package is a set of instructions given to a team to produce one or more products. It includes what to build, the quality standards, the budget, and the deadline.
The frequency is defined in the Communication Management Strategy for the project. It is typically weekly or monthly, but not daily.
The Project Manager does not accept the product. They require the team to fix the defects. The Work Package is only closed once the products meet the agreed quality criteria.
No, the Project Board must review Highlight Reports to stay informed. If they do not, the Project Manager cannot be sure the board is in control, and the project risks losing direction.
You've finished Controlling a Stage Process. Continue through the PRINCE2F study guide to build a complete picture of the exam.
Done with this chapter?