Scope normalization
Do not compare cover-page totals until every offer uses the same reference bottle, accepted-output definition, revision, supply boundary and commercial responsibility.
Write one basis at the top of the comparison sheet and reject silent substitutions.
Use included, optional, excluded, buyer-supplied or open. “Standard scope” and blank cells are not decision states.
A bidder deviation should name the affected requirement, supporting document, price or schedule effect, acceptance impact, owner and resolution status.
Record buyer-side costs and unresolved responsibilities beside the quoted amount. Do not manufacture a single landed total when freight, duties or site work remain unknown.
They may use different bottles, output definitions, equipment boundaries, component standards, FAT scope, trade terms and service responsibilities. Normalize those fields before comparing price.
Common omissions include bottle and cap handling, product-water interfaces, change parts, spares, FAT materials and duration, documents, export packing, installation, travel and buyer-side work. Confirm the actual offer rather than assuming an omission.
Only when the project actually requires them. Keep required additions, discretionary options and unresolved items separate so the comparison remains auditable.
Quotation normalization
The comparison becomes useful when the buyer can trace why totals differ. Keep the common requirement, bidder response, supporting document, price or schedule consequence, acceptance effect, owner and status in the same row.
| Field | What to record | Why it changes the decision |
|---|---|---|
| Document control | RFQ revision, quote revision, date and valid replacement documents | Prevents comparing superseded scopes |
| Performance basis | Bottle/cap revision, setup speed, rated speed and accepted good output | Exposes non-equivalent output claims |
| Scope state | Included, optional, excluded, buyer-side or open for every interface | Reveals the real purchase boundary |
| Deviation impact | Technical reason plus price, schedule and acceptance consequence | Makes trade-offs explicit |
| Responsibility total | Equipment, required options, services and known buyer-side work | Avoids treating subtotal as project cost |
Guides
Next procurement decision
Compare configuration assumptions, interfaces, FAT, documents, delivery and service before ranking price.