Why should the supplier response identify an event as well as a duration?
The warranty line should retain the supplier's actual wording and document reference. Delivery, shipment, purchase, acceptance and startup are different events. Do not substitute one for another while levelling offers, or assume that a delayed project automatically extends coverage.
FAR 52.246-17 is a US federal procurement example that requires a specified warranty period after delivery or a specified terminating event. It is not a universal warranty for private electrical equipment. The useful lesson for this original RFQ worksheet is to obtain an explicit time and event basis.
RFQ Templates is independent and is not affiliated with the US General Services Administration. This guide is not legal advice. The actual offer and contract require the responsible procurement and legal review.
Sources: US General Services Administration: FAR 52.246-17, Warranty of Supplies of a Noncomplex Nature
Which warranty fields should suppliers return?
Keep the same requested fields for all offers and show any differences. Do not mark an unanswered field included. If a supplier offers revised terms, retain both the original and revised responses with dates.
| Response field | Supplier evidence | Comparison question |
|---|---|---|
| Covered equipment | Selected model and supplied components | Does the scope match the RFQ? |
| Start milestone | Actual contractual event and definition | Which record establishes that event? |
| Duration and outer limit | Actual period and any separate cap | Do both constraints apply? |
| Coverage | Parts, labor, travel or other stated inclusions | What remains excluded? |
| Storage and startup | Actual conditions and required evidence | Does the planned programme meet them? |
| Notice or claim route | Supplier's stated process and recipient | How are questions escalated? |
| Confirmed variation | Accepted change reference if applicable | Has the requested change actually been agreed? |
How can the same stated duration give different comparison results?
Illustrative example. Two fictional offers both state 90 days. Offer A starts at an explicitly defined delivery event, called day 0 in the example. Offer B starts at the explicitly defined startup event, assumed to be day 30. No other outer limit or condition is assumed for this arithmetic example.
On day 30, A has 60 days of the stated interval left and B starts its 90-day interval. Those results follow the synthetic event assumptions; they do not establish any real manufacturer coverage, entitlement or recommended warranty duration.
If B has an additional outer limit, record and assess it separately rather than use the simplified example. The buyer should ask both suppliers for a response against the same approved programme assumptions before concluding the offers are comparable.
What should remain a clarification rather than a promise?
If delivery or startup timing is provisional, show that status in the comparison. Request the supplier's actual storage requirements and any effect of programme changes. Do not invent an extension, storage fee or accepted commissioning date.
Keep requested changes separate from agreed terms. A supplier's acknowledgment of an RFQ question is not necessarily agreement to a revised warranty. Link the comparison to the final authorized response and retain unresolved commercial issues for decision.
Common questions
What else should the bid team know?
Does a duration establish the start date?
No. Obtain the actual start event and its definition.
Does delayed startup automatically extend coverage?
Do not assume it. Review the actual terms and confirmed changes.
Does the federal example bind every private supplier?
No. It illustrates why an explicit period and event basis matters.
Primary sources
- FAR 52.246-17, Warranty of Supplies of a Noncomplex NatureUS General Services Administration