Sequencing a Department's First Agent Rollout

The secretary wanted AI in the department before the budget session. The wishlist mixed a circulars chatbot, automatic sanction drafting, a grievance router, and a land-status answer for the public portal. That is four products, three risk classes, and at least two statutes. Sequencing them as one rollout is how shelfware and hearings are born in the same quarter.

A first agent is a clerk with a closed drawer. It may read what you pin. It may draft what an officer will sign. It may open a ticket. It may not move money, mutate land, or issue a speaking order. The order in which you turn those abilities on is the control. The model is interchangeable compared with that order.

This playbook is for principal secretaries, CIOs and heads of e-governance societies starting the first departmental agent. It is written on 17 August 2026. It is not legal advice. It pairs with the 90-day pilot article later in this batch.

The only order that is boring enough to work

Step A: signed circulars and public scheme FAQs, officer-facing first. No citizen PII. Quality sample against the pack. This proves pin, export, and the refusal to invent a circular number. Step B: officer-facing status reads from a lagged wrap of the legacy system, as-of stamped, default-deny on anything a citizen would treat as a promise. This proves the wrap.

Step C: ticket opening into the existing grievance or file system, with category and draft, no closure, no routing that skips a statutory desk. This proves the agent can write somewhere that already has an owner. Step D, if ever: citizen-facing answers that only repeat A, with a notice that status lives on the official portal. Identity at the portal standard, not a chat OTP you invented. Not in the first year unless a separate project exists: sanctions, payments, mutations, FIRs, licences, exam marks, anything that is a speaking order.

Sequence versus the excuse that usually jumps it.

Step	Allowed	Usual bad jump
A — circulars	Retrieve signed pack; draft notes	Index the entire file room to be useful
B — status wrap	Three read views, as-of stamp	Free SQL; live payment status to the public
C — tickets	Open a ticket with a draft	Auto-close; auto-escalate to the minister's office
D — citizen face	Repeat A; point at the portal for status	WhatsApp group with unofficial promises
Later project	Officer-gated drafts of defined orders	The agent issues the order

Pick one wing

A department is not a person. Scheme, establishment, field offices, a commissionerate, a society. The first agent belongs to one wing with one records officer. Horizontal department-wide on day one is the campus-wide mistake in khaki. Pick the wing whose circulars are actually signed and whose tickets already have a system. Do not pick the wing whose register is in a fight with NIC over the true table. Field offices get a read-only copy of A before they get B. Otherwise every tehsil will invent a prompt.

Governance that fits a first rollout

An AI register with one row: workflow, model hash, pack owner, competent authority, sunset. MeitY's 2025 guidelines talk about accountability as a principle. Your register is how that principle becomes a file. A weekly quality sample of twenty items scored by someone who did not build the pack. A freeze around budget day, assembly questions, and any public-facing deadline. A kill-switch the CIO can pull without the vendor.

What the budget speech can say

It can say the department is retrieving its own circulars with a logged clerk and measuring error rates. It cannot say the department has deployed AI across citizen services after step A. Over-claiming in the House is how you are forced to jump to D before B works. Write the speech from the sequence, not the sequence from the speech.

Two rooms you can walk into

Sequence was the difference between a clerk and a scandal.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note.

Other departments launched citizen bots first.

Ask what those bots may retrieve. Many are A with a public skin, which is step D done honestly. If they answer live status from OLTP, they are a risk you need not copy.

The minister's office wants routing.

Routing is politics plus a statutory desk. An agent that skips the desk is a vigilance problem. Offer C as ticket-open, not as a private escalator.

We do not have signed circulars in one pack.

Then step A is the project, and it is already worth doing even if you never buy a model. Do not skip to B to avoid stationery work.

Sequence will make us look slow.

Hearings make you look slower. Publish the sequence so slowness reads as control.

A ninety-day first sequence (A only)

If you try to finish A–D in ninety days, you will finish none of them.

1. Days 1–15: pick the wing, name the pack owner, finish the live-versus-archival circular list. Legacy audit go/no-go if B is even on the horizon.
2. Days 16–45: pin the pack, stand the officer tool, DPA, training ban, export, weekly sample. No citizen face.
3. Days 46–75: freeze a week; fix errors; write the AI register row; practise the kill-switch.
4. Days 76–90: decision — remain on A, or open a design for B as a separate work order. Speech text matches the decision.

How this shows up in the file

Subject: Sequence for the department's first agent. Step A (circulars, officer-facing) is the only authorised workflow this quarter. Steps B–D require separate go notes. Payments, sanctions, mutations and speaking orders are out of scope. Pack owner named. Sunset dated. Public language will not claim citizen-wide AI on the strength of step A.

What we will and will not claim

Prcept AI will deliver step A on your rack and refuse to jump to money or land. If a competitor offers the whole wishlist in one SOW, ask them which drawer the clerk is forbidden to open. If they say none, they are not sequencing. They are stacking risk.

This article is informational field guidance for Indian universities and public institutions, not legal, procurement, audit or engineering advice. Confirm against the live Gazette, GFR, state financial rules, GeM terms, UGC text, GIGW, DPDP commencement, departmental manual and your counsel before you file it.

How to sequence this in a state, not a slide

“Sequencing a Department's First Agent Rollout” 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 “AI rollout government department”.

A department's first agent should retrieve signed circulars, then read a lagged status view, then open tickets. Payments, sanctions and mutations are not a first sequence. 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 “Sequencing a Department's First Agent Rollout” 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. “AI rollout government department” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.

What must be true before you file this

If “Sequencing a Department's First Agent Rollout” is only a heading, it will not survive a file inspection. A P1 CIO/CTO should be able to attach one artefact that proves “AI rollout government department”: a log export, a clause, a scored row, a dated notice, or a refusal rule.

Write three dated sentences: what was decided, who owns it, and when it will be re-checked. Unsigned sentences are souvenirs. Dated sentences are controls.

• Name the owner of “AI rollout government department” inside the institution.
• Attach one artefact a stranger can open next year.
• Revisit when the model, the notice, or the SI changes.
• Do not treat a vendor slide as evidence.

What the next file must contain

“Sequencing a Department's First Agent Rollout” earns a line in the noting only if a P1 CIO/CTO can attach proof of “AI rollout government department.” 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 “AI rollout government department.”
• 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.