The AOG Panel Exists. Most Agencies Treat It Like a Search Engine. It Isn't.
A procurement lead has a requirement. They go to the AOG panel. They find a supplier name they recognise. They send an email. Work starts.
No mini-tender. No evaluation. No defined requirements. No documented decision.
Technically compliant. Practically useless.
This is happening constantly across NZ government agencies. And it's quietly eroding the value of one of the better procurement frameworks the public sector has built.
What the AOG Panel Actually Is
The All of Government panel isn't a pre-approved list of suppliers you can use without thinking. It's a pre-qualified market MBIE assembled on your behalf.
The distinction matters.
MBIE did the evaluation work. They assessed suppliers against defined criteria. They negotiated commercial terms. They established performance expectations. That's the infrastructure underneath the panel — and it's there so agencies don't have to rebuild it from scratch every time they need ICT capability.
But the framework was designed around a critical assumption: that agencies would still run a competitive process within it.
Mini-tenders between panel suppliers. Requirements that actually describe the work. Responses evaluated on merit. Decisions documented.
That's how a pre-qualified market creates value. When you skip that step, you're not using the framework. You're wearing it like a rubber stamp.
The Search Engine Problem
Here's what the shortcut looks like in practice.
Agency needs a cloud infrastructure lead. Procurement officer goes to the panel list. Sees a supplier they've dealt with before. Sends a brief. Gets a CV back. Done.
Three other panel suppliers would have sent stronger candidates. One of them has a specialist with exactly the background this project needs. But they never got the brief. Nobody knew to ask.
The panel gave the agency access to a competitive market. The agency used it to avoid competing.
That's not procurement. That's just picking the first name you recognise and calling it a process.
Why It Keeps Happening
Procurement teams in NZ government agencies are stretched thin. Demand for ICT capability has grown. Headcount hasn't kept pace. Running a proper mini-tender — writing a defined statement of work, issuing to multiple suppliers, evaluating responses, documenting the decision — takes time that teams don't feel they have.
So corners get cut. The familiar supplier gets the call. The timeline pressure becomes the justification.
I understand this. Capacity constraints are real. But the corner being cut isn't a minor administrative one. It's the competitive step that makes the whole framework function.
Speed to contract is not the same thing as value for money.
And when the shortcut leads to a mismatched supplier, a stalled project, or a capability gap nobody spotted until month three, the timeline pressure that justified the shortcut looks a lot smaller than the cost of fixing what it caused.
What Good AOG Use Actually Looks Like
Running a proper mini-tender within the panel doesn't have to be a six-week exercise. It just has to be real.
Write a requirement that means something. Not "senior ICT contractor." Something like: "Azure infrastructure architect with experience in hybrid identity, 3+ days on-site per week, six-month engagement with a three-month right of renewal." The specificity is the point. Vague requirements produce vague responses and make evaluation impossible.
Go to at least three suppliers. The panel was built with multiple suppliers for a reason. Give them a week. A clear brief, a defined response format, a submission date. That's it.
Evaluate against the requirement. Not against familiarity. Score the responses. Make a call. Document why you chose who you chose. That documentation isn't bureaucracy — it's your audit trail and your decision quality check in one.
Have the SLA conversation before you sign. Panel suppliers have agreed to performance standards as part of getting on the panel. Ask them specifically: what does that mean for this engagement? How do you measure it? What happens if you miss it? Get that in writing, not implied.
None of this adds months. A well-run mini-tender inside the panel takes two weeks if you know what you need going in.
The Panel Degrades When Agencies Don't Use It Properly
This isn't just a process compliance issue. It has downstream effects that compound over time.
When work goes to whoever responds fastest rather than whoever offers the best capability, suppliers stop investing in depth. Why build genuine specialisation when speed and familiarity win? The race to the bottom on quality starts the moment merit stops being the criteria.
Agencies end up with suppliers on the panel who've won work without being tested against real requirements. Nobody finds out they're not the right fit until the engagement is already live.
And when it goes sideways — and it does — the audit trail is thin. "We used a panel supplier" is not the same as "we ran a compliant, competitive process and selected on merit." MBIE's framework protects you when you follow it. It doesn't protect you when you use it as a label.
The panel is only as good as the discipline of the agencies drawing on it.
The Simple Version
If you're procuring ICT capability through the AOG panel:
Write down what you actually need. Go to three suppliers. Give them a reasonable timeframe to respond. Evaluate the responses. Document your decision.
That's the whole thing. That's the framework working as intended.
If your timeline doesn't have room for even that, you have a planning problem. A procurement shortcut won't fix it — it'll just move the problem downstream, where it'll cost more to solve.
The panel is there to make good procurement faster. Not to make skipping procurement look acceptable.
Lexel operates on the All of Government panel for ICT services. We think the panel works — when it's used properly.