The warranty documentation in an airport fixture procurement package needs to do three things: state the coverage period and scope in writing tied to the specific line item, map to whatever FAR or DFARS flowdown clauses govern the contract, and produce a paper trail that survives an audit years after the faucets are installed. A warranty line that just says “manufacturer’s standard warranty applies” is not documentation. It is a placeholder that will fail review.
Why Warranty Terms Belong in the Spec Package, Not Just the Purchase Order
Procurement teams sometimes treat warranty terms as a commercial afterthought, something the vendor attaches to the invoice. On airport contracts, especially those touching FAA-funded terminal work or DoD installations, the warranty clause is part of the technical package. It has to be reviewable alongside flow rate specs, ADA reach requirements, and finish callouts because the warranty period determines when replacement parts become a contract remedy versus a maintenance budget line.
If the spec package separates “what we bought” from “what happens when it fails,” the audit trail breaks. Reviewers need to see the warranty clause referenced in the same document that specifies the fixture, not cross-referenced to a vendor catalog page that may not exist five years later.
Standard Fixture Warranty Structures
Commercial faucet warranties generally split into two tiers, and the spec package should state which tier applies to which components rather than citing a single blanket term.
- Full-coverage period: covers the complete assembly, including cartridge, body, and finish, against defects in material and workmanship for a defined term from the date of installation acceptance.
- Parts-only period: after the full-coverage term expires, some manufacturers continue to warrant specific components, most commonly the cartridge or valve body, while finish and cosmetic defects are excluded.
Procurement documentation should record both periods separately, with start dates, because a facilities team troubleshooting a leaking unit three years post-installation needs to know immediately whether the finish is covered or only the internal mechanism. This distinction also matters when specifying replacement parts for high-use restroom and lavatory fixtures, where cartridge failure is the most common service call. If the spec is silent on which tier applies to which failure mode, the vendor will default to the narrower reading.
Mapping Warranty Clauses to FAR 46.706
FAR 46.706 governs warranties on supplies and services acquired by federal agencies, and it requires the contracting officer to determine that a warranty is in the government’s interest before including one, then to document the rationale. For airport procurement teams working under federally funded improvement programs, this means the warranty clause in the fixture spec cannot simply mirror the manufacturer’s boilerplate. It has to align with the government’s warranty determination on file for that acquisition, including the specified remedy period and the conditions under which the government can require correction or replacement at no additional cost.
Practically, this means the procurement file should contain a short memo or determination that ties the fixture’s stated warranty period to the FAR 46.706 requirement, rather than assuming the manufacturer’s standard term automatically satisfies the regulation. If the contracting officer’s determination specifies a minimum warranty period longer than what the manufacturer offers as standard, that gap needs to be resolved and documented before award, not discovered during an audit.
DFARS 252.246-7001 for Defense-Funded Terminal Work
Airport projects funded in whole or part through defense channels, joint-use terminals near military installations being the most common case, trigger DFARS 252.246-7001, which addresses warranty of data and requires specific clause language when warranties are included in the contract. This clause is more prescriptive than the general FAR provision. It requires the warranty terms to be spelled out in the contract itself, including the warranted supplies, the warranty period, and the remedies available.
If your procurement package touches a DFARS-flowdown contract, the fixture-level warranty documentation needs to reference the specific clause number and confirm that the vendor’s warranty terms have been incorporated into the contract text, not left as an attachment. Reviewers checking DFARS compliance will look for the clause citation next to the fixture warranty term, not buried in a separate vendor quote.
Certificate of Conformance as Warranty Proof
A certificate of conformance (CoC) is the document that ties a specific delivered unit to the specification it was ordered against, and it functions as the evidentiary backbone of the warranty claim. Without a CoC on file, a warranty dispute becomes a matter of the vendor’s word against the government’s, because there is no document establishing that the unit delivered actually matched the spec that carried the warranty terms.
The CoC package should include the fixture model, lot or batch identifier where applicable, the applicable spec reference (flow rate, ADA compliance, material grade), and a signed statement from the manufacturer or authorized distributor that the delivered units conform. For fixtures like shower faucet sets installed in crew rest facilities or employee locker rooms at larger terminals, the CoC should also note valve type and cartridge specification, since these are the components most likely to trigger a warranty claim and the ones most often missing from an incomplete CoC.
Documenting Warranty Start Dates After Handoff
Warranty periods almost never start at delivery. They start at installation acceptance, substantial completion, or beneficial occupancy, depending on how the contract defines handoff. This distinction matters enormously on airport projects where fixtures might sit in a staging warehouse for months before installation, or where a terminal wing opens in phases.
The procurement file needs a signed acceptance document that states the exact date the warranty clock starts, tied to the specific fixtures or fixture group covered. If forty faucets are installed across three phases over six months, there should be three warranty start dates on file, not one blanket date applied retroactively. Facilities teams filing a warranty claim two years later need to know precisely which start date applies to which unit, and that information has to live in the procurement record, not in institutional memory.
Retaining Warranty Records for Audit Readiness
Audit windows on federally funded airport projects can extend well beyond the warranty period itself. The documentation package should be retained for the full record-retention period specified in the contract’s audit clause, which is typically longer than the warranty term, and organized so that an auditor can trace a single fixture from spec sheet to purchase order to CoC to installation acceptance to any warranty claim filed against it.
A practical retention checklist for the warranty portion of the file includes the original spec sheet with warranty terms stated, the FAR 46.706 determination memo (or DFARS 252.246-7001 clause reference where applicable), the signed CoC, the installation acceptance document with warranty start date, and copies of any warranty claims filed along with the vendor’s response and resolution date. Missing any one of these breaks the chain and turns a routine audit into a longer conversation with the contracting officer.
Before closing out a fixture procurement package, confirm that the warranty clause is stated in the spec document itself, that it references the correct FAR or DFARS provision for the funding source, that a CoC is on file for the delivered units, and that installation acceptance documents show explicit warranty start dates. If any of these four items is missing, resolve it before the file is archived, not after a warranty dispute forces someone to go looking for it.