Contracting, Governance, Power and Trust

Introduction

Supplier relationship management (SRM) is not sustained by goodwill alone. It is institutionalized through contracts, operating routines, information systems, escalation procedures, and patterns of interaction that shape how parties behave when conditions change. A contract specifies obligations and remedies; governance coordinates activities that cannot be fully specified in advance; power influences whose interests prevail; and trust affects the willingness to share information, invest, and accept vulnerability.

These elements are interdependent. A highly detailed contract may reduce ambiguity but increase rigidity. Trust can reduce monitoring costs, but excessive reliance on trust may expose a buyer to opportunism. Power can secure short-term concessions, but coercive use may weaken innovation, resilience, and supplier commitment. Effective SRM therefore requires a portfolio of contractual and relational mechanisms rather than a choice between “formal” and “informal” management.

This chapter examines how managers design that portfolio, including service levels, incentives, intellectual property, confidentiality, disputes, dependency, ethical bargaining, and the use of technology and artificial intelligence.

Learning objectives

By the end of this chapter, the reader should be able to:

1. Distinguish transactional, contractual, relational, and hybrid governance.
2. Design contracts that address performance, risk allocation, incentives, confidentiality, and intellectual property.
3. Translate operational requirements into measurable service-level agreements (SLAs).
4. Diagnose power asymmetry, dependency, opportunism, and trust in supplier relationships.
5. Select proportionate monitoring, escalation, dispute-resolution, and collaboration mechanisms.
6. Evaluate ethical and regulatory limits on bargaining power and data use.
7. Apply these ideas to a complex supplier-management decision.

1. The governance problem in buyer–supplier relationships

A supply relationship is governed whenever parties establish rules, processes, and expectations for making decisions and resolving conflicts. Governance answers five practical questions:

• Who has authority to decide?
• What must each party deliver, and how is delivery measured?
• How are benefits, costs, and risks allocated?
• What happens when circumstances change or performance fails?
• How can the relationship adapt without constant renegotiation?

Transaction cost economics

Transaction cost economics (TCE) explains governance choice through uncertainty, frequency, and asset specificity. Asset specificity exists when an investment has substantially greater value in a particular relationship than elsewhere. Examples include a supplier’s dedicated tooling, a buyer-specific information system, or specialized employee training.

When transactions are simple, repetitive, and supported by general-purpose assets, market purchasing may be efficient. As uncertainty and asset specificity increase, parties face greater exposure to hold-up: after one party invests, the other may attempt to renegotiate terms because the investment is difficult to redeploy. Longer-term contracts, safeguards, joint governance, or vertical integration may then be appropriate.

TCE does not imply that contracts eliminate opportunism. Contracts are incomplete because future states, causal responsibility, and performance requirements cannot all be specified at reasonable cost. The managerial task is to identify which matters should be specified, which should be delegated, and which require adaptive relational governance.

Principal–agent theory

In a buyer–supplier relationship, the buyer (principal) often depends on a supplier (agent) whose effort, cost structure, or quality decisions are imperfectly observable. Moral hazard arises when actions are hidden; adverse selection arises when capabilities or risks are hidden before contracting. Governance responses include qualification, audits, incentives, information sharing, warranties, outcome measures, and carefully designed risk allocation.

A fixed-price contract places more cost risk on the supplier and may motivate efficiency, but it can encourage quality reduction or claims when specifications are incomplete. A cost-plus arrangement protects the supplier from uncertainty but can weaken cost discipline. Gain-sharing, open-book costing, target-cost arrangements, and performance bonuses can combine incentives, though they require credible measurement and protection against manipulation.

Relational contracting and the relational view

Relational contracting treats the relationship as an ongoing social and economic exchange rather than a sequence of isolated transactions. Its mechanisms include reciprocity, information sharing, joint problem solving, flexibility, mutual dependence, and norms of solidarity. The relational view further argues that advantage can arise from relationship-specific investments, knowledge-sharing routines, complementary capabilities, and effective governance that competitors cannot easily copy.

Relational governance is not the absence of formality. A mature relationship commonly combines a legal contract with joint steering committees, shared forecasts, technical working groups, escalation protocols, and norms concerning fair dealing.

2. Choosing a governance portfolio

Governance should fit the risk and strategic importance of the relationship. A useful diagnostic considers four dimensions:

A transactional model may use purchase orders, standard terms, competition, and price-based evaluation. A contractual model adds explicit obligations, warranties, remedies, and risk allocation. A relational model adds joint planning and norms. A hybrid model combines all three and is normally appropriate for strategically important, uncertain relationships.

Governance should also be proportionate. Excessive approval layers and audits create cost, delay, and defensive behavior. Insufficient controls leave the organization exposed to quality failures, corruption, cyber incidents, and supply interruption.

3. Contract architecture

A supply contract should be read as an operating system for the relationship, not merely as a legal document. Its major components normally include:

1. Scope and definitions: goods or services, specifications, sites, quantities, documentation, and applicable standards.
2. Commercial terms: price, currency, tax, payment, indexation, open-book rights, and change-order rules.
3. Performance obligations: delivery windows, capacity, quality, service availability, response times, and reporting.
4. Risk allocation: forecasts, inventory, obsolescence, force majeure, transport, regulatory change, and continuity.
5. Assurance: inspection, audit, traceability, corrective action, warranties, and insurance.
6. Information and technology: data ownership, cybersecurity, access control, retention, incident notification, and system integration.
7. Intellectual property (IP): background IP, newly created IP, licenses, improvements, usage rights, and third-party materials.
8. Confidentiality: protected information, permitted use, disclosures, exceptions, duration, and return or destruction.
9. Governance and change: review meetings, decision rights, escalation, change control, and transition assistance.
10. Termination and exit: cause, convenience, insolvency, transition, stock disposition, tooling, records, and continuing obligations.

Service-level agreements

An SLA converts broad expectations into observable performance. A sound SLA identifies the metric, measurement method, data source, target, tolerance, reporting frequency, responsibility, and consequence of failure.

For a period, delivery attainment can be represented as:

This metric assumes that the delivery window, scheduled quantity, and treatment of authorized changes are defined consistently. It should not be confused with fill rate, which measures the proportion of demand supplied in the required quantity.

For an information-technology service, availability is often calculated as:

The parties must define whether scheduled maintenance, force majeure, customer-caused downtime, and partial degradation are included. A target without a measurement protocol is an invitation to dispute.

SLAs should avoid metric gaming. If a supplier is rewarded only for delivery speed, it may increase freight cost or ship incomplete orders. A balanced scorecard can include quality, total cost, delivery, safety, sustainability, responsiveness, and improvement. Metrics should be limited to those that support decisions; measuring everything can obscure priorities.

Incentives and remedies

Incentives should reward outcomes that the supplier can materially influence and that the buyer values. A bonus is credible only when baseline performance, data rights, calculation rules, and payment timing are clear. Penalties should compensate or protect against harm rather than function as arbitrary punishment. Service credits may be appropriate for recurring minor failures; liquidated damages may be appropriate where a reasonable pre-estimate of loss is difficult to calculate, subject to applicable law. Unreasonable penalties may be unenforceable or ethically questionable.

A balanced incentive design includes:

• a threshold below which corrective action is required;
• a target associated with normal performance;
• a stretch level for exceptional performance;
• a cap to limit unintended exposure;
• exclusions for events outside reasonable control;
• a process for disputing data; and
• safeguards against sacrificing safety, quality, or labor standards.

Gain-sharing is useful where supplier actions generate measurable savings. The contract must define the baseline, validation method, implementation cost, sharing percentage, duration, and treatment of savings caused by demand or specification changes rather than supplier effort.

4. Intellectual property, confidentiality, and data

IP negotiations should distinguish background IP, owned before the relationship; foreground IP, created during the relationship; and improvements, which may combine both. Ownership is only one issue. A buyer may need a perpetual license to operate, modify, maintain, or transfer a product, while a supplier may need rights to reuse general know-how that does not reveal the buyer’s confidential information.

A practical contract should address:

• who owns designs, software, models, documentation, and test results;
• rights to pre-existing components and third-party licenses;
• rights to improvements and derivative works;
• escrow or source-code access where business continuity requires it;
• restrictions on reverse engineering and unauthorized reuse;
• treatment of open-source software;
• responsibilities for infringement claims; and
• rights after termination.

Confidentiality provisions should define protected information and legitimate exceptions, such as information already public, independently developed, lawfully received from another source, or required to be disclosed by law. Security obligations should be risk-based. Sensitive data may require encryption, least-privilege access, segregation, logging, secure deletion, and prompt incident notification.

AI intensifies these issues. Buyers should specify whether supplier data may be used to train models, whether prompts and outputs are retained, how personal or commercially sensitive information is protected, and how model errors are tested. A supplier should not quietly reuse a buyer’s proprietary specifications to improve a general model unless the contract and applicable law clearly permit it.

5. Disputes, change, and exit

Dispute prevention is usually less expensive than dispute resolution. Effective mechanisms include a shared issue log, named representatives, response deadlines, root-cause analysis, and a graduated escalation ladder. A typical sequence is operational discussion, contract-manager review, executive negotiation, mediation, and arbitration or litigation as a final step. The appropriate mechanism depends on jurisdiction, confidentiality, enforceability, urgency, and the need for technical expertise.

Change control is equally important. A change process should specify who may request a change, how its cost and schedule effects are assessed, whether work proceeds while the change is disputed, and how emergency changes are authorized. Without disciplined change control, a relationship may experience scope creep, unplanned cost, and claims.

Exit planning is not evidence of distrust; it is continuity governance. Contracts should address notice, transition services, data and tooling return, inventory, employee transfer where lawful, replacement qualification, knowledge transfer, and cooperation during emergencies. Critical suppliers should be assessed for substitutability before a crisis rather than after termination becomes necessary.

6. Power, dependence, and ethical bargaining

Power is the capacity to influence another party’s choices. It may arise from purchasing volume, alternatives, technical knowledge, control of market access, switching costs, information, legal rights, or reputational influence. Dependence is relational: a party is more dependent when it has fewer acceptable alternatives and greater importance attached to the relationship.

Power is not inherently unethical. A buyer may legitimately require safety, transparency, audit access, or corrective action. The ethical issue concerns how power is exercised and whether conduct is proportionate, transparent, lawful, and respectful of affected stakeholders.

Coercive tactics—retroactive price reductions, arbitrary payment extensions, threats unrelated to performance, forced disclosure of competitors’ confidential bids, or unilateral specification changes—can produce short-term gains while damaging trust and supply resilience. Responsible bargaining uses objective cost drivers, fair notice, documented assumptions, and reciprocal commitments.

Managers should examine dependency in both directions. A buyer dependent on a sole-source supplier faces continuity and bargaining risks. A small supplier dependent on one powerful customer may face financial distress if forecasts are withdrawn or payment is delayed. Remedies include dual sourcing, standardization, qualification of alternatives, inventory or capacity reservations, joint investment, fair payment practices, and transparent transition planning.

A useful governance question is not “Who has more power?” but “What safeguards are justified by the vulnerability created by this power imbalance?”

7. Trust and control

Trust is the willingness to accept vulnerability based on positive expectations about another party’s competence, integrity, and benevolence. These dimensions should be distinguished. A supplier may be technically competent but ethically unreliable; another may be well intentioned but operationally incapable.

Trust develops through repeated evidence: accurate information, fulfillment of commitments, fair problem solving, and acknowledgment of mistakes. It can reduce the need for duplicated inspections and allow faster adaptation. However, trust should complement—not replace—verification. Blind trust creates concentration risk, weakens accountability, and may conceal misconduct.

The most robust relationships use “trust but verify” controls:

• verify critical facts through reliable data;
• audit proportionately to risk;
• separate personal relationships from approval authority;
• document exceptions and conflicts of interest;
• protect whistleblowers; and
• review controls when ownership, technology, or market conditions change.

Trust is also affected by procedural justice. Suppliers are more likely to cooperate when decisions are consistent, explanations are provided, evidence can be challenged, and similar cases receive similar treatment. Thus, fairness in process may matter even when the commercial outcome is unfavorable.

8. A governance design process

A practical design process has seven steps.

Step 1: Segment the relationship. Assess criticality, spend, substitutability, uncertainty, asset specificity, regulatory exposure, and supplier capability.

Step 2: Map dependencies and risks. Identify single points of failure, confidential information, human-rights risks, cyber exposure, and potential hold-up situations.

Step 3: Define desired outcomes. Separate essential outcomes from preferred methods. Specify quality, continuity, innovation, cost, service, safety, and sustainability priorities.

Step 4: Select controls. Combine specifications, warranties, audits, incentives, information sharing, joint teams, and escalation. Match control intensity to risk.

Step 5: Allocate rights and responsibilities. Decide who owns decisions, data, IP, capacity, inventory, and change costs. Ensure the party controlling a risk has a reasonable ability to manage it.

Step 6: Test scenarios. Examine demand shocks, supplier failure, cyberattack, regulatory change, quality crisis, insolvency, and relationship termination.

Step 7: Review and learn. Use performance data and post-incident reviews to adjust the contract and relationship. Governance should be revisable, not static.

Illustrative case: Northstar Medical Devices

Background

Northstar Medical Devices, a fictional manufacturer, buys a sterilized polymer component from MedForm, a specialist supplier. The component is critical to a regulated product, requires buyer-specific tooling, and has a twelve-month qualification cycle. MedForm is technically strong but financially dependent on Northstar, which represents 55% of its sales.

Problem

Northstar’s previous annual purchase order specified price and quantity but not capacity reservation, forecast commitment, change control, or recovery time. When demand rose unexpectedly, MedForm prioritized another customer with a longer-term contract. Northstar experienced shortages. In response, Northstar proposed a large unilateral price reduction and threatened to transfer tooling immediately. MedForm then reduced engineering support and withheld early-warning information.

Analysis

The relationship contains high asset specificity, high switching cost, regulatory constraints, and mutual dependence. A purely price-based contract is unsuitable. Northstar has purchasing power, but MedForm controls specialized knowledge and near-term capacity. The dispute is therefore not simply a supplier-performance problem; it is a governance failure involving incomplete contracting and poorly managed power.

Approach

The parties negotiate a three-year framework with annual price review based on agreed labor, resin, energy, and productivity drivers. Northstar provides a rolling forecast, with a defined firm zone and a nonbinding planning zone. MedForm reserves minimum capacity, while Northstar pays a reasonable reservation fee and commits to a minimum annual volume.

The revised SLA defines delivery attainment, defect rates, response times, and corrective-action deadlines. A joint quality team validates measurement. A gain-sharing clause rewards verified process savings without reducing sterilization quality. Northstar retains ownership of its tooling and receives inspection and maintenance rights; MedForm retains its general process know-how but grants Northstar a continuity license for buyer-funded developments. Both parties establish confidentiality, cybersecurity, and incident-notification duties.

A governance committee meets quarterly, while operational representatives use a five-step escalation process. The contract provides mediation before formal proceedings, emergency allocation rules, and transition assistance. Northstar also qualifies a second source for a lower-volume backup and funds part of the qualification cost.

Outcome

In this illustrative case, delivery reliability improves, emergency freight declines, and engineering information is shared earlier. MedForm receives greater demand visibility and a fair return on dedicated capacity. Northstar pays somewhat more than the lowest spot-market quotation but reduces interruption exposure and protects regulatory continuity.

Learning points

1. Criticality and switching cost justify governance beyond price competition.
2. Forecasts create value only when their binding status is explicit.
3. Ethical power use can improve, rather than weaken, commercial outcomes.
4. IP and exit provisions are continuity tools, not merely legal safeguards.
5. Dual sourcing may be valuable even when it is not the lowest immediate-cost option.

Challenges and limitations

Governance frameworks have limits. TCE can overemphasize opportunism and understate identity, professional norms, and learning. Agency theory may assume measurable objectives when quality and innovation are multidimensional. Relational governance can become exclusionary if it favors insiders and reduces competitive challenge. SLAs can create local optimization and metric gaming. Audits may provide false assurance when evidence is staged or when auditors lack technical independence.

Contracts also operate within law and institutional context. Competition law may restrict collusion or abuse of dominance; privacy and data-protection rules may govern personal data; labor and modern-slavery requirements may extend through supply chains; and sectoral rules may impose traceability, validation, or record-retention duties. Legal advice is essential for jurisdiction-specific drafting.

Contemporary developments and best practices

Digital procurement platforms improve contract visibility, obligation tracking, and evidence-based performance review. Smart-contract technologies may automate portions of payment or verification, but automation cannot resolve ambiguous definitions or unreliable input data. AI can identify clause conflicts, predict service failures, and summarize disputes, yet outputs require human review because training data may be biased, confidential information may be exposed, and accountability cannot be delegated to a model.

Best practice is therefore to:

• maintain a single controlled contract repository;
• link obligations to owners, data sources, and review dates;
• use balanced, auditable metrics;
• align risk with control and capability;
• combine formal safeguards with relationship-building;
• test dependency and exit scenarios;
• prohibit retaliation and conflicts of interest;
• protect confidential and personal data; and
• review governance after major incidents, market changes, or technology changes.

Chapter Summary

Contracting, governance, power, and trust form an integrated system for managing supplier relationships. Contracts specify obligations, rights, remedies, information, IP, confidentiality, and exit arrangements, but they cannot anticipate every future condition. Transaction cost economics highlights uncertainty, frequency, and asset specificity; principal–agent theory emphasizes hidden action and information; relational contracting explains adaptation, reciprocity, and joint value creation.

Effective governance is usually hybrid. It combines measurable SLAs, proportionate audits, incentives, change control, escalation, and continuity planning with information sharing, joint problem solving, and procedural fairness. Power should be exercised lawfully and ethically, particularly where a small supplier or critical buyer is highly dependent. Trust is valuable but must be supported by verification and accountability. Digital tools and AI can strengthen visibility and analysis, but they do not remove the need for human judgment, legal compliance, or responsible stewardship.

Key Terms

Transaction cost economics: A theory explaining governance choices through transaction costs, uncertainty, and asset specificity.

Asset specificity: The degree to which an investment has greater value in one relationship than in alternative uses.

Hold-up: Opportunistic renegotiation after one party has made a relationship-specific investment.

Principal–agent theory: A framework addressing conflicts and information asymmetry between a party delegating work and the party performing it.

Moral hazard: Risk that hidden actions after contracting reduce performance or increase risk.

Adverse selection: Risk that hidden information before contracting leads to unsuitable partner selection.

Relational contracting: Governance based on continuing exchange, reciprocity, flexibility, and shared norms.

Hybrid governance: A combination of market, contractual, and relational mechanisms.

Service-level agreement: A documented set of measurable service obligations and consequences.

Gain-sharing: An arrangement in which verified benefits are shared between parties.

Background IP: Intellectual property owned before a particular relationship or project.

Foreground IP: Intellectual property created during a relationship or project.

Confidentiality: Protection against unauthorized disclosure or use of information.

Dependency: Reliance on another party because alternatives are limited or switching is costly.

Opportunism: Self-interested behavior that exploits contractual gaps or another party’s vulnerability.

Trust: Willingness to accept vulnerability based on expectations of competence, integrity, or benevolence.

Escalation: A structured movement of unresolved issues to higher authority.

Exit governance: Processes that preserve continuity and protect rights when a relationship ends.

Procedural justice: Perceived fairness of the process used to make and review decisions.

Review Questions

5 Short Answer Questions

1. What are the three principal dimensions commonly used by transaction cost economics to explain governance choice?
2. Why is a service-level metric incomplete without a measurement protocol?
3. Distinguish background IP from foreground IP.
4. What is the difference between trust and blind reliance?
5. Identify two ethical risks associated with buyer power.

5 Long Answer Questions

1. Compare transactional, contractual, relational, and hybrid governance, and explain when each is appropriate.
2. Explain how principal–agent theory informs the design of supplier incentives and monitoring.
3. Discuss the major components of a robust supply contract.
4. Explain how dependency and asset specificity can create hold-up risk and describe suitable safeguards.
5. Evaluate the proposition that trust and control are substitutes in supplier relationships.

3 Analytical / Application Questions

1. A buyer wants a penalty for every late delivery, although delays are sometimes caused by the buyer’s own engineering changes. Design a fair SLA and remedy structure, explaining measurement, exclusions, incentives, and dispute handling.
2. A sole-source supplier owns critical process know-how, while the buyer owns dedicated tooling and represents most of the supplier’s revenue. Analyze the power and dependency structure and recommend a governance portfolio.
3. A supplier proposes using buyer production data to train an AI model that will support future services. Identify the contractual, ethical, confidentiality, IP, cybersecurity, and governance questions that should be resolved before approval.

Multiple Choice Questions with Answers

Question 1

Which condition most strongly supports moving beyond spot-market purchasing toward stronger contractual or relational governance?

A. Low uncertainty and fully generic assets

B. High asset specificity and uncertain future conditions

C. Many interchangeable suppliers and simple specifications

D. A one-time purchase with no operational dependence

Correct Answer: B. High asset specificity and uncertain future conditions

Question 2

Which statement best describes moral hazard in a buyer–supplier relationship?

A. The buyer cannot identify supplier capability before contracting

B. The supplier takes hidden actions after contracting that affect performance

C. The buyer and supplier use different currencies

D. A supplier invests in general-purpose equipment

Correct Answer: B. The supplier takes hidden actions after contracting that affect performance

Question 3

What is essential for a meaningful delivery-attainment SLA?

A. A target without a defined delivery window

B. A penalty independent of measurement rules

C. A defined metric, data source, and treatment of authorized changes

D. A requirement that every delivery use premium freight

Correct Answer: C. A defined metric, data source, and treatment of authorized changes

Question 4

Which arrangement most directly rewards verified supplier-generated savings?

A. Gain-sharing

B. Unconditional price escalation

C. A confidentiality clause

D. A termination-for-convenience clause

Correct Answer: A. Gain-sharing

Question 5

Which item is normally classified as background IP?

A. A design created entirely during the current project

B. A process improvement jointly developed after contract signature

C. Software owned by the supplier before the relationship began

D. A buyer-funded prototype created under the current statement of work

Correct Answer: C. Software owned by the supplier before the relationship began

Question 6

Why can excessive reliance on a single SLA metric be harmful?

A. It always eliminates supplier accountability

B. It can encourage metric gaming and local optimization

C. It makes all performance data confidential

D. It prevents contracts from containing remedies

Correct Answer: B. It can encourage metric gaming and local optimization

Question 7

Which practice is the clearest example of ethical use of buyer power?

A. Imposing retroactive price reductions without explanation

B. Requiring disclosure of a competitor’s confidential bid

C. Using objective cost drivers and reciprocal commitments in negotiations

D. Extending payment terms unilaterally after delivery

Correct Answer: C. Using objective cost drivers and reciprocal commitments in negotiations

Question 8

What is the primary purpose of exit governance?

A. To prevent any supplier from improving its processes

B. To preserve continuity and protect rights when the relationship ends

C. To replace all performance measurement with legal action

D. To eliminate the need for alternative suppliers

Correct Answer: B. To preserve continuity and protect rights when the relationship ends

Question 9

Which statement best captures the relationship between trust and verification?

A. Trust makes all audits unnecessary

B. Verification proves that trust is unethical

C. Trust can support cooperation, while proportionate verification protects accountability

D. Verification is appropriate only after contract termination

Correct Answer: C. Trust can support cooperation, while proportionate verification protects accountability

Question 10

A service has 1,000 agreed hours in a month and 20 hours of qualifying unplanned downtime. Using the availability formula in the chapter, what is availability?

A. 2%

B. 20%

C. 98%

D. 99.8%

Correct Answer: C. 98%