PSU Procurement Timelines: A Realistic Chart

A founder told a plant that 'PSU procurement takes 90 days' because a blog said so. The plant's last service tender, with two corrigenda, a pre-bid, a technical clarification, a CVO query and a missed finance meeting, had taken nine months to a work order. The founder's runway assumed day 91. The plant's file assumed nothing of the kind.

This is a data study without a fake dataset. We will not invent a national mean for CPSE AI purchases. There is no honest published average that mixes GeM direct, GeM custom bid, IREPS services, advertised open tenders, PAC, and a draw on an existing NICSI or PSU panel. What we can give you is planning envelopes we use in files, the drivers that push a file from the left of the envelope to the right, and a chart you must replace with this company's last five comparable files.

GFR, GeM terms, Railway Board instructions, and each CPSE's purchase manual are different clocks. A 50-lakh GeM service buy and a 20-crore advertised integration are not cousins. Do not average them.

Not a promise. Not a statutory timeline. If your last five files say otherwise, your last five files win.

Envelopes, not means

Read every range as a planning box. The left edge assumes a clean specification, a live portal registration, no PAC fight, and a CVO who is not already drowning. The right edge assumes one corrigendum, one clarification loop, one missed committee, and a normal vigilance query. Catastrophes — a stay, a retender, a missing DSC at close — sit outside the box. Do not plan the catastrophe as zero. Plan slack.

Planning envelopes from indent freeze to work order, in calendar weeks, for a first AI-agent buy. Replace with your last five files.

Path	Clean box (weeks)	Normal-friction box (weeks)	What pushes right
GeM existing service listing, low value	3–8	6–14	Category argument, incident, buyer-side competence
GeM custom bid / L1 or QCBS	8–16	14–28	Spec fight, pre-bid, PAC rumour, price reasonableness
IREPS services (registered vendor)	10–20	16–32	Unregistered vendor, CRIS interface, zonal calendar
Advertised open tender on CPPP / own portal	16–28	24–44	Two corrigenda, committee quorum, holidays
Draw on a live panel / rate contract	4–12	8–20	No rate, plant-level re-presentation, SI queue
PAC / proprietary path	6–16	12–30	PAC justification fight, CVO, board date

Queues the chart always forgets

Vigilance query: 2–8 weeks when the file is clean, longer when the spec looks tailored. CAB / SDC VLAN: 2–6 weeks. SI hours: whatever their paid backlog is. DSC and portal registration: 1–6 weeks if you start late. Board or investment committee: the next date, not your date. Isolation hardware on GeM or import: read the GPU lead-time companion; it can dominate.

Add the queues that apply. Do not add all of them as if they were sequential if some can run in parallel. Do not pretend they are zero because a ministry speech was in a hurry.

How to build your own chart this month

Ask procurement for the last five service or software files nearest this value. Note path, indent-freeze date, NIT date, work-order date, number of corrigenda, whether vigilance queried, whether a PAC was used. That sample is small and better than a blog. Put it in the business case. The CFO will trust your own dead files more than our table.

Founders: ask the officer for that sample before you staff a team against your 90-day blog. If they will not share dates, assume the right edge of the relevant box.

What not to promise in a bid

Do not promise go-live 30 days from award if the award does not include a VLAN, a role, and a classified corpus. Promise go-live 30 days from those gates, and write the gates. Tender schedules that ignore PSU queues are how you eat LDs you priced as theatre.

Do not promise that GeM is always faster than IREPS. A messy GeM custom bid can outlast a clean IREPS service tender. Path plus friction, not brand of 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. A spoken answer without paper will be forgotten by the next officer.

Startup India means faster PSU cycles.

Some relaxations exist on eligibility and EMD in some paths. They do not delete CVO queries or board calendars. Read the instrument. Do not generalise a DPIIT tweet.

We measured GeM and it is 21 days.

For which category, which value, which buyer competence? Publish those conditions or treat 21 days as an anecdote.

The CMD wants it this quarter.

Then pick a path that can live in this quarter — usually a small GeM service or a draw on a priced panel — and shrink the purpose. Do not pick an advertised integration and a speech.

Putting long ranges in the bid makes us look slow.

Putting fantasy dates in the bid makes you look like LD bait. Officers who have lived through a file respect a range with drivers.

A four-week timeline honesty playbook

Do this before you print a Gantt for the board or the investor.

1. Week 1: identify the actual path (portal, PAC, panel). If unknown, you do not have a timeline.
2. Week 2: pull the last five comparable files. Build your own envelope. Compare to the table above; keep yours if they differ.
3. Week 3: add vigilance, CAB, SI and hardware queues that apply. Mark what can run in parallel.
4. Week 4: write the bid or the board Gantt from gates, not from award-plus-magic. Share the drivers in a footnote so a later officer can update them.

How this shows up in the file

Subject: Planning envelope for (path) — not a commitment.

Based on this company's last comparable files (annexure) and the path (GeM / IREPS / advertised / panel / PAC), the planning envelope from indent freeze to work order is (x–y) weeks, plus (queues). This is not an SLA. Corrigenda, stays and missing registrations sit outside the box. The live NIT and manual prevail.

This note is not procurement advice.

This article is informational field guidance for Indian public sector undertakings and their vendors, not legal, audit, labour, energy-regulatory, banking-regulatory or procurement advice. Confirm the live circular, DPE guideline, CVC instruction, sector regulator text, purchase manual and your counsel before you file it.

How this clears vigilance and the board

A P5 Startup/Vendor in a PSU will meet CVC-shaped questions even when there is no special 'AI circular'. “PSU Procurement Timelines: A Realistic Chart” has to survive a technical committee, a cost centre, and a union conversation if jobs appear threatened.

We did not run a census of every maharatna. We did watch files die on fake averages. Use path-based ranges, then add vigilance, CAB and the SI's calendar. 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 “PSU Procurement Timelines: A Realistic Chart” 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 Startup/Vendor, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “PSU procurement timeline” 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 “PSU Procurement Timelines: A Realistic Chart” is only a heading, it will not survive a file inspection. A P5 Startup/Vendor should be able to attach one artefact that proves “PSU procurement timeline”: 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 procurement timeline” 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

“PSU Procurement Timelines: A Realistic Chart” earns a line in the noting only if a P5 Startup/Vendor can attach proof of “PSU procurement timeline.” 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 “PSU procurement timeline.”
• 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.