Departmental Champions: Finding and Keeping Them

Every GovTech war story ends the same way. The additional director who understood the scheme went on deputation. The WhatsApp group went quiet. The new incumbent asked why a vendor was sitting in the weekly meeting. The exception queue had not been opened in six weeks. The dashboard was still green. The champion had been a person. The State needed a post.

Founders look for charm. Charm is how you get the first meeting. Keeping a champion is a records problem. You need a standing order, a deputy, a packet a stranger can run, and a reason for the post to care that is not your friendship.

This guide is dated 17 August 2026. It is not HR or legal advice. Transfer is a feature of Indian administration. Design for it.

Find the post, not the fan

Map the workflow to the post that already owns the pain. Scheme eligibility belongs to the scheme directorate, not to IT. Single-window completeness belongs to the facilitation cell. Permit clerks belong to transport. NIC hosts; they are rarely the scheme champion. If you cannot name the post, you are still in a CIO tour.

Test the candidate with fifty files, not with lunch. The person who will re-time a permit renewal and argue with your extractor is the champion. The person who wants a keynote is a sponsor. Keep both. Do not confuse them.

• A written standing order they will sign.
• A deputy named before go-live.
• Time on the official roster, not hero hours.
• Access to the exception queue as a counted duty.
• No personal stipend from the vendor.

Signals that you have a champion, and signals that you have a tourist.

Signal	Champion	Tourist
First request	Show me the fifty files	Show me the dashboard for the visit
On transfer	Hands the packet to the deputy	Takes the WhatsApp group and the context
On exclusion	Opens the queue	Asks to hide the number
On NIC	Sends the one-page ask	Minutes that NIC is the blocker
On your invoice	Wants the CR envelope visible	Wants a free phase two

Keep them by making them replaceable

This sounds unkind. It is the only kindness that survives deputation. Write the packet: standing order, purpose tags, exception-queue duty, model hash, who to call at NIC, how to reprint a receipt. Review it with the deputy in the champion's presence. If the champion refuses a deputy, you have a risk, not a partner.

Keep them by removing humiliation. Do not surprise them in a steering committee. Do not let your CSM out-talk them in front of a secretary. Do not dump a public-API incident on their desk on a Friday. Loyalty in government is often the memory of who did not embarrass whom.

Two handovers after transfer season

Objections you will hear — and what to do with them

We need a political champion more than a director

You need both, and they are not substitutes. Political cover opens a door. A director opens the queue. MCC can freeze the political champion overnight. The director remains.

If we document everything they will not need us

Good. You want a renewable contract on a living service, not a hostage situation. Hostages do not survive vigilance.

The only willing person is in IT

Then you have a host, not a champion. Keep looking in the business directorate. An IT-only champion is how the service becomes a portal nobody in the scheme owns.

We will offer an award

Awards are fine if the department gives them. A vendor trophy can look like a gift. Stay boring.

A four-week playbook for one directorate

1. Week 1: name the post that owns the pain. Meet that post without a deck.
2. Week 2: run fifty files together. If they will not, you do not have a champion.
3. Week 3: draft the standing order and name the deputy. Get both initials.
4. Week 4: do a transfer tabletop. The champion leaves the room. The deputy runs the queue. Whatever breaks becomes the packet.

File note you can paste

Subject: Departmental ownership of the agentic workflow — champion post and deputy.

The owner of this workflow is the post of [scheme / cell / additional commissioner], not the vendor and not a personal mobile number. A deputy will be named before go-live. A packet sufficient for a stranger to run the exception queue will be filed on the official store. Vendor stipends to individuals are not authorised. Transfer will trigger a handover on the register, not a pause of the service.

This note is an internal aid. It is not HR or legal advice.

Prcept AI will not be your only motivated adult. If we are, we have failed at replacement. Ask us to leave the room while the deputy runs the tabletop. That is how you keep a champion — by not needing the same one forever.

Sponsors are not deputies

A minister or a secretary who likes the demo can open a door and can also vanish under MCC or a reshuffle. Do not write them into the packet as the person who opens the queue. Thank them. Send them a one-page outcome after the sample of fifty. Do not put their personal office on the incident roster.

When a sponsor asks for a Friday go-live that the champion has not sampled, protect the champion in the room. Founders who throw the director under the visit will not keep the next director. This is not sentiment. It is how files survive.

If you cannot name a deputy after four weeks, you do not have a department. You have a tourist. Pause the bid. Selling into a tourist is how you fund a personality and invoice a vacancy.

This article is informational field guidance for Indian public institutions and vendors, not legal, HR, vigilance or procurement advice. Confirm against conduct rules, CVC expectations, and your department's own transfer orders before you file it.

How to sequence this in a state, not a slide

“Departmental Champions: Finding and Keeping Them” is a department problem. A P5 GovTech Founder should name the legacy system, the officer who owns the file, and the citizen charter clock before buying “government champion stakeholder”.

The champion is not the person who liked your demo. The champion is the post that will still open the exception queue after transfer season. Find that post. Give them a packet. Fund a deputy. Do not marry a phone number. 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 “Departmental Champions: Finding and Keeping Them” 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 P5 GovTech Founder, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “government champion stakeholder” 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 “Departmental Champions: Finding and Keeping Them” is only a heading, it will not survive a file inspection. A P5 GovTech Founder should be able to attach one artefact that proves “government champion stakeholder”: 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 “government champion stakeholder” 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

“Departmental Champions: Finding and Keeping Them” earns a line in the noting only if a P5 GovTech Founder can attach proof of “government champion stakeholder.” 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 “government champion stakeholder.”
• 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.