Government Procurement Needs Reasoning, Not Just Rules. Enter AI

People sometimes ask me why automating government procurement is so difficult.
After all, procurement involves rules. Computers are good at rules. Put the rules into a workflow, build some forms, add approval buttons, and let the system move the purchase from beginning to end.
I wish it were that simple.
After years of working in public-sector technology procurement, I think the fundamental obstacle is something we don't discuss enough:
Procurement is not merely a rules-based process. It is a reasoning process.
That distinction may explain why artificial intelligence can potentially accomplish what generations of traditional workflow systems could not.
There Isn't One Procurement Process
One misconception about government procurement is that there is a single process.
There isn't.
Two requests can both be called "IT procurements" and follow materially different paths.
What are we buying?
Is it hardware, software, maintenance, a subscription, or professional services?
How much does it cost?
Is the funding expense, capital, or mixed?
Does an existing government contract already cover it?
Is competition required?
Is the product manufacturer-specific?
Is a certified M/WBE involved?
Is the solution cloud-based?
Will government data be stored or transmitted?
Is sensitive information involved?
Are implementation services included?
Does the purchase require approval from another oversight entity?
Does it require a new contract, or can we issue a purchase order against an existing one?
Those questions lead to more questions.
And the answers interact.
That is why I have increasingly come to think of procurement not as one workflow, but as a series of decision gates with conditional branches.
The Hardest Part Comes Before the Checklist
This distinction became especially apparent to me while thinking about how to build a better electronic procurement-management process.
You can create a master checklist containing hundreds of possible tasks.
The hard part isn't creating the checklist.
The hard part is determining which parts of the checklist apply to this particular procurement.
That is what experienced procurement professionals do almost instinctively.
A request comes across my desk, and I begin reasoning through it.
What is actually being purchased?
What is its estimated value?
What funding is available?
Is there an existing City contract?
Could a state contract be used?
Is another government purchasing vehicle legally and practically available?
Does the requirement fit within that contract's scope?
If no existing vehicle works, what procurement methods are authorized?
What additional approvals does the chosen method trigger?
There isn't always a single hard-and-fast rule telling me, "For Procurement X, press Button Y."
I evaluate the facts, identify the permissible options, and determine the best fit.
Then the rules become much easier to apply.
That first reasoning step is precisely what has historically been so difficult to automate.
Traditional Automation Still Needed Me to Think for It
Traditional workflow software works well when business rules can be fully predetermined.
If A, then B.
If the purchase exceeds a certain amount, trigger an approval.
If capital funding is selected, display the capital section.
If the expiration date is 90 days away, send an alert.
Government should automate as much of that as possible.
But somebody still has to define all those if-then statements.
And procurement contains an enormous number of them.
Worse, some decisions aren't binary.
Suppose an existing government contract appears to cover the product.
Can we use it?
A traditional system might ask whether a contract exists.
An experienced procurement professional asks considerably more.
Is our agency authorized to use it?
Is this particular product or service actually within scope?
Is the proposed reseller authorized?
Does the pricing comply with the contract?
Is additional competition required?
Are there special forms?
Are the contractual terms acceptable?
Does another available vehicle produce a better result?
The database can store the answers.
The workflow can route the approvals.
But historically, a human being had to determine what questions to ask in the first place.
That is a very different computing problem.
This Is Where AI Becomes Interesting
Modern AI doesn't eliminate that reasoning requirement.
ChatGPT, Claude, and other large language models still need instructions, context, and human oversight.
But for the first time, I can realistically imagine teaching a system something much closer to the methodology an experienced procurement professional uses rather than programming every possible transaction path individually.
That is potentially transformative.
Instead of programming:
If field 17 equals X and field 23 exceeds Y, open workflow Z,
we may increasingly be able to tell an AI system:
Here are the applicable procurement rules.
Here are our available contract vehicles.
Here are our policies.
Here are previous procurements.
Here is how we evaluate funding.
Here is how we assess competition.
Here are the questions an experienced analyst asks.
Here are the exceptions.
Here are the circumstances that require escalation.
Now evaluate this requirement and identify the permissible procurement pathways.
That is much closer to how I actually work.
Technology Can Also Democratize Public Procurement
There is another reason I am optimistic about technology in procurement that has little to do with replacing administrative work.
Technology can democratize access to government business.
For decades, one practical barrier to public-sector competition has simply been knowing that an opportunity exists. A business cannot compete for a government contract it never hears about, and smaller companies generally have fewer people monitoring procurement opportunities than large government contractors do.
Technology can change that equation.
Platforms and marketplaces such as SAP-based procurement systems, Fairmarkit and GSA Advantage demonstrate different ways technology can expose government requirements and pricing to a much broader marketplace. Instead of relying primarily on familiar vendors, manually emailing a limited bidder list or expecting businesses to know where to look for opportunities, technology makes it increasingly possible to reach more potential suppliers much faster.
That matters to me because competition is not merely a procurement requirement. It is one of government's best tools for protecting taxpayers.
If technology allows me to solicit 50 potentially qualified businesses in roughly the time it once took to contact five, that is not simply administrative efficiency. It potentially gives small businesses, M/WBEs, regional suppliers and companies that have never previously sold to government a better opportunity to compete for public dollars.
It also gives government better market intelligence.
More competition can produce more pricing data, more alternatives and a better basis for determining whether a proposed price is fair and reasonable. It can reduce our dependence on the vendors we already know simply because they are the easiest ones to find.
AI could push this much further.
Imagine a procurement system that doesn't merely post a solicitation and wait for vendors to discover it. Based on the requirement, it could help identify potentially qualified suppliers, search appropriate contract vehicles and marketplaces, compare available products and pricing, identify businesses that have supplied similar requirements elsewhere, and help procurement staff broaden the competitive pool.
The objective should never be to have AI secretly decide who receives government business. Quite the opposite.
Use technology to make the front door wider.
Public procurement should be accessible to the broadest reasonably qualified marketplace, not primarily to companies that have mastered the art of finding government solicitations.
That is one of the most promising possibilities I see in procurement technology: making government purchasing simultaneously faster, more competitive and more inclusive.
The best procurement technology should not merely automate bureaucracy.
It should democratize opportunity.
AI Could Help Define the Business Rules
Ironically, one of AI's greatest contributions to procurement automation may occur before AI automates anything.
It can help us finally articulate the business rules.
Experienced employees carry enormous amounts of institutional logic in their heads.
I may look at a procurement and immediately recognize that I need to investigate an existing contract, determine whether the requirement fits its scope, examine pricing, consider an alternative vehicle, and determine whether additional approvals are triggered.
But unless someone documents that reasoning, the organization doesn't really own the process.
The employee does.
That creates key-person dependency and makes succession, training, and automation extraordinarily difficult.
AI creates an opportunity to interview the process itself.
Why did you choose that procurement method?
What alternatives did you consider?
What fact eliminated this option?
What approval did this characteristic trigger?
What would have changed your decision?
Repeat that exercise across hundreds of procurements, and we can begin turning professional judgment into an explicit decision architecture.
That has value even if AI never makes the final decision.
Imagine an AI Procurement Intake
I can envision a future procurement system beginning with a conversation rather than a static form.
The program office describes what it needs.
The system asks follow-up questions.
Is this a subscription?
Will government data be stored externally?
Is implementation included?
Is the manufacturer predetermined?
Why?
What is the estimated value?
What funding source will be used?
Is there an incumbent solution?
When must it be operational?
Based on those answers, the system conducts an initial analysis.
It identifies potentially available contract vehicles.
It flags missing information.
It suggests permissible procurement methods.
It identifies likely approvals.
It generates a preliminary checklist specifically for that procurement.
And, critically, it explains its reasoning.
Not:
Procurement Method: X.
But:
Procurement Method X appears potentially appropriate because of A, B, and C. Method Y may also be available if condition D can be established. Method Z appears unavailable because of E. Procurement staff should confirm the determination.
Now we are no longer simply automating a checklist.
We are augmenting professional judgment.
The Human Still Matters
I would not allow AI to make consequential procurement determinations autonomously.
At least not based on the technology as it exists today.
Government procurement involves law, policy, fiscal controls, market conditions, contractual interpretation and circumstances that do not always fit neatly into historical patterns.
AI can hallucinate.
Source documents can be outdated.
Rules change.
And sometimes experienced professionals disagree about the correct approach.
Human judgment remains essential.
But there is an enormous difference between saying AI should not make the final decision and saying AI cannot dramatically improve how we reach that decision.
I want AI to do the first-pass research.
I want it to identify the options.
I want it to tell me what information is missing.
I want it to compare the facts against documented rules.
I want it to challenge my assumptions.
I want it to explain why a particular path appears appropriate.
Then I want a knowledgeable professional to decide.
The Real Opportunity Is Institutional Knowledge
This may ultimately be AI's greatest contribution to government administration.
Government has extraordinary institutional knowledge.
Unfortunately, much of it resides in people's heads.
An experienced budget analyst knows which questions OMB is likely to ask.
A procurement professional recognizes when a purchasing vehicle doesn't quite fit.
A contract manager knows which provisions repeatedly cause problems.
A veteran employee knows which apparently simple request will become complicated three steps later.
When that employee retires or leaves, some of that knowledge walks out the door.
Traditional databases were good at storing information.
They were much less capable of capturing reasoning.
AI may finally give us a practical way to preserve and operationalize some of that reasoning.
Don't Replace Judgment. Scale It.
I remain enthusiastic about artificial intelligence precisely because I don't think its most important government use is replacing people.
It is scaling what our best people know.
For years, we tried to automate procurement by forcing professional judgment into rigid workflows.
Sometimes that worked.
Often it didn't, because the human still had to sit in front of the computer and answer all the questions that determined which branch of the workflow came next.
AI doesn't magically eliminate that problem.
ChatGPT, Claude, and every other current model still need humans to establish the rules, provide authoritative information, validate the reasoning, and make consequential decisions.
But there is an important difference.
For the first time, the machine may be able to help us reason through the branches, not merely execute them after a human has already figured everything out.
That is the breakthrough I am watching.
The future government procurement system should not simply ask an employee to select a procurement method from a drop-down menu.
It should help the employee determine which methods are available, explain why, identify what additional facts are needed, build the appropriate workflow, and then route the transaction through it.
The objective isn't to remove human reasoning from procurement.
It is to capture the best of that reasoning, make it methodical, make it teachable, and make it scalable.
After decades of trying to automate the checklist, artificial intelligence may finally help us automate something much more valuable: figuring out which checklist we need.





Join the discussion
Members can read and add comments on every article.