Chapter 03ProcurementArticle 3.2
Technical Evaluation Decision Chain
A recommendation is stronger when every decision can be traced from requirement to bidder evidence, clarification and final outcome.
- ProblemA recommendation that cannot be traced back to evidence.
- SignalsRequirement, offer, quotation status, compliance, certificates, clarifications.
- DecisionAccept technically, clarify, reject or hold.
- ControlEvery outcome linked to a reason and a document.
01Business problem
A technical evaluation decides whether supplier offers meet the requirement. It sounds straightforward. In practice offers arrive incomplete, quote an equivalent instead of the requested part, leave lines unquoted, promise certificates later, or answer a clarification with another question.
If the evaluation is reduced to a list of compliant and non-compliant bidders, the reasoning disappears. Months later, when a delivered item causes a problem or a decision is questioned, nobody can show why an offer was accepted.
02Core concept
A technical evaluation is a decision chain: each step is checked against the requirement, and each outcome rests on evidence.
A few distinctions do most of the work:
- Quoted, partially quoted, not quoted: a missing line is a different outcome from a non-compliant line, and neither is compliant.
- Requested item or equivalent: an equivalent is acceptable only when it is shown to be equivalent.
- Declared or evidenced: a supplier's statement of compliance is not evidence of compliance.
- Open or closed clarification: an open clarification is a decision that has not been made yet.
The output is a technical recommendation. The commercial evaluation and the award decision belong to procurement.
03Decision rule
Accept an offer technically only when it is quoted in full, compliant with the requirement, supported by the required evidence and free of open clarifications.
Technically compliant does not automatically mean the best lifecycle decision. Where compliant offers differ in reliability, support or compatibility, the recommendation should say so.
04Signals and inputs
- Technical requirement
- What is required, including documentation.
- Quotation status
- Quoted, partially quoted or not quoted, per line.
- Offered item
- The requested part or a proposed equivalent.
- Equivalence evidence
- Datasheets, OEM statements, test reports.
- Certificates
- Required documents and their status.
- Clarification status
- Questions open or closed.
- Compliance concerns
- Separate controls such as sanctions screening, where they apply.
05Model
- 01RequirementSpecification, quantity, documentation and equipment reference.
- 02Supplier offerItem, manufacturer and part number per line.
- 03Quoted?Quoted, partially quoted or not quoted.
- 04ComplianceSpecification, compatibility and equivalence.
- 05Certificates and evidenceRequired documents present, valid and consistent.
- 06ClarificationQuestions raised, answers received and closed.
- 07Risk and judgementDifferences that compliance alone does not show.
- 08Technical recommendationAccept, clarify, reject or hold, with reasons.
06Worked example
Illustrative example
Two offers for one spare
The requirement is a specific spare with a material certificate as required documentation.
- Bidder A offers the requested part number and provides the certificate.
- Bidder B offers an alternative from another manufacturer, declares it fully compliant, and states that the certificate will follow with delivery.
Bidder A can be accepted technically. Bidder B cannot be, yet: the equivalence needs evidence, and the certificate is a required element of the offer, not a delivery formality. The professional outcome for B is a clarification with a deadline. If the certificate and the equivalence evidence do not come, B is rejected technically with that reason recorded.
The technical recommendation says nothing about price or award. It tells procurement which offers it can act on, and why.
07Professional judgement
The purpose of technical evaluation is not only to select a bidder. It is to preserve the reasoning.
The difficult cases are rarely clear rejections. They are offers that are probably acceptable: an equivalent that looks right, a certificate promised later, a deviation described as minor. The temptation is to accept them to keep the tender moving. The professional choice is to make the open point explicit and close it, or to record why it was accepted.
Price does not belong in the technical judgement. A cheaper offer with an evidence gap is still an offer with an evidence gap.
08Failure modes
Not quoted treated as compliant
A missing line is discovered at delivery.
ControlRecord the quotation status per line.
Equivalent accepted without evidence
An item that does not perform is bought.
ControlRequire datasheets or OEM statements for equivalents.
Certificate checked too late
Material arrives that cannot be used.
ControlCheck certificate requirements during evaluation.
Clarification left open
The recommendation rests on an unanswered question.
ControlClose or escalate clarifications before recommending.
Rejection without reason
The decision cannot be defended or reviewed.
ControlRecord the reason and the evidence for each rejection.
Price drives the technical decision
Technical gaps are overlooked for a lower price.
ControlKeep the technical evaluation separate from the commercial one.
Unsupported assumption
A reviewer's guess becomes part of the record.
ControlLink every outcome to a document or a recorded clarification.
09Field note
10Practical checklist
- The requirement, including documentation, is clear before offers are opened.
- Quotation status is recorded per line: quoted, partial or not quoted.
- Equivalents are supported by evidence, not by declaration.
- Certificate requirements are checked now, not at delivery.
- All clarifications are closed or escalated.
- Each acceptance and rejection has a reason and a document.
- The recommendation is technical; commercial evaluation and award stay with procurement.
11Try the decision logic
Decision Lab
Technical evaluation
Bidder B offers an alternative. Can it be accepted technically?
Try the decision logic. There is no score: choose a decision and compare it with a professional review.
01Situation
Illustrative scenario
The requirement is a specific spare with a material certificate as required documentation. Bidder A offers the requested part with the certificate. Bidder B offers an alternative from another manufacturer and declares it fully compliant. Inspect the evidence for Bidder B and decide its technical status.
- Requirement
- Specified spare; material certificate required
- Bidder A
- Requested part number; certificate provided
- Bidder B
- Alternative manufacturer; declared fully compliant
02Signals
- Bidder B quotationLine quoted in full · Partly quoted · Not quoted
- Equivalence evidenceDatasheet comparison and OEM statement · Datasheet only, one parameter differs · Declaration only
- Material certificateProvided with the offer · Promised with delivery · Not offered
- ClarificationNot sent · Sent, no answer yet · Sent and answered
- Supplier statementDeclares full compliance · Declares a deviation
03Decision
- Accept technically
- Clarify with the bidder
- Reject technically
- Hold for an engineering opinion
04Professional review
The interactive review needs JavaScript. Without it, the complete logic is in the rules below.
How the review is reached
The rules are checked from the top; the first one that matches the signals gives the professional position. Values in square brackets are filled in with the calculated numbers.
IfBidder B quotation: Not quoted
Professional positionReject technically
Any other decision: not supported by the signals
The line is not quoted. A missing quotation is not a compliant offer and cannot be accepted, whatever the bidder states elsewhere.
IfBidder B quotation: Partly quoted
Professional positionClarify with the bidder
ConditionalReject technically
Any other decision: not supported by the signals
Only part of the requirement is quoted. The quoted part can be evaluated, but the offer is not complete.
IfMaterial certificate: Not offered · Clarification: Sent and answered
Professional positionReject technically
Any other decision: not supported by the signals
The certificate is a required element and the bidder has confirmed that it will not be provided. The offer does not meet the requirement, whatever the declaration says.
IfEquivalence evidence: Declaration only · Clarification: Sent and answered
Professional positionReject technically
ConditionalHold for an engineering opinion
Any other decision: not supported by the signals
After clarification, equivalence still rests on a declaration only. An alternative is acceptable only when it is shown to be equivalent.
IfClarification: Sent, no answer yet
Professional positionClarify with the bidder
ConditionalHold for an engineering opinion
Any other decision: insufficient information
A clarification is open. The recommendation cannot be made until it is answered or escalated.
IfMaterial certificate: Not offered
Professional positionClarify with the bidder
ConditionalReject technically
Any other decision: not supported by the signals
The required certificate is not offered. The declaration of full compliance does not override a missing required document.
IfMaterial certificate: Promised with delivery · Clarification: Sent and answered
Professional positionHold for an engineering opinion
ConditionalReject technically
Any other decision: not supported by the signals
Even after clarification, the bidder offers the certificate only with delivery. Whether that is acceptable as a delivery condition is a decision for the requirement owner and QA/QC, recorded before any recommendation.
IfMaterial certificate: Promised with delivery
Professional positionClarify with the bidder
ConditionalHold for an engineering opinion
Any other decision: not supported by the signals
The certificate is promised with delivery. It is a required element of the offer, not a delivery formality: the bidder should confirm it now, with its type and content.
IfEquivalence evidence: Declaration only
Professional positionClarify with the bidder
ConditionalReject technically
Any other decision: not supported by the signals
Equivalence rests on the bidder's declaration only. An alternative is acceptable only when it is shown to be equivalent.
IfEquivalence evidence: Datasheet only, one parameter differs
Professional positionHold for an engineering opinion
ConditionalClarify with the bidder
Any other decision: escalation required
One technical parameter differs from the requested part. Whether that difference matters in this application is an engineering question: the evaluation should ask it, not answer it.
IfSupplier statement: Declares a deviation
Professional positionHold for an engineering opinion
ConditionalClarify with the bidder
Any other decision: escalation required
The bidder declares a deviation. It has to be assessed against the requirement by the engineering authority before the offer can be accepted.
IfAny other combination
Professional positionAccept technically
Any other decision: not supported by the signals
The line is quoted in full, equivalence is evidenced, the required certificate is provided and nothing is open. The offer can be accepted technically. Price and award remain with procurement.
Neutral illustrative scenario: no real tender, supplier, price or award. The lab covers the technical evaluation only; commercial evaluation and award belong to procurement.
12Connected intelligence
13Evidence and basis
Bidder A and Bidder B are neutral; no real tender, supplier or award is described. Basis: technical evaluations prepared as Spare Parts Engineer and reviewed as Spare Parts Superintendent (CV), and training in certification of equipment and materials. The chain is a framework developed from that work, not a company procedure.
Continue reading
Total Cost of Ownership
The cheapest quotation is not always the lowest-cost decision over the full lifecycle.
Procurement · Lifecycle cost
Formula4 min read