Agentic AI for PSU Procurement Back-Offices

A materials chief in a Navratna wanted AI for procurement. What he needed, by Friday, was a clerk who could tell him which indent was missing a last-purchase-price sheet, which GeM bid would time out while the technical member was on tour, and a first draft of a note that did not invent a circular. He did not need a system that awarded.

PSU procurement back-offices drown in PDFs, not in strategy. Agents that retrieve, checklist and draft can give officers back the afternoon. Agents that score, disqualify or notify bidders are how you enter a vigilance file.

This guide draws the line for the back office. Tender-cell scope has its own piece. L1 has its own piece. Here we stay with the unglamorous middle: the room behind the GeM login.

Work that is safe enough to try

• Completeness checks against the department's own indent checklist — missing annexes, unsigned notes, expired OEM letters.
• File-movement summaries: where the physical or e-file sits, how long, who last touched it.
• First drafts of routine notes that cite only the circulars in the approved corpus.
• Comparison tables that copy bidder-declared values into a sheet the officer still signs.
• Calendar prompts for bid expiry, pre-bid meetings, and AMC renewals.
• Retrieval of the last accepted specification for a repeat item, clearly marked as last time, not as this time.

Work that stays human

• Eligibility, disqualification, and responsiveness.
• Opening of bids and recording of prices.
• Award recommendations and purchase orders.
• Rewriting technical specifications after seeing who is likely to bid.
• Negotiation, if your rules allow it at all.
• Any message that leaves the organisation toward a bidder.

Data classes in the back office are not just vendor data

Cancelled cheques, GST, PAN, bank details, personal mobiles of sellers, and internal notings about a bidder's past performance are personal or commercially sensitive. They do not belong in a hosted prompt. They do not belong in an eval notebook on a laptop.

DPDP still cares about identifiable individuals even when the file is titled procurement. CVC cares about fairness even when the model only drafted. Design the corpus as if both will read a sample.

Do not index live bids on a shared RAG store that also serves another plant. Bid data is a purpose. A shared index is how purpose dies.

GeM is a system of record; the agent is not

Whatever GeM, your ERP, or your e-procurement portal already records remains the record. The agent may read an extract you are allowed to take. It may not become a second place where prices live. It may not send a bidder a clarification that is actually a negotiation.

If a portal other than GeM is in scope for a later workflow, treat it as its own paper. This batch does not pretend to specify every portal.

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 it cannot award, the ROI is small

The ROI is fewer travelling files and fewer invented citations. Award is not where you should be seeking ROI from a sampler.

We will keep a human in the loop by email

Email is not the system of record. Put accept on the note in the official file.

Bidders already use AI, we must too

Use it on your homework, not on their rights. Their use does not licence your unfairness.

L1 is objective, the agent can compute it

Eligibility is not a sum. Even a sum can be wrong if the extract is wrong. Read the L1 piece. Do not let a model declare L1 in a mail.

Four weeks in one materials cell

1. Week 1: pick one plant or one category. Photograph the actual indent checklist. That is the corpus seed, plus the circulars you will allow the model to cite.
2. Week 2: implement completeness and file-age only. No bidder-facing text. Run it on closed files.
3. Week 3: add first-draft notes on those closed files and compare to what the officer actually signed. Measure invented citations.
4. Week 4: write the no-list into the standing order. Only then open a narrow production path for completeness flags.

How this shows up in the file

Subject: Agent assistance in the procurement back-office — permitted duties.

Agents may check completeness against the official checklist, summarise file movement, and draft internal notes that cite the approved corpus. They shall not open bids, declare eligibility, recommend award, rewrite specifications, or message bidders.

Bid data shall not sit in a shared index with unrelated purposes. This note is an internal aid. It is not legal advice.

Plants and the shared drive that knows too much

A corporate materials cell often sees every plant's last-purchase prices. A plant user often should not. If you index the corporate share for completeness, you will leak another plant's commercial history into a local draft. Split collections the way you already split cupboards.

Prcept AI will run this on your rack. We will not put live bids in a hosted tenant. We will not add a send-to-bidder tool. If you want award automation, we will refuse and point at the tender-cell limits piece.

Last-purchase price is not a gossip file

LPP sheets help an indent. They also teach a contractor what you paid last time if they leak. Keep LPP in a collection that only the materials cell can query. Do not let a plant stores clerk retrieve another plant's LPP because the tag prefix matched. That leak is a commercial fact and sometimes a vigilance fact.

Bank details on seller letters are personal and payment-adjacent. Completeness checks should flag 'cancelled cheque missing', not embed the cheque. If a clerk pastes the cheque into chat, the filter should refuse. The same rule we use for Aadhaar applies to account numbers. CERT-In logs do not need the digits.

When a file sits with finance for three weeks, the agent should say so without inventing a reason. 'Probably objected to GST' is gossip. 'Last movement: finance, date D' is a fact. Gossip in a draft is how a vendor hears a story you never decided.

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 P1 CIO/CTO in a PSU will meet CVC-shaped questions even when there is no special 'AI circular'. “Agentic AI for PSU Procurement Back-Offices” has to survive a technical committee, a cost centre, and a union conversation if jobs appear threatened.

The back office is where AI can be dull and useful: completeness, file movement, first drafts. The award stays human. The specification stays human. 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 “Agentic AI for PSU Procurement Back-Offices” 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. “PSU back office automation” 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 “Agentic AI for PSU Procurement Back-Offices” is only a heading, it will not survive a file inspection. A P1 CIO/CTO should be able to attach one artefact that proves “PSU back office automation”: 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 “PSU back office automation” 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.