Working With NIC Teams: A Practical Guide

The most expensive sentence in a state AI file is 'NIC will not cooperate'. It is usually false in the way that matters. Someone sent a twenty-page architecture with twelve write APIs, a public-cloud failover and a request for production data by Friday. NIC did not answer with a sonnet. They asked who would be responsible when the write was wrong. That is cooperation. It just does not feel like a yes.

This guide is practical and it is respectful on purpose. Prcept AI sells on-prem agents. We still need NIC and SDC people to keep the lights on, the identity tied, and the change calendar honest. If your strategy requires them to look foolish in a steering committee, your strategy will lose the keys.

It is dated 17 August 2026. It is not an NIC circular and not legal advice. NIC is a MeitY organisation with state centres and national projects. Local culture varies. The method below still travels.

What NIC is already doing while you discover AI

They host and build systems that already have users: service portals, often Vahan-adjacent access, land stacks in some states, scholarship and treasury adjacent work, GIGW-facing websites, email, and the unglamorous identity that makes eOffice feel boring. They work under change windows, audit, and a political cost when a site dies. An agent project that ignores that metabolism will be scheduled after the things that already break when ignored.

They are also not a single mind. A national project team, a state centre, and a district informatics officer are different calendars. Address the person who can actually give you a VLAN or a letter. Do not send the DIO a request for a national write API and then record that 'NIC refused'.

The one-page ask

Write one page. Name the workflow. Name the data class. Name the purpose tag. Say read or write. If write, name the competent officer who will still act. Ask for a test tenancy, not production. Attach the deny-outbound design. Attach the no-training clause. Offer to walk the SDC readiness rows with them. Sign it as the department, not as the vendor.

• One workflow per letter. Twelve boxes is how you go to the bottom of the pile.
• A purpose tag a later auditor can read.
• A test tenancy. Production is not a sandbox because you are late.
• A named departmental owner who will take the incident call.
• A sentence that admits which APIs do not exist.

Behaviours that get a VLAN, and behaviours that get a silence.

Behaviour	What NIC hears	What to do instead
Minutes: NIC not AI-ready	A smear they will remember	Score GPU, power, ops, egress with them in the room
Vendor-led workshop as the first contact	A sale	Department-led one-page ask
Need production data to start	An incident request	Synthetic or redacted pack; test tenancy
Unbounded write API	A request to share statutory authority	Read plus human write in the system of record
Friday-night patch window	A threat to someone else's batch	The existing change calendar

Two letters to the same centre

Objections you will hear — and what to do with them

We do not have time for NIC process

You have time for the incident that follows a bypass. Process is how shared infrastructure stays shared. If your clock cannot survive a fortnight, your scope is wrong.

NIC will steal the project

Then write who owns the product, who owns the host, and who owns the model runtime. Shared hosting is not theft. Unclear ownership is how both sides look bad.

They only know old stacks

They know the stacks that have users. Learn those stacks. Bring a runtime that does not require a research lab. Contempt for 'old' is how you propose Kubernetes on a floor that already runs the treasury.

A national NIC cloud will replace the state centre

Maybe, for some workloads. You still need a person who will take the ticket next month. Name that person before you name the cloud.

A four-week playbook for the first decent working relationship

1. Week 1: department-only meeting with the NIC state centre. No vendor. Listen to what they already host and what broke last quarter.
2. Week 2: send the one-page ask. Copy only people who must act.
3. Week 3: walk the SDC readiness table together. Write numbers they will initial.
4. Week 4: if a test tenancy exists, bring the vendor. If it does not, write the blocker as a dated ask, not as a character judgement.

File note you can paste

Subject: Working arrangement with NIC for the agentic programme.

This department records that NIC and SDC teams already operate critical public systems. Requests will be one workflow, one purpose tag, read or write stated, test tenancy preferred, deny-outbound described, departmental owner named. Vendors will not be the first voice in the room. Minutes will not describe NIC as 'not AI-ready' without the completed readiness table. Going around NIC with public APIs or scrapes is forbidden.

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

Prcept AI will sit second. If we cannot explain the runtime to the person who already runs the floor, we should thin the runtime, not raise our voice. Respect is a delivery strategy.

District informatics officers are not unpaid SIs

A DIO already has a ticket queue you have never seen. Dumping an agent install on them on a collector's order is how the install happens on a shared login at midnight. If you need a district host, send the runbook, a change window, and a named departmental owner who will take the incident. Offer to sit through the first restart. Do not offer a T-shirt.

When something breaks, call the DIO with the log line, not with a theory that NIC stacks are old. Bring the two-page runbook you promised. If the runbook does not work in their hands, the runtime is wrong. Fix the runtime. Do not write a minute about culture.

Copy the DIO on the monthly register row for any workflow that touches their floor. Surprise is the opposite of respect. So is leaving them out of the success photograph and in the incident call.

This article is informational field guidance for Indian public institutions, not an NIC instruction or legal advice. Confirm against local NIC / SDC procedure, CERT-In directions, GIGW 3.0, and your department's own hosting rules before you file it.

How to sequence this in a state, not a slide

“Working With NIC Teams: A Practical Guide” is a department problem. A P4 System Integrator should name the legacy system, the officer who owns the file, and the citizen charter clock before buying “working with NIC government”.

NIC is not a villain in your architecture slide. It is the group that already hosts the applications citizens touch. Ask for one purpose, one test tenancy and one named owner. Bring respect. Leave the smear in the taxi. 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 “Working With NIC Teams: A Practical Guide” 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 P4 System Integrator, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “working with NIC government” 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

“Working With NIC Teams: A Practical Guide” earns a line in the noting only if a P4 System Integrator can attach proof of “working with NIC government.” 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 “working with NIC government.”
• 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.