OdysseyGPT
Blog postUpdated 17 Nov 2026

Catching a Missed Requirement at Tender, Kickoff or FAT: What Each Point of Discovery Costs

Where you find an unanswered requirement decides the cost: a declared exception at tender, or a re-test or back-charge at FAT. Compare all four stages.

LeadReader brief

Where you find an unanswered requirement decides the cost: a declared exception at tender, or a re-test or back-charge at FAT. Compare all four stages.

A requirement nobody answered at bid stage costs least when you find it at tender. At that point it is still a status on a row in your compliance matrix, and you can declare it in the offer. Found at order kickoff, it becomes a change you have to negotiate. Found through EPC queries, you are defending it after the fact. Found on the shop floor or at FAT, it becomes a re-test, a non-conformance or a back-charge, and the margin on the job goes with it.

This guide follows one unanswered requirement through those four points of discovery. At each one it shows what changes and who holds the negotiating position. It ends with a self-assessment you can run on your own recent orders.

Why the same missed requirement costs more the later you find it

A missed requirement costs more the later you find it because each stage removes an option you had before. At tender you can price it, clarify it or take exception. After award you can only negotiate. At FAT you can only re-test, accept a non-conformance or absorb a back-charge.

The miss itself usually starts with how the package arrives. A valve, pump or actuator enquiry rarely comes as one document. Requirements sit across the project specs, the material requisition (MR), the ITP, customer data-sheets and the standards they call up, such as API 6D. Many are buried in running text and tables. Some depend on documents the package never included.

Bid desks have limited engineering hours per tender. When the package is long and the deadline is fixed, engineers skim, and skimming is how clauses get missed. The clause does not go away. It waits in the order the EPC places.

For each of the four points of discovery below, three things change:

  • Who knows about the gap: only you, you and the EPC, or everyone including the inspector.
  • What it costs: bid-stage engineering hours, a negotiated change, or rework and schedule.
  • Who holds the position: you, with a declared exception, or the EPC, with a spec your offer never challenged.

Point 1: At tender, in a full bid-stage review

Finding a requirement at tender is the cheapest point of discovery. The gap is a row in the compliance matrix marked deviates, needs a clarification or not addressed, and the exception goes into the offer.

Cost. Engineering hours at bid stage. The exception can be priced into the quote or raised as a clarification before the price is fixed.

Negotiating position. Yours. The EPC evaluates a declared exception at technical bid evaluation. The EPC may push back or ask questions, but it does so knowing your position, and you have not committed to a price that ignores the gap.

Why 'not addressed' matters. Every requirement should be marked complies, deviates, needs a clarification or not addressed, with a quote and page from your own data-sheet or test procedure behind it. The 'not addressed' status is what makes a gap visible before the price is fixed. Without it, an unanswered clause looks the same as a clause nobody read.

Missing documents. Some requirements depend on a document the package does not contain, such as an ITP that was never sent. A full bid-stage review treats that as a document to request on the D&C list, not as an assumption baked into the price. If you need a refresher on what that document should contain, see what an inspection and test plan covers.

Point 2: At order kickoff, in the post-order review

Finding a requirement at order kickoff means the price is already committed. The project team reads the full package after award, often more closely than the bid desk had time to. It finds a clause the bid never answered.

Cost. Any change now has to be raised as a change request or a concession, not as part of the offer. Whatever the requirement costs to meet is either negotiated with the EPC or absorbed by you.

Negotiating position. It shifts to the EPC. The order was placed against the spec, and silence in the offer can read as acceptance. You are now asking for something, not stating a position.

The addenda trap. Addenda and revised MRs are a common source of kickoff surprises. When the bid desk answers the first issue closely and only skims the revisions, a tightened test duration or material requirement goes out unanswered. The order is placed against the revision, and the gap surfaces at kickoff, at FAT or on the shop floor. Other tender guidance points the same way. According to BrainBox, a tender's critical requirements are often buried in annexes and addenda rather than the main document, and addenda should be reviewed last so outdated requirements don't carry through.

Point 3: Through EPC queries during evaluation or after award

Finding a requirement through EPC queries puts you on the defensive. The EPC asks where a 'complies' came from, and the team cannot quickly point to the page in its own data-sheet or test procedure.

Cost. Rounds of queries, delayed evaluation, and a weaker technical score. Vague exceptions make it worse. So do internal to-dos such as 'check with QA' that leak onto the customer copy and tell the EPC the offer is unfinished. These cost bid evaluation points even when the engineering underneath is sound.

Negotiating position. Defensive. You are explaining after the fact instead of stating a position up front. Each round of queries also tells the EPC the offer was not reviewed line by line.

What helps. Agree one row pattern as a bid desk standard: the requirement, where it sits in the customer's documents, the status, your position, and the quote and page from your own data-sheet or test procedure. Tying each row to the same source is what makes wording consistent between engineers. It also turns most EPC queries into a page reference you can send back the same day.

Point 4: On the shop floor or at FAT

Finding a requirement on the shop floor or at FAT is the most expensive point of discovery. The equipment is built or tested against your standard practice, and the customer's ITP or spec calls for something else.

Cost. This is where re-tests, non-conformances and back-charges land, often with schedule pressure on top. The hold points, test durations and witness requirements in the customer's ITP are now fixed, and the equipment either meets them or it doesn't.

Negotiating position. The weakest of the four. The requirement was in the package, and the offer never took exception to it. The inspector is working from the spec the order was placed against.

Inspection and test requirements are the ones most likely to surface here, because they are only exercised at the test bench. The ITP Validator page shows how checking the customer's ITP against your test procedures works. That tool is currently in beta. The Inspection & Testing module shows how inspection and FAT requirements carry from tender to test.

Side by side: cost and leverage at each point of discovery

Options narrow at each stage. A gap found at tender is a priced exception. After award it is a negotiated change. At FAT it is a re-test or a back-charge. No dollar figure is needed to see the pattern. What changes is how many choices you still have.

Point of discovery What is still open to change Typical consequence Who holds the position
Tender (full bid-stage review) Price, scope, exceptions, clarifications, documents to request Declared exception or clarification in the offer You
Order kickoff (post-order review) Only what the EPC agrees to as a change or concession Negotiated change, or cost absorbed Shifts to the EPC
EPC query (evaluation or after award) Your explanation and evidence Rounds of queries, lower technical score, delayed award EPC, with you on the defensive
Shop floor or FAT Rework, re-test and schedule recovery Re-test, non-conformance or back-charge EPC and inspector

The table also shows why declining a tender is not the only cost to weigh when the bid desk is overloaded. Rushing the technical review is not always better than declining. A requirement nobody answered at bid stage can come back after the order, and a rushed bid can turn a won order into a job with no margin. For more on how equipment makers structure these outputs, see this page on the compliance matrix and deviation list for equipment makers.

Why common fixes still let requirements slip to FAT

The usual fixes add effort but do not give every requirement a status. That is why misses still surface at kickoff and FAT.

Reading the whole package by hand. Reading every clause against your own data-sheets works on a single tender. It does not scale with tender volume. When the desk is busy, the full read becomes a skim, and the skim is where clauses get missed.

General-purpose chat assistants. A general chat assistant returns answers, not an exhaustive record. It does not give every requirement a status, including 'not addressed'. It also does not quote the source and page so an engineer can check the finding before the offer goes out. An answer you can't trace back to a page is hard to sign off and harder to defend in an EPC query.

Adding headcount. More engineers help with volume. They still leave no consistent, cited trail behind each row of the compliance matrix, and each engineer words exceptions their own way.

Inconsistent D&C lists. When D&C lists vary between engineers, with to-dos mixed in and exceptions worded vaguely, EPCs come back with queries even when the engineering is sound. That pushes discovery from Point 1 to Point 3.

What good looks like: every requirement carries a status at tender

Good bid-stage coverage means every requirement in the spec package carries a status at tender, backed by a quote from your own documents, so exceptions are declared in the offer and not discovered at FAT. In practice that comes down to six steps:

  1. Check each requirement only against the documents that can answer it. A test duration is answered by your test procedure, not by a general brochure.
  2. Quote the evidence for each finding with its page, sheet or cell. Any finding whose quote cannot be verified in the source goes to review, not into the matrix.
  3. Flag missing documents, such as an ITP that was never sent, as items to request from the EPC in the D&C list before the offer is priced.
  4. Split the customer D&C list into three parts: exceptions you take, questions you need answered, and documents you still need. The D&C list sits alongside the compliance matrix and should never contradict it.
  5. Keep internal to-dos on a separate internal sheet from the start of the tender, so nothing like 'check with QA' reaches the customer copy.
  6. Have a named engineer review and sign off the matrix and the D&C list, because your engineers own what goes out.

For the clause-by-clause method behind steps 1 to 3, see the guide on how to analyze a tender specification clause by clause.

One way to get there is software that does the first pass. OdysseyGPT's cited spec compliance review for tenders and RFQs reads the spec package and your own data-sheets and test procedures (PDF, Word, Excel and CSV). It marks each requirement complies, deviates, needs a clarification or not addressed, and quotes the page, sheet or cell behind each finding. It checks the quote against the source and flags documents to request. It then drafts an editable compliance matrix and D&C list for your engineers to review.

This approach has limits. It covers the written spec package. OdysseyGPT does not read engineering drawings such as general arrangements or P&IDs, so requirements shown only on drawings still need an engineer's eye.

Self-assessment: at which stage do your misses usually surface?

Your own recent orders show where your misses surface. Take the last few orders that had a re-test, a non-conformance or a back-charge, and work through these questions for each one.

  1. Where was the gap first found? Tender, kickoff, EPC query or FAT.
  2. Where did the requirement come from? Was it in the original issue, or in an addendum or revised MR?
  3. Was a document missing? Did the requirement depend on a document, such as an ITP, that was missing from the package and never requested?
  4. What did the offer say? Did your offer give that requirement any status, or was it silent?

Run a decline log alongside it. For each declined RFQ, record the package size, the reason, the rough order value and whether the scope fit your range. After a quarter, total the order value of well-fitting RFQs you declined for lack of reading time. Add the margin lost on rushed bids that led to back-charges or re-tests. Together these give you the real cost of limited bid-stage hours.

Then read the pattern. If most misses surface at kickoff or FAT, the gap is in bid-stage coverage, not in shop-floor quality. If most trace back to addenda, your revision review is the weak point. If most trace to missing documents, your D&C list needs a 'documents to request' section that is filled in before pricing.

Your next step: run the four questions on your last few orders with a re-test or back-charge. Then use the guide How to Analyze a Tender Specification to tighten your bid-stage review where the pattern points.

Frequently asked questions

Where is the cheapest point to find a missed requirement in a tender?

The cheapest point is at tender, in a full bid-stage review, because the gap is still a row in the compliance matrix that you can price, clarify or declare as an exception in the offer.

What status should every requirement get at tender?

Every requirement should be marked complies, deviates, needs a clarification or not addressed, with a quote and page from your own data-sheet or test procedure behind it. The 'not addressed' status is what makes a gap visible before the price is fixed.

How do addenda and revised MRs lead to back-charges?

When the bid desk answers the first issue closely and only skims the revisions, a tightened test duration or material requirement goes out unanswered. The order is placed against the revision, and the gap surfaces at FAT or on the shop floor.

Should internal notes ever appear on the customer D&C list?

No. Internal to-dos such as 'check with QA' tell the EPC the offer is unfinished, so keep them on a separate internal sheet from the start of the tender.

Does OdysseyGPT read drawings or P&IDs in the tender package?

No. OdysseyGPT does not read engineering drawings such as general arrangements or P&IDs; it checks the written spec package against your own documents and drafts the compliance matrix and D&C list for your engineers to review.