Project Organisation, Roles and Accountability

Control guidance

Why a temporary organisation is needed

Projects cut across permanent functions and create decisions that normal line structures may not allocate clearly. The project organisation provides a temporary hierarchy of accountability for the investment and its products. It does not replace corporate authority, employment responsibilities or specialist professional obligations. Instead, it defines who can authorise project work, accept products, control baselines, approve deviations and escalate decisions during the temporary endeavour.

A useful structure contains four levels. The commissioning authority sits outside the project and sets the overall mandate and project tolerances. A governing body directs the project and represents the primary stakeholder interests. A project manager controls day-to-day work within the authorised stage. Delivery leads and teams create specialist products through agreed work packages. Assurance and support responsibilities cut across these levels without taking accountability away from the decision-makers.

Role descriptions should name decisions, not only tasks. 'Attend meetings' is not an accountability. 'Approve the next stage within project tolerance after reviewing justification, risk and readiness' is. Each role also needs authority, competence, availability, information access, escalation route and a deputy or continuity arrangement where absence would block control.

Control guidance

Represent the three project interests

The business interest protects the reason for investment, value for money, strategic alignment and affordability. It is led by one accountable business decision-maker who chairs or leads the governing body. This accountability cannot be diluted across a committee. The user interest represents those who will use, operate, support or be affected by the products. It defines needs and acceptance, protects usability and owns benefit realisation. The supplier interest represents the capability that designs, builds and verifies the products, whether internal or external.

These interests are perspectives, not company labels. One organisation may contain all three, or several organisations may share them. Multiple user groups may need representation when acceptance or benefits differ. Multiple suppliers may be represented through one senior technical authority if integration and feasibility remain covered. The structure should stay small enough to decide while creating consultation routes for stakeholders who do not sit on the governing body.

Conflicting interests are expected. Users may prefer broader scope, suppliers may seek technical certainty, and business leadership may protect affordability. Governance exists to make those trade-offs visible against the business case and authorised tolerances. It fails when one interest dominates without challenge or when representatives lack authority to commit the group they speak for.

Control guidance

Direction and the governing body

The governing body is accountable for overall direction within the mandate set by the commissioning authority. It authorises initiation, the project, each management stage, exception plans and closure. It confirms that the business case remains valid, risk exposure is acceptable, resources are committed and the project manager has a viable tolerance envelope. Between gates it provides advice and responds to escalated exceptions rather than managing daily delivery.

An effective governing body has authority to decide, credibility with stakeholders, ability to delegate, and availability when decisions are required. Members should review concise evidence before meetings and issue clear decisions with conditions, owners and dates. A meeting without a decision need can be replaced by a report; a decision should not wait for the next calendar meeting when a forecast breach requires earlier action.

The business lead is ultimately accountable and should ensure balanced representation rather than act as an unchallenged owner. User and supplier representatives are accountable for the decisions assigned to their perspectives. Collective accountability for direction does not eliminate individual accountability for benefits, feasibility or business value.

Control guidance

Project management and delivery

The project manager integrates the project on behalf of the governing body. Responsibilities normally include preparing and maintaining plans and management approaches, authorising work packages, monitoring stage status, controlling risks and issues, protecting baselines, taking corrective action within tolerance, reporting progress, escalating exceptions, preparing stage boundaries and recommending closure. The project manager coordinates specialist work but does not automatically own technical approval or user acceptance.

A delivery lead accepts a work package, prepares a team plan where useful, coordinates product creation, performs or arranges quality work, reports checkpoints, raises forecast deviations and delivers completed products with evidence. The acceptance of a work package is a two-way agreement: the project manager confirms what is authorised and the delivery lead confirms feasibility, resources, reporting and constraints. Unagreed work should not be treated as authorised scope.

Delivery team members remain accountable for their professional and safety responsibilities. Project urgency does not override technical standards, permits, delegated financial authority or safe systems of work. These external constraints should be built into work packages, product descriptions and assurance rather than discovered during acceptance.

Control guidance

Assurance and support

Project assurance gives stakeholders confidence that the project is being conducted properly. It examines business, user and supplier perspectives, including justification, requirements, solution integrity, plans, controls, quality, risk and progress. The governing body remains accountable for assurance even when review work is delegated. Assurance must be independent of the project manager and the work it reviews; otherwise self-assessment may conceal weak evidence or conflicts.

Quality assurance is different: it provides confidence to the wider organisation that applicable quality systems, policies and standards are being followed. It normally sits outside the project. Project assurance may use quality-assurance results, but the two should not be collapsed without understanding their different audiences and accountabilities.

Project support provides administration, tools, records, planning support, meeting coordination, configuration administration and reporting assistance. Support can be centralised or performed by the project manager on a small project. It does not own decisions simply because it maintains the system. Record ownership and decision accountability must remain with the designated roles.

Control guidance

Combining roles without losing control

Small projects often require one person to perform several roles. Combine work only after mapping responsibilities and conflicts. The business lead and project manager should remain separate because the same person should not both justify the investment and report objectively on their own day-to-day management. The governing body should not delegate assurance back to the project manager, delivery lead or support function responsible for the subject being reviewed.

A project manager may also perform delivery-lead duties when the package is small, but the package should still be defined and completion independently accepted. One person may represent user and supplier interests only where those interests genuinely align and an independent business decision-maker can resolve trade-offs. Support can be combined widely because it is advisory, but administrative access should not become uncontrolled authority to change baselines.

Capacity is as important as conflict. A nominally assigned executive who cannot attend decisions, a user representative without time to define acceptance, or a technical authority without access to delivery evidence creates a governance gap. Confirm availability and delegated authority in writing, and review it when personnel or organisational conditions change.

Control guidance

Decision rights and communication

A responsibility matrix is useful only when it is tied to named decisions and records. For each control decision, identify who recommends, who assures, who decides, who executes and who must be informed. Avoid multiple accountable owners. Set response times for exception, change, acceptance and safety decisions so authority does not exist only on paper. Define deputies and quorum for time-critical decisions.

The communication approach should identify stakeholders, information needs, sender, frequency, medium, confidentiality, feedback route and owner. Communication is two-way: stakeholders may supply risk, acceptance or change information and should know how to raise it. Stakeholder engagement must be integrated with the project's issue and decision systems rather than treated as a separate public-relations plan.

Organisational boundaries need explicit interfaces. A supplier's delivery manager may report to a commercial contract manager while accepting project work from the project manager. An operational user may have line authority outside the project but acceptance authority inside it. Mapping both relationships prevents project decisions from conflicting with contracts or permanent governance.

Control guidance

Organisation health check