In PRINCE2 7, Change Authority and Delegated Authority are important concepts linked to the Organizing practice and the management of a project's governance structure. The Project Board holds overall accountability for the project, but it cannot always handle every decision itself. To maintain effi…In PRINCE2 7, Change Authority and Delegated Authority are important concepts linked to the Organizing practice and the management of a project's governance structure. The Project Board holds overall accountability for the project, but it cannot always handle every decision itself. To maintain efficiency, the board may assign certain responsibilities to other roles, which is where delegated authority becomes relevant.
Change Authority is a role, or sometimes a group, to whom the Project Board delegates the responsibility for reviewing and approving requests for change and off-specifications, up to a defined limit. Rather than referring every change to the full Project Board, the Change Authority can make these decisions within agreed boundaries. This helps the project respond to changes efficiently while keeping control. The Change Authority operates within a change budget, which sets the financial limit for approving changes. If a change exceeds this limit or the authority's scope, the matter is escalated to the Project Board.
Delegated Authority refers to the broader principle of passing down decision-making powers through the project management structure. The Project Board delegates day-to-day management to the Project Manager, who in turn may delegate the management of work packages to Team Managers. Each level operates within defined tolerances, which are permissible deviations around time, cost, scope, quality, risk, and benefits. As long as the delegated person stays within these tolerances, they can proceed; if a tolerance is forecast to be exceeded, the issue is escalated upward.
Together, these concepts support the principle of 'manage by exception', allowing senior managers to focus on strategic oversight while empowering others to handle routine matters. By clearly defining who can make which decisions and within what limits, PRINCE2 ensures accountability, efficient decision-making, and appropriate escalation, which strengthens the overall governance and organization of the project throughout its lifecycle and stages.
Change Authority and Delegated Authority in PRINCE2 Practitioner V7
Why Change Authority and Delegated Authority Matter
In any project, changes are inevitable. Requirements evolve, stakeholders request enhancements, and issues arise that need resolution. Managing these changes efficiently is crucial to keeping the project on track. This is where the concepts of Change Authority and Delegated Authority become essential within the PRINCE2 framework.
Understanding these concepts helps ensure that decisions about changes are made at the appropriate level, preventing bottlenecks and empowering the right people to act. It supports the PRINCE2 principle of manage by exception, allowing senior managers to focus on strategic matters while routine decisions are handled lower down the chain.
What is Change Authority?
A Change Authority is a person or group to whom the Project Board may assign responsibility for reviewing and approving (or rejecting) requests for change and off-specifications. Rather than referring every single change to the Project Board, the board can delegate this responsibility to make the process more efficient.
The Change Authority operates within defined limits known as a change budget. This budget represents the amount of money the Change Authority is permitted to spend on approved changes before needing to escalate decisions to a higher level.
What is Delegated Authority?
Delegated Authority refers to the broader mechanism by which responsibility and decision-making power are passed down through the management levels of a project. PRINCE2 defines four levels of management:
- Corporate, programme management or the customer - Directing (Project Board) - Managing (Project Manager) - Delivering (Team Manager)
Each level delegates authority to the level below, along with corresponding tolerances. These tolerances define the limits within which each level can operate before they must escalate to the level above.
How It Works
The Project Board holds overall authority for the project but cannot be involved in every minor decision. To enable smooth operation, the board sets tolerances for the Project Manager across six aspects: time, cost, quality, scope, benefits, and risk.
When it comes to changes, the Project Board can either handle change requests themselves or appoint a Change Authority to deal with them within an agreed change budget. If a proposed change would exceed the change budget or the Change Authority's remit, the matter is escalated upward.
Similarly, the Project Manager delegates work to Team Managers through Work Packages, each with its own set of tolerances. If a Team Manager forecasts that a tolerance will be exceeded, they raise an issue to the Project Manager.
This layered approach ensures that each decision is made at the most suitable level, keeping the project agile while maintaining proper control and governance.
Key Points to Remember
- The Project Board may delegate change decisions to a Change Authority. - A change budget sets the financial limit for the Change Authority. - Tolerances enable each management level to make decisions within set boundaries. - When tolerances are forecast to be exceeded, the issue must be escalated. - Delegation supports the manage by exception principle.
Exam Tips: Answering Questions on Change Authority and Delegated Authority
1. Know who can be the Change Authority. Remember that the Project Board can appoint a person or group as the Change Authority, or it may choose to retain this role itself. Watch for scenarios where the board delegates this to keep the project moving.
2. Link change budget to the Change Authority. Exam questions often test whether you understand that the Change Authority operates within a defined change budget. If a change exceeds this budget, it should be escalated to the Project Board.
3. Connect delegation to tolerances. Many questions will describe a situation where a tolerance is forecast to be exceeded. The correct response usually involves escalating the matter to the next management level, rather than making the decision alone.
4. Apply the manage by exception principle. When a scenario asks about efficient decision-making, consider how delegation and tolerances allow higher levels to be involved only when necessary.
5. Read scenario-based questions carefully. Identify which management level is involved and what authority they hold. The answer often depends on recognising whether a decision falls within someone's delegated remit.
6. Watch for escalation triggers. Any forecast breach of tolerance or budget is a signal that escalation is required. Choose answer options that reflect proper escalation procedures.
By mastering these concepts and practising scenario-based questions, you will be well prepared to handle any exam items relating to Change Authority and Delegated Authority confidently.
