State CIO Priorities for the Next Budget Cycle

Budget season in a state secretariat produces a familiar pile: every department wants an agent, a dashboard and a centre of excellence. The CIO is asked for a number. Vendors arrive with national percentages. Someone quotes a 38 percent procurement jump as if it were a mandate to spend. The finance secretary asks what will still work if the model vendor disappears. That last question is the only one that should set the order of the pile.

This data study is a method. It is not a ranked census of Indian state CIOs for FY 2026-27. Anyone circulating such a census without a methods note is selling access. What follows is how to build a one-page priority list that a finance department can dislike in detail rather than in mood.

It is dated 17 August 2026. MeitY's India AI Governance Guidelines of 5 November 2025 are principles, not a budget circular. DPDP operational duties phase toward May 2027; your citizens did not wait. Fund controls now.

A working order you must overwrite

First, the human gate and the reconstructable packet on any live citizen-facing agent. If you already have a scheme or single-window pilot that can deny without an officer, that is not an innovation line. It is a repair line. It outranks new GPUs.

Second, SDC readiness: power, a modest enclosure if the walk supports it, ops people, deny-outbound. Without this, every later line becomes a public API in a moment of panic.

Third, one or two clerks that recover hours — permit completeness, circular retrieval, eligibility assembly — with sampled exclusion rates. Not twelve departments.

Fourth, vernacular-first interfaces and GIGW work on anything a citizen will see. This is not decoration. It is how rural exclusion does not hide in English error strings.

Fifth, a change-request and freeze-calendar envelope. Go-live is not the end of spend. Elections will stop you. Departments will change the circular. If you do not fund that, you will raid the next scheme.

Starter priority rows for a composite state CIO. Replace the comments with your incident list and your finance circular.

Priority	Line	Why it sits here	Do not fund instead
1	Human gate and packet on live agents	Exclusion and audit land first	A new chatbot on the same broken workflow
2	SDC power / enclosure / ops / egress	Parent for everything else	Temporary public-API 'until the rack comes'
3	One reconstructable clerk	Hours you can re-time	Twelve departmental COEs
4	Vernacular and GIGW on citizen surfaces	Exclusion hides in language	English-only 'phase 2 localisation'
5	CR envelope and MCC calendar	Go-live is not the end	A year-one scope that assumes no elections and no circulars

What not to put in the first cut

Do not put police auto-FIR, health public-API summarisation, or land auto-mutation in the first cut. Those are high-line files. A governance body (a later playbook in this batch) should see them before a budget line exists.

Do not put a 'state LLM' as a prestige object without a parent, a corpus you have rights to, and a denied-egress test. Prestige models consume the ops people you needed for the clerk.

Do not put a spend target derived from someone else's GeM growth rate. The next article is the method for that number. Until you run it, it is a title, not a priority.

Two budget notes after the same retreat

Objections you will hear — and what to do with them

Other states are announcing more

Other states also bury programmes after MCC or after the first writ. Announce what you can reconstruct. Copying a press note is not a peer review.

If we do not spend the AI head we will lose it

Then spend it on the parent and the gate, not on twelve half-agents. Surrendering a head is better than buying an incident that defines the next cycle.

Departments will revolt if they are not in year one

Give them the circular-retrieval clerk on a shared platform when they bring a human gate. That is a door. It is not a veto.

Governance can wait until we have systems

Governance is how you decide which systems you are allowed to have. Fund the body as a cheap line. It will save you an expensive one.

A four-week playbook before the budget circular hardens

1. Week 1: list live agents and score them for silent denial. Those repairs are priority 1.
2. Week 2: finish the SDC walk. If the numbers are missing, you cannot fund a model line honestly.
3. Week 3: pick one clerk. Time fifty cases. Write the hours.
4. Week 4: write the one-page priority note, the MCC calendar, and the CR envelope. Leave prestige objects in an annex called 'not this cycle unless the gate exists'.

File note you can paste

Subject: Proposed CIO priorities for the next budget cycle — method, not a national ranking.

This department has not relied on an invented census of state CIOs or on an unverified procurement-growth percentage. Proposed order: (1) human gates and reconstructable packets on live citizen-facing agents; (2) SDC readiness; (3) one or two clerical workflows with sampled hours; (4) vernacular and GIGW on citizen surfaces; (5) a change-request envelope and an election-freeze calendar. High-line domains — police records, clinical text to public APIs, land writes — are out of the first cut. This note is an aid to finance concurrence. It is not a budget circular.

This note is not legal or procurement advice.

Prcept AI will not give you a fake ranking of your peers. We will help you re-time fifty files and host the clerk where you can see it. If that is too small for the retreat, the retreat is the wrong room.

How to write the one page to finance

Finance does not want a vision. They want a parent, a unit of work, and a cap. Write: the SDC walk numbers; the one clerk and the fifty-file timing; the CR schedule; the MCC freeze list; the refused public-API line. Attach the agent register if you have one. Leave the centre-of-excellence floor plan in an annex labelled year two.

If they cut the enclosure and keep the model line, refuse the model line. A model without a parent is a public API with extra steps. Say that in the note. It is easier to say before the retreat than after the incident.

Do not pad the page with a 38 percent procurement growth claim. Send them to the method article if someone upstairs asks. A CIO who inflates a headline will not be trusted on the enclosure kW either.

This article is informational field guidance for Indian public institutions, not legal, budget or procurement advice. Confirm against your state's finance rules, GFR where adopted, GeM terms, MCC instructions, DPDP, and counsel before you file it.

How to sequence this in a state, not a slide

“State CIO Priorities for the Next Budget Cycle” is a department problem. A P1 CIO/CTO should name the legacy system, the officer who owns the file, and the citizen charter clock before buying “state CIO priorities India”.

There is no official ranked list of what every state CIO will fund next cycle. There is a method: protect the human gate, buy readiness, fund vernacular and change requests, and refuse programmes that invent APIs or 38 percent facts. Do not invent league tables of states. Read tenders and policies. Election Model Code of Conduct can freeze a rollout. NIC is a partner, not a villain. SDC readiness is GPU, power, ops and egress — not a logo.

• Audit the legacy store first.
• Keep mutation and money as officer actions.
• Map SLAs to the citizen charter.
• Budget change requests after go-live.

Close this loop before the next CAB

Put “State CIO Priorities for the Next Budget Cycle” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P1 CIO/CTO, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “state CIO priorities India” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.

What the next file must contain

“State CIO Priorities for the Next Budget Cycle” earns a line in the noting only if a P1 CIO/CTO can attach proof of “state CIO priorities India.” A heading is not proof. A vendor slide is not proof. A workshop photograph is not proof.

Write three dated sentences: what was decided, who owns it after the next posting order, and when it will be re-checked. If you cannot write the three sentences, you are not ready to buy, to sell, or to go live.

Leave unsourced percentages out of the note. DPDP is not a blanket localisation statute. The November 2025 AI governance text is guidance, not an Act. CERT-In’s 28 April 2022 directions still set specified incident and log clocks. A PAC, when lawful, lives in GFR Rule 166.

• Name the designation that owns “state CIO priorities India.”
• Attach one artefact a stranger can open next year.
• Record the instrument you are actually using.
• Revisit when the model, the SI, the notice or the posting changes.