Cooling Water Chemical RFQ Checklist: COA, TDS, SDS and Trial Acceptance Criteria
TL;DR A cooling-water chemical RFQ should ask for a decision-ready evidence package, not just a price and a product name. Define the system and water envelope, exact product role, active-basis/specification fields, current TDS and SDS, representative and shipment-specific COA expectations, storage/handling and compatibility questions, and a trial/acceptance/change-control plan. Documents establish what must be checked; they do not create a guaranteed corrosion, scale or microbiological result for a different site.
What belongs in a cooling-water chemical RFQ?
This guide is about procurement evidence after a team knows the buying task—not a single-phosphonate comparison. Use it after the HEDP vs PBTC selection guide or a similar engineering screen, and keep it distinct from the site’s water-analysis program selection. An RFQ should let procurement, operations and engineering compare like-for-like candidates, understand safety and handling, and agree what evidence would support acceptance or a controlled change. It should not ask a supplier to promise outcomes that the site has not bounded.
| Document or record | Primary role in the RFQ | Minimum cross-check | What it does not establish |
|---|---|---|---|
| Technical Data Sheet (TDS) | Product-level technical identity, intended use and stated properties/specification context. | Revision date, exact grade/form, units and consistency with the requested specification. | That a future shipment lot met the stated range or that the program will work at the site. |
| Certificate of Analysis (COA) | Lot-specific quality evidence for agreed parameters and methods. | Product/grade, lot identity, production/test date where supplied, units, method and result versus agreed criterion. | Safety handling, compatibility, universal performance or a substitute for site acceptance. |
| Safety Data Sheet (SDS) | Hazard communication, handling, storage, exposure, transport and emergency information. | Exact product identity/revision; Section 1, hazard, composition, handling/storage and transport relevance to destination. | Product quality, active assay or a performance claim. |
| Trial and acceptance record | Defines what site evidence will be compared before a release decision. | Baseline, method, sample points, operating window, roles, hold points and change triggers. | A pre-set supplier guarantee independent of site water, operations and equipment. |
Why COA, TDS and SDS must stay separate
OSHA’s Hazard Communication Standard requires a safety data sheet for each hazardous chemical produced or imported and specifies the standardized SDS headings, including identification, hazards, composition, handling/storage, physical/chemical properties and transport information. That makes the SDS a safety and handling document, not a lot assay. Conversely, a COA should be treated in the RFQ as evidence against the buyer’s agreed lot criteria: request the fields and test methods needed for the particular chemical and contract. The TDS is a product-level technical reference. If the three documents identify different grades, revisions, forms or units, stop and clarify before trial or receipt.
RFQ acceptance matrix: define evidence before the quote is awarded
| RFQ field | Buyer should provide or request | Acceptance boundary |
|---|---|---|
| System and water context | Open/closed boundary, volume/flow where relevant, metallurgy, makeup and recirculating analysis, cycles basis, temperature, deposit/corrosion history and biocide/oxidant context. | Use current, dated site data; a supplier cannot validate an undisclosed system boundary. |
| Product identity and active basis | Required role, exact grade/form, active-basis convention, agreed test parameters, units and accepted analytical methods. | Do not infer active content, formulation or equivalence from a product-family name or an old web page. |
| Documents | Current TDS and SDS; representative COA format before award; lot COA tied to each shipment as contractually required; applicable destination/regulatory declarations only when specified. | Verify document revision and lot/grade identity. Do not request or claim certificates that have not been verified. |
| Delivery, compatibility and storage | Delivery form, container compatibility, handling/storage constraints, shelf-life statement if supplied, transport and receiving requirements. | Confirm against the current SDS/TDS and the site’s storage/feed equipment; no generic compatibility promise. |
| Trial and technical acceptance | Baseline, operating envelope, duration, sample points, methods, responsibilities, records, non-conformance route and re-test/stop conditions. | Acceptance is conditional on agreed methods and actual system data—not a copied lab dose or universal KPI. |
| Change control | Written notice/review for grade, active basis, raw-material/process site, delivery form, document revision or test-method change that could affect the agreed scope. | Site-specific contract language and risk review are required; this is a procurement control, not legal advice. |
Trial acceptance and change-control workflow
- Write the buyer task first. State whether the candidate addresses mineral scale, suspended solids/dispersancy, corrosion context or microbial control. Link it to actual equipment and water constraints rather than a generic “cooling chemical” label.
- Set document identity controls. Record product name, grade, revision, delivery form and request date. Require a discrepancy route if the sample, TDS, SDS and COA do not describe the same requested item.
- Separate a representative COA from a shipment COA. A format example helps set expectations before award; an actual shipment COA must be tied to the received lot and the agreed fields. Whether and how incoming testing is needed depends on risk and contract.
- Bound the trial. Define baseline data, analytical methods, operating range, sample locations, responsible reviewers and decision timing. Avoid turning a benchtop or supplier result into a permanent site setpoint.
- Document change triggers. Review a change in product form, active basis, stated specification, test method, SDS/TDS revision, packaging or supply source before assuming prior acceptance still applies.
Cooling-water RFQ checklist to attach to an inquiry
- System diagram and open/closed boundary; water volume/flow, cooling duty, materials and equipment limitations that are known.
- Dated makeup and recirculating-water analyses with sample point, method and units; cycles/blowdown and oxidant/biocide context where relevant.
- Deposit, corrosion, filtration, cleaning and maintenance history—clearly labelled as observations, not a diagnosis.
- Candidate product role and required documentation: current TDS, SDS, representative COA format and lot-specific COA expectation.
- Agreed active-basis/specification fields, units, methods, delivery form, storage/feed compatibility questions and destination requirements.
- Trial baseline, data method, review window, acceptance evidence, hold/retest condition and a written change-control path.
Use the water-treatment chemicals category as the commercial starting point, then connect the actual system to the cooling-water treatment application, deposit-investigation guide and generic supplier-quote data checklist. The VCYCLETECH video library is visual process context only, not batch or performance proof. Send the RFQ matrix for a documented technical review; specifications, documents and any trial scope remain subject to the actual product and site context.
Frequently asked questions
What is the difference between a COA, TDS and SDS for cooling-water chemicals?
A TDS provides product-level technical context; a COA is lot-specific evidence against agreed quality parameters; and an SDS communicates hazards, handling, storage and related safety information. They should identify the same requested grade and form but do not replace one another.
Should a cooling-water RFQ require a COA for every shipment?
The RFQ should state the contract expectation for lot-specific COA evidence and which fields/methods must be present. The appropriate incoming-verification level depends on the chemical, application risk, contract and site quality system.
Can a technical data sheet set a cooling-tower dose or guarantee performance?
No. A TDS may provide technical context, but a site setting or outcome depends on water chemistry, metallurgy, operating conditions, formulation, feed arrangement and agreed verification. Define a bounded trial instead.
What should trigger change control after a cooling-water chemical is accepted?
Review material changes that could affect the agreed scope, such as grade or delivery-form change, active-basis/specification change, test-method change, relevant document revision, packaging change or supply-source change. Set the exact triggers in the purchase and quality process.
What data should accompany a cooling-water chemical trial?
Use a dated baseline for water and operating conditions, material/equipment context, current treatment history, document identity, defined sample points and methods, observation records, trial boundaries and pre-agreed review/stop/retest conditions.
Author, review and evidence boundary
VCYCLETECH Technical Team prepares this engineering and procurement material from public technical guidance, industry sources and document-process context. It does not certify a facility, prescribe an analysis or dose, verify a product, provide legal advice or guarantee deposit control, compatibility or system performance. Final decisions require representative site data, current product documents and qualified site-specific review.
Sources
- OSHA Hazard Communication Standard: SDS and hazard-communication requirements
- OSHA Safety Data Sheet QuickCard: standardized SDS sections
- Nghi Son Refinery procurement screening: TDS, SDS and sample-COA evidence context
- Cooling Technology Institute 2026 journal: evolving cooling-water treatment and inspection context
