Contract Award Challenges: What Triggers Them

The representation arrived on a Tuesday, fourteen pages, copied to the FA, the CVO and a WhatsApp group the section officer did not know existed. L1 had been announced on GeM the previous Friday. The L2 seller did not say the product was better. They said the technical committee had used a demonstration score the bid document never described.

That is how most Indian award challenges begin. Not with a philosophy of public procurement. With a gap between the published scheme and the marking that happened in a conference room. Once that gap is visible, everyone — the losing seller, the vigilance cell, sometimes a court — has a handle.

This explainer is for procurement officers, DDOs and committee chairs who buy software and agent platforms. It is not a litigation manual and it is not legal advice. It is a map of the triggers that turn a defensible award into a file you cannot explain six months later.

What an award challenge is not

It is not a re-tender because someone is sad. Public procurement is allowed to produce a loser. CVC guidance, departmental manuals and GeM process all assume a responsive L1 or a QCBS winner under the published method. Disappointment is not a ground.

It is also not automatically a stay. Many representations are answered on the file and die. Some become incidents on GeM. Some become court or tribunal matters. The buyer’s job is not to fear every letter. The buyer’s job is to have a file that can answer the letter without inventing a new evaluation.

Sellers sometimes send a 'challenge' that is really a request to relax a mandatory they failed. That is not an evaluation dispute. That is an attempt to rewrite the ATC after opening. The answer is the bid document, dated, as uploaded.

The triggers that actually bite

The dangerous triggers are process facts, not product opinions. Did you evaluate against criteria that were not in the bid? Did you ignore a mandatory that you enforced against another bidder? Did you change the QCBS weights after seeing prices? Did you allow one seller to cure a missing paper and refuse another? Did you apply an MSE or startup preference the bid did not write, or refuse one the bid did write?

GeM and CPPP both create a timestamped trail. That is good for an honest committee. It is fatal for a committee that 'decided in the room' and typed the portal later. If the demonstration rubric lived only in a member’s notebook, you have given the challenger their exhibit A.

Price reasonableness notes matter when competition is thin. A single-bid award, a PAC-adjacent software buy, or a custom bid with two responsive packets will be read with GFR price-reasonableness expectations in mind. The note does not need poetry. It needs a method you could defend to audit.

Challenges attach to paper gaps. Fill the paper before you announce L1, not after the representation arrives.

Trigger	What the challenger will say	What the file should already contain
Undisclosed criterion	You marked a demo / 'look and feel' that the bid never scored	The published evaluation table, and marks that map only to those rows
Unequal cure	They were allowed to upload a missing GST; we were not	A written rule: clarification versus new mandatory paper, applied to every packet
Mandatory ignored for the winner	L1 failed a shall-clause you treated as optional	A responsiveness checklist completed before any scoring of quality
Preference misapplied	MSE / MII / startup relief granted or denied against the bid text	The clause, the certificates as on opening day, the arithmetic
Negotiation theatre	You bargained only with a favoured firm after opening	The method the bid named, and any post-tender negotiation recorded with authority
Reasonableness vacuum	The rate cannot be explained	A short note on last purchase, rate discovery, or why a novel agent has no last purchase

Representations, GeM incidents, vigilance, courts

Most sellers start with a representation to the buyer. Answer it on the file, with the bid text quoted, within a time the department can defend. A mute buyer trains the seller to escalate.

On GeM, incident management is a separate track from a polite letter. Incidents have their own workflow, and after a show-cause some closures sit with GeM admin rather than with the parties. Read the live incident FAQs on gem.gov.in before you type in the ticket. Do not promise a 'mutual close' the policy does not give you for that incident type.

Vigilance interest grows when the same gap would look like favour. You do not need a corrupt officer for a CVO to ask questions. You need an evaluation that cannot be reconstructed. Court challenges are slower and rarer for modest software bids, but they feed on the same exhibits: published criteria versus actual marks.

None of this is a reason to freeze every award. It is a reason to announce only when the comparative statement and the responsiveness sheet can be printed without embarrassment.

How to run an evaluation that can be reconstructed

Write the evaluation table into the bid as if a stranger will mark it. If a live demonstration is worth marks, publish the rubric and the time box. If it is only a clarification of the written technical, say that it carries no extra marks.

Separate responsiveness from quality. A packet that missed a mandatory annexure is out before anyone falls in love with the demo. Mixing those steps is how a committee 'gives them a chance' and then cannot explain the chance to L3.

When two members disagree on a technical row, record the disagreement and the chair’s resolution. Silence in the minutes is not consensus. It is an empty space a representation will fill.

• Comparative statement that cites clause numbers, not adjectives.
• Signed attendance of the committee that actually marked, not a standing committee that was not in the room.
• Certificates relied upon for MSE, MII or startup relief, downloaded or stamped as on opening day.
• A one-page reasonableness note when bids are few or the category is novel.
• The exact portal extract of the award, stored outside GeM.

What a losing seller should actually put in a letter

If you are the founder reading this from the other side, challenge process, not taste. 'Your committee has poor technical judgement' will be filed under disappointment. 'Clause 6.2 published a 30-mark security row and the comparative statement shows no such row' is a fact.

Ask for the documents the transparency path allows — comparative statement extracts, reasons for rejection — through the route the bid and the portal provide. Do not threaten a CVO in the first paragraph of a letter that has not yet identified a clause.

If you lost because you were non-responsive, the letter should be a post-mortem for your next bid, not a challenge. Challenging your own missing affidavit wastes everyone’s year.

What committees say when they want to skip the paper

These lines sound efficient in a closing meeting. They are how representations are born.

Everyone knows what a good demo looks like.

Then write what it looks like, in marks, in the bid. Unwritten taste is not an evaluation criterion. It is a gift to the losing seller.

If we answer the representation we admit doubt.

Silence admits a file that cannot speak. A dated reply that quotes the bid and attaches the comparative statement is what a later CVO wants to see. Doubt is not created by answering. Doubt is created by having nothing to quote.

L1 is on GeM, so the portal has already blessed the process.

GeM records the transaction. It does not cure an evaluation that departed from the uploaded ATC. Portal success is not a vigilance opinion.

The challenger is a habitual litigant.

Then your file should be boring enough that habit has nothing to hold. Characterising the seller is not a substitute for clause-mapped marks.

The week before you announce — a buyer’s reconstruction test

Run this before the award button, not after the fourteen-page letter.

1. Day 1: reprint the evaluation section of the live bid. Highlight every numbered criterion and weight.
2. Day 2: complete responsiveness for every packet against mandatories only. No quality talk yet. Record outs with clause numbers.
3. Day 3: mark quality only on published rows. If a demo happened, file the rubric you used and show it matches the bid — or show that it carried zero marks.
4. Day 4: apply any MSE / MII / startup arithmetic using the bid text and the opening-day certificates. Write the arithmetic on one page.
5. Day 5: write the reasonableness note if competition was thin. Get the chair to sign the comparative statement. Then announce. Not before.

What goes in the file before anyone writes L1

The award file should let a stranger reconstruct the result: the bid as uploaded, every packet, the responsiveness sheet, the marked comparative statement, the preference arithmetic, the reasonableness note where needed, the committee attendance, and the portal extract of the award.

After a representation, add the letter, the dated reply, and any GeM incident reference. Do not add a new scoring sheet that 'clarifies' marks you did not give at the time. Reconstruction is allowed. Reinvention is how the second letter writes itself.

This article is informational field guidance for Indian public buyers and bidders, not legal, vigilance or litigation advice. Award remedies depend on the bid, the portal, the department’s manual and the forum. Confirm against the live notice, CVC circulars on cvc.gov.in, and counsel.