Technical deviation sheet: how evaluators read it and how to write yours

What does an evaluator do with your deviation sheet?

You already know the columns; the compliance matrix guide and our post on technical datasheets both show a sample sheet. This post sits on the other side of the table, with the person who has to read 20 offers and recommend which ones go through to price opening.

In central government goods procurement, the technical member of the tender committee examines the specifications and other technical terms, and the manual calls the bidder's exceptions and deviation form "an important document". The committee has to judge whether each deviation is minor or major (para 7.4.2-2 of the Manual for Procurement of Goods (opens in a new tab), 2024). Private EPC buyers work the same way in their technical bid evaluation.

1. Read the deviation sheet first, to see what you admit to.
2. Check the filled datasheets, drawings and catalog pages against the specification, looking for differences you did not list.
3. Raise technical queries on anything unclear, with a reply date.
4. Sort each deviation: waive it, price it, or reject the offer.
5. Write the evaluation report, which states each offer's deviations and comments on their acceptability.

Step two is the one bidders forget. A catalog note that says "standard paint system" or a drawing that shows a different flange rating is a deviation the evaluator found for you, and found ones look worse than declared ones.

Acceptable, priceable or fatal: how evaluators sort deviations

The legal test for a substantive deviation is summarized in our compliance matrix guide. In practice, the goods manual lets a buyer accept a minor deviation only if it has no fiscal impact, does not change the ranking of bidders and gives no undue advantage (para 7.3.4-6). For commercial terms, deviations from critical provisions count as material. Where the tender does not name them, the manual lists governing law and jurisdiction, contractor obligations, performance security, force majeure, taxes and duties, and the code of integrity (para 7.4.2-4).

Loading of deviations: how a deviation gets a price

Some deviations are not bad enough to reject but would cost the buyer money. Many PSU and EPC tenders handle those by loading: the evaluator adds an amount to your price, for comparison only, so you are ranked as if the deviation were not there. Payment terms and delivery are the classic cases, loaded by a formula set in the tender.

Other formats ask you to price your own deviations in a "cost of withdrawal" column. The buyer can then accept the deviation or ask you to withdraw it at that price. Read the rule for blank cells: in some formats an unpriced deviation is treated as having nil cost of withdrawal, which means you remove it for free if asked.

Loading never runs the other way. The goods manual says variations and benefits above the scope of the goods shall not influence the evaluation; if you win, the buyer simply takes the extra as part of the contract (para 7.3.4-4). A bigger motor or a better coating is not a credit. If it is also a change, it is still a deviation.

No deviation clauses and the nil deviation certificate

Some tenders say bidders shall not take any deviation, or that offers with deviations will be rejected. Read that as a closed door. The only routes left are a pre-bid query, which the buyer may answer with a corrigendum, or a decision to comply in full.

Do not plan to fix things later. Under para 7.3.5-1 of the goods manual, a buyer may seek clarifications, but no change in prices or substance may be sought, offered or permitted, and post-bid clarifications at the bidder's initiative are not entertained. A deviation you meant to withdraw after opening is, in practice, part of your bid.

• Before signing a nil deviation certificate, read your own catalog, drawings and test certificates for anything that contradicts the specification.
• Remove or mark catalog pages for models you are not offering, so their values cannot be read as your offer.
• Make the datasheet, drawings and nil deviation certificate say the same thing. A conflict between them can be read as a conditional bid.
• If the tender also asks for a compliance statement, fill it consistently with the certificate.

How to write a deviation with justification

Write each entry so an evaluator who has not read the rest of your offer can decide it. That means five parts: the tender clause and its exact requirement, what you offer in the same units, the technical reason, the evidence, and what changes for the buyer.

Words like "subject to", "if possible", "noted" and "manufacturer's standard" are the ones that turn a fixable deviation into a conditional bid. Replace each with a value.

Deviations that usually sink an offer

• Deviations on eligibility or qualification criteria. Those are pass or fail, and no deviation sheet changes that.
• Anything that reduces a guaranteed parameter: capacity, efficiency, rating, life or emission limit.
• Changes to critical commercial terms such as liability caps, liquidated damages or performance security.
• Deviations listed somewhere other than where the tender asks, which some buyers simply ignore. A BHEL tender (opens in a new tab) goes further and refuses to evaluate an offer without its deviation list.
• A price, discount or cost figure in the technical bid, unless the format asks for cost of withdrawal there.
• Deviations first raised after technical bids are opened.

Illustrative example: an evaluator works through a gearbox offer

A cement plant near Kalaburagi tenders four conveyor gearboxes. A gearbox maker from Ahmedabad lists five deviations. Here is how the plant's evaluator reads them. The plant, the maker and the figures are invented.

1. Service factor 1.75 offered against 2.0 specified. This affects performance. The evaluator cannot let the bidder raise it after opening, so the offer is marked technically non-responsive.
2. Bearing make outside the approved list. The tender allows equivalents with proof; a technical query asks for load ratings, and the reply settles it.
3. Paint thickness 200 microns against 240 microns, with a cost of withdrawal stated. The evaluator records the deviation and the cost; the buyer will ask for withdrawal if this bidder wins.
4. Delivery 20 weeks against 16 weeks. The tender loads late delivery by a stated percentage per week for comparison, so the evaluated price rises.
5. An oil cooler supplied though not asked for. No credit in evaluation; it becomes part of the contract if the bidder wins.

One line out of five decided the result. If the maker had found the service factor gap at the enquiry stage, it could have offered the next frame size or raised a pre-bid query, and the other four deviations would have been ordinary work for the evaluator.

Where software helps with deviations, and what stays a human call

Most hidden deviations come from a requirement nobody saw: a row on a datasheet, a clause in the special conditions, a test in the inspection plan. TenderGenie's Enquiry Checklist turns the buyer's requirements into what to supply, what you meet and what is missing, so gaps surface while there is still time for a pre-bid query. Risk & Compliance maps requirements to your response so differences show before submission.

At the end, TenderGenie's Response Builder checks that every required document, including the deviation sheet or nil deviation certificate, is in the package. For the full workflow from tender pack to a source-linked matrix, see the tender compliance matrix use case.

Whether to deviate, how to word it, what the withdrawal costs and whether the offer is still worth sending are decisions for your engineering and commercial leads. Software can find the gap; it cannot decide what your company is willing to commit to.

Questions and answers