The lowest bid wins the contract. The highest change order wins the project. Project directors who have run more than one capital project have seen this pattern play out: the contractor who submitted the most aggressive number at bid time is often the same one who comes back eighteen months later with the largest claim for scope changes, schedule extensions and unforeseen conditions. EPC contractor selection built on commercial comparison alone cannot tell the difference between genuine efficiency and a bid that was priced to win rather than priced to deliver. Project directors building their selection process can book a session with iFactory AI to see how capability evidence and historical performance data get structured into the evaluation before contract award.
EPC Contractor Selection Criteria for Industrial Projects
The lowest bid wins the contract and the highest change order wins the project. Selection needs capability evidence, not just a commercial comparison.
Why Commercial Comparison Alone Fails
A bid tabulation that ranks contractors purely by submitted price answers one question: who priced lowest today. It does not answer the question that actually determines project outcome: who can execute this specific scope, on this specific site, with this specific set of long-lead equipment and interface risks, without the price growing substantially after award.
Scope gaps priced as savings
A contractor can submit a lower number by quietly excluding scope the other bidders included, commissioning spares, a piece of site logistics, a portion of the civil package. The gap doesn't show up in the bid comparison; it shows up as a change order once construction starts.
Buy-low, claim-later strategy
Some contractors bid near or below their actual cost to win the award, planning to recover margin through change orders, scope interpretation disputes and schedule claims once they are the only contractor on site and the owner's leverage has dropped.
Capability assumed, not verified
A contractor's marketing materials and a contractor's actual bench strength for your specific process technology are not the same thing. Without verification, the owner discovers the gap when the detailed engineering team turns out to be two people stretched across four projects.
Reference calls as formality
A reference check that asks "would you hire them again" and accepts a polite yes misses the actual signal. The useful question is how the relationship performed when something went wrong, not whether the relationship was pleasant when nothing did.
Financial capacity unexamined
A contractor whose backlog is near its bonding capacity, or whose working capital is stretched across several concurrent large projects, carries a financial fragility that a bid tabulation never surfaces but a capital markets or surety review would.
Contract structure mismatched to risk
Awarding a lump-sum contract for a scope with significant undefined geotechnical or brownfield conditions transfers risk the contractor will simply reclaim through claims, because no fixed price can absorb genuinely unknown conditions without someone eventually paying for the difference.
Each of these gaps is invisible in a bid tabulation sorted by price. They become visible only when the owner builds an evaluation that looks for evidence of capability and discipline, not just a number. Project directors building their evaluation framework can book a selection framework session with iFactory AI.
Evidence Versus Claims: What to Actually Verify
Every contractor's proposal makes claims about experience, capability and capacity. The selection process exists to separate the claims that are backed by verifiable evidence from the claims that are simply well-written.
The pattern across all five is the same: a claim becomes evidence only when it names something specific enough to be checked independently. A proposal that answers every question in general terms, without naming projects, people or numbers that can be verified, is not necessarily lying, but it has not yet given the owner anything to verify. iFactory AI structures reference and performance verification into a standard data request so every bidder answers the same specific questions in the same format. Teams ready to build their verification framework can contact iFactory support for a process review.
Matching Contract Structure to Risk, Not to Convenience
The contract structure selected at award time sets the incentive the contractor operates under for the life of the project. A mismatch between contract type and the project's actual risk profile is one of the most common sources of the change orders that erode the apparent savings of a low bid.
Best when scope is well-defined
Transfers cost risk to the contractor, which works well when engineering is substantially complete, site conditions are known, and scope is unlikely to change materially during execution. Applied to a project with significant unknowns, it pushes the contractor toward aggressive claims to recover margin on anything genuinely unforeseen.
Best when scope is still evolving
Keeps cost risk with the owner but removes the contractor's incentive to find savings unless fee structures are designed carefully. Appropriate for early-stage or fast-track projects where engineering and procurement happen concurrently with construction, but requires much tighter owner oversight of cost control.
Best for a defined transition point
Starts reimbursable during early engineering, then converts to a fixed or target price once scope definition reaches an agreed maturity level. This structure directly addresses the problem of locking in a fixed price before the scope is actually known well enough to price fairly.
The selection criteria should include an explicit assessment of whether each bidding contractor's proposed contract structure fits the project's actual scope maturity, not just whether the number looks attractive under that structure. A contractor proposing a lump-sum price for a brownfield project with significant undefined subsurface conditions is either absorbing real risk at a real cost, or planning to recover that cost later through claims; the evaluation should determine which. Project directors structuring their contract strategy can book a contract strategy session with iFactory AI.
Evaluate Capability, Not Just Price
iFactory AI structures contractor verification, reference checks and change-order risk assessment into one evaluation framework your team can apply consistently across every bidder.
Change Order Risk: Reading the Pattern Before Award
A contractor's change order history on past projects is one of the most predictive pieces of evidence available before award, and one of the least frequently requested in a standard bid evaluation. The pattern matters more than the total.
Owner-directed versus contractor-initiated changes
A history dominated by owner-directed scope changes reflects the owner's own scope discipline, not the contractor's performance. A history dominated by contractor-initiated claims for schedule, interpretation disputes or "differing site conditions" is a signal about how that contractor behaves once under contract.
Timing of change order filing
Change orders filed early and resolved collaboratively suggest a contractor managing scope as it genuinely evolves. Change orders filed late, in clusters, or near milestone payment dates suggest a contractor using claims as a cash flow or leverage tool rather than a genuine scope management process.
Resolution method and dispute history
A contractor whose past projects resolved change orders through documented negotiation is different from one whose past projects required formal claims processes or litigation. The second pattern predicts a more adversarial relationship on your project, regardless of how the proposal reads.
Correlation with bid aggressiveness
Comparing a contractor's historical bid-to-final-cost ratio across several past projects reveals whether their bids tend to hold or tend to grow. A consistent pattern of final costs well above bid price is a far stronger signal than any single project's explanation for why that one ran over.
None of this data appears in a standard proposal. It has to be requested explicitly as part of the evaluation, ideally from projects the owner can independently verify with the client of record rather than relying solely on the contractor's own characterization of its history. iFactory AI aggregates historical change order and bid-to-final-cost data across a contractor's verified project history to surface this pattern before award rather than after. Project directors building their change-order risk assessment can book a risk assessment session with iFactory AI.
Red Flags That Should Stop a Bid, Not Just Lower Its Score
Most selection frameworks treat every weakness as a point deduction in a weighted score. Some weaknesses are serious enough that they should function as a stop, removing the bidder from consideration regardless of how attractive the commercial number looks.
| Red flag | Why it matters | Recommended action |
|---|---|---|
| Backlog near or above bonding capacity | Financial fragility risks a contractor unable to properly staff or finance your project alongside existing commitments | Require updated bonding capacity letter before shortlisting |
| No comparable project in your process technology | Technical risk of a learning curve happening on your project rather than a prior one | Require named technology-specific subcontractor or licensor partnership |
| Declining revenue over consecutive years | May indicate broader business distress that outlasts any single project relationship | Request explanation and audited financials; escalate to finance review |
| Refusal to provide verifiable references | A contractor confident in its track record has no reason to avoid independent verification | Treat as disqualifying unless a credible confidentiality reason is documented |
| History of safety citations with willful violations | Predicts both human risk on your site and potential project delay from regulatory action | Disqualify regardless of commercial terms |
| Pattern of litigation on past change order disputes | Predicts an adversarial relationship once your project hits its own inevitable scope questions | Require detailed explanation; weight heavily against commercial advantage |
The distinction between a point deduction and a disqualifying flag should be decided before bids are received, not debated after a favorite low bidder turns out to carry one of these flags. Setting the rule in advance protects the integrity of the evaluation from the pressure to rationalize a convenient price. Teams building their red-flag criteria can book a session to define disqualifying criteria before the next bid cycle opens.
Structuring the Evaluation Process Itself
The sequence and separation of evaluation steps matters as much as the criteria themselves. A process that lets commercial price influence technical scoring, even unconsciously, tends to rationalize the lowest bid regardless of what the capability evidence actually shows.
Separate technical and commercial evaluation teams
The team scoring technical capability, safety record and reference verification should not see commercial pricing until after technical scores are finalized. This prevents price from anchoring judgment on criteria that should be assessed independently of cost.
Require a standard data submission format
Every bidder answers the same specific, verifiable questions in the same format, rather than being allowed to submit a general capability narrative. This makes claims comparable and makes gaps in a given bidder's response immediately visible.
Independently verify a sample of references
Rather than accepting the contractor's chosen references at face value, independently contact at least one client from a project the contractor did not list, when that information is available through industry or public project records.
Combine scores only after both are final
Only after technical and commercial scores are each independently finalized should they be combined into a weighted total. This preserves the integrity of the technical assessment and makes the final decision defensible if challenged later.
iFactory AI is smart manufacturing and industrial software delivered as a pre-configured NVIDIA AI server. For capital projects it structures bidder data submission, reference verification and change-order history analysis into a consistent evaluation pipeline, typically deployed within six to twelve weeks ahead of a bid cycle. Project directors ready to scope their next contractor selection can book a scoping session with the iFactory team.
Select the Contractor Who Can Actually Deliver
iFactory AI structures capability verification, change-order risk assessment and reference checks into one evaluation process. Book a session scoped to your next bid cycle.
Frequently Asked Questions
How much weight should price carry relative to capability evidence in the final decision?
There is no universal ratio, but price should never be the sole determinant once bidders have passed a capability threshold. A common approach weights technical and capability evidence collectively above commercial price, often in a 60/40 or 70/30 split, with safety and financial fragility treated as pass/fail gates before weighting even applies. Book a demo to see weighting frameworks applied to a project like yours, or contact support for a quick framework discussion.
How do we verify a contractor's change order history when it isn't in the proposal?
Request it explicitly as part of the standard data submission, including bid-to-final-cost ratios on named past projects and a breakdown of owner-directed versus contractor-initiated changes. Where possible, verify the data independently with the client of record rather than accepting the contractor's own summary at face value. Book a session to see change-order data aggregation in practice.
Should a contractor ever be disqualified purely on commercial grounds, such as bidding too low?
Yes, when a bid falls significantly below the median of qualified bidders without a clear, verifiable explanation, such as a genuine efficiency advantage tied to specific equipment or methodology. An unexplained low bid often predicts a buy-low, claim-later strategy rather than genuine savings. Book a session to build an outlier-bid review process, or contact support for guidance on your current bid tabulation.
What is the right contract structure when scope is only partially defined at award?
A convertible or target-price structure, starting reimbursable through detailed engineering and converting to a fixed price once scope reaches an agreed maturity threshold, usually fits better than forcing a lump-sum price before the scope is genuinely known. This avoids both the owner's cost exposure under pure reimbursable and the change-order risk of a premature fixed price. Book a contract strategy session to map the right structure to your project's scope maturity.
Can iFactory AI help structure the evaluation for a project already out to bid?
Yes. The platform can be deployed to structure reference verification, change-order history analysis and red-flag screening even mid-cycle, as long as there is time before the award decision to request the additional data from bidders. Earlier engagement, before the RFP issues, allows the standard data request to be built into the bid package itself. Contact support to discuss your bid timeline, or book a scoping call to see what's possible before your award date.
