OdysseyGPT

Bid engineering guide

Technical deviation list: format, worked valve example and free template

Written for the manufacturer answering the tender: the bid engineers, proposal engineers and project managers at valve, pump, actuator and instrument makers.

By Ademola Afolabi, Founder, New Odyssey Ltd · Last reviewed:

The short answer

A technical deviation list is the table a manufacturer submits with its offer. It lists, clause by clause, every point where the offered equipment differs from the client's specification, the reason, and what it would cost to comply instead. Evaluators use it to accept, reject or clarify each point before the bid is scored.

Key Takeaways

  • Use seven columns: spec clause, requirement, offered, status, deviation or clarification, justification and cost of withdrawal.
  • Every row cites the exact clause, so the evaluator can check it in seconds.
  • A deviation that is not on the list is usually treated as not offered, or the bid is held to full compliance.
  • Cost of withdrawal tells the buyer the price and lead-time impact of complying instead, which keeps the bid comparable.

What a technical deviation list is, from the manufacturer's side

Most explanations of deviation lists are written for the EPC evaluator who reads them. This guide is for the people who write them. That is the bid engineer, proposal engineer or project manager with a requisition, a project specification, an owner standard, several addenda and a datasheet. They have to say exactly where the offer does not match.

The list is not paperwork. Some owners decide whether a bid is scored at all from it. BHEL valve tenders are one example. They reserve the right to accept or reject any quoted deviation. They ignore deviations that appear only in the priced copy. They use fixed columns for spec reference, description, reason and cost of withdrawal (BHEL corrigendum). Some BHEL ball- and check-valve tenders are declared "no deviation" tenders, where nothing can be added after submission (BHEL tender).

On the buyer's side, the evaluator checks each quote against the correct requisition issue and its reference documents. They produce clarification requests, a list of unacceptable deviations and a technical bid comparison (Red Bag CM-PE-510). Your list is the input to that process. See technical bid evaluation for what happens next.

The seven columns and what goes in each

Recommended columns for a manufacturer-side technical deviation list
ColumnWhat to writeCommon mistake
Spec clauseDocument number, revision and clause, for example "PS-VAL-001 Rev 2, §4.2". One clause per row.Citing a whole section, or the wrong revision after an addendum.
RequirementThe requirement in short, in your own words, with the key value (material, rating, test, certificate).Pasting a whole paragraph, so the evaluator cannot see the point at issue.
OfferedWhat you actually offer, with the same units and the datasheet reference.Writing "as per our standard" with no value.
StatusOne of: Complies, Clarification, Deviation, Not offered. See the status table below.Mixing statuses, such as "complies with deviation".
Deviation / clarificationThe exact difference, stated once, in one or two sentences.Restating the requirement instead of the difference.
JustificationWhy the offer is technically acceptable: equivalence, service conditions, qualification evidence, attached certificate.Commercial reasons only ("our standard design").
Cost of withdrawalPrice and lead-time impact if the buyer rejects the deviation and you must comply, or "no cost".Leaving it blank, which forces a clarification round.

If the tender supplies its own deviation form, use the tender's form and its column order. Map these seven fields onto it rather than attaching a second table.

Status values: use four, and define them

StatusMeaningWhen to use it
CompliesThe offer meets the requirement as written.Only when you can point to the datasheet or certificate that shows it.
ClarificationThe offer meets the intent, but wording, reference or method differs, or the requirement is ambiguous.An equivalent test standard, a conflicting clause, a missing value in the spec.
DeviationThe offer does not meet the requirement as written.Different material, rating, test, certificate type or scope.
Not offeredThe item is excluded from the scope of supply.Spares, site services or documents you are not quoting.

Some tenders ask for a full compliance statement (every clause, including those you comply with) and a separate deviation list (only the exceptions). The first is a compliance matrix. The deviation list carries only the rows that are not "Complies".

The free templates add a fifth value, Not applicable, for compliance-matrix rows where a clause does not apply to the equipment offered, such as a sour-service clause on a non-sour duty.

Worked example: 6-inch Class 600 trunnion ball valve

The example below uses an invented project specification (PS-VAL-001) for a 6-inch, ASME Class 600, full-bore trunnion-mounted ball valve. Every value is illustrative. It shows how one row should read, not what any real specification requires.

Illustrative deviation list rows (invented specification PS-VAL-001 Rev 2)
Spec clauseRequirementOfferedStatusDeviation / clarificationJustificationCost of withdrawal
PS-VAL-001 §4.2Body and closures forged ASTM A350 LF2 Cl.1Cast ASTM A352 LCC body, forged A350 LF2 closuresDeviationCast body offered instead of forged.ASTM A352 covers steel castings for pressure-containing parts in low-temperature service, and grade LCC has a usual minimum test temperature of −46 °C, which covers the design minimum temperature in the datasheet (ASTM A352). Casting inspection levels are listed in the datasheet.Forged body available: +9% unit price, +5 weeks.
PS-VAL-001 §4.5Seat inserts PEEKReinforced PTFE seat insertsDeviationSeat insert material differs.Design temperature in the datasheet is within the RPTFE rating; PEEK is offered as an option.PEEK seats: no price change, +2 weeks.
PS-VAL-001 §5.1Fire tested to API 607API 607 fire-type test certificate from an earlier edition, for this valve familyClarificationQualification is to an earlier edition of the fire-test standard.The design has not changed since the qualification test. Buyer to confirm the earlier-edition certificate is acceptable.New API 607 qualification: not offered within the bid lead time.
PS-VAL-001 §6.3Stem seal qualified to ISO 15848-1, class BH, CO1Type test report to ISO 15848-1 class BH, CO1 on a qualified stem seal of the same design familyClarificationQualification is by family, not on this exact size.Buyer to confirm that the family qualification covers this size; report reference listed in the datasheet.Size-specific test: +USD 14,000 one-off, +6 weeks.
PS-VAL-001 §7.2EN 10204 type 3.2 certificates for pressure-containing partsEN 10204 type 3.1 certificatesDeviation3.1 offered instead of 3.2.Material is tested by our authorised inspection department; 3.2 needs the buyer's or a third-party inspector's validation. See EN 10204 3.1 vs 3.2.3.2 certificates: +3% and +2 weeks, inspector fees by buyer.
PS-VAL-001 §9.4Pressure testing to API 598Pressure testing to API 6DClarificationValve tested to its product standard rather than API 598.API 6D, the governing product standard in §3.1, has its own shell and seat test requirements. Buyer to confirm API 6D testing is acceptable.Additional API 598 test: no cost, +1 week.
PS-VAL-001 §11.1Two-year operating sparesCommissioning spares onlyNot offeredTwo-year spares excluded from this price.Quoted separately on request so the base price stays comparable.Two-year spares: priced separately.

Read the example row by row

Each row names one clause, states the offer in the same terms as the requirement, gives one status, says what differs, gives a technical reason and prices the alternative. An evaluator can accept or reject each row without calling you.

Deviation, clarification, exception and TQ: the differences

TermWho raises itWhenWhat it means
DeviationManufacturerIn the offerThe offer does not meet a requirement as written.
ClarificationManufacturerIn the offerThe offer meets the intent, but a reference, method or wording differs, or the spec is unclear.
Exception / exclusionManufacturerIn the offerScope not supplied. Often listed as "Not offered".
Technical query (TQ)Either sideBefore or during evaluationA question that needs a written answer before the offer can be completed or evaluated. See technical query.

How to build a deviation list in seven steps

  1. Collect every governing document: requisition, project specification, owner standards, datasheets, addenda and the tender's own deviation form. Note each revision.
  2. Decide which document wins when two disagree. Most requisitions state an order of precedence; if not, raise a TQ. See governing-document precedence.
  3. Go clause by clause through the specification and datasheet. Record each requirement with its value, even where you comply, so nothing is missed.
  4. Compare each requirement with your datasheet, catalogue and past qualification records, and set one status.
  5. For every row that is not "Complies", write the difference once, a technical justification and the cost of withdrawal.
  6. Have a second engineer check the non-compliant rows and every row that cites a test, certificate or material.
  7. Copy the final rows into the tender's form, check that the priced and unpriced copies match, and submit.

Step 3 is where most of the time goes and where most misses happen. A free deviation list template and compliance matrix template give you the columns ready to fill, with drop-downs and this valve example already filled in.

Mistakes that make a bid non-responsive

  • Leaving a deviation off the list. Many tenders hold you to full compliance for anything not declared.
  • Declaring a deviation in the priced copy only. BHEL, for one, ignores deviations that are not in the unpriced technical copy (BHEL corrigendum).
  • Missing a mandatory document. A missing API 6D certificate or manufacturer authorisation letter is a typical reason for rejection in OGDCL evaluations. There, a zero in any key sub-category makes the bid non-responsive, even if the total clears the 70-point pass mark (OGDCL clarification; OGDCL evaluation report).
  • Citing the wrong revision after an addendum.
  • Commercial justifications for technical deviations.
  • No cost of withdrawal, which forces a clarification round and can push the bid down the evaluation queue.

Where OdysseyGPT fits, and where it does not

OdysseyGPT reads the whole specification package. It checks each customer requirement against your own datasheets and standard specifications. Each one gets a status: complies, deviates, clarification, not addressed, document requested, not applicable or out of scope. Each status comes with a quote from the source page, sheet or cell. It exports an editable compliance matrix and a deviations & clarifications list. A bid engineer, proposal engineer or project manager then decides every open item and writes the justification and cost of withdrawal. It is built for manufacturers of engineered equipment. See OdysseyGPT for manufacturing.

Its limits matter. It does not interpret engineering drawings such as general arrangements or P&IDs, it does not send anything to the customer, and it cannot know an owner's unwritten preferences. Your engineers decide every open item and own what goes out.

Buyer questions

20 questions bid engineers, proposal engineers and buyers ask. Last reviewed:

Who writes the technical deviation list?

The manufacturer writes it, as part of its offer. In practice the bid engineer, proposal engineer or project manager drafts it, with input from design, quality and specialist engineers. On the buyer's side, the EPC or owner's discipline engineers read it during technical bid evaluation and decide whether each deviation is acceptable.

When is the deviation list submitted?

It is usually submitted with the technical, or unpriced, part of the offer by the bid closing date. Many tenders say that deviations not declared at that point will not be considered. After submission, it is updated through technical queries and clarification rounds. Check the instructions to bidders for exactly where it must sit in your offer.

Should I use the tender's deviation form or my own format?

Use the tender's form whenever one is given. Evaluators compare bidders side by side, and a different layout slows them down or can make the offer non-compliant with the instructions. If no form is given, use clear columns for clause, requirement, offered, status, justification and cost of withdrawal. Our free template follows that layout.

What is the difference between technical and commercial deviations?

Technical deviations are about the equipment, its tests, documents and scope. Commercial deviations are about terms such as payment, delivery, warranty, liability and price validity. Most tenders want them in separate lists, because different people evaluate them. Keep prices and commercial terms out of the technical list, especially if the technical offer is unpriced.

Can I just state 'no deviations' in my offer?

Only if it is true. A no-deviation statement means you will be held to every requirement in the package, including referenced standards, notes and addenda. If the offer differs on any point, declare it. A deviation found after award is usually far more expensive to resolve than one declared in the bid.

Are blanket statements like 'as per our standard' acceptable?

Usually not. A line such as 'as per manufacturer's standard' or 'all clauses subject to our standard terms' does not tell the evaluator what differs. Many buyers reject such statements or treat them as non-responsive. Name each clause, say what you offer instead, and explain why. That is the only form an evaluator can accept or price.

How long should a deviation justification be?

Keep it to one to three sentences. Say why your offer still meets the purpose of the requirement, or why the requirement cannot be met as written. Point to evidence, such as a test report, qualification record or field history. Avoid commercial reasons for technical deviations; evaluators judge the technical case on its own.

How do I update the deviation list after technical queries?

Issue a new revision of the list after each clarification round, not just an email reply. Mark which rows changed, which were withdrawn and which the buyer accepted. Keep the revision number and date on the list. The final revision should match exactly what the purchase order says was agreed. See technical query.

How do I handle two tender documents that conflict?

Check the order of precedence first. If it settles the conflict, comply with the winning document and add a clarification row naming both. If it does not, raise a technical query before closing, or state the basis you offered on as a clarification. See governing-document precedence.

What does the evaluator do with my deviation list?

The evaluator checks each row against the requirement and decides to accept it, reject it, or ask a question. Rejected deviations usually have to be withdrawn, often at the cost you stated. The result feeds the technical bid comparison that decides which offers are technically acceptable. See technical bid evaluation.

Do I need to list deviations for bought-out components?

Yes. Your offer covers the whole scope of supply, including actuators, gearboxes, motors, seals and instruments you buy in. If a sub-supplier's item differs from the specification, it is your deviation. Check sub-supplier datasheets against the same clauses, and confirm the makes are acceptable if the tender lists approved sub-suppliers.

What happens to accepted deviations after award?

Accepted deviations should be written into the purchase order or one of its attachments, often as a final agreed deviation list. Check that they are. If the order only says supply to specification, you may be held to the original requirement. Keep the agreed list with the order file so design and quality teams build to it.

Should the deviation list be in Excel or Word?

Follow the tender. Many EPCs issue an Excel form because it can be filtered and merged into their evaluation sheet. Others ask for a Word or PDF table signed with the offer. If you can choose, keep a working copy in Excel and issue a locked PDF with the offer, so the submitted version cannot change.

Will a long deviation list lose me the bid?

Not by itself. Evaluators care whether each deviation is acceptable and how much it costs to remove. A short list that hides a key deviation is worse than a long, honest one. Deviations on key points, such as materials, design standard or mandatory tests, can make a bid technically unacceptable on their own.

Is a tender deviation the same as a deviation request after award?

No. A tender deviation is declared in the offer, before award. After award, a change to the agreed requirements usually goes through a formal deviation, waiver or concession request that the buyer must approve. Names and forms vary by company. The later route is slower, so declare what you know at bid stage.

How do I write a deviation against a referenced standard?

Name the standard, its edition and the part that you do not meet, then say how the offer differs. Also cite the specification clause that calls the standard up, so the evaluator can trace it. If the difference is only the edition, list it as a clarification. See API 6D for an example of edition checks.

Should an alternative offer go in the deviation list?

Usually it should go in a separate alternative offer, if the tender allows one. Submit a compliant base offer first, with its own deviation list. Then describe the alternative, its benefits and its own deviations separately. Mixing them makes it unclear what you are offering. Some tenders do not accept alternatives at all, so check first.

Do I need a cover sheet for deviations and clarifications?

Some tenders ask for a short summary sheet, signed by the bidder, that counts and lists the main deviations and clarifications. It helps the evaluator see the key points first. Our clarifications and deviations summary template gives one layout. Make sure the summary matches the full list exactly.

How does OdysseyGPT help build a deviation list?

OdysseyGPT reads the whole tender package and checks each customer requirement against your own datasheets, standard specifications and test procedures. Each requirement gets a status with a quote and the page, sheet or cell it came from. You export an editable compliance matrix and a deviations and clarifications list, with internal to-dos on a separate sheet.

Does OdysseyGPT write the justification and cost of withdrawal?

No. Those are engineering and commercial decisions, so your engineers write them. OdysseyGPT finds the rows that do not comply and shows the source quote for each, so the engineer starts from evidence. It does not send anything to the customer, and it does not interpret drawings such as general arrangements or P&IDs.

Frequently asked questions

What is tender deviation?

A tender deviation is any point where a bidder's offer does not meet the tender's technical or commercial requirements as written. Bidders declare deviations in a deviation list so the buyer can accept, reject or price them before award.

What is the difference between a deviation and a clarification?

A deviation means the offer does not meet the requirement as written. A clarification means the offer meets the intent but a reference, method or wording differs, or the requirement itself is unclear.

Should a deviation list include clauses where we comply?

Usually not. The deviation list carries only exceptions. A full clause-by-clause statement that includes compliant rows is a compliance matrix, which some tenders ask for as well.

What is cost of withdrawal?

Cost of withdrawal is the price and lead-time change if the buyer rejects your deviation and you must comply with the original requirement. Some tender forms, such as BHEL's, include it as a fixed column.

Can I add deviations after submitting the bid?

Often not. Some tenders are declared no-deviation tenders, and many treat anything not declared at submission as fully compliant. Check the instructions to bidders before you submit.

References

BHEL corrigendum: deviation sheet columns and rules

BHEL

Visit source

BHEL valve tender declared as a no-deviation tender

BHEL

Visit source

OGDCL tender clarification: technical pass mark and key sub-categories

OGDCL

Visit source

OGDCL technical evaluation report

OGDCL

Visit source

ASTM A352/A352M: steel castings for low-temperature service

ASTM International

Visit source

CM-PE-510 Procedure for technical evaluation of quotations

Red Bag

Visit source

Related Pages