Application Data Sheet Template for Chemical Product Selection
Summary
An application data sheet for a chemical product recommendation needs 6 sections: request, current product, requirements by priority, success criteria, operating window, open items. A supplier's technical service engineer or the customer's process engineer fills it in before candidates are compared, so that must-haves rule products out and preferences only rank the products left.
What is a chemical application data sheet for, and who fills it in?
A chemical application data sheet is a fill-in form that records what a customer's application needs from a chemical product, so that a recommendation rests on stated requirements rather than on the product used last time. It is not a safety data sheet: a safety data sheet describes a product's hazards, while the application data sheet describes the process the product has to work in.
Quality systems ask for customer requirements to be determined and controlled. ISO 9001:2026 is the sixth edition of the quality management standard, published on 16 September 2026, and ISO's summary of its operation requirements reads: "The processes necessary to meet customer requirements and increase customer satisfaction must be planned, implemented and controlled" (ISO 9001:2026). A filled sheet is one way to show what those customer requirements were at the time of the recommendation.
Several people on the customer side fill in different parts. The table below shows who usually holds each section; the roles are illustrative and vary by site.
Section | Usually filled in by (illustrative) |
|---|---|
1. Request | Buyer or project owner |
2. Current product | Operations, with purchasing for usage |
3. Requirements by priority | Operations, quality, purchasing, engineering, EHS |
4. Success criteria | Quality or laboratory |
5. Operating window | Process engineering and maintenance |
6. Limitations and open items | The supplier engineer, with the owner of each answer |
The key row is section 3: each requirement names the role that stated it, because two roles often give different values for the same item. The editable Word template is at the end of this page.
Which sections and fields does a chemical application data sheet have?
A chemical application data sheet has six sections in a fixed order, from the request to the open items, and each field carries its unit and basis so that values from different people can be compared. The table below previews every section and decides which customer answers are must-haves that rule a candidate out and which only rank the candidates left; example values are illustrative.
Section or field | What goes in it (units) | Example value (illustrative) |
|---|---|---|
1. Request type | First selection, re-check after a change, replacement of a discontinued product, or comparison of named candidates | Replacement of a discontinued product |
1. Request as worded | The customer's words, date, account and use | "Need a drop-in for our cooling loop inhibitor" |
2. Current product | Product, dose with basis (mg/L as delivered or as active), usage (kg per month) | Product X, 150 mg/L as delivered, 220 kg per month |
2. Baseline performance | Measured value, unit, method and date | Corrosion rate 0.05 mm/y, coupon, 2026-08 |
3. Requirements | Each requirement tagged mandatory, preferred or welcome, the stating role and the function it protects, the source document and date | Mandatory: no nitrite, wastewater permit (EHS) |
4. Success criteria | Criterion, threshold, unit, direction, method, sampling point, detection limit | Copper below 0.1 mg/L at return line, ICP, limit 0.005 mg/L |
5. Operating window | Range for normal operation and for start-up, shutdown, cleaning, seasonal swing and storage (unit per condition) | 25 to 40 °C normal; 5 °C winter shutdown |
5. Coexisting chemicals and wetted materials | Other products in the system, cleaning agents, metals, elastomers, dosing point | Biocide dosed weekly; carbon steel, copper, EPDM |
6. Limitations and open items | What is unknown, which candidate judgment it changes, whether it stops a candidate or only moves a score, who answers, by date | Permit limit for total organic carbon, stops a candidate, EHS |
The key row is section 3: a mandatory requirement removes every candidate that fails it, while a preferred or welcome one only changes the order of the candidates that pass.
The order of the sections follows the order of the decision. The request type says which sections need a baseline, the current product gives that baseline, the requirements and the operating window screen the candidates, and the success criteria say how the survivors will be judged. A field that cannot be filled in at the visit stays on the sheet and moves to section 6 with the name of the person who will answer it.
Which request types does an application data sheet need to tell apart?
An application data sheet needs to tell apart four request types: a first selection, a re-check after a condition changed, a replacement of a discontinued product, and a comparison of candidates the customer has already named. The type decides which sections carry the weight, so it goes at the top of the sheet before any requirement is written.
A first selection has no baseline product, so the requirements and the operating window carry the whole decision, and the success criteria have to be set from the customer's specification or permit rather than from current performance. A re-check after a change, such as a new raw material, a higher throughput or a new wastewater permit, needs the condition that changed with its old and new value, because that change is the reason the current product is in question.
A replacement of a discontinued product needs the strongest baseline: the current product's dose, usage and measured performance with dates, since the customer will judge the replacement against them. A comparison of named candidates narrows the population at the start; record who named them and why, because a candidate named by purchasing for price and one named by operations for performance answer different questions.
Write the request in the customer's own words next to the type. A request worded as "drop-in" often hides a requirement, such as no change to the dosing equipment or to the permit, and the sheet should turn that hidden requirement into a written one in section 3.
What goes in the current product section of a chemical application data sheet?
The current product section of a chemical application data sheet records the product in use, its dose with a stated basis, its usage over time and its measured performance with dates. Together these form the baseline a recommended product is compared against, and a replacement or re-check request without them cannot be judged.
State the dose basis every time. A dose in mg/L as delivered and a dose in mg/L as active ingredient differ by the product's active content, and a dose per batch differs from a dose per throughput. Write the basis next to the number, and convert both the current and the candidate product to the same basis before they are compared.
Usage comes from records, not memory. Take the months with a purchase or consumption record and the total over that period, in kg or L; where units differ between records, give the record count instead. A usage figure converted from a free-text note is marked estimated.
Baseline performance needs a value, a unit, a method and a date. A corrosion rate, a residual concentration, a cycle count or a defect rate written without its date cannot show whether performance was stable when the request came in. Attach the product's safety data sheet and technical data sheet, and note their revision dates, since a later revision may change the composition or the recommended dose range.
How do you separate must-have requirements from preferences on an application data sheet?
Separate must-have requirements from preferences on an application data sheet by asking, for each requirement, whether a product that fails it would be rejected regardless of its other results; if yes, it is mandatory, and if it would only lose points, it is preferred or welcome. Only a condition that changes the outcome belongs in the mandatory group.
Record the role that stated each requirement, among operations, quality, purchasing, engineering and EHS, and the function it protects. A mandatory specification such as "no phosphate" protects something: a discharge permit, a downstream process or a product approval. Writing the function down exposes a mandatory item that no one can explain. STLE's best practices column gives the same advice for metalworking fluid bans: when a plant asks to ban boron, it calls this "a good opportunity to contact the customer and ask about his concerns" (STLE TLT, 2009).
When two roles give different values for the same requirement, keep both values with their roles rather than averaging them, and compare them on one stated basis, such as weight or volume, as delivered or as active. The difference is itself an open item for section 6.
Requirements engineering treats this record as a discipline of its own. ISO/IEC/IEEE 29148:2018 specifies the processes that result in requirements for systems and software products, including services, and the information items those processes produce (ISO/IEC/IEEE 29148:2018). Its ISO stage is "to be revised" as of 2026-10-23 (ISO/IEC/IEEE 29148:2018).
Which success criteria and test methods belong on an application data sheet?
The success criteria that belong on an application data sheet are the ones the customer will use to accept or reject the product, each written as the customer's document words it, with a threshold, a unit, a direction, a test method, a sampling point and the method's detection limit. A criterion missing any of these cannot be judged after a trial.
Take limit values from the customer's specification, contract or permit, and write where each came from. A criterion such as "copper below 0.1 mg/L at the return line" names the direction, the unit and the sampling point in one line (illustrative). If the customer gives no limit, write "limit unconfirmed" rather than proposing one, and move the item to section 6.
Record the method's detection limit next to the threshold. In US wastewater methods, the method detection limit "is defined as the minimum measured concentration of a substance that can be reported with 99% confidence that the measured concentration is distinguishable from method blank results" (US EPA, 40 CFR Part 136, Appendix B, Revision 2, 2017). A threshold close to that limit leaves little room to tell a pass from a fail, so ask the laboratory about a more sensitive method before the criterion is agreed.
Choose methods that match the real process. STLE advises that laboratory screening tests relate to the actual operation, and warns that an ASTM test method developed for one application may give misleading results in an unrelated one (STLE TLT, 2009). Mark each criterion decidable or not yet decidable.
Which operating extremes should an application data sheet record besides normal conditions?
An application data sheet should record start-up, shutdown, cleaning, seasonal swing and storage conditions besides normal operation, as a numeric range for each condition that can decide whether a product works. A product chosen for the normal range can fail at a cleaning cycle or shutdown no one wrote down.
Write each condition with its unit and the phase it belongs to, such as temperature in °C during normal running and during a cleaning cycle, or pH during normal dosing and during a cleaning cycle. A value with no phase evidence is written as "phase unknown". Name the dosing point and the basis for it, since a product dosed before a heat exchanger meets a different temperature from one dosed after it.
Coexisting chemicals and wetted materials belong in the same section. Under EU REACH, section 10.5 of a safety data sheet lists incompatible materials: substances "such as water, air, acids, bases, oxidising agents, with which the substance or mixture could react to produce a hazardous situation" (ECHA, Guidance on the compilation of safety data sheets, Version 4.0, 2020). The same guidance says that in determining incompatibility, the substances, containers and contaminants the product might be exposed to during transportation, storage and use shall be considered (ECHA, 2020). In the US, the safety data sheet's section 10 includes conditions to avoid and incompatible materials (29 CFR 1910.1200, Appendix D). List every other product in the system, every cleaning agent and every material the product touches.
Chemical application data sheet filled in (illustrative)
A filled chemical application data sheet for the replacement of a discontinued corrosion inhibitor in a closed cooling loop shows how answers become mandatory requirements, preferences and success criteria. Every product, value, role and limit in this example is illustrative and comes from no real site. The table below decides which answers remove a candidate product in this example (illustrative).
Answer (illustrative) | Priority | Stated by and function |
|---|---|---|
Copper and carbon steel in the loop, EPDM gaskets | Mandatory | Maintenance; protects the heat exchanger and seals |
No nitrite in the product | Mandatory | EHS; the wastewater permit excludes it |
Same dosing pump and dose range | Preferred | Operations; avoids new equipment |
Single drum size for all sites | Welcome | Purchasing; simplifies stock |
Copper below 0.1 mg/L at the return line, ICP, detection limit 0.005 mg/L | Success criterion | Quality; customer specification attached |
Loop drops to 5 °C at the winter shutdown | Operating extreme | Process engineering; product must stay stable |
The key row is the nitrite ban: because EHS stated it and the permit is attached, it removes every nitrite-based candidate before any comparison of performance (illustrative). Open items in this example are the permit's limit for total organic carbon and the cleaning agent used at the annual shutdown, each with the person who will supply it. The baseline is the discontinued product's corrosion rate of 0.05 mm/y by coupon, measured 2026-08 (illustrative).
Where a chemical application data sheet does not fit
A chemical application data sheet does not fit an incident, a trial plan or a formulation project. A leak, an exposure or an existing quality complaint needs a troubleshooting record first; the data sheet describes what a product must do, not why the current one failed.
The sheet also stops before a trial. Once the customer has accepted a recommended product, the trial's acceptance criteria, duration and responsibilities belong in a trial plan, which can reuse the success criteria from section 4 but freezes them for the run. Judging trial results is another document again.
If no product on the market can plausibly meet the mandatory requirements, the sheet has done its job by showing that, and the next step is a formulation design or a change of requirement, recorded as a finding rather than forced into a ranking.
The sheet is not a regulatory review. Requirements such as a permit limit or a substance restriction are recorded as the customer states them, with the document behind them; whether a candidate product complies needs its own safety data sheet, regulatory data and the rules of the site's jurisdiction. The sheet does not replace the customer's own quality system records either; it adds one record to them.
Application data sheet checklist
An application data sheet checklist confirms, before the sheet is sent to suppliers or filed, that each answer can rule a candidate in or out.
The request type is one of the four, with the request in the customer's own words.
A re-check names the condition that changed, with old and new values.
The current product has a dose with its basis, usage from records and a dated baseline.
The current product's SDS and TDS are attached with revision dates.
Every requirement is tagged mandatory, preferred or welcome.
Every requirement names the role that stated it and the function it protects.
Conflicting values from two roles are both kept, on one basis.
Every success criterion has a threshold, a unit, a direction, a method, a sampling point and a detection limit.
Every limit names the document it comes from.
The operating window covers start-up, shutdown, cleaning, seasonal swing and storage.
Coexisting chemicals, cleaning agents and wetted materials are listed.
The dosing point and its basis are named.
Every open item names the candidate judgment it changes and who answers it.
Lubinpla's product recommendation task works in the same order from your own records: it confirms the requirements and success criteria first, applies the blocking checks to every candidate before it compares suitability, and returns one cited document for your review.