Why most government AI initiatives stall between pilot and production — and a practical path from ambition to governed, monitored deployment across digital infrastructure programs.
Every ministry of communications, public utility and development bank INA has advised in the past two years has an AI pilot underway — a chatbot for citizen services, a predictive-maintenance model for a fiber network, a scoring tool for permit reviews. Very few have a second one running at the same time, and fewer still have retired a pilot into standard operating procedure. The gap between AI enthusiasm and AI infrastructure — the governance, data, procurement and workforce foundations that let a pilot survive contact with a real budget cycle — is where public sector adoption actually fails.
This paper sets out a practical adoption path for public sector infrastructure organizations: what is different about applying AI inside government versus inside a private operator, the five barriers that recur across the projects INA has structured, an adoption framework built around five pillars, and a concrete first-180-days roadmap that a mid-sized ministry, utility or program office can execute without waiting for a national AI strategy to be finalized first.
“The public sector does not have an AI adoption problem. It has a project structuring problem that AI happens to be exposing faster than any prior technology wave.”INA AI Advisory Methodology™ — Field Notes, 2026
Three trends are converging on public infrastructure programs at the same time, and each raises the cost of waiting.
None of this means every agency should be building large language models. It means every agency structuring a digital infrastructure program in 2026 needs an explicit position on where AI fits — even if that position is “not yet, and here is why.”
These are the barriers INA sees repeat across public infrastructure AI initiatives, regardless of country or sector.
Network management, billing and asset systems are frequently procured as closed platforms. The agency owns the infrastructure but not an exportable, model-ready copy of its own operational data.
AI pilots get sponsored by whichever unit finds a use case first. Without a standing owner, each pilot restarts governance, procurement and risk review from zero.
Standard IT procurement assumes a fixed deliverable. It rarely addresses model retraining, drift monitoring, or the right to audit training data — all of which need to be contractual, not aspirational.
A single technically fluent champion often carries an entire program's AI literacy. When that person moves on, so does institutional capacity to evaluate vendor claims.
Ethics review, bias testing and human-in-the-loop checkpoints are usually written after a model has already made a visible mistake — at far higher political cost than if they had shipped with the pilot.
INA applies its AI Advisory Methodology™ (F4) — one of the seven INA Frameworks™ — to public sector infrastructure programs. It treats AI adoption as a governance discipline that moves across five pillars, not as a single technology purchase.
| Pillar | Applied to Public Infrastructure | Key Deliverable |
|---|---|---|
| Strategy & Use-Case Prioritization | Rank candidate use cases (predictive maintenance, permit triage, demand forecasting, fraud detection in public works spend) by data readiness and citizen impact, not by vendor pitch. | Use-Case Register |
| Data Readiness | Establish which operational data the agency can legally export, clean and retain outside vendor platforms before any model is scoped. | Data Readiness Report |
| Technology & Infrastructure | Decide build-vs-buy-vs-partner per use case, and where model inference needs to run relative to legacy OT/SCADA and network management systems. | Reference Architecture |
| Governance & Ethics | Define who can approve a model going live, what human-in-the-loop checkpoints are non-negotiable, and how bias and error rates get monitored post-launch. | Governance Charter |
| Adoption & Change Management | Build frontline staff capability and trust before scale-up — the pillar most public programs skip, and the one most correlated with pilots that survive. | Adoption Roadmap |
Programs move through four stages. Most public sector AI initiatives INA reviews sit at Stage 1 with the visibility of Stage 3 — a single successful pilot creates the appearance of maturity the underlying governance doesn't yet support.
Every AI Advisory engagement INA runs applies the same principle used across all seven INA Frameworks™: no AI agent or model holds final decision authority over a public resource, a citizen-facing determination, or public funds. Its role is always assistive.
A useful test for any proposed use case: name the specific person who is accountable if the model is wrong, and confirm they see the model's output before it affects a citizen or a budget line — not after.
AI capability for public infrastructure is rarely financed as a standalone line item. It is more often embedded inside a broader connectivity, data center or digital government program — which means it needs to be scoped early enough to shape that program's business case.
| Pathway | Typical Fit | Key Consideration |
|---|---|---|
| Multilateral development bank technical assistance | Data readiness assessments, governance charter design, use-case prioritization studies | Usually grant-funded and can start before a capital project is approved |
| Embedded within capital project financing | Predictive maintenance, network operations AI bundled into a fiber, FWA or datacenter loan | Must be scoped in the Business Case, not added after financial close |
| National digital government or innovation funds | Citizen-facing service pilots (permit triage, service chatbots) | Typically smaller tickets, useful for proving Stage 1–2 pilots |
| Vendor-financed pilots | Fast proof-of-concept for a single use case | Negotiate data portability and exit terms before the pilot, not at renewal |
See INA's Multilateral Finance page and the Multilateral Finance Navigator™ (F6) for how AI-enabled components are evaluated alongside the rest of a project's financing structure.
| Risk | Probability | Impact | Primary Mitigation |
|---|---|---|---|
| Vendor lock-in on proprietary models or data formats | High | High | Contractual data portability and export rights, negotiated before signature |
| Biased or unrepresentative training data | Medium | High | Bias testing against demographic and geographic segments before go-live |
| Model outputs treated as final without review | Medium | High | Named human-in-the-loop reviewer at every citizen- or fund-affecting decision |
| Sensitive citizen or operational data exposed to external AI providers | Medium | High | Data-handling policy and confidentiality terms fixed before any pilot starts |
| Pilot fatigue — no path from proof-of-concept to budget line | High | Medium | Adoption Roadmap with a funded Stage 2→3 transition built in from day one |
| Legacy OT/SCADA systems unable to expose data safely | Medium | Medium | Data Readiness assessment scoped before technology selection, not after |
A program office does not need a finished national AI strategy to start. It needs these four moves, in this order.
Designate a single accountable owner for AI adoption inside the program office. Inventory every AI idea already circulating — formal or informal — into one Use-Case Register.
Gate — Ownership confirmedConfirm which operational data can legally be exported from vendor systems. In parallel, draft the Governance Charter defining approval authority and human-in-the-loop checkpoints.
Gate — Charter approvedSelect the single highest-readiness use case from the register and run it end-to-end under the new charter — including the human reviewer step, not just the model.
Gate — Pilot reviewUse the completed pilot's results to write the budget line or financing request that carries the use case into standard operating procedure — before institutional momentum fades.
Gate — Budget securedAI adoption in public sector infrastructure succeeds or fails on the same discipline that determines whether any infrastructure project succeeds: clear ownership, data that is actually available when needed, procurement written for what is really being bought, and governance that exists before the first incident rather than after it. Treat AI as a new layer on the same Project Structuring Framework™ discipline already applied to fiber, spectrum and datacenter programs, and it stops being a special case.
Published by International Network Advisors (INA), September 2026. Part of the INA Knowledge library, drawing on the INA AI Advisory Methodology™ (F4).
INA's advisory team can run this framework against your program in a structured engagement, starting with a Use-Case Register and Data Readiness assessment. Request Advisory →