Decision rights
Clarifies who can select suppliers, approve spend, sign contracts, accept deviations and release urgent purchases.
Service detail
Design procurement so the business knows who decides, who owns and how control works.
A procurement operating model translates business strategy into practical governance, decision rights, category ownership, policies, routing logic and management routines that people can use in daily work.
NuWayMind service detail
From purchasing activity to management discipline
The operating model defines how demand, suppliers, commitments, contracts, approvals and performance are governed before spend becomes cost.
Leadership purpose
Strategy becomes executable only when decision rights are visible in daily work.
Many organisations have policies, but still operate through local habits, unclear ownership and email-based exceptions. The operating model turns purchasing into a controlled management system: who may request, who must approve, who owns suppliers, when Finance or Legal is involved, how exceptions are escalated and how performance is reviewed.
For CEO, CFO and COO stakeholders, the value is not efficiency alone. The real benefit is better command over commitments, third-party exposure, cash impact, operational continuity and compliance evidence.
Business ownership
Defines how budget owners, operations, finance, legal, quality and procurement share accountability without duplicating approvals.
Control routines
Converts governance into recurring routines: category reviews, supplier reviews, spend reports, exception logs and KPI checkpoints.
Main challenges
Most operating-model gaps look like speed issues; underneath, authority and risk logic are unclear.
Decision rights are unclear
Business users, procurement, finance and leadership may all influence provider decisions, but no one has a single accepted accountability model. This creates rework, delayed approvals, bypassed processes and inconsistent provider choices.
Policy exists outside the workflow
Rules may be documented in PDF policies, but users work in email, spreadsheets and disconnected systems. When the workflow does not enforce policy logic, exceptions become normal practice and evidence is difficult to reconstruct.
Approval thresholds are not risk-based
Many organisations approve based only on value. A low-value supplier may create quality, data, service continuity or compliance risk. The operating model must combine value, supplier type, category risk and business impact.
Category ownership is weak
Spend categories are often managed transaction by transaction. Without category owners, supplier strategy, demand consolidation, framework agreements and savings initiatives remain fragmented.
Local entities work differently
Groups with multiple entities, clinics, sites or countries often have different approval habits, vendor records and contract practices. This prevents comparable reporting and makes group-level control difficult.
KPIs do not drive behaviour
Performance reports may show savings or order volume, but they often miss commitment visibility, contract coverage, PO compliance, supplier risk and process-cycle bottlenecks.
Operating-model design
The target setup defines practical governance by spend type, risk class and supplier criticality.
Governance architecture
Define management forums, escalation routes, procurement mandate, decision rights and executive sponsorship.
Delegation of authority
Translate spend value, risk and contract exposure into clear approval thresholds and sign-off requirements.
Role model and RACI
Clarify accountability between business owner, budget owner, procurement, finance, legal, quality and operations.
Category and supplier ownership
Define category segmentation, supplier tiers, preferred supplier logic and ownership of commercial strategy.
Policy and SOP structure
Document only rules that can be executed, monitored and trained; remove policy complexity that users cannot follow.
Management reporting
Create dashboards for commitments, compliance, savings, supplier risk, exceptions and process health.
Typical outputs
Deliverables are prepared for implementation, not for presentation only.
| Output | What it defines | Management value |
|---|---|---|
| Target operating model | Procurement mandate, role design, governance forums and ownership logic. | Creates a common management language for procurement control. |
| DoA and approval matrix | Who approves what, at which value, risk level, category and exception type. | Reduces ambiguity and prevents unmanaged commitments. |
| Procurement policy and SOP set | Practical rules for supplier onboarding, sourcing, contracts, PR/PO, receiving and invoices. | Makes daily execution consistent and auditable. |
| Category governance model | Category owners, supplier tiers, review cadence and savings pipeline logic. | Moves procurement from reactive buying to active spend management. |
| KPI and reporting pack | Performance measures for compliance, value, cycle time, risk and adoption. | Allows leadership to steer procurement through evidence. |
Performance indicators
Measures need to prove that the model is being used in real decisions.
PO complianceShare of addressable spend routed through approved PR/PO workflow before supplier commitment.
Contract coverageSpend and critical suppliers covered by valid agreements, renewals and ownership.
Approval-cycle timeAverage time from request submission to final approval, split by value and risk class.
Exception rateTransactions bypassing standard policy, threshold, preferred supplier or documentation rules.
Preferred vendor usageShare of relevant demand channelled to approved suppliers and negotiated agreements.
Supplier risk review completionCompletion of scheduled reviews for critical, high-spend or regulated suppliers.
Implementation roadmap
Build the control logic first; then embed it into workflows, routines and dashboards.
0–6 months
Clarify
Confirm mandate, decision rights, approval thresholds, urgent policy gaps and core supplier governance.
6–12 months
Standardise
Deploy common SOPs, category ownership, reporting routines and cross-functional review forums.
12–24 months
Embed
Automate approvals, supplier controls and KPI dashboards so the model becomes the way people work.