Study guide
6.3 Features of Different Contractual Relationships
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
6.3 Features of Different Contractual Relationships
Key Takeaways Explain This Topic AI
The contractual relationship decides who is responsible for what; the reimbursement method then decides who carries the cost consequence.
Design ownership is the pivotal question: a client that specifies the solution in detail keeps design risk, while design-and-build transfers it along with control of the outcome.
Using many specialist packages gives the client price transparency and control but leaves the client owning the interfaces between them.
No relationship type is inherently best — the right choice puts each risk with the party best able to manage it.
Obligations such as payment terms, ethical standards, and quality requirements only reach sub-contractors if they are flowed down through the first-tier contract.
Last updated: August 2026
Outcome 5c has two halves. The first is to know the features of different contractual relationships ; the second, covered in the next section, is to understand supplier reimbursement methods. This section takes the relationship itself — who is contracted to whom, who owns design, and who manages the interfaces between packages.
Contractual relationships on the PMQ
Learning outcome coverage for procurement includes features of different contractual relationships and supplier reimbursement methods , with judgement on when each is appropriate . Relationship design and payment mechanism work together: the same technical scope can produce very different behaviour under a one-off fixed-price order versus a multi-year framework with shared targets.
A contract creates enforceable rights and obligations. A contractual relationship is the pattern of interaction, trust, information sharing, and commercial stance that develops around those terms. Project managers influence relationship quality through specification clarity, fair change control, prompt payment, and joint problem-solving — not only through legal clauses.
Features of different contractual relationships
Think of relationship types as a spectrum. Labels vary by sector; PMQ answers should describe features and fit , not argue for one branded model.
Relationship style Typical features Best fit Watch-outs
Transactional / adversarial lean Discrete purchase; detailed specification; price-focused competition; limited collaboration beyond delivery Clear, simple, well-specified goods or services; one-off buy Claims culture if scope was ambiguous; little incentive to innovate
Collaborative / partnering Shared objectives, open information, joint risk workshops, early warning of problems, continuous improvement Complex, uncertain, or long-duration work needing joint problem-solving Needs cultural commitment; weak if one party still acts purely transactionally
Framework / call-off Pre-competed terms and suppliers; call-offs for packages over a period Multiple similar packages over time; speed of award; consistent standards Mini-competitions still need fairness; capacity may be constrained at peaks
Prime contractor / integrated supply Single point of responsibility coordinating many subcontractors Buyer wants one accountable interface for complex delivery Prime markup and interface risk; ensure flow-down of critical obligations
Transactional relationships
Transactional relationships treat each purchase as a largely self-contained exchange: specify, bid, deliver, pay, close. They suit catalogue products, routine maintenance tasks with clear standards, or one-off specialist inputs that are easy to define. Management overhead is lower when specifications are solid. They fail when uncertainty is high and parties need ongoing joint design — rigid terms then generate variations and conflict.
Partnering and collaborative relationships
Partnering (and related collaborative models) emphasise mutual objectives, early involvement of suppliers in design or planning, transparent cost and risk data where agreed, and processes for resolving issues before they become disputes. They are appropriate when interfaces are complex, innovation is needed, or long programmes make "win-lose" behaviour destructive. Partnering does not remove the need for a contract, clear scope boundaries, or change control; it changes how parties work within commercial rules.
Framework arrangements
A framework pre-establishes terms with one or more suppliers so individual call-offs can be awarded faster for defined categories of work. Frameworks suit programmes with many similar packages (for example regional site works, IT professional services days, or facilities projects). They improve speed and consistency but still require package-level definition, capacity checks, and compliant mini-competition or direct award rules as applicable.
Relationship choice scenario
A university is building a research facility. Structural steel packages are standard and well specified — a transactional competitive fixed-price route may be efficient. The experimental fit-out is novel and will evolve with researchers — a collaborative relationship with early supplier design input and a reimbursement method that handles uncertainty (for example target cost or carefully controlled cost-plus for defined design stages) is more appropriate than a rigid low-bid fixed price on incomplete drawings.
Choosing the relationship before choosing the price mechanism
Candidates often jump straight to fixed price versus cost plus. The syllabus puts the relationship first for a reason: the relationship decides who is responsible for what , and the reimbursement method then decides who carries the cost consequence . Get them in that order in a written answer.
Three questions settle the relationship in a scenario:
Who owns the design? If the client specifies the solution in detail, the client keeps design risk and the supplier is executing someone else's design. If the supplier designs and builds, design risk transfers with it — but so does control over the outcome.
How many interfaces is the client willing to manage? Many specialist contracts give the client control and price transparency but leave the client integrating between them, and carrying the risk when two packages do not meet. A single main contractor absorbs those interfaces at a price.
How much does the client need to change its mind later? Highly defined, arm's-length arrangements punish change. Collaborative and framework arrangements are built to absorb it.
Where relationships fail
Relationship pattern Typical failure mode Early warning sign in a scenario
Client-designed, supplier-built Client's design is incomplete; every gap becomes a claim Rising volume of requests for information and variations
Design-and-build Supplier optimises for its own cost, not the client's operating cost Whole-life cost queries answered vaguely at tender
Multiple specialist packages Nobody owns the interfaces between packages Two suppliers each say the other is responsible
Framework / call-off Convenience erodes competitive tension over time No benchmarking of call-off prices against the market
Partnering / collaborative Good relations substitute for records; no evidence when it goes wrong Decisions agreed verbally, contract never varied
The examinable judgement is that no relationship type is inherently best . The right answer names the project's dominant uncertainty and constraint — design maturity, need for price certainty, interface complexity, likely change — and selects the relationship that puts each risk with the party best able to manage it.
Relationships in the supply chain, not just the first tier
Finally, remember that the client's contract is with the main supplier, but delivery usually depends on sub-contractors the client has no contract with . Payment terms, ethical standards, and quality requirements only reach those tiers if they are flowed down through the main contract. A scenario describing modern slavery risk, late payment of small sub-contractors, or a critical sub-supplier failing is testing whether you understand that the first-tier contract has to carry those obligations downward.