A sourcing project can involve procurement, the business owner, finance, legal, technical specialists, risk functions, senior management, and the eventual contract owner.

Everyone may be involved, but involvement does not automatically create clarity.

Questions soon arise:

• Who defines the requirement?
• Who runs the supplier process?
• Who owns the commercial recommendation?
• Who approves the supplier decision?
• Who gives legal advice?
• Who may negotiate with the supplier?
• Who has authority to sign?
• Who owns performance after the contract begins?

When these responsibilities are unclear, work is duplicated, decisions are delayed, important reviews are missed, and suppliers may receive conflicting instructions.

A RACI matrix can help procurement define who performs the work, who owns the outcome, who provides input, and who needs information.

However, RACI must be implemented carefully. It does not replace delegated authority, signing rules, process controls, or professional judgment.

This article explains how to use RACI in procurement without turning it into another layer of bureaucracy.

LHTS classification

Primary role: Management
Supporting role: Tactical
Process: Procurement organization and governance across Source-to-Contract, contract management, and selected Procure-to-Pay decisions
Learning level: Advanced
Related course: Introduction to Procurement Management

Quick answer: What is RACI in procurement?

RACI is a role-allocation model used to clarify participation in procurement tasks and decisions.

The four roles are:

• Responsible: Performs or coordinates the work.
• Accountable: Owns the result and ensures the task or decision is completed correctly.
• Consulted: Provides relevant input before the work or decision is completed.
• Informed: Receives information about progress or the result.

A procurement RACI works best when it is applied to specific deliverables and decisions, aligned with delegated authority, and adjusted according to value, risk, complexity, and business impact.

What does RACI mean?

RACI is an acronym for Responsible, Accountable, Consulted, and Informed.

RACI role	Practical meaning	Procurement example
Responsible	Performs or coordinates the activity	The buyer prepares and issues the RFQ
Accountable	Owns the outcome and makes sure the activity is properly completed	The Procurement Manager owns the sourcing-process outcome
Consulted	Provides knowledge or advice before completion	Legal advises on contractual risk
Informed	Receives an update but does not participate directly	Operations receives notification of the implementation date

The model appears simple, but the quality of a RACI depends on how clearly the organization defines the underlying work.

“Manage sourcing” is usually too broad for one row.

A better matrix separates the process into meaningful deliverables and decisions, such as:

• Approve the sourcing strategy.
• Define the technical requirement.
• Qualify participating suppliers.
• Approve the evaluation model.
• Issue the RFQ.
• Evaluate technical proposals.
• Evaluate commercial proposals.
• Approve the supplier recommendation.
• Negotiate the contract.
• Approve deviations from standard terms.
• Sign the contract.
• Implement the agreement.
• Manage supplier performance.

Clear tasks produce clearer roles.

What RACI can—and cannot—do

RACI is a clarification tool. It helps the organization agree who should participate in a task or decision.

It can support:

• Process ownership.
• Cross-functional cooperation.
• Sourcing-project governance.
• Contract handover.
• Decision preparation.
• Stakeholder communication.
• Escalation.
• Compliance.
• Process improvement.

RACI does not, by itself, create authority.

This distinction is essential in procurement.

RACI does not replace delegated authority

Delegated authority defines who may approve expenditure, accept risk, approve a supplier award, or make another formal company decision.

A Procurement Manager may be Accountable for ensuring that a sourcing project is correctly executed but may not have authority to approve the final investment.

Similarly, a business sponsor may own the business outcome without being authorised to sign the supplier contract.

The RACI matrix should therefore be checked against the organization’s:

• Approval policy.
• Delegation-of-authority matrix.
• Budget authority.
• Investment governance.
• Contract approval policy.
• Signing authority.
• Risk acceptance rules.
• Sourcing Board charter.

Where the RACI and formal authority rules conflict, the RACI must be corrected.

RACI does not automatically define signing authority

Signing authority is the formal authority to bind the organization contractually.

The person who signs may not be the person who performed the sourcing work, negotiated the contract, or owns supplier performance.

For example:

• The buyer may be Responsible for negotiating.
• The Procurement Manager may be Accountable for the sourcing process.
• Legal may be Consulted on contractual risk.
• The business sponsor may approve the commercial recommendation.
• An authorised company officer may sign the contract.

These are different responsibilities.

The RACI should show the contract-signature step separately rather than assuming that the Accountable person automatically signs.

RACI does not replace segregation of duties

Procurement controls may require different people to:

• Request a purchase.
• Approve the budget.
• select the supplier.
• Create the supplier record.
• Issue the purchase order.
• Confirm receipt.
• Approve the invoice.
• Release payment.

A RACI matrix can describe these responsibilities, but it does not determine whether the control design is adequate.

The matrix must be reviewed against financial-control and segregation-of-duties requirements.

Why use RACI in procurement?

Procurement is naturally cross-functional.

The business understands the operational need. Procurement understands the sourcing process and supply market. Legal advises on contractual risk. Finance assesses budgets and financial consequences. Technical specialists evaluate capability. Risk functions examine specific exposures. Management approves decisions within defined authority.

RACI helps connect these contributions.

Clearer ownership

Every important task should have an identifiable owner.

Without clear ownership, project participants may assume that somebody else is responsible. Requirements remain incomplete, reviews are delayed, and decisions reach approval forums without sufficient preparation.

Faster decisions

RACI can reduce unnecessary meetings and consultation.

When participants know who decides, who provides input, and who only needs an update, the project team can avoid involving every stakeholder in every discussion.

Better stakeholder expectations

RACI clarifies that consultation is not the same as decision authority.

A stakeholder may provide important technical input without owning the commercial process. Procurement may lead supplier communication without owning the operational requirement.

Stronger procurement compliance

A well-designed matrix can make governance more visible by showing:

• Who owns each process step.
• Which specialists must be consulted.
• Who prepares a recommendation.
• Who approves a decision.
• Who controls contract changes.
• Who receives information.
• Where escalation is required.

RACI is therefore closely connected to procurement compliance, but it remains only one part of the control framework.

Improved contract handover

Many sourcing projects lose clarity after the agreement is signed.

The sourcing buyer assumes that the business will manage the contract. The business assumes that procurement will manage the supplier. Finance expects somebody to monitor commercial conditions. Legal expects the contract owner to track obligations.

A RACI matrix can make implementation and contract-management responsibilities explicit before signature.

Where RACI fits in the procurement process

RACI can be used across the complete procurement lifecycle.

Procurement strategy and governance

At management level, RACI can define responsibility for:

• Procurement strategy.
• Procurement policies.
• Category-management governance.
• Supplier-risk governance.
• Procurement systems.
• Compliance reporting.
• Competence development.
• Process ownership.
• Internal-audit responses.

Need definition

The matrix can clarify who:

• Owns the business need.
• Defines technical requirements.
• Confirms the budget.
• Challenges demand.
• Approves the business case.
• Involves procurement.

Sourcing preparation

RACI can allocate responsibility for:

• Market analysis.
• Sourcing strategy.
• Supplier prequalification.
• Specifications.
• Evaluation criteria.
• Confidentiality arrangements.
• Project timelines.
• Sourcing Board preparation.

RFQ and supplier selection

The matrix can clarify who:

• Communicates with suppliers.
• Answers technical questions.
• Receives bids.
• Evaluates technical proposals.
• Evaluates commercial proposals.
• Conducts due diligence.
• Consolidates the recommendation.
• Approves the supplier award.

Negotiation and contracting

RACI can distinguish responsibility for:

• Negotiation preparation.
• Commercial negotiation.
• Legal drafting.
• Risk review.
• Financial approval.
• Deviation approval.
• Final contract approval.
• Contract signature.

Supplier implementation

The matrix can define who:

• Creates the supplier record.
• Configures purchasing systems.
• Communicates the new agreement.
• Trains users.
• Establishes operational contacts.
• Confirms implementation readiness.
• Owns the contract after handover.

Contract and supplier management

RACI can clarify responsibility for:

• Supplier-performance reviews.
• Contractual obligations.
• Price adjustments.
• Forecasts.
• Claims.
• Corrective actions.
• Risk monitoring.
• Contract changes.
• Renewal or termination.
• Supplier development.

Procure-to-Pay

For operational purchasing, RACI can support clarity around:

• Purchase requests.
• Budget approval.
• Purchase-order creation.
• Order confirmation.
• Goods receipt.
• Service acceptance.
• Invoice deviation.
• Payment approval.
• Supplier master data.

A single RACI should not necessarily cover all these processes. Separate matrices may be more practical for sourcing, contracting, supplier management, and Procure-to-Pay.

How to implement RACI in procurement

A practical implementation can be organised into seven steps.

Step 1: Define the problem the RACI should solve

Do not begin by creating a large matrix for the entire procurement organization.

Start with a real problem, such as:

• Sourcing projects are delayed by unclear approvals.
• Buyers and stakeholders disagree about supplier communication.
• Legal is involved too late.
• Nobody owns contract implementation.
• Contract changes are agreed without authority.
• Supplier-performance actions are not completed.
• Sourcing Board decisions are poorly prepared.
• Procurement and finance duplicate approval activities.

A RACI should solve a defined role problem.

Step 2: Choose one process or decision flow

Select a manageable scope.

Examples include:

• Strategic sourcing projects.
• Supplier qualification.
• Contract approval.
• Contract implementation.
• Supplier-performance management.
• New-supplier creation.
• Purchase-to-Pay exceptions.

A matrix covering everything is likely to become too broad to use.

Step 3: Map deliverables and decisions

List the outputs that must be completed and the decisions that must be made.

Use action-oriented descriptions.

Weak task descriptions include:

• Legal.
• Finance.
• Sourcing.
• Contract.
• Supplier management.

Stronger descriptions include:

• Approve sourcing strategy.
• Review liability clauses.
• Confirm budget availability.
• Issue the RFQ.
• Approve the supplier recommendation.
• Sign the contract.
• Accept the delivered service.
• Approve a contract change.

A participant should understand what completion means for every row.

Step 4: Identify roles, not individual names

Use organizational roles in the main matrix:

• Business sponsor.
• Business owner.
• Category Manager.
• Buyer.
• Procurement Manager.
• Contract owner.
• Technical evaluator.
• Finance.
• Legal.
• Information security.
• Sourcing Board.
• Authorised signatory.

Names change. Roles are more stable.

A project-specific version may then assign named individuals to those roles.

Step 5: Assign R, A, C, and I

Apply the following principles.

Assign one clear Accountable role

Each row should normally have one Accountable role.

Several people may contribute, but one role should own the outcome.

When two people are both described as fully accountable, accountability often becomes unclear.

Identify one Responsible lead

More than one person may perform the work, but there should normally be a clear lead responsible for coordinating completion.

Limit Consulted roles

Consult only roles whose input can materially improve the deliverable or decision.

Every Consulted role creates communication and lead-time requirements.

Use Informed selectively

Information should support action, coordination, or awareness.

Adding senior managers to every Informed cell can create unnecessary reporting without improving governance.

Step 6: Validate the matrix against authority and controls

Before approval, compare the draft RACI with:

• Delegated authority.
• Budget authority.
• Signing authority.
• Sourcing thresholds.
• Legal-review requirements.
• Financial controls.
• Segregation of duties.
• Information-security requirements.
• Sustainability requirements.
• Sourcing Board governance.
• Contract-approval workflows.

The workshop should include representatives who understand these controls.

Step 7: Test, implement, and review

Pilot the RACI in one or more real procurement activities.

During the pilot, ask:

• Did participants understand their roles?
• Was an important role missing?
• Were too many people consulted?
• Did the Accountable person have the required authority?
• Did the matrix match the system workflow?
• Were decisions faster?
• Did any control become weaker?
• Did participants still create workarounds?
• Was contract handover clearer?

Update the matrix before wider implementation.

A RACI should also be reviewed when:

• The procurement process changes.
• Authority levels change.
• A new system is implemented.
• The organization is restructured.
• Audit identifies unclear ownership.
• New regulatory or risk requirements arise.
• Repeated deviations indicate a role problem.

A practical sourcing RACI example

Consider a cross-functional project sourcing a business-critical service.

The following example is illustrative. Actual roles must be adapted to the organization’s authority structure and risk profile.

Deliverable or decision	Responsible	Accountable	Consulted	Informed
Define business requirement	Business owner	Business sponsor	Buyer, technical experts	Procurement Manager
Develop sourcing strategy	Buyer	Procurement Manager	Business owner, finance, legal	Business sponsor
Approve sourcing strategy	Buyer prepares recommendation	Sourcing Board chair or authorised sponsor	Sourcing Board members	Project team
Prepare and issue RFQ	Buyer	Procurement Manager	Business owner, legal	Business sponsor
Complete technical evaluation	Technical team	Business owner	Buyer	Procurement Manager
Complete commercial evaluation	Buyer	Procurement Manager	Finance, business owner	Business sponsor
Complete risk and legal review	Relevant specialist	Functional risk owner	Buyer, business owner	Procurement Manager
Approve supplier recommendation	Buyer prepares recommendation	Authorised business sponsor or Sourcing Board	Procurement Manager, finance, legal	Project team
Negotiate commercial conditions	Buyer	Procurement Manager	Business owner, finance, legal	Business sponsor
Approve contract deviations	Buyer coordinates	Authorised risk owner	Legal, finance, business owner	Procurement Manager
Sign the contract	Contract coordinator routes document	Authorised signatory	Legal, procurement	Contract owner
Implement the agreement	Contract owner	Business sponsor	Buyer, supplier, finance	Users
Manage supplier performance	Contract owner	Business owner	Procurement, users	Business sponsor
Approve material contract change	Contract owner prepares request	Authorised approver	Procurement, legal, finance	Relevant users

The example separates:

• Preparation from approval.
• Technical evaluation from commercial evaluation.
• Contract approval from contract signature.
• Sourcing ownership from contract ownership.
• Specialist advice from decision authority.

These distinctions reduce ambiguity.

How a Sourcing Board fits into RACI

A Sourcing Board can provide governance at defined sourcing tollgates.

Typical decisions may include:

• Approving the sourcing strategy.
• Approving a non-competitive sourcing route.
• Confirming the supplier shortlist.
• Approving the award recommendation.
• Approving a major commercial deviation.
• Authorising progression to contracting.

RACI can show how the project team interacts with the board.

For example:

• Responsible: The buyer prepares the decision material.
• Accountable: The authorised board or board chair approves the tollgate.
• Consulted: Legal, finance, risk, and the business owner provide relevant input.
• Informed: Other project participants receive the decision.

However, writing “Sourcing Board” in the Accountable column is not sufficient by itself.

The organization should define:

• The board’s mandate.
• Which decisions require board approval.
• Membership.
• Chair.
• Quorum.
• Voting or consensus rules.
• Delegated authority.
• Required decision material.
• Meeting frequency.
• Escalation route.
• How decisions are documented.

Without this structure, collective accountability may become unclear.

Create a tiered RACI based on value and risk

One RACI model should not automatically apply to every purchase.

A routine, low-risk purchase should not require the same consultation and approval as a strategically important outsourcing agreement.

The governance level should reflect:

• Total contract value.
• Financial exposure.
• Supply risk.
• Operational criticality.
• Contract duration.
• Legal complexity.
• Information-security exposure.
• Personal-data processing.
• Sustainability and ethical risk.
• Supplier dependency.
• Reputational impact.
• Difficulty of switching supplier.
• Strategic importance.

Low-risk procurement

A low-risk sourcing activity may involve:

• Buyer as Responsible.
• Procurement Manager as Accountable.
• Limited specialist consultation.
• Business owner kept appropriately informed.
• Standard terms and approval workflows.

Medium-risk procurement

A medium-risk sourcing project may require:

• A senior or category buyer.
• Business-owner involvement.
• Finance or legal consultation.
• Formal sourcing-strategy approval.
• Documented supplier recommendation.
• More structured contract handover.

High-risk or strategic procurement

A high-risk project may require:

• Cross-functional governance.
• A formal Sourcing Board.
• Senior business sponsorship.
• Legal, finance, security, risk, or sustainability review.
• Defined tollgate approvals.
• Executive or investment approval.
• Formal contract-management governance.

The tiers should be based on company-defined criteria rather than universal monetary thresholds.

A relatively low-value software agreement involving sensitive personal data may require more governance than a higher-value catalogue purchase.

Connecting RACI to procurement compliance

RACI supports the first pillar of procurement compliance: clear governance, policies, and decision rights.

It can help answer:

• Who must be involved?
• Who owns the work?
• Who approves the decision?
• Who provides specialist advice?
• Who receives the result?
• Who owns the next process step?

This reduces the risk that procurement activities fall between functions.

RACI can also address causes of non-compliance identified elsewhere in the LHTS framework, including:

• Unclear responsibilities.
• Late stakeholder involvement.
• Conflicting expectations.
• Unauthorised supplier communication.
• Uncontrolled contract changes.
• Weak contract handover.
• Limited accountability.

A matrix does not guarantee compliance, but it makes expectations easier to communicate, apply, and audit.

RACI and a compliance-driven culture

A compliance-driven procurement culture requires people to understand what is expected of them.

RACI contributes by making roles visible.

For example:

• The stakeholder understands that owning the requirement does not create authority to commit the supplier.
• The buyer understands that leading the sourcing process does not mean owning the technical decision.
• Legal understands when its advice is mandatory and when it is optional.
• The contract owner understands that responsibility continues after signature.
• Senior management understands which decisions require its involvement.

When leaders follow the agreed RACI and respect the defined authority boundaries, they reinforce the expected culture.

When leaders bypass the model, they signal that role clarity is optional.

Common mistakes when implementing RACI in procurement

Mistake 1: Confusing Accountable with authorised signatory

Accountability in a process model does not automatically create legal or financial authority.

Always check the matrix against delegated and signing authority.

Mistake 2: Assigning several Accountable roles

Multiple Accountable roles often mean that nobody clearly owns the result.

Use consultation to recognise important contributors while retaining one clear owner.

Mistake 3: Making everybody Consulted

Consulting too many people slows the process and weakens the distinction between advice and decision-making.

Consult roles whose input materially affects the outcome.

Mistake 4: Informing everybody about everything

Excessive reporting creates noise.

Define which milestones or decisions each Informed role needs.

Mistake 5: Building the matrix around people rather than roles

Named individuals change positions or leave the organization.

Define the role model first and assign names at project level.

Mistake 6: Using vague task descriptions

“Procurement,” “legal review,” or “approval” may cover several different actions.

Describe a measurable deliverable or decision in each row.

Mistake 7: Using only contract value to determine governance

Value is only one risk dimension.

Consider business criticality, information security, legal exposure, duration, dependency, and reputational impact.

Mistake 8: Treating the Sourcing Board as a vague collective owner

A board must have a clear mandate and decision procedure.

Otherwise, responsibility may move from the project team to a committee without creating real accountability.

Mistake 9: Creating a RACI that does not match the workflow

A document may say that one person approves while the procurement system routes approval to somebody else.

The RACI, policy, and system should describe the same operating model.

Mistake 10: Ending the matrix at contract signature

Value and risk continue after signing.

Include implementation, contract ownership, supplier performance, changes, renewal, and termination where relevant.

Mistake 11: Creating one matrix and never reviewing it

Processes, systems, risks, and organizational structures change.

The RACI should be reviewed when those conditions change.

Mistake 12: Using RACI as a substitute for leadership

A matrix cannot resolve every disagreement.

Management must still set priorities, allocate resources, resolve conflicts, and hold people accountable.

A procurement RACI quality checklist

Before approving a RACI matrix, check whether:

• The scope is clear.
• Each row describes a deliverable or decision.
• Roles rather than names are used.
• Each row normally has one Accountable role.
• The Responsible lead is clear.
• Consulted roles are limited to necessary contributors.
• Informed roles receive relevant rather than excessive updates.
• Delegated authority supports the assignments.
• Signing authority is shown separately where needed.
• Segregation-of-duties requirements are maintained.
• Value, risk, and complexity influence governance.
• Sourcing Board authority is formally defined.
• Contract implementation and ownership are included.
• The system workflow matches the matrix.
• Escalation routes are clear.
• A review owner and review date are assigned.

How procurement management uses RACI

RACI is primarily a procurement-management tool because management defines:

• The procurement operating model.
• Process ownership.
• Decision rights.
• Interfaces with other functions.
• Approval governance.
• Sourcing Board structure.
• Escalation routes.
• Role descriptions.
• Competence requirements.
• System workflows.

The Procurement Manager should ensure that the matrix provides enough control without requiring unnecessary management involvement in routine work.

A well-designed RACI delegates execution while retaining appropriate accountability.

How tactical buyers use RACI

Tactical buyers apply RACI in sourcing projects by:

• Confirming who owns the requirement.
• Agreeing stakeholder participation.
• Planning specialist reviews.
• Clarifying supplier communication.
• Preparing tollgate decisions.
• Escalating unresolved issues.
• Documenting approval.
• Planning contract handover.

The matrix helps the buyer lead the process without assuming authority that belongs to another role.

Learn more about procurement management

RACI connects procurement organization with procurement processes.

The Learn How to Source course Introduction to Procurement Management explains how procurement leadership works with organization, competences, roles, processes, methods, and tools.

This provides the foundation needed to design a RACI that supports the procurement operating model rather than existing as an isolated spreadsheet.

Frequently asked questions

What is a procurement RACI matrix?

A procurement RACI matrix assigns Responsible, Accountable, Consulted, and Informed roles to procurement tasks, deliverables, and decisions.

What is the difference between Responsible and Accountable?

Responsible performs or coordinates the work. Accountable owns the result and ensures that the work or decision is properly completed.

Can there be more than one Responsible person?

Several people can contribute to a task, but one clear Responsible lead normally makes coordination easier.

Can there be more than one Accountable person?

There should normally be one Accountable role for each task or decision. Multiple Accountable roles can create unclear ownership.

Is the Accountable person always the contract signatory?

No. Signing authority is established through formal company delegation. It should be checked and, where relevant, shown as a separate step.

Can a Sourcing Board be Accountable?

A formally mandated Sourcing Board can approve defined tollgates. Its authority, chair, quorum, decision method, and documentation requirements must be clear.

Should RACI be based only on purchase value?

No. Governance should also reflect risk, complexity, business criticality, duration, supplier dependency, legal exposure, and other relevant factors.

Who should create a procurement RACI?

Procurement management normally owns the model, but it should be developed with the functions that participate in the process, including business stakeholders, finance, legal, risk functions, and contract owners.

Does RACI replace procurement policy?

No. RACI supports the policy by clarifying roles. It does not replace authority limits, procedures, controls, or legal requirements.

When should a RACI be reviewed?

Review it when the process, organization, systems, authority structure, or risk requirements change, or when audits and repeated deviations reveal unclear ownership.

Conclusion

RACI can make procurement faster, clearer, and more controlled—but only when it is applied to specific work and connected to the organization’s actual governance.

An effective procurement RACI:

1. Defines clear deliverables and decisions.
2. Assigns one clear owner for each outcome.
3. Distinguishes execution, ownership, consultation, and communication.
4. Separates RACI accountability from approval and signing authority.
5. Reflects value, risk, complexity, and business impact.
6. Connects sourcing with contract implementation and supplier management.
7. Matches policies, workflows, and formal decision rights.
8. Is tested and updated through practical use.

The goal is not to involve more people.

The goal is to involve the right people, in the right role, at the right time—so procurement decisions can move quickly without losing accountability, transparency, or control.

Learn more about Procurement Management

This course package Procurement management program aims to provide learners with a comprehensive understanding of the responsibilities typically on the agenda of a Chief Procurement Officer (CPO).

Note: Illustration to the blogpost was created by CHAT GPT on Sept 14, 2024.