Procurement Operating Model Design for Australian Organisations
Most Australian organisations have a procurement function. Far fewer have a deliberately designed procurement operating model.
The distinction matters more than it might appear. A procurement function is a group of people who handle purchasing activities. A procurement operating model is the architecture — the structure, governance, roles, processes, technology, and capability — that determines how much value that function can actually deliver. The same spend base, managed through a well-designed operating model versus a poorly designed one, can produce radically different outcomes: not percentage points of difference, but multiples.
This article explains what a procurement operating model is, what the core design choices are, how Australian organisations approach the design process, and what the failure modes look like. It is written for Chief Procurement Officers, CFOs, and operational leaders who are thinking seriously about whether their current procurement structure is fit for purpose — and what to do if it is not.
What Is a Procurement Operating Model?
A procurement operating model defines how the procurement function is organised and how it operates. It answers a set of interconnected questions:
- Structure: Where does procurement authority sit — centralised, decentralised, or some hybrid?
- Scope: What spend categories and business units does procurement cover?
- Roles and responsibilities: Who does what — and who decides?
- Governance: What authorities, policies, and delegations govern procurement activity?
- Processes: How are sourcing, contracting, purchasing, and supplier management activities performed — and to what standard?
- Technology: What systems support the procurement function, and how are they used?
- Capability: What skills and capacity does the function require to execute its mandate?
- Performance: How is procurement value measured and reported?
The operating model is the blueprint that holds these elements together. When it is well designed and well implemented, procurement operates as a coherent function with clear accountability, consistent processes, and the capacity to deliver value at scale. When it is poorly designed — or not designed at all — the result is fragmentation: duplicated effort, inconsistent supplier terms, maverick spend, compliance failures, and a function that struggles to demonstrate its contribution.
The Three Core Structural Models
The foundational structural choice in procurement operating model design is the degree of centralisation. Three broad models exist, each with distinct trade-offs.
Centralised Procurement
In a centralised model, all procurement authority is held by a single function — typically a central procurement team reporting to a CPO or CFO. All significant purchasing decisions flow through this team, regardless of which business unit, division, or site is the end user.
Centralised models deliver the most spend visibility, the strongest aggregation of volume across the organisation, and the most consistent supplier terms. They are the natural structure for organisations that want to maximise leverage with suppliers, enforce compliance, and build deep category expertise. They work well in organisations with relatively homogeneous spend across business units, or where the cost efficiency and governance benefits of centralisation outweigh the need for local responsiveness.
The risk of full centralisation is distance from the business: a central procurement team that is perceived as slow, rigid, or insufficiently attuned to operational requirements will be bypassed. Maverick spend — purchasing outside approved channels or contracts — is the most visible symptom of a centralised model that has lost the confidence of its internal customers.
Decentralised Procurement
In a decentralised model, procurement authority sits with individual business units, divisions, or sites. Each unit manages its own purchasing, selects its own suppliers, and negotiates its own terms. There is little or no central oversight.
Decentralised models maximise responsiveness and local flexibility. They suit organisations where business units have genuinely different requirements — different sectors, different geographies, different supply markets — where centralising procurement would produce a function that is too generic to be useful. They are common in early-stage or rapidly growing organisations that have not yet accumulated the scale or the management bandwidth to build a central function.
The cost is predictable: fragmented spend visibility, duplicated effort across units, inconsistent supplier terms, no volume aggregation, and a higher risk of compliance failures. Organisations with decentralised procurement consistently pay more for the same goods and services than they need to — because they are not leveraging their combined purchasing power.
Centre-Led Procurement
The centre-led model is the dominant structure in well-run Australian organisations of meaningful scale. It combines centralised strategy with decentralised execution: a central procurement team owns category strategy, sourcing processes, supplier agreements, policy, and governance. Business units and operational teams operate within that framework — accessing approved suppliers, placing orders, and managing day-to-day supplier relationships within defined parameters.
The centre-led model resolves the core tension in procurement structure: the need for volume aggregation and strategic coherence on one side, and operational responsiveness and local relevance on the other. It does not require all purchasing to flow through a central team. It requires that the strategic decisions — who the organisation buys from, on what terms, and under what conditions — are made centrally, with the benefits distributed operationally.
Research by The Hackett Group indicates that around two-thirds of organisations are moving toward hybrid models that combine elements of different approaches. Ankura In Australian practice, the centre-led model in some form has become the default for organisations above approximately $500M in revenue — though the specific design varies considerably.
The Six Design Dimensions
Choosing a structural model is necessary but not sufficient. A well-designed procurement operating model requires deliberate choices across six dimensions.
1. Scope and Mandate
Define what the procurement function is responsible for. This sounds obvious but is frequently ambiguous in practice — with different assumptions held by the procurement team, the CFO, and operational leaders about which categories and activities procurement owns.
Scope decisions include: which spend categories are under procurement management (indirect categories like FM, IT, professional services, and fleet alongside direct materials or operational inputs), which business units or entities are within the procurement mandate, and whether procurement's role is to execute sourcing or to set strategy and governance while execution sits elsewhere.
A narrow mandate — procurement responsible only for major sourcing events on a subset of categories — limits the function's impact. A broad mandate — procurement responsible for all significant external spend — maximises value but requires the capability and capacity to match. The right scope for any organisation depends on its procurement maturity, the complexity of its spend base, and the appetite of leadership to resource the function appropriately.
2. Organisational Structure and Roles
Design the team structure: how many people, in what roles, reporting to whom, and organised around what logic — category, business unit, or a combination.
In centre-led models, the typical structural tension is between category management depth (teams organised by spend category, building deep market knowledge) and business unit alignment (teams organised by internal customer, building strong relationships with operational stakeholders). Larger procurement functions typically combine both: category specialists who own sourcing strategy and market expertise, and business partners who own the relationship with specific business units and translate operational requirements into category plans.
Role definition is as important as headcount. A clear distinction between strategic roles (category management, strategic sourcing, contract management, supplier relationship management) and transactional roles (purchase order management, invoice resolution, supplier onboarding) is essential for a function that wants to mature beyond execution toward genuine strategic contribution.
Reporting lines matter too. Procurement functions that report to the CFO are typically treated as cost control functions — valued for savings and compliance. Functions that report to a COO or CEO have a broader mandate and are more likely to be engaged on supply chain strategy, risk management, and supplier innovation. Neither structure is inherently superior, but the reporting line signals — to the rest of the organisation — what the function is for.
3. Governance and Decision Rights
Governance defines the rules within which procurement operates: what authority levels apply, who can approve what, how exceptions are handled, and how compliance is monitored.
In practice, procurement governance breaks down into three layers:
Policy: The principles and rules that govern procurement activity — what processes must be followed, what minimum requirements apply to sourcing events of different values, what conflict of interest and probity obligations apply.
Delegation of authority: The specific dollar thresholds and category boundaries that determine who can approve purchases at each level of the organisation — from operational managers approving low-value purchases to CPOs or boards approving major contracts.
Compliance and audit: The mechanisms that monitor adherence to policy and delegation — spend visibility tools, purchase order compliance tracking, contract register management, and periodic audit of sourcing activities.
Governance design is where procurement operating models most frequently fail in practice. Governance that is too tight creates friction, drives maverick spend, and makes procurement the enemy of operational speed. Governance that is too loose is effectively no governance: policy exists on paper but not in practice, and the organisation has no reliable visibility into what it is spending or with whom.
4. Category Management Structure
Category management is the ongoing strategic oversight of groups of related spend — the activity that determines how the organisation approaches its supply markets, develops its sourcing strategies, and manages its supplier relationships over time.
A well-designed operating model defines which categories exist, who owns them, what the category manager is accountable for (category strategy, sourcing events, contract management, supplier performance, spend reporting), and how frequently category strategies are reviewed and refreshed.
The number and depth of categories the organisation can actively manage is constrained by the size of the procurement team. Prioritisation is therefore essential: not every category warrants the same investment of category management effort. High-spend, strategically important, or competitively sensitive categories deserve dedicated category management. Lower-spend, commodity categories may be managed more lightly — through standing contracts, catalogue purchasing, or periodic sourcing events rather than continuous active management.
5. Process Architecture
Define the standard processes through which procurement operates: the source-to-contract process (from category strategy and sourcing through to contract execution), the purchase-to-pay process (from purchase requisition through to invoice payment), the supplier onboarding and management process, and the contract management process.
Process architecture design involves decisions about which activities are standardised (the same process applies regardless of category or business unit), which are scaled (different processes apply at different spend thresholds), and which are flexible (category-specific processes apply for specific contexts).
Technology is inseparable from process architecture. The procurement technology landscape has matured substantially — e-sourcing platforms, contract management systems, supplier information management tools, and procure-to-pay systems each support specific process domains. Designing the process architecture and the technology architecture together, rather than sequentially, produces much better outcomes than retrofitting technology onto existing processes.
6. Capability and Capacity
The operating model cannot exceed the capability of the team that operates it. Capability assessment — an honest evaluation of the skills, experience, and capacity the procurement team currently has against what the target operating model requires — is essential before designing a model that the team cannot deliver.
Common capability gaps in Australian procurement functions include: strategic sourcing and category management skills (moving beyond transactional tendering to genuine market strategy), commercial negotiation (the structured negotiation of complex supplier arrangements), data analytics (building and using spend analytics and market benchmarking), and supplier relationship management (developing differentiated relationships with strategic suppliers).
Capability gaps can be addressed through recruitment, training and development, or the targeted use of external expertise for categories where the internal team lacks sufficient depth. The operating model design should include a capability roadmap — a realistic plan for building the skills the function needs to deliver its mandate over a 2–3 year horizon.
The Design Process
Designing a procurement operating model from scratch — or redesigning an existing one — follows a structured process.
Diagnose the current state. Before designing anything, understand the current position: what the existing model looks like, where it is performing well, and where it is failing. Current state assessment typically covers spend analysis (what is being spent, with whom, in which categories), organisational review (team structure, roles, headcount, reporting lines), process review (how sourcing, contracting, and purchasing actually operate — not just on paper), governance review (what policies and delegations exist and whether they are followed), and technology review (what systems are in use, how they are used, and where the gaps are).
Define the design principles. Before making structural decisions, agree on the principles that should guide the design. These typically include: the balance between centralised control and operational flexibility, the ambition level (cost control function vs. strategic business partner), the technology investment appetite, and the timeline for implementation. Design principles prevent the process from becoming a debate about specific structural choices before the underlying priorities have been agreed.
Develop and evaluate structural options. Model two or three structural scenarios — typically a more centralised option, a centre-led option, and a more decentralised option — against the design principles and the specific context of the organisation. The evaluation should be explicit about the trade-offs: each model will perform better on some dimensions and worse on others. The right choice is the one that best fits the organisation's priorities, not the theoretically optimal model.
Design the target model in detail. Once the structural approach is agreed, design the target model across all six dimensions: structure, scope, governance, category management, processes, and capability. This produces the operating model blueprint — a detailed specification of how the function will operate at the end of the transformation.
Develop the implementation roadmap. Design the path from current state to target state: the sequence of changes, the transition arrangements, the change management plan, and the milestones that track progress. Operating model transformations typically take 12–24 months to implement meaningfully, with the full value of the new model visible over a 3–5 year horizon.
What Australian Organisations Get Wrong
Several failure modes appear repeatedly in procurement operating model work across Australian organisations.
Designing for theory, not context. Generic best-practice frameworks — "you should be centre-led with category management" — are a starting point, not an answer. The right operating model for a $2B retail group is different from the right model for a $500M government-owned corporation, which is different again from the right model for a $5B integrated resort operator. Operating model design must be grounded in the specific context of the organisation — its sector, its spend profile, its geographic footprint, its culture, and its procurement maturity.
Structural change without process change. The most common failure in procurement operating model transformations is reorganising the team without changing the processes. Restructuring from a decentralised to a centre-led model while leaving the sourcing, contracting, and purchasing processes unchanged produces a new org chart, not a new capability. Structure and process need to be redesigned together.
Underestimating change management. Procurement operating model change affects every business unit that interacts with procurement — which is most of the organisation. The transition from decentralised purchasing (where operational managers have autonomy) to a centre-led model (where strategic decisions sit with a central team) is a significant change for the business, not just for the procurement function. Failing to manage that change — to communicate why the new model is better, to train stakeholders on new processes, to build trust between the central team and business units — produces resistance, workarounds, and maverick spend.
Technology as the solution, not the enabler. A recurring pattern is organisations that invest in a Source-to-Pay technology platform expecting it to transform their procurement function — and are then surprised when it does not. Technology enables a well-designed operating model. It cannot substitute for one. Investing in e-sourcing or P2P technology before designing the operating model and processes it needs to support typically produces a technology deployment that is underused, resisted, or bypassed.
Underfunding the function. The procurement function is consistently underfunded relative to its potential return. A function managing $500M in external spend, staffed with five people predominantly focused on transactional processing, has neither the capacity nor the capability to run a strategic sourcing programme that captures 10% improvement across the spend base. Organisations that design an ambitious operating model and then refuse to resource it appropriately will be disappointed by the outcomes.
How Trace Consultants Can Help
At Trace Consultants, procurement operating model design is core to what we do. We work with Australian organisations to diagnose their current procurement capability, design the operating model that is right for their context, and implement the changes needed to make it work — including the process design, governance frameworks, technology selection, and capability development that sit alongside the structural changes.
Our Procurement team brings direct category expertise and operating model experience across sectors including retail, property and hospitality, health and aged care, government and defence, and FMCG and manufacturing. We have designed and implemented operating models for organisations at very different starting points — from government agencies building a procurement function from near-scratch, to large commercial organisations redesigning a mature function that has stopped delivering value.
Our approach is distinctive in three ways. We design operating models that are realistic: calibrated to the organisation's actual capability, culture, and appetite for change, not idealised models that exist only on paper. We integrate operating model design with category strategy work — because the operating model is only valuable insofar as it enables better sourcing outcomes. And we focus on implementation, not just design: the blueprint is only the starting point.
Whether your challenge is fragmented spend and no visibility, a procurement team that is overwhelmed by transactional work and unable to do category strategy, governance failures and compliance risk, or a function that has simply stopped delivering value, we can help.
We also offer Organisational Design capability for broader functional design work, and Project & Change Management for operating model implementation programmes.
Explore our Procurement capability →
