State IT Empanelment: Mapping the Big Six

A founder asked for 'the list' of state IT empanelments — current vendors, expiry dates, category codes — as if someone in Delhi kept a census. Nobody does. Maharashtra’s IT department, Karnataka’s e-procurement, ELCOT, UPDESCO-linked tenders, TSTS and GIL each publish on their own clocks. Last quarter’s PDF is a rumour this quarter.

What you can have is a method. For any large state you pick a triangle: the IT/e-governance department that writes policy, the state corporation or society that often runs empanelments (a MahaIT, a Keonics, an ELCOT, a TSTS, a GIL), and the e-procurement portal where the RFE actually lives. You search all three, you download what you find, you date the download, and you refuse to memorise the vendor list as law.

This data study is that method applied to six large states founders keep naming. It is not a complete official census of who is empanelled today. Lists change. URLs redirect. Corporations merge. If you need to bid this month, run the method this month.

The triangle method you can reuse on any state

Vertex one: the state IT, electronics or e-governance department site. Look for circulars, empanelment policies, rate-contract OMs and links to corporations. Department sites explain intent. They sometimes forget to take down a 2019 PDF.

Vertex two: the commercial or delivery entity — a state informatics corporation, e-governance agency, or electronics corporation. These bodies often issue the RFE, hold the panel, and raise the work order. Their vendor pages, when they exist, are closer to operations than a minister’s speech.

Vertex three: the e-procurement portal (often an NIC NIC-eProc instance, or a state engine such as nProcure). Search for 'empanelment', 'rate contract', 'empanelment of agencies', 'software', 'AI', 'cloud'. Download the RFE, not a news recap.

Then run a fourth, unromantic pass: GeM and CPPP, because some state buyers still purchase centrally, and some state corporations publish on eprocure.gov.in as well. Empanelment is a habit, not a monopoly.

Six starting triangles — doors, not directories

The table below is a door list. It is not a statement that an AI empanelment is open behind every door. It is not a statement of current vendor names. Use it to start the search, then believe only the PDF you download.

State corporations change names and websites. If a URL 404s, start again at the department vertex rather than at a five-year-old blog.

District collectors and universities in the same state may ignore the state panel and buy on GeM. Mapping the panel is necessary. It is not sufficient to know how that state actually spends.

Doors as of a 2026 working map. Hostnames move. Re-resolve from the department home page before you bid.

State	Department / policy door	Corporation / agency door to check	E-procurement door
Maharashtra	it.maharashtra.gov.in	Search from the department for MahaIT / IT corporation notices; do not trust a blog’s org chart	mahatenders.gov.in
Karnataka	itbtst.karnataka.gov.in	Centre for e-Governance / Keonics pages linked from the department	eproc.karnataka.gov.in
Tamil Nadu	tnega.tn.gov.in and the IT department site linked there	ELCOT (elcot.in) — frequent issuer of IT empanelments and rate contracts	tntenders.gov.in
Uttar Pradesh	upite.gov.in	Look for UPDESCO / UPLC / corporation RFEs linked from the department — names shift	etender.up.nic.in
Telangana	it.telangana.gov.in	TSTS (tsts.telangana.gov.in) — often the commercial/delivery counterpart	State tender portal linked from ITE&C / TSTS (verify current hostname)
Gujarat	dst.gujarat.gov.in and GIL pages	GIL (gil.gujarat.gov.in)	nprocure.com and the current Gujarat e-procurement hostname GIL names

What to extract from each PDF — a comparable sheet

Build one spreadsheet for all six, with a row per live instrument, not per state. Columns: state, issuer, tender ID, category (software / cloud / manpower / security audit / AI if named), window dates, panel tenure, whether continuous empanelment, consortium rule, startup/MSE language, security certifications named, and whether later work is rate-contract or mini-bid.

Add a column called 'last verified' with an ISO date. The sheet becomes false the week you stop dating rows.

Add a column called 'fit for an on-prem agent'. Many state panels are manpower or generic software development. You may need to be on a boring software panel to receive an interesting AI work order. That is still a fit.

• Search terms in English and the state language if the portal supports it.
• Include closed RFEs from the last 24 months — they predict the next category shape.
• Save PDFs in a folder named state-year-id. Portals vanish documents.
• Note the paying entity. A TSTS work order and a department GeM order are different receivables.

Patterns you will see — without pretending a census

Large states often split cloud, network, software development and security audit into different panels. AI may sit under software services until someone writes a dedicated RFE. Do not wait for the word 'agentic' in a title.

State corporations like a local office clause, a prior-state-work clause, or a turnover clause sized for SIs. Those clauses are where DPIIT relaxations, if the notice adopts them, matter. If the notice does not adopt them, the corporation is not obliged to invent them.

Some states refresh panels on a calendar; some run continuous empanelment; some quietly extend a 2018 list. Extensions are why you never treat a blog’s 'current vendors' table as complete.

What not to do with the sheet

Do not publish it as 'the official list of Indian state AI vendors'. It is your research artefact.

Do not skip GeM because a state panel exists. Many departments will still be told to use GeM under their financial rules.

Do not fly to six capitals in a week to 'relationship-build' before you can name the live instrument. The PDF is the relationship.

Why teams want a census that does not exist

Investors and tired founders prefer a single table. States prefer sovereignty over their own panels.

Someone must maintain the official all-India list.

MeitY and NICSI maintain central instruments. They do not replace state corporations. Treat any unofficial aggregator as a hint, then verify on the state portal.

If we are on NICSI we can ignore state panels.

A state buyer may still need you on their panel, or may buy on GeM, or may use NICSI. Map the buyer you want, not the logo you already have.

The method is too slow. We will hire a consultant who 'knows the lists'.

Hire them to run this method weekly and hand you dated PDFs. If they only hand you names, you have bought a rumour.

Smaller states do not matter.

This article started with six large ones because founders name them. The same triangle works for a smaller state that will actually sign a first work order. Do not confuse market size with signature speed.

A fortnight to map six states without lying to yourself

Two states a day is how you miss corrigenda. Do one state every two days.

1. Days 1–2: Maharashtra triangle. Save RFEs. Fill the sheet. Stop.
2. Days 3–4: Karnataka. Same sheet, new rows.
3. Days 5–6: Tamil Nadu, including ELCOT and TNeGA searches.
4. Days 7–8: Uttar Pradesh, including older corporation names in the search box.
5. Days 9–10: Telangana ITE&C and TSTS.
6. Days 11–12: Gujarat GIL and nProcure.
7. Days 13–14: rank live instruments by fit and date. Pick two to actually pursue. Schedule a quarterly re-run on the calendar, or the sheet dies.

What goes in the file — a dated research pack

For each live instrument: PDF, corrigenda, your fit note, last-verified date, and the URL path you used. For each state: a one-paragraph conclusion — 'no live software panel found on this date' is an acceptable, honourable conclusion.

When a salesperson wants to say 'we cover the big six', they may say it only if the pack still has unexpired letters or live applications. Otherwise they may say 'we know the doors'. That second sentence is already rare enough to be valuable.

State portals, corporation names and empanelment lists change. This is a research method, not an official census and not legal advice. Re-resolve URLs from department home pages. Do not treat any table in this article as a complete or current vendor list.

How to run the route without confusing the letterhead

“State IT Empanelment: Mapping the Big Six” is a route problem. A P5 GovTech Founder should know which legal person they are talking to — NIC, NICSI, a state IT corporation, iDEX, or a GeM buyer — and which paper that person can actually issue. Searching “state IT empanelment India” is not the same as being on a panel that can receive a work order.

There is no single national census of state IT panels. There is a repeatable method: official IT department, state corporation, and e-procurement portal — re-run every quarter, because lists change. Empanelment letters are not purchase orders. DPIIT recognition is not a technical score. Reserved startup seats, if a notice writes them, are local to that notice. IndiaAI compute empanelment is not NICSI application-software empanelment.

Keep a warm evidence pack: CIN, GST, DPIIT, Udyam, financials, work-completion letters, architecture one-pager, DPA draft. Renewals are lost by people who treat the panel as a trophy.

• Screenshot the live RFE paragraph you are relying on, dated.
• Match the bidding entity name across every certificate.
• Do not mix iDEX, TDF, NICSI and GeM clocks on one tracker cell.
• Record the validity end date 90 days before it dies.

Close this loop before the next CAB

Put “State IT Empanelment: Mapping the Big Six” 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. “state IT empanelment India” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.