
Are You Managing Procurement, or Just Processing Purchases?
A requisition lands on Tuesday. Supplier named. Specification written to that supplier’s product sheet. Delivery date already promised to a client. Budget approved. Your job, as described, is to raise the order and get the price down if you can. You will do it well. You will also have had no influence whatsoever on the decision that determined what this costs, which happened three weeks ago in a meeting you were not in. How many of the requisitions you handled last month arrived in that condition?
Make your first decisionRead on. The first one arrives in about twenty seconds.
Why this matters now
The economics of that pattern have worsened. Where local content or ICV weighting affects award decisions, the choice of supplier is increasingly constrained by policy as well as by price and capability, and those constraints are far easier to work with at specification stage than at requisition stage.
The Saudi Local Content and Government Procurement Authority raised minimum local content requirements for the Mandatory List in a February 2026 decision phasing in from August 2026. In the UAE, an ICV certificate is voluntary but carries evaluation weight, and a supplier who has not certified scores nothing on that element.
If a specification has already been written around a supplier who cannot score on those elements, procurement receives a requisition that is expensive in a way that no negotiation can repair.
Procurement implicationBy the time a requisition names a supplier, most of the value has already been decided by somebody who was not accountable for it.
An honest count
Of the purchase requisitions your team handled last month, roughly what share arrived with the supplier already effectively chosen?
•Under a quarter. We are involved before requirements are fixed
•Around half. It depends on the category and the stakeholder
•Most of them. We influence price and terms, rarely the choice
•Nearly all. The specification usually names or describes one supplier
•I have never measured it, which is probably the more interesting answer
The third and fourth options are the norm rather than the exception, particularly in technical categories where the requester has genuine expertise and procurement does not. That is not a governance failure. It becomes one only when nobody has asked whether the specification could have been written differently.
What happened to Daniel
Daniel is a senior buyer at a Gulf healthcare group. He is quick, accurate and liked by his stakeholders, which in a hospital environment is worth more than it sounds.
His annual review is positive. Requisition turnaround is the fastest in the group. Supplier complaints are low. Savings are respectable. His manager tells him he is doing everything right and, on the terms he has been given, that is true.
What nobody discusses is that in the previous twelve months, roughly eighty per cent of what he processed arrived with the supplier already selected by a clinical or technical stakeholder. His contribution was speed and a modest discount on a decision made elsewhere.
The change starts accidentally. A consultant asks his opinion on a consumable, not as procurement but because Daniel had noticed a pattern in the failure rates across two brands. He had noticed it because he sees every order and nobody else does.
That conversation leads to a review of the category, which leads to a specification written around outcome rather than around a product, which leads to three suppliers bidding where previously there had been one. The price falls. More usefully, the clinical team ends up with a better product than they had specified for themselves.
Nothing about Daniel’s technical skill changed. What changed is that he brought information to a conversation that happened before the requisition, instead of processing the requisition efficiently after it.
Your turn. Six decisions.
There is no trick answer here. At least two options in most of these are defensible. What separates them is what you are prepared to trade, and whether you could defend the trade afterwards.
Decision 1The named supplierA requisition specifies a supplier by name and the specification matches their product sheet exactly.
AProcess it. The requester knows their requirement
BAsk what the requirement is, separately from the product
CSeek two comparative quotes for the file
DPush back and require an open specification
What this usually costs: B is the move that changes anything. Asking what problem the product solves is not a challenge to the requester’s expertise and it is usually welcomed. C produces quotes that nobody will act on, because the specification has already excluded the alternatives. D creates a fight you will lose in a technical category.Decision 2The information you already holdYou have visibility of failure rates, delivery performance and price movement across every supplier. The requesters see only their own.
AReport it if asked
BCirculate a quarterly summary to stakeholders
CBring it into individual conversations as they arise
DBuild it into the specification review process
What this usually costs: B and D together, and this is the single highest return activity available to a procurement team. The information asymmetry is real and it is in your favour for once. Most stakeholders do not know what you can see, and they are usually glad to.Decision 3The urgent requestA stakeholder needs something in four days and has approached a supplier directly to check availability.
AProcess the order and note the process breach
BHandle the urgency and diagnose the cause afterwards
CInsist on a competitive process despite the timeline
DEscalate to their director
What this usually costs: B. Fighting the urgency in the moment costs you the relationship and does not get the item any faster. Diagnosing it afterwards, when the pressure has gone, is when you find out whether it was genuinely unforeseeable or a planning failure that recurs monthly.Decision 4The specification you cannot assessA technical specification is beyond your expertise. You suspect it is unnecessarily narrow but cannot prove it.
AAccept it. Technical judgement is not yours to make
BAsk which requirements are functional and which are preferences
CBring in a second technical opinion
DAsk the market whether alternatives exist that meet the function
What this usually costs: B then D. You do not need technical expertise to ask which clauses are mandatory and why. And the market will tell you what alternatives exist far faster than an internal review will. Neither move requires you to challenge anybody’s expertise.Decision 5Where your time goesYour team spends most of its capacity on transactional processing. Category work happens when there is space, which is rarely.
ARecruit to create capacity
BAutomate or devolve low value transactions
CReduce service levels on transactional work to force the issue
DPick one category and protect time for it regardless
What this usually costs: D is the only one available to most people immediately, and it works. Waiting for capacity to appear is waiting forever, because transactional demand expands to fill whatever is available. One category, properly worked, produces the evidence that funds the rest.Decision 6What you report upwardYour monthly report shows requisition volumes, cycle times and savings.
AKeep it. Those are the agreed measures
BAdd the share of spend influenced before requirement setting
CAdd category level market movement against your prices
DReplace volume metrics with value metrics entirely
What this usually costs: B and C. Volume metrics describe how busy you are, which nobody senior is asking about. The share of spend you influenced early is the number that shows whether the function is strategic or clerical, and it is usually uncomfortable the first time you produce it.Influence is upstream, and it is not granted
The comfortable explanation for why procurement is consulted late is that the organisation does not understand procurement’s value. It is a satisfying explanation and it is mostly wrong.
Stakeholders involve people who bring something to the conversation. A procurement professional who arrives at specification stage with market intelligence, supplier performance data and a view on what alternatives exist is useful and gets invited back. One who arrives with a process requirement and a compliance reminder is an obstacle, and obstacles get routed around.
The uncomfortable part is that the information which makes procurement useful upstream already sits inside most procurement functions. Delivery performance, failure rates, price movement, supplier capacity. It is collected as a by product of transactional work and almost never packaged for anybody outside the team.
Influence is not granted by a governance policy. It is earned by being the person who knew something the requester did not.
Move one category upstream
Do this with a single category rather than attempting to reposition the whole function. It takes about six weeks and it produces the evidence you need to do it again.
1.Choose a category with a repeating pattern. Pick something bought regularly where you can see performance across suppliers over time. Repeatability is what makes your data credible. Ask yourself: Where do I already know something the requester cannot see?
2.Package what you already know. One page. Failure rates, delivery performance, price movement, alternatives in the market. No recommendations yet. Ask yourself: What would surprise the person who specifies this?
3.Ask about function, not product. Open the conversation with what the requirement has to achieve rather than with what should be bought. Ask yourself: What is this actually for, and what would count as a better outcome?
4.Rewrite the specification around outcome. Convert product descriptions into performance requirements wherever the technical position allows. Ask yourself: Which clauses describe a need and which describe a preferred supplier?
5.Measure the difference and say so. Compare price, competition and outcome against the previous cycle. Report it in one paragraph to the people who were in the room. Ask yourself: What changed because procurement was involved earlier?
Your upstream influence score
Take last month’s requisitions. This is a counting exercise rather than an opinion, which is what makes it useful.
What to write down
A. Total requisitions processed last month.
B. Of those, how many arrived with a supplier already named or effectively determined by the specification.
C. How many did you influence before the requirement was finalised.
D. Total value of the requisitions in C, as a percentage of total requisition value.
Then work out: Upstream influence rate equals C divided by A, as a percentage. Value weighted influence equals D. Compare the two figures.•Value weighted influence above 50 per cent. You are operating strategically on the spend that matters, regardless of what your requisition count looks like.
•25 to 50 per cent. Solid. The usual next gain is concentrating attention on fewer, larger categories rather than spreading it.
•10 to 25 per cent. The function is mostly downstream. Pick one category and run the framework above rather than attempting a general repositioning.
•Under 10 per cent. Procurement is being used as an execution service. That is a solvable problem and the first step is measuring it, which you have just done.
Why capable buyers stay downstream
The gap between transactional and strategic procurement is discussed constantly and diagnosed badly. The usual explanation blames organisational maturity, or stakeholder education, or the absence of a mandate. Those factors exist and they are rarely the binding constraint.
The binding constraint is usually time, and specifically the way transactional work protects itself. Requisitions have deadlines, visible queues and unhappy people attached to them. Category work has none of those. In any week where both compete, the requisition wins, every time, and it wins for good operational reasons. That is not a failure of discipline. It is what happens when urgent work and important work sit in the same inbox.
The functions that break out of it do one specific thing. They ringfence capacity for one category, accept a small deterioration in transactional service while doing it, and produce a result concrete enough to justify the next ringfence. They do not attempt a transformation programme. They do one category and then point at it.
The second constraint is that procurement rarely packages what it knows. A procurement team sits on the only complete view of supplier performance in the organisation. Requesters see their own experience. Finance sees the spend. Procurement sees both, across suppliers, over time. That is a genuine information advantage and in most organisations it is never written down, which means it cannot travel and cannot influence anybody.
What an experienced procurement leader examines first is not the operating model or the policy. It is whether anybody outside the function has ever received a page of procurement intelligence they could not have produced themselves. If the answer is no, the function will stay downstream regardless of what the governance document says.
The strategic reading is that procurement influence is a market position rather than an entitlement. You hold it by being more useful upstream than the alternative, which is nobody consulting anybody. Organisations do not resist that. They just rarely encounter it.
Where do you actually stand?
Seven questions on where your function actually operates. Count rather than estimate where you can.
1. Do you know what share of your spend you influenced before the requirement was finalised?
2. Have you ever changed a specification from a product description to a performance requirement?
3. Do stakeholders approach you before deciding what to buy in at least one category?
4. Do you circulate supplier performance information to anybody outside procurement?
5. Is any of your team’s capacity formally protected for category work?
6. Does your monthly reporting contain any measure other than volume, cycle time and savings?
7. Could you name the three categories where earlier involvement would produce the largest gain?
Score two points for a confident yes, one point for partly, zero for no. Then read your band below.
Execution focused0 to 4 pointsStrengths. Your service levels are good and your stakeholders rely on you.Likely gaps. Influence sits upstream of where you operate, so your effort is applied after the expensive decisions are made.Next step. Measure your upstream influence rate this month. The number itself usually starts the conversation.
Selectively strategic5 to 8 pointsStrengths. You have earned early involvement in at least one area and you know what it is worth.Likely gaps. It depends on individual relationships rather than on a repeatable method, so it does not scale or survive turnover.Next step. Document how you achieved it in that category and apply the same sequence to a second.
Category managing9 to 11 pointsStrengths. You shape requirements in your major categories and you can evidence the difference it makes.Likely gaps. The usual gap is at function level. Leading a team that works this way is different from working this way yourself.Next step. CIPM covers the leadership and governance layer specifically.
Commercially embedded12 to 14 pointsStrengths. Procurement is consulted as a matter of course before requirements are set.Likely gaps. Sustaining it through growth and staff changes is the real risk at this level.Next step. Build the practice into how the team is trained rather than how you personally operate.
The part nobody puts in a job description
A job title tells you what an organisation calls you. It does not tell you where in the decision chain you sit, and those two things separate more often than people expect.
It is entirely possible to hold a procurement manager title while performing senior buyer work, and to do it for years without anybody noticing, because the transactional load is real and the work gets done. The organisation is satisfied. The individual is busy. Nothing is visibly wrong.
What is quietly happening is that responsibility grows while capability grows more slowly, because the day never contains the kind of work that develops strategic judgement. You get better at the job you are doing rather than the job you are supposed to be doing.
The test is uncomfortable but simple. If your spend doubled tomorrow, would you need more people, or would you need to work differently? Answering more people is not wrong. But it is the answer of somebody operating downstream, and it is worth knowing that about yourself before somebody senior works it out first.
Where a formal programme actually helps
Moving upstream is partly organisational and partly a matter of capability. The organisational part is yours to negotiate. The capability part, strategic sourcing, cost analysis, category strategy and procurement leadership, is structured and teachable.
Blue Ocean Academy addresses it through two programmes at different levels.
CIPP or CIPM, in one line each
•CIPP. Build complete professional level procurement capability across sourcing, cost, contracts and supplier management. Choose this if you want the full practitioner foundation, or if parts of your experience are self taught.
•CIPM. Move from running a procurement process to leading a procurement function. Choose this if you already hold most of the practitioner ground and the gap is strategy, financial argument, risk and leading people.
If both look plausible, the honest test is the one in the assessment above. If you scored in the lower two bands, start with CIPP. If you scored in the upper two and the gaps were strategic rather than technical, CIPM is the better fit.
Get my procurement skills gap reportTwo questions only. When would you realistically start, and would this be self funded or employer sponsored?
One question before you go
Worth putting to your team. If procurement disappeared for a month and somebody else raised the orders, what exactly would the organisation lose? The honest answer to that is your actual value, and it is usually different from your job description.
Sources
Saudi Local Content and Government Procurement Authority, minimum local content increase for the Mandatory List, decided 15 February 2026, phased from 1 August 2026. Global Trade Alert record
UAE Ministry of Industry and Advanced Technology, National In Country Value programme. MoIAT programme page and the official UAE government platform
UAE MoIAT, issuing an ICV certification, including the audited financial statement requirement. MoIAT service page
The professional and the company in this article are composites written to illustrate a realistic situation. They are not a documented case study.