Study guide
3.2 Governance Frameworks, Policies and Delegated Responsibility
APM Project Management Qualification PMQ
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Exam Format & Question Types 1.3 How to Study for APM PMQ
2 Life Cycles
2.1 Linear Life Cycles and Why Work Is Phased 2.2 Iterative and Hybrid Life Cycles 2.3 Project Life Cycles and Extended Life Cycles 2.4 Choosing a Life Cycle: Context, Culture, Strengths and Limitations
3 Governance Arrangements
3.1 Functional, Matrix and Projectised Structures 3.2 Governance Frameworks, Policies and Delegated Responsibility 3.3 Life-Cycle Impact on Governance and Limits of Financial Authority 3.4 Project Roles and Responsibilities 3.5 Project Manager and Project Sponsor Through the Life Cycle 3.6 Linking Projects to Organisational Objectives
4 Sustainability
4.1 Sustainability Responsibilities, Principles and Impact 4.2 Monitoring and Reporting Sustainability Measures
5 Business Case
5.1 Business Case Fundamentals and Analysis Tools 5.2 The Business Case as Baseline and Reviewing Change
6 Procurement
6.1 Procurement Strategy: Purpose and Contents 6.2 Supplier Selection and Negotiation 6.3 Features of Different Contractual Relationships 6.4 Supplier Reimbursement Methods
7 Reviews & Assurance
7.1 Reviews, Decision Gates, Benefits Reviews and Audits 7.2 What Gets Reported and Informing Decisions 7.3 Why Activities Are Re-Planned After a Review 7.4 Project Assurance
8 Transition & Benefits Management
8.1 Transition Requirements and Business-as-Usual Readiness 8.2 Knowledge Transfer and Agreeing the Transition Plan 8.3 Benefits Management: Identification to Realisation 8.4 Aligning and Communicating Benefits
9 Stakeholder Engagement & Communication
9.1 Stakeholder Analysis, Influence and Engagement 9.2 The Communication Management Plan and Its Benefits 9.3 Managing Stakeholder Expectations 9.4 Communication Methods and Tailoring the Message 9.5 Factors That Help and Hinder Communication
10 Conflict Resolution
10.1 Sources and Impacts of Conflict 10.2 Addressing Conflict and the Thomas-Kilmann Model
11 Leadership
11.1 Leadership, Motivation and Team Performance 11.2 Changing Leadership Styles for the Situation 11.3 Coaching, Mentoring and Emotional Intelligence
12 Team Management
12.1 Team Development Stages and Models 12.2 Characteristics and Benefits of Effective Teams 12.3 Leading Virtual and Hybrid Teams
13 Diversity & Inclusion
13.1 Diversity Characteristics and the Equality Act 13.2 Incorporating Diversity and Diverse Thinking 13.3 Conscious and Unconscious Bias and Fair Treatment
14 Ethics, Compliance & Professionalism
14.1 Continuing Professional Development and Competence 14.2 Sources of Specialist Advice and Standards 14.3 The Legal and Regulatory Landscape
15 Requirements & Solutions
15.1 Establishing Scope Through Requirements Management 15.2 Managing Scope Through Configuration Management 15.3 Solutions Development and Prioritisation
16 Quality Management
16.1 Quality Planning, Indicators and the Business Case 16.2 Quality Control and Success Criteria
17 Integrated Planning
17.1 The Integrated Project Management Plan: Format and Contents 17.2 Why an Integrated Plan Matters
18 Schedule Management
18.1 Defining Scope and Breakdown Structures 18.2 Dependencies and What Drives the Schedule 18.3 Re-Estimating and Schedule Optimisation
19 Resource Management
19.1 Determining Resource Requirements and Availability 19.2 Organisational Breakdown Structure and RACI 19.3 Categorising and Allocating Resources 19.4 Resource Smoothing and Resource Levelling
20 Budgeting & Cost Control
20.1 Creating a Budget and Cost Types 20.2 Earned Value and Cost Forecasting 20.3 Monitoring and Reporting Financial Performance 20.4 Closing Down Project Finances
21 Risk & Issue Management
21.1 Benefits of Risk and Issue Management and Contingency Planning 21.2 The Risk and Issue Management Processes 21.3 Proactive and Reactive Risk Responses 21.4 Governance in Risk and Issue Management
22 Change Control
22.1 The Change Control Process and Its Stages 22.2 What a Change Request Must Capture 22.3 Assessing Options and the Impact of a Change 22.4 Recommending Decisions and Updating Plans
3.2 Governance Frameworks, Policies and Delegated Responsibility
Key Takeaways Explain This Topic AI
The organisation’s governance approach — policies, regulations, functions, processes, procedures, and delegated authority — informs how each project is governed.
Project governance is a tailored subset of corporate rules, not something each project manager invents from scratch.
Delegated responsibility exists so timely decisions can be made without every item returning to the board.
Bypassing a control does not remove the exposure it manages; it moves that exposure somewhere less visible.
Governance must be proportionate to value, risk, and novelty — disproportionate control produces compliance theatre rather than assurance.
Last updated: August 2026
Two learning outcomes meet in this section. Outcome 2a closes with the requirement to know that an organisation's governance approach will inform the approach used for a project ; outcome 2c requires you to understand why aspects of project management governance are required — policies, regulations, functions, processes, procedures, and delegated responsibilities. Treat them as one chain: corporate rules cascade down, and delegation is how they are made workable at project level.
How Corporate Governance Cascades to Project Governance
The syllabus states that an organisation’s governance approach will inform the approach used for a project . Project governance is not invented from scratch by each project manager. It is a tailored subset of corporate rules.
Typical cascade:
Corporate / enterprise governance — board-level duties, risk appetite, financial control frameworks, legal and regulatory compliance, ethics, and strategy.
Portfolio / programme governance — prioritisation of investments, funding envelopes, dependency management, and benefits ownership across multiple change initiatives.
Project governance — project board or steering group, sponsor accountability, delegated tolerances, reporting cadence, stage gates or iteration reviews, and change-control thresholds.
If the organisation requires independent assurance for high-risk change, regulated data handling, or capital expenditure above a threshold, those requirements appear in the project’s governance framework (terms of reference, decision rights, mandatory reviews). A project that tries to “skip governance to go faster” is usually misaligned with organisational practice and will fail assurance or gate reviews.
Policies, Regulations, Functions, Processes, Procedures, and Delegated Responsibilities
The syllabus asks why aspects of project management governance are required. Use these building blocks precisely:
Element What it is Why it is required on projects
Policies High-level statements of intent and rules (e.g. risk policy, information security policy) Set non-negotiable boundaries the project must respect
Regulations External legal or industry requirements Create mandatory constraints (safety, data protection, financial conduct)
Functions Standing organisational capabilities (finance, PMO, legal, assurance, HR) Provide specialist control, advice, and independent challenge
Processes End-to-end flows for how work is controlled (change control, risk escalation, gate review) Create repeatable decision paths and audit trails
Procedures Detailed how-to steps within processes Reduce variation and ensure consistent execution
Delegated responsibilities Authority assigned downward within limits Enable timely decisions without every item returning to the board
Without these, projects rely on personality and ad hoc negotiation. That may work for tiny internal tasks; it fails for investments where sponsors, users, regulators, and suppliers need predictable accountability.
Delegated authority is especially examinable. A sponsor or steering group cannot approve every purchase order. They set limits of financial authority (and often schedule/scope/risk tolerances) so the project manager can act within bounds and must escalate beyond them. Escalation is not failure — it is correct governance when the decision would change business justification, strategic fit, or exposure outside agreed appetite.
Why "we skipped governance to go faster" is always the wrong answer
Exam scenarios often present governance as friction: a sponsor wants speed, a team resents paperwork, an approval is "slowing us down". The examinable judgement is that governance is the mechanism that makes speed safe , and that removing it transfers risk rather than removing it.
Work the trade-off explicitly in an answer:
What was skipped What it was protecting Where the risk lands instead
Gate review before build Confirmation that the business case still holds Organisation funds a project that no longer pays back
Procurement procedure Fair, auditable supplier selection and contract terms Legal challenge, unenforceable terms, audit finding
- Change control Integrity of the baseline and of reporting Nobody can say what "on plan" means any more
- Information security policy Regulatory compliance and data subjects Breach, fine, reputational damage
Delegated authority limits Alignment of spend with those accountable for it Unauthorised commitment the sponsor must defend
The correct response in a scenario is almost never "comply because the rules say so". It is: identify which control is being bypassed, name the exposure that control exists to manage, and propose the proportionate route — an expedited review, a delegated decision within limits, or a documented and approved exception — rather than a silent omission.
Proportionality is part of good governance
Governance that ignores scale is its own failure mode. A £30,000 internal process change does not need the assurance regime of a £300m infrastructure programme, and imposing one produces theatre: forms completed to satisfy a process nobody believes in. APM's framing is that governance must align with organisational practice — which includes the organisation's own rules about what level of control applies at what value, risk, or novelty. In an answer, say what tier of control the scenario's project falls into and why, rather than asserting that more governance is always better.