The deviation list is the first thing a Korean EPC reads in your technical bid

Your technical bid to a Korean EPC runs to two hundred pages. The engineer evaluating it opens one sheet first: the deviation list. If it is missing, or if it says "none", the assumption is not that you comply. The assumption is that you have not read the specification carefully.

Why the list is read first

A project specification for a plant item is assembled from the owner's standard, the EPC's practice, and the process requirements of that particular unit. It is long, and parts of it are inherited rather than written for your equipment.

The evaluating engineer knows this. What they need to establish quickly is where your offer departs from the document, because those points determine whether the offer is comparable to the others and whether anything downstream has to change.

So the deviation list is not an admission of weakness. It is the working document of the evaluation. A clear one lets the engineer assess you efficiently; its absence forces them to find the gaps themselves, which costs them time and costs you goodwill.

There is a practical reason the sheet carries so much weight. Bids are usually compared on a single spreadsheet, one column per supplier, assembled by one engineer under time pressure. Anything not stated in a form that can be transferred into that sheet tends not to be transferred at all. A deviation buried in the body of a technical description exists legally and disappears practically.

"Full compliance" is the riskiest answer

Declaring full compliance on a specification you have not reconciled line by line creates a problem that surfaces after award, not before.

At that point the specification is contractual. If a clause requires a material, a test, or a document that your standard product does not include, you supply it at your cost or you negotiate from a weak position, having already stated that you comply.

There is a second cost that is harder to see. Experienced evaluators treat blanket compliance statements as unreliable, which means the rest of your submission receives closer scrutiny. A bid with twelve well-reasoned deviations often scores better than one claiming none.

What belongs on the list

A deviation is any point where what you offer differs from what the specification asks. Four categories cover most of them.

Scope deviations cause the most disputes later, because they are the easiest to leave unstated. If the specification assumes the supplier provides the first fill of lubricant, special tools, or the foundation bolts, and you do not, that belongs on the list — even though it feels commercial rather than technical.

Documentation deviations deserve particular attention because they are rarely checked at bid stage and always checked later. A clause requiring a specific certificate type, a calculation report in a named format, or drawings under the client's own numbering system represents real work. If you cannot produce it in that form, listing an equivalent is straightforward at bid stage and awkward once the document schedule is contractual.

How to write an entry that gets accepted

Each entry needs four things: the clause reference, what the specification requires, what you offer, and why. The fourth is the one that decides the outcome.

"Not applicable to our design" invites a query. "Clause 5.3 requires a bolted cover; our design uses a welded closure because the operating pressure exceeds the bolted range for this size, with the calculation attached" gives the engineer something they can approve without further correspondence.

Where your alternative is technically equivalent, say what makes it equivalent and offer the evidence. Where it is genuinely inferior on one axis but better on another, say that too. Engineers accept trade-offs described honestly far more readily than they accept claims of universal superiority.

Keep the list in the format requested. If the enquiry provides a template, use it — a submission that forces the evaluator to re-enter your deviations into their comparison sheet is doing the opposite of what the list is for.

Length is worth managing as well. A list with sixty entries, most of them trivial wording differences, buries the four that matter and suggests the specification was processed mechanically rather than read. Group the minor points, state the substantive ones individually, and put the entries with schedule or cost consequences at the top where they will be seen. An evaluator who reaches the fourth page of minor items has usually stopped reading closely.

Deviations that should be raised before the bid

Some points are better clarified during the enquiry period than listed as deviations afterwards.

If a clause appears to contain an internal contradiction, or specifies something physically inconsistent with another requirement, ask. Bidders often stay silent, assuming a question signals inexperience. In practice the opposite holds: a well-framed technical question during the tender period marks you as someone reading the document properly, and the clarification is issued to all bidders, which removes the ambiguity from the comparison.

The same applies where a specification names a component or a standard you believe has been superseded. Raising it early gets it corrected. Raising it after award makes it your problem.

What happens to the list after award

Accepted deviations become part of the contract. This is the part that gets handled carelessly.

During negotiation, items are discussed, some accepted, some withdrawn, some modified. If the final agreed list is not attached to the purchase order, the original specification governs in full — including the clauses you thought you had deviated from. Weeks of technical negotiation can evaporate at the moment of order placement.

Two practical steps prevent it. Reissue the deviation list at each revision with a clear status per line: accepted, withdrawn, or under discussion. And confirm in writing that the final revision is an attachment to the order, referenced by its revision number.

How it reads to the people who did not meet you

The list travels further than the bid. It is read by the owner's technical function, by whoever later writes the inspection plan, and sometimes by a maintenance engineer years afterwards trying to understand why a component differs from the specification on file.

That means the reasoning has to make sense without you in the room. An entry that reads as a shortcut — "supplied as per manufacturer standard" — becomes an unexplained non-conformance in someone else's audit later. One that states the engineering reason remains defensible indefinitely.

It also means the tone matters. The list is a technical document, not a negotiating position. Entries that argue rather than explain make the evaluation adversarial for no gain.

The bid that complied and still lost the point

There is a case that runs against the pattern above. Occasionally a supplier submits an accurate, well-reasoned deviation list and still finds the clause enforced as written at inspection — because the deviation was accepted by the EPC's engineering function and never reached the inspector.

The inspector works from the specification and the inspection plan. If the agreed deviations were not carried into the inspection plan, the item is assessed against the original clause, and the equipment is held at the shop while the correspondence is retrieved.

So the last step is not securing acceptance; it is checking that the accepted list is reflected in the inspection and test plan before manufacturing starts. If you have a specification and an enquiry deadline in front of you, we can look at which clauses usually need a deviation entry for your item class — talk to us about sourcing. How the inspection side then handles it is covered under vendor registration.