One of PRINCE2’s greatest strengths is its clarity around accountability.
Unlike many project environments where responsibilities are vague or shared by default, PRINCE2 defines who is responsible for what — and at what level.
Importantly, PRINCE2 defines roles, not job titles. One person may perform multiple roles on a small project, or roles may be distributed across many people on a large or complex initiative. What matters is that each role is clearly assigned and understood.
Why PRINCE2 Roles Matter
When PRINCE2 roles are not clearly defined, projects typically experience:
- Slow or blocked decision-making
- Unclear escalation paths
- Weak ownership of risks and benefits
- Blurred accountability between business and delivery
PRINCE2 roles exist to ensure:
- Strategic decisions sit at the right level
- Day-to-day management is delegated appropriately
- Delivery responsibility is clear
- Independent assurance is maintained
The PRINCE2 Project Board
The Project Board is accountable for the success of the project. It provides direction, approves key decisions, and ensures the project remains viable.
The Project Board is made up of three distinct roles.
Executive
- Ultimately accountable for project success
- Owns the Business Case
- Ensures the project delivers value for money
- Balances business, user, and supplier interests
💡 In government projects, this role is often held by a Director, Executive Director, or senior responsible officer.
Senior User
- Represents the needs of those who will use the project’s outputs
- Defines acceptance criteria
- Ensures expected benefits are realised
💡 For example, a clinical director representing hospital staff affected by a facility upgrade.
Senior Supplier
- Represents those designing, building, or delivering the solution
- Confirms technical feasibility and resourcing
- Ensures deliverables meet quality expectations
💡 This may be an internal technical lead or an external contractor representative.
The Project Manager
The Project Manager runs the project on behalf of the Project Board.
Key responsibilities include:
- Planning and controlling day-to-day delivery
- Managing risks, issues, and change
- Producing reports (e.g. Highlight Reports)
- Escalating by exception when tolerances are exceeded
The Project Manager does not own the Business Case — they manage delivery within the boundaries set by the Project Board.
Team Manager(s)
Team Managers are responsible for delivering specific outputs or work packages.
Key responsibilities include:
- Accepting Work Packages from the Project Manager
- Managing team-level delivery
- Ensuring outputs meet agreed quality criteria
- Reporting progress back to the Project Manager
💡 On smaller projects, the Project Manager may also perform the Team Manager role.
Project Assurance
Project Assurance provides independent confidence to the Project Board that the project is being run properly.
PRINCE2 defines three assurance perspectives:
- Business Assurance – Is the project still viable?
- User Assurance – Will outputs meet user needs?
- Supplier Assurance – Are technical solutions sound?
Assurance is independent of the Project Manager and may be performed by one or more people.
Project Support
Project Support provides administrative and specialist support to the project.
This may include:
- Maintaining registers and logs
- Supporting reporting
- Configuration management
- Tool and system support
Project Support is often provided by a PMO, but the role may not exist on very small projects.
Roles Can Be Combined — Responsibilities Cannot
PRINCE2 allows flexibility in how roles are resourced, but not in whether responsibilities exist.
For example:
- One person may act as Executive and Senior User on a small project
- A Project Manager may also act as Team Manager
- Assurance roles may be combined
What matters is that:
- Accountability is explicit
- Decision authority is clear
- Escalation paths exist
| Role | Primary Responsibility |
|---|---|
| Executive | Owns Business Case and project success |
| Senior User | Represents users and benefits |
| Senior Supplier | Ensures technical feasibility and quality |
| Project Manager | Manages day-to-day delivery |
| Team Manager | Delivers specific outputs |
| Project Assurance | Provides independent oversight |
| Project Support | Provides admin and tool support |
Key Takeaways
- PRINCE2 roles create clear governance and accountability
- Roles define responsibilities, not job titles
- Small projects can combine roles; large projects must separate them
- Clear role definition prevents delays, confusion, and risk
Next Steps
If your projects struggle with slow decisions, unclear ownership, or weak escalation, reviewing PRINCE2 roles is often the fastest way to improve control.
Fill in the form below to download the free Project Kick-Off Checklist, which includes prompts to confirm governance roles, decision authority, and escalation paths at the start of a project.
If you want ready-to-use, government-aligned documents, the PRINCE2 Starter Kit provides practical templates that help you assign roles, maintain governance, and apply PRINCE2 proportionately across projects of any size.
You Might Also Like
If you’re building your understanding of PRINCE2 governance, you may also find The 7 Themes of PRINCE2 – Practical Examples useful for understanding the core management areas that run throughout the project lifecycle.
To see how PRINCE2 flows from initiation to closure, The 7 Processes of PRINCE2 – Step by Step explains how roles interact at each stage of delivery.
If you’re unsure how much PRINCE2 is “enough,” Tailoring PRINCE2 – What You Can and Can’t Adapt explores how to scale roles and controls without losing governance.
