All insights

PSU & CPSE

Navratna Autonomy and Faster AI Buying

· 10 minute read

Navratna is not a hall pass. It can shorten a money path. It does not delete DPDP, vigilance, or the need for a board-quality file.

A founder told a Navratna CIO that you people can buy anything now. The CIO asked for the current DPE threshold that would actually let him sign. The founder did not have it. He had a blog from 2019 and a slide that said autonomy. The meeting ended.

Maharatna, Navratna and Miniratna are real DPE classifications. They carry greater financial autonomy than a department that must go to a ministry for every large indent. The exact rupee powers change. We will not print a number here that will be wrong next quarter. Open dpe.gov.in and your company's own delegation. Write the dated extract into the file.

Faster money is not informal money. DPDP still applies. CVC still exists. Boards still want the three spines. OT still cannot take a chatbot. Aadhaar still cannot live in traces. Autonomy is a shorter corridor, not a hole in the wall.

What the status is, and what it is not

The labels are administrative and financial. They affect investment ceilings, joint-venture powers, and how far a board or CMD can go without a ministry indent — according to the live DPE instruments. They are not a data-protection exemption. They are not a vigilance exemption. They are not a licence to skip GeM where GeM is still required by the rules you actually follow.

Uncategorised CPSEs, subsidiaries, and joint ventures may sit under different practical constraints even when the parent is a Maharatna. Do not assume the parent's poster applies to the JV's purchase.

State PSUs are not Navratnas in the DPE sense just because someone used the word in a speech. Check the actual classification.

Where autonomy actually makes AI buying faster

  • A board that can sanction the metal and the AMC in one calendar instead of a ministry queue.
  • An ability to run a proper [QCBS or a two-envelope process without waiting for a template from elsewhere — if your own manual allows it.
  • A chance to staff a DPO and a CVO review in parallel because the company already has those seats.
  • Less excuse for a twelve-month we are waiting for Delhi that was actually fear of writing the data spine.

Where it does not make you faster, and should not

  • Skipping isolation design because the CMD is enthusiastic.
  • A free POC on live vendor invoices because we can regularise.
  • A branded specification that only the demo vendor can meet.
  • Putting the agent on OT because the plant head is a director.
  • Citing an unsourced 22% market fall to panic the board into a single-source.
  • Inventing a CVC AI circular — or claiming one — to bless a shortcut.

How founders should sell into autonomy without lying

Ask who the competent authority is for this rupee band this quarter. Ask to see the extract. If they will not show it, you do not know your sales cycle.

Offer a file that a Navratna board can vote in one sitting: commercial, vigilance, data. Do not offer a shortcut around those spines. The autonomy you are selling into is the right to decide, not the right to be vague.

Price the year-two AMC. Autonomous buyers still lapse budgets. A cheap year one is how you get a hostile CVO in year two.

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.

If we tell them to check DPE we look uninformed

Printing a stale rupee figure is uninformed. Sending them to the live instrument is the job. We will not compete on memorised ceilings.

Autonomy means GeM is optional

Only if the live procurement rules that bind that CPSE say so for that object. Many still use GeM. Do not take a founder's word. Take the manual.

Miniratna is too small to bother with spines

Miniratna is a label, not a data-class exemption. Small companies leak too.

The board wants speed more than paper

Give them short paper. Six pages with spines is speed. A film plus a regularisation later is how autonomy becomes a para.

Four weeks to use autonomy without burning it

  1. Week 1: download the current DPE classification list and the company's delegation extract. Date them. Do not quote this article for rupees.
  2. Week 2: map the proposed AI buy to the competent authority. If it is the board, start the three-spine memo now.
  3. Week 3: run DPO and CVO in parallel, not after the sanction. OT if a plant is in scope.
  4. Week 4: put the dated extracts in the annex and ask for the vote or the CMD signature the instrument actually allows. Refuse informal we will ratify.

How this shows up in the file

Subject: Use of Maharatna / Navratna / Miniratna autonomy for agent purchases.

Financial autonomy shall be read from the live DPE instruments and this company's delegation, dated and annexed. This note does not record a rupee threshold. Autonomy does not displace DPDP, ordinary vigilance expectations, or human gates. Agents shall not write to OT.

Vendor claims that a classification allows informal purchase shall be rejected. This note is an internal aid. It is not legal advice.

A shorter corridor, not a hole in the wall

The point of autonomy is that a ready file can be decided inside the company. The point is not that an unready file can skip DPO, CVO, OT and the board. Founders who sell the second story will lose the first buyer the first time a para lands.

Prcept AI will not print a rupee ceiling. We will ask for the dated extract. We will bring the three spines. We will refuse OT write-back and Aadhaar in traces even when the CMD is in a hurry. That is how you use a Navratna corridor without setting it on fire.

This article is informational field guidance for Indian public institutions, not legal, procurement, security-accreditation, engineering or board advice. Confirm against the live Gazette, GFR, GeM term, CVC instruction, CERT-In direction, UIDAI regulation, DPE guideline, DPDP text, departmental charter, plant safety manual and your counsel before you file it.

How this clears vigilance and the board

A P5 GovTech Founder in a PSU will meet CVC-shaped questions even when there is no special 'AI circular'. “Navratna Autonomy and Faster AI Buying” has to survive a technical committee, a cost centre, and a union conversation if jobs appear threatened.

Navratna is not a hall pass. It can shorten a money path. It does not delete DPDP, vigilance, or the need for a board-quality file. OT networks stay off-limits. Navratna autonomy speeds buying; it does not waive DPDP or data classification. IREPS is not GeM. RBI-shaped rules still localise payment data.

  • Classify data before the POC.
  • Keep agents off OT.
  • Write the board memo with residual risk.
  • Engage unions on retrieval vs replacement.

Close this loop before the next CAB

Put “Navratna Autonomy and Faster AI Buying” 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. “Navratna procurement autonomy” 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 “Navratna Autonomy and Faster AI Buying” is only a heading, it will not survive a file inspection. A P5 GovTech Founder should be able to attach one artefact that proves “Navratna procurement autonomy”: 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 “Navratna procurement autonomy” 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

“Navratna Autonomy and Faster AI Buying” earns a line in the noting only if a P5 GovTech Founder can attach proof of “Navratna procurement autonomy.” 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 “Navratna procurement autonomy.”
  • 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.

Questions this usually raises

What is the current Navratna investment ceiling in rupees?
Do not take it from this page. Open the Department of Public Enterprises' current guidelines and your board-approved delegation. Thresholds change. A blog that prints a number is already dating.
Does Maharatna status let us skip DPDP?
No. Classification is not a data statute. Purpose, security and processor control still have to be written.
Can a Navratna buy AI on a single source because it is strategic?
Only if the procurement rules you follow allow single source for those facts, and you record them. Autonomy is not itself the reason. Vigilance will ask for the reason.
Are state PSUs covered by DPE Navratna rules?
Not automatically. DPE classification is a central CPSE story. State enterprises follow their own government and board instruments. Check those.
Will autonomy make us buy faster than a ministry?
It can, if the file is ready. A ministry delay is often a missing spine, not only a missing ceiling. Write the spines and use whatever corridor you actually have.

Sources