The project context: organizations and management layers

Every project is commissioned by someone, for some purpose, inside some organization. Before a project manager can lead people, they need to understand who those people are, where they sit and what authority they hold. PRINCE2 describes this through the idea of a commissioning organization and four layers of management: business, directing, managing and delivering. This lesson explains those layers in people terms, shows how they connect to the organizational and project ecosystems introduced in lesson 1, and works through the kinds of context questions that appear in exam scenarios.

The commissioning organization

The commissioning organization is the organization that asks for the project and provides its mandate. It may be a single company, a government department, a charity, a joint venture or a group of organizations acting together. Within it, someone with sufficient authority decides that a project is needed and appoints an executive. That person or body sits in the business layer. They are not part of the project management team, but they set the boundaries within which the project operates: the strategic objectives it must support, the standards it must follow, the overall tolerances it is given and the governance it must report to.

In a large organization the business layer might be a portfolio board, an investment committee or a program management office. In a small business it might simply be the owner. In a public body it might include a deputy minister, a cabinet committee or an agency head. Whatever its form, the business layer is the level to which the project board escalates when a project-level tolerance is forecast to be exceeded. It is also the level that receives the project's benefits and that remains in place long after the project has closed.

The four layers in people terms

Each layer has a different relationship with the project and different people concerns. Understanding those concerns helps the project manager predict what each layer will want to know and how it will react.

Note that the delivering layer is where most people on a project actually work, yet it is often the layer least represented in governance discussions. PRINCE2 7 encourages project managers to involve team managers and team members in planning and estimating, partly because they know the work best and partly because people who help shape a plan are more committed to delivering it.

Management by exception across the layers

Each layer sets tolerances for the layer below and manages by exception. The business layer sets project tolerances for the board. The board sets stage tolerances for the project manager. The project manager sets work package tolerances for team managers. As long as forecasts stay within tolerance, the lower layer gets on with the work and reports progress. When a forecast breach appears, the issue moves up one layer. This structure is efficient because senior people only need to engage with matters that genuinely require their authority.

The people side of this mechanism is easy to overlook. Team managers who fear blame may delay reporting a forecast breach until it has grown. Project managers who want to look capable may absorb problems that should be escalated. Boards that react angrily to exceptions teach the layers below to hide them. The structure works only when each layer treats an escalation as the system working correctly, not as a failure.

The organizational and project ecosystems revisited

Lesson 1 introduced two ecosystems. The four layers help us place people within them. The business layer belongs firmly to the permanent organization. The delivering layer is often made up of people on loan from permanent departments or from supplier organizations. The directing and managing layers sit at the interface, which is why board members and project managers spend so much of their time managing relationships in both directions.

Mapping both ecosystems early is good practice. A simple map lists the organizations involved, the key people in each, their relationship to the project and the channels through which the project will interact with them. That map then feeds the communication management approach, the stakeholder engagement work in lesson 7 and the change impact assessment in lesson 5.

Corporate, program and portfolio context

Many projects are not standalone. They sit within a program, which coordinates several projects to deliver a larger transformation, or within a portfolio, which balances an organization's investment across many initiatives. When a project is part of a program, some responsibilities shift. The program may provide the business case framework, own the benefits, set standards for reporting and supply shared resources. The project executive may be a program manager or a business change manager. PRINCE2 expects these arrangements to be agreed and recorded when the project is initiated.

Context in different sectors

The business layer looks different across sectors. In the Government of Canada, the Treasury Board Policy on the Planning and Management of Investments and the Directive on the Management of Projects and Programmes set expectations for governance, and departments assess project complexity and risk to decide which approvals are needed. Provincial and municipal governments have their own frameworks. In a federally regulated business, the board of directors and executive committee form the top of the business layer. In a charity, a volunteer board may play that role, with funders imposing reporting conditions. Each of these shapes who the executive answers to and what tolerances the board receives.

For exam purposes you do not need to know sector-specific frameworks. You do need to recognize that the business layer exists, that it is outside the project management team, that it sets project tolerances and that the board escalates to it when project tolerances are forecast to be exceeded.

Organizational culture as context

Context is not only structure. Each organization has a culture: shared assumptions about how decisions are made, how much risk is acceptable, whether bad news is welcome and how formal communication should be. A project in a hierarchical, risk-averse organization will need more formal approvals and more careful communication than one in a flat, experimental start-up. When several organizations work together, their cultures may clash. A supplier used to fast decisions may become frustrated with a customer whose approvals take weeks.

The project manager cannot change an organization's culture, but can read it and adapt. That might mean scheduling board decisions to fit the commissioning organization's committee calendar, writing reports in the style senior managers expect, or agreeing explicit ways of working when organizations with different cultures form a joint team. These adaptations are part of tailoring, which we return to in lesson 10.

Context changes during the project

The context is not fixed at initiation. A reorganization may move the executive to a new role, a program may be paused, a supplier may be acquired or a new regulation may arrive. Each of these changes the layers, the relationships or the constraints. Stage boundaries are the natural time to ask whether the context has shifted: is the business layer still the same, does the executive still hold the authority the role needs, are the suppliers and their key people still in place, and have new stakeholders appeared? Where the answer is no, the project manager should update the context map, the communication management approach and, if needed, the project management team structure, and ask the board to approve the changes.

A change of executive deserves particular care. The new executive inherits a business case they did not write and decisions they did not make. A short handover meeting with the outgoing executive, a review of the business case and tolerances, and a fresh onboarding conversation help the new executive take genuine ownership rather than simply continuing whatever was decided before. Without this, a project can drift for months under an executive who does not feel accountable for it.