Contract Management for Large PSU Vendors

A three-thousand-crore package does not fail only at award. It fails when a milestone slipped in silence, when a notice went to the wrong address, when LD was calculated on a napkin, or when two plants treated the same default differently. That is contract management. It is mostly calendar, clause, and courage.

An agent is good at calendar and clause. It is bad at courage. Do not ask it to terminate. Do not ask it to declare force majeure. Do not ask it to settle.

This guide is for commercial and project heads who already have a contract cell. It is not legal advice. Your GCC, SCC, and any arbitration seat will beat this page.

In scope: remembering

• Milestone registers extracted from the signed contract, with owners.
• Alerts when a date approaches, to the owner, not to the vendor.
• Retrieval of the clause that matches a notice type — delay, defect, suspension — with the clause number showing.
• First drafts of internal noting and of notices, from templates counsel has blessed.
• A comparison of how the same clause was applied on an earlier package, if those files are in the corpus on purpose.

Out of scope: acting

• Sending the notice.
• Calculating LD as a payable without a human recomputation in the official sheet.
• Blacklisting, banning, or advisory public language.
• Settlement offers.
• Interpreting a vague force-majeure paragraph as a yes.
• Reading the vendor's private mail that happened to be forwarded into the index.

Fairness across vendors is a vigilance fact

If the agent reminds you to notice vendor A and nobody loads vendor B's contract, you have built an uneven whip. Load the register for the class, or do not claim the system is the cell's memory.

Do not train a risk score on vendor nationality, size, or past complaints unless counsel and CVO have written that such a score is allowed — which, for a first year, it should not be.

Privilege and traces

Legal notings and arbitration strategy do not belong in the same collection as a milestone bot. Split. Mark privileged. Keep them off vendor laptops.

Notices you actually sent are often disclosable later. Drafts that accuse may not be. Retention is a counsel question. Default to less chat stored, more official PDFs stored.

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 send, we will still forget

Then fix the roster. An unattended bot that sends legal notices is worse than forgetting. Forgetting is a management failure you can see.

Our GCC is standard, the model knows it

Your SCC is not standard. Retrieval must prefer the signed book. A general model of Indian GCC will invent a clause.

Vendors already use AI against us

Let them. Your duty is evenness and a defendable notice, not a faster insult.

We will start with one hostile contractor

Starting with one looks like targeting. Start with a class of contracts or do not start.

Four weeks on one live package class

1. Week 1: pick a class, for example all active civil packages above a threshold you already use. Extract milestones into a register humans accept.
2. Week 2: internal alerts only. Counsel blesses two notice templates. No send tool.
3. Week 3: draft notices on closed historical events and compare to what was actually sent. Measure invented clauses.
4. Week 4: standing order: no send, no auto-LD, no risk score, privileged files split. Then open production alerts.

How this shows up in the file

Subject: Agent assistance in large-vendor contract management.

The agent may maintain a milestone register, alert internal owners, retrieve signed clauses, and draft from counsel-blessed templates. It shall not send notices, levy LD, terminate, settle, or score vendors.

Privileged legal files shall not share an index with the milestone bot. This note is not legal advice.

Even whip or no whip

Vigilance will ask why vendor A got a timely notice and vendor B did not. If the answer is we only loaded A's PDF, you have a targeting problem. Load the class. If you cannot load the class, do not claim the agent is the cell.

Prcept AI will not send notices. We will not auto-levy. We will not score nationality. We will remember dates you already signed. Courage stays with the officer.

Addresses and deemed service

A notice sent to last year's project mailbox is a gift to the contractor. The register should store the address block from the signed contract and any formal change. The agent can retrieve that block. It cannot decide that a WhatsApp read-receipt is service. Deemed service is a legal question. Put it back with counsel.

Force majeure letters arrive in floods and in political seasons. The agent may file them against the clause number and the date. It may not reply 'accepted'. A silent accept in a draft that an officer forwards at night is still an accept in the contractor's folder.

If two plants share a contractor and only one plant loaded the package, you will notice one and sleep on the other. That is the targeting problem again. Corporate commercial should own the class list. Plants execute. The bot is memory for the class, not a plant's private whip.

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'. “Contract Management for Large PSU Vendors” has to survive a technical committee, a cost centre, and a union conversation if jobs appear threatened.

Large vendor contracts die in forgotten milestones and uneven notices. An agent can remember. It cannot levy, terminate or settle. 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 “Contract Management for Large PSU Vendors” 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. “contract management AI PSU” 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 “Contract Management for Large PSU Vendors” is only a heading, it will not survive a file inspection. A P1 CIO/CTO should be able to attach one artefact that proves “contract management AI PSU”: 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 “contract management AI PSU” 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.

One more artefact before you close the file

Add a one-page owner map: who runs this after the vendor leaves, who can stop it, and where the logs live. If those three names are missing, the project is still a demo.

Date the page. File it next to the contract. That is the difference between a blog you read and a control you can audit.

If you cannot export the last month of traces into the department SIEM without the vendor, you do not own the workflow. Own the traces before you expand the use case.

What the next file must contain

“Contract Management for Large PSU Vendors” earns a line in the noting only if a P1 CIO/CTO can attach proof of “contract management AI PSU.” 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 “contract management AI PSU.”
• 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.