A project without a clear structure is like a football team with eleven goalkeepers - everyone is confused and nothing gets scored. The Organisation Theme solves this by defining who makes decisions, who manages the work, and who actually does the tasks. For your PRINCE2F exam, this theme is essential because it answers the single most important question: who is responsible for what?
Jump to a section
Your cousin's wedding. The main hall of a local hotel, decorated with fairy lights and centrepieces. The bride and groom (the Project Board) are not arranging chairs or tasting cake - they are making the big decisions: the budget, the date, the colour scheme, and when to say 'I do'. They meet once a month to check progress and approve any major changes, like switching from a sit-down dinner to a buffet.
The wedding planner (the Project Manager) runs the day-to-day. They book the caterer, chase the florist, manage the timeline, and report back to the couple. If the band cancels, the planner finds a replacement without bothering the bride and groom - unless the replacement costs an extra £500, which is outside the planner's authority.
The head chef, the florist, and the band leader are Team Managers. They each lead a small team doing specific work. The chef does not worry about the flower arrangements; the florist does not worry about the playlist. Each Team Manager is responsible for their own piece of the puzzle and reports progress to the wedding planner.
The key insight: the wedding succeeds because everyone knows their role. The bride and groom do not micro-manage the kitchen. The planner does not make decisions about the budget. The chef does not try to choose the dress. This clear separation of who decides, who does, and who manages is exactly how the PRINCE2 Organisation Theme works.
The Organisation Theme is the backbone of any PRINCE2 project. It answers two fundamental questions: who needs to be involved, and what are their responsibilities? Without this theme, a project would be chaotic - people would either do the same work twice or ignore critical tasks, assuming 'someone else' was handling them.
PRINCE2 defines three levels of management within a project. Think of them as layers in a cake: the top layer makes strategic decisions, the middle layer manages the day-to-day, and the bottom layer does the specialised work. These three layers are: the Project Board, the Project Manager, and the Team Managers.
The Project Board is the top tier. It is a group of people who represent three distinct interests: business, user, and supplier. The business interest (the Executive) ensures the project is worthwhile and stays within budget. The user interest (the Senior User) represents the people who will use the final product - they make sure it actually meets their needs. The supplier interest (the Senior Supplier) provides the resources and expertise to build the product and ensures the work is technically feasible.
The Project Board does not do the day-to-day work. They meet at key decision points - what PRINCE2 calls 'management stages' - to approve progress, authorise the next stage, or decide to stop the project. They are the 'what' and 'why' people, not the 'how' people.
The Project Manager sits in the middle. This person is the day-to-day leader of the project. They plan the work, assign tasks to team members, monitor progress, manage risks and issues, and report to the Project Board. The Project Manager is the glue that holds everything together. If the Project Board is the board of directors, the Project Manager is the chief executive who runs the operations.
Team Managers handle the actual execution. They lead the teams that build the product. In a software project, a Team Manager might be a lead developer. In a construction project, they might be the site foreman. Team Managers report to the Project Manager and are responsible for delivering their specific piece of work on time and to the required quality.
PRINCE2 also recognises other roles:
Project Assurance is a monitoring role. Someone (or a group) checks that the project is being run properly and that nothing is going wrong. They are independent of the Project Manager - they report directly to the Project Board. Think of them as the internal auditor.
Change Authority is a role that can approve certain changes without needing to call a full Project Board meeting. The Project Board delegates this authority for small, low-risk changes to keep the project moving quickly.
Project Support provides administrative help to the Project Manager. They might handle filing, scheduling meetings, or maintaining the project documents.
The Organisation Theme also introduces the concept of the Project Management Team, which includes all these roles working together. The key principle is that roles are defined, but people can hold multiple roles. A single person could be both the Project Manager and a Team Manager, or one person might hold all three Project Board roles in a very small project. But the responsibilities must still be distinct - a person cannot audit their own work (Project Assurance must be separate from Project Management).
Why does this matter for the PRINCE2F exam? Because the exam loves to test your understanding of who does what. You will get questions like 'Who approves the project plan?' or 'Who manages the team on a daily basis?' The answers depend on knowing exactly which role sits at which level. Remember the three layers: Board (strategic), Manager (tactical), Team (operational).
Define the Project Board
The first step in the Organisation Theme is appointing the three Board roles: Executive, Senior User, and Senior Supplier. These people are chosen because they have the authority and interest to make strategic decisions. Without this step, there is no one to approve the project's direction or to stop it if it fails.
Appoint the Project Manager
The Board selects a person to run the project day-to-day. This person must understand how to plan, monitor, and report. They will be the main point of contact between the Board and the teams. The Project Manager cannot be a Board member because that would cause a conflict of interest.
Identify work packages and assign Team Managers
The Project Manager breaks the project into smaller pieces of work called Work Packages. For each package, a Team Manager is assigned to lead the team doing the work. This step ensures that specialised work is managed by people with relevant expertise.
Set up Project Assurance
Someone independent is appointed to check that the project follows PRINCE2 properly and that risks are managed. This person reports directly to the Board. This step prevents the Project Manager from hiding problems or cutting corners.
Define authority levels and delegate Change Authority
The Project Board sets limits on what the Project Manager can decide without approval. They may also delegate a Change Authority to approve small changes. This step keeps the project moving quickly while retaining board control over major impacts.
Establish the communication and reporting structure
The Organisation Theme defines how information flows: Team Managers report to the Project Manager, the Project Manager reports to the Board, and Project Assurance reports to the Board independently. This step ensures everyone knows who to tell and when.
Let us walk through a realistic scenario: a medium-sized company, 'GreenTech Ltd', wants to build a new mobile app for customers to track their energy usage. The project is called 'EcoTrack'.
First, the company's senior executives decide to invest in the project. They appoint a Project Board. The Chief Financial Officer takes the Executive role because they control the budget. The Head of Customer Services takes the Senior User role because their team will support customers using the app. The Head of IT takes the Senior Supplier role because they provide the developers and infrastructure.
The Project Board then appoints a Project Manager, Sarah. Sarah has experience running IT projects but is not a developer herself. Her first job is to create the Project Initiation Documentation (PID), which includes the business case, the project plan, and the risk register.
Sarah then needs to structure the work. She splits the EcoTrack project into three work packages:
The 'Backend Development' work package, managed by a Team Manager named Raj. Raj leads five developers who build the server-side code that processes energy data.
The 'Mobile App Interface' work package, managed by a Team Manager named Mei. Mei leads two front-end developers and a designer who create the screens users see and interact with.
The 'Testing and Quality' work package, managed by a Team Manager named Carlos. Carlos leads three testers who check everything works correctly.
Each Team Manager receives a Work Package from Sarah - a formal document that describes what to do, how much it can cost, and the deadline. Sarah meets with each Team Manager weekly to review progress. If a Team Manager discovers a problem, they tell Sarah. Sarah decides whether she can handle it herself or if she needs to escalate to the Project Board.
One month in, Carlos discovers that the testing tool they planned to use is not compatible with the app. This is a risk that could delay the project. Sarah analyses the issue, finds a replacement tool that costs £2,000 extra, and since she has authority to spend up to £5,000 without Board approval, she authorises the purchase. She then updates the risk register and reports the decision to the Project Board at the next monthly meeting.
Project Assurance is performed by a senior IT auditor named Priya. Priya does not work on the project directly. She reviews Sarah's plans, checks that risks are being managed, and confirms that the project is following PRINCE2 guidelines. If Priya spots something concerning, she reports directly to the Project Board, bypassing Sarah entirely.
The Project Board meets at the end of each management stage. For EcoTrack, the stages are: Initiation, Design, Build, Test, and Launch. At the end of Design, the Board reviews Sarah's report on progress, budget, and quality. They approve the next stage - Build - by signing off the Stage Plan. They also consider whether any changes need Board approval. For example, if the users suddenly demand a new feature to compare energy usage with neighbours, that would be a change request that needs to go to the Board.
An IT professional working on this project knows exactly who to go to for decisions. A developer does not email the CFO directly. They tell their Team Manager, who tells Sarah, who tells the Board if needed. This chain of communication prevents chaos and ensures accountability.
The PRINCE2F exam tests the Organisation Theme heavily. Expect roughly 6-8 questions on this theme, covering roles, responsibilities, and the three levels of management.
Key exam topics:
The three primary roles on the Project Board: Executive (business), Senior User (user), Senior Supplier (supplier). Know which interest each represents and what each cares about.
The Project Manager's specific responsibilities: day-to-day management, producing plans, managing risks and issues, reporting to the Board, authorising Work Packages for Team Managers.
The difference between Project Assurance and Project Support. Project Assurance checks compliance and reports to the Board; Project Support provides admin help to the Project Manager.
The Change Authority role: who can approve changes without the full Board, and what limits they have.
The concept of the Project Management Team and how multiple roles can be combined (but Project Assurance must be separate from Project Management).
Common traps and patterns:
The exam will try to make you confuse the Executive with the Project Manager. Remember: the Executive owns the business case and has ultimate authority to stop the project. The Project Manager runs the project day-to-day.
Questions about who 'chairs' the Project Board are tricky. PRINCE2 does not assign a chairperson. The Executive typically leads, but the official answer is 'the Board runs by consensus, not by one person's authority.'
Questions about who approves the Project Plan: the Project Board approves the Project Plan, not the Project Manager. The Project Manager creates it.
The exam loves the term 'Work Package'. A Work Package is a document given by the Project Manager to a Team Manager. It defines what to do, the cost, and the deadline.
You will see questions about 'management stages' versus 'technical stages'. For the Organisation Theme, the key point is that the Project Board approves the end of each management stage.
Key definitions to memorise:
Executive: ultimate accountability for the project, owns the business case.
Senior User: specifies user needs, ensures the product meets those needs.
Senior Supplier: provides resources and expertise, ensures technical feasibility.
Project Manager: day-to-day leader, manages plans, risks, and team performance.
Team Manager: manages one specific team, reports to Project Manager.
Project Assurance: independent oversight, checks compliance, reports to Board.
Change Authority: delegated power to approve low-risk changes.
Project Support: administrative assistance to Project Manager.
Work Package: formal assignment of work to a Team Manager.
Correct answer pattern: When a question asks 'who is responsible for X', map X to the appropriate level. If X is strategic (budget, business case, stopping the project), it is the Board (specifically the Executive). If X is tactical (daily management, planning, reporting), it is the Project Manager. If X is operational (building the product, leading a team), it is the Team Manager.
The Organisation Theme defines three management levels: Project Board (strategic), Project Manager (tactical), and Team Manager (operational).
The Project Board has three roles: Executive (business), Senior User (user interests), and Senior Supplier (technical feasibility).
The Executive owns the business case and has ultimate authority to stop the project.
Project Assurance is an independent monitoring role that reports directly to the Project Board, not to the Project Manager.
The Project Manager creates the Project Plan and Work Packages, but the Project Board approves the Project Plan.
Multiple roles can be held by one person, but Project Assurance must always be separate from the Project Manager role.
The Change Authority is a person or group delegated by the Project Board to approve low-risk changes without a full Board meeting.
A Work Package is a formal document from the Project Manager to a Team Manager defining work, budget, and deadlines.
These come up on the exam all the time. Here's how to tell them apart.
Project Board
Provides strategic direction and approval for each stage
Does not handle day-to-day tasks or team management
Includes Executive, Senior User, and Senior Supplier
Project Manager
Runs the project day-to-day and manages the team structure
Creates plans, manages risks, and reports to the Board
Single role, not a group
Executive
Owns the business case and budget
Has ultimate authority to stop the project
Focuses on business value and return on investment
Senior User
Represents the people who will use the product
Ensures the product meets user needs and is usable
Focuses on functionality, training, and support
Project Assurance
Monitors compliance and checks for problems
Reports directly to the Project Board independently
Must be separate from Project Manager role
Project Support
Provides administrative help like scheduling and filing
Reports to the Project Manager
Can be part of the Project Manager's own team
Project Manager
Manages the entire project
Creates Work Packages and authorises work
Reports to the Project Board
Team Manager
Manages one specific team or work package
Receives and executes Work Packages
Reports to the Project Manager
Mistake
The Project Manager is in charge of the project and can make all decisions, including budget changes.
Correct
The Project Manager can only make decisions within authority limits set by the Project Board. Major decisions, especially budget changes, require Board approval.
Beginners see 'manager' and assume full control, but PRINCE2 deliberately limits PM authority to prevent one person from derailing the project.
Mistake
Project Assurance and Project Support are the same thing - both help the Project Manager.
Correct
Project Assurance monitors and checks the project independently, reporting to the Project Board. Project Support provides administrative help to the Project Manager.
The words 'assurance' and 'support' sound similar, and beginners group them together. But their roles are opposite in governance: one checks, one assists.
Mistake
The Senior User is always the person who will use the final product day-to-day.
Correct
The Senior User represents the interests of all users, including the people who will maintain, support, and operate the product - not just the end users.
Beginners think 'user' means the person clicking buttons, but in PRINCE2 it includes everyone whose work is affected by the product.
Mistake
In a small project, you can skip roles like Project Assurance because there aren't enough people.
Correct
Roles must still be fulfilled, but one person can hold multiple roles as long as they are not conflicting. Project Assurance must be separate from Project Management, but a single person can handle both Executive and Project Manager roles.
Beginners assume smaller means simpler rules, but PRINCE2 maintains governance principles regardless of size - you just combine roles carefully.
Mistake
The Project Board includes the Project Manager as a member.
Correct
The Project Manager is not a member of the Project Board. The Project Manager attends Board meetings to present and report, but does not vote or make Board decisions.
Beginners see everyone in a meeting and assume they are all equal members, but PRINCE2 separates the management from the decision-making body.
Mistake
Team Managers are optional; the Project Manager can manage all team members directly.
Correct
Team Managers are required when the project has multiple teams or specialised work. The Project Manager cannot effectively manage more than a few people and needs Team Managers to delegate.
Beginners think flat structures are more efficient, but PRINCE2 recognises that direct management of large teams is impractical, so Team Managers are a key role.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
The Executive is ultimately accountable. They own the business case and have the final say on whether the project continues or is stopped.
Yes, in a very small project, one person can be the Executive, Senior User, and Senior Supplier. However, this is risky because there is no independent check. PRINCE2 allows it but recommends against it.
The Project Manager runs the entire project day-to-day and reports to the Board. The Team Manager leads a single team working on one Work Package and reports to the Project Manager.
Yes, the Project Manager attends Board meetings to present progress reports and answer questions, but they are not a member of the Board and do not vote on decisions.
Only the Project Board, specifically the Executive, can decide to terminate a project early. The Project Manager can recommend it, but cannot make the decision.
A Work Package is a formal document given by the Project Manager to a Team Manager. It describes what work to do, the budget, the deadline, and the quality standards.
You've finished Organization Theme. Continue through the PRINCE2F study guide to build a complete picture of the exam.
Done with this chapter?