Lubinpla

How to write a technical comparison against the incumbent product

Summary

A technical comparison against the incumbent needs 6 sections: customer conditions, criteria, same-method data, sources, incumbent strengths and a conditional conclusion. The incumbent is what the customer already runs in a named application. The structure fits when a supplier or distributor sets its own chemical product against it and the customer decides from the document whether to trial a switch.

  • ASTM E177-26a says a precision statement gives the magnitude of variability to expect between test results in one, or in two or more, reasonably competent laboratories (ASTM International, 2026).

  • ISO 4259-2:2026 specifies how to decide specification conformance when supplier and receiver test results conflict, for homogeneous petroleum and related products (ISO, 2026).

  • Directive 2006/114/EC permits comparative advertising in the EU when it objectively compares material, relevant, verifiable and representative features (Directive 2006/114/EC, Article 4(c), 2006).

  • A closed-cup flash point is usually a few degrees lower than an open-cup result on the same liquid, so the method must be listed with the value (ILPI MSDS HyperGlossary, accessed 2026).

Who reads a technical comparison against the incumbent, and what do they decide?

Three people at the customer read a technical comparison against the incumbent: the process or maintenance engineer, the quality or approvals reviewer and the buyer. Together they decide whether a switch is worth a trial, and each brings a different question. The engineer wants to know whether the new product holds up under the plant's own conditions. The quality reviewer wants every claimed difference checkable against a document. The buyer wants to know what the switch puts at risk if the comparison turns out to be wrong.

The fourth reader is easy to forget: the incumbent supplier. A customer may forward the comparison to the current supplier and ask for a reply, so the people who know the incumbent product best will read every row. They will find and answer a value copied from an old data sheet, a test run under different conditions or a dismissive adjective, and the whole document then loses weight with the customer.

Write the technical comparison for all four readers at once. In the opening lines, state which application it covers, which decision the customer is asked to make and which evidence is attached. The comparison succeeds when the engineer can approve a trial from it and the incumbent supplier cannot fault a row. It fails when the customer has to ask for the test reports before the discussion can start.

Which sections does a technical comparison of your product and the incumbent need?

A technical comparison of your product and the incumbent needs six sections in a fixed order, running from the customer's conditions to a conclusion that states when it holds. The table below shows what the customer decides from each section and the evidence that section should carry.

Section

What the customer decides

Evidence to attach

1. Customer conditions

Whether the supplier understood the application

Customer specification, equipment maker limits, measured operating conditions with dates

2. Comparison criteria

Whether the right properties are compared

Link from each criterion to a condition in section 1

3. Same-method data

Which differences are real

Test reports and data sheets with method, edition and sample identity

4. Source of every value

Whether each row can be checked

Document title, revision date and section for every value

5. Where the incumbent is stronger

Whether the comparison is fair

The rows the incumbent wins, with their effect under section 1 conditions

6. Conditional conclusion

What to approve and what the trial must confirm

Conditions under which the conclusion holds, open checks, trial scope

Section 3 carries the most weight, because a difference between two values means something only when both come from the same test method. Sections 1 and 2 come first so that the criteria are fixed before any value appears; a reader who sees the data first suspects the criteria were picked to fit it. Section 6 states the conclusion as a condition rather than a general verdict, for example that the new product is preferred while the operating temperature stays within the range tested. Keep each section short enough for the quality reviewer to check in one reading, and attach the documents instead of summarizing them.

Which criteria should a technical comparison take from the customer's conditions?

A technical comparison should use as criteria only the properties that the customer's specification, the equipment maker's limits and the measured operating conditions make decisive for this application. Every criterion should trace back to a line in section 1. A property that no condition depends on adds a row the customer cannot use, and it invites the question of why it is there.

Start from three documents. The customer specification gives the hard limits, often with a named test method. The equipment maker's manual gives approvals and limits for the machines involved. The plant's records give the conditions the product meets in service, such as temperature range, contaminants, water quality or cycle time. Write each criterion as a value, unit, method and the source of the limit.

Then split the criteria into two groups. Must-have criteria decide whether a product can be used at all: a product that fails one is out, whatever else it offers. Comparison criteria then rank the products that pass. The EU rules on comparative advertising apply the same logic to marketing claims: a comparison must concern goods "meeting the same needs or intended for the same purpose" and must compare features that are "material, relevant, verifiable and representative" (Directive 2006/114/EC, Article 4(b) and (c), 2006). A criterion that is not relevant to the customer's conditions fails that test as well as the engineer's.

Why should a technical comparison set only values from the same test method side by side?

A technical comparison should set only values from the same test method side by side, because different methods measure the same property under different conditions and give different numbers for the same liquid.

In flash point, a closed-cup method keeps vapors in, so it "usually results in a flash point that is a few degrees lower than in an open cup", and the same glossary adds that "one must always list the testing method when listing the flash point" (ILPI MSDS HyperGlossary, accessed 2026). ASTM D92-24, the Cleveland open cup method, notes that the closed-cup method D93 should be used to detect small but significant concentrations of lower flash point substances that may escape detection by D92 (ASTM International, 2024). An open-cup value for your product beside a closed-cup value for the incumbent compares two methods, not two products.

Even the same method is not enough when the gap is small. ASTM E177-26a explains that a precision statement gives the variability to expect between results "in one, or in two or more, reasonably competent laboratories" (ASTM International, 2026), and ASTM D6300-26 notes that repeatability and reproducibility are defined in the precision section of every Committee D02 test method (ASTM International, 2026). Before calling a difference real, check it against that method's reproducibility, the spread to expect between laboratories. Where results from two laboratories conflict near a limit, ISO 4259-2:2026 gives a procedure for deciding conformance, and ASTM D3244-24 requires the acceptance probability to be agreed between both parties before testing (ISO, 2026; ASTM International, 2024).

How should a technical comparison cite the source of each competitor value?

A technical comparison should cite each competitor value with the document it came from, that document's revision date, the section or table, and whether the value is a typical value, a specification limit or a test result. The customer cannot check a row that has no source, and the incumbent supplier will challenge it.

Three kinds of source are common, and each needs its own note. A published data sheet value is usually a typical value, not a limit, and makers say so: one lubricant data sheet states that typical properties "do not constitute a specification" (ExxonMobil, Mobil Xtra EP WT product data sheet, accessed 2026). Keep typical values and specification limits in separate rows, and never compare your specification limit with the incumbent's typical value. A test you ran on the incumbent product needs the method and edition, the laboratory, the sample source and date, and the lot or batch if known. A value from the customer's own records, such as an in-service analysis, needs the date and the equipment it came from.

When a value is not published, write "not published" in the cell rather than estimating it. One reason is the EU condition that compared features be "verifiable" (Directive 2006/114/EC, Article 4(c), 2006). Another is that a single estimated value makes the reader doubt the measured ones. The US Federal Trade Commission likewise says comparative advertising "requires clarity, and, if necessary, disclosure to avoid deception" (US FTC, 16 CFR 14.15, eCFR 2026).

Should a technical comparison admit where the incumbent product is stronger?

A technical comparison should admit where the incumbent product is stronger, in its own rows, and state whether that strength matters under the customer's conditions. The engineer and the incumbent supplier already know where the current product does well. Leave those rows out and they will read the comparison as written to win rather than to inform.

An honest row costs less than it seems. A property where the incumbent is stronger often sits outside the customer's conditions: a higher maximum operating temperature matters little if the plant never runs near it. Say so in the row, with the measured operating range from section 1, and the strength becomes a reason the switch is still safe. Where the incumbent's strength does matter, the comparison has found a risk for the trial to test, and naming it first protects the supplier from a failed trial later.

The EU rules point the same way for comparisons that count as advertising. Article 4(c) of Directive 2006/114/EC asks for features that are "representative" as well as material, relevant and verifiable (Directive 2006/114/EC, 2006). A comparison that shows only the rows your product wins is harder to defend as representative. Whether a given document meets the condition, though, is a legal question for counsel in the relevant jurisdiction. Write the conclusion so that it holds with the incumbent's strengths in view, for example by naming the operating range in which the new product is preferred.

Which wording should a competitor product comparison avoid?

A competitor product comparison should avoid wording that claims more than the data shows, that calls the incumbent equivalent or inferior without a method, or that talks about the competitor rather than the product. The table below sets each kind of wording against the reason it fails and a replacement.

Wording to avoid

Why it fails

Write instead

"Superior to" or "outperforms"

No property, method or condition

"Lower wear scar in ASTM D4172 at the stated load and temperature" (illustrative)

"Equivalent to" or "drop-in replacement"

Implies approval the document cannot give

"Meets the customer limits listed in section 1; trial to confirm"

"Their product is unreliable"

Discredits the competitor, not the product

The measured value and method, with its source

"Same as, but better"

Can present the product as a replica

Properties compared row by row

The second row matters most. "Equivalent to" claims an approval that only the customer or the equipment maker can grant, so the replacement wording names the limits met and leaves the trial to confirm.

Jurisdictions differ on tone. In the EU, comparative advertising must not "discredit or denigrate" a competitor's goods or activities (Directive 2006/114/EC, Article 4(d), 2006), and the UK regulations repeat that condition (UK SI 2008/1276, regulation 4, 2008). The US FTC holds that disparaging advertising "is permissible so long as it is truthful and not deceptive" (US FTC, 16 CFR 14.15, eCFR 2026). A comparison sent to customers in several countries should meet the stricter rule. Internal notes such as margin or the customer's other suppliers stay out of the customer version entirely; the practice of deciding what to leave out of a technical report for a customer applies to the comparison as well.

What does an illustrative technical comparison table look like?

An illustrative technical comparison table for a hydraulic or circulating oil sets out each property with its test method, both values and a column that says whether the row can be used for the decision. The table below decides which rows the customer can use for the switch decision and which need a same-method retest. Every product, value and verdict in it is illustrative.

Property (test method)

Your product

Incumbent

Comparable?

Kinematic viscosity at 40 °C (ASTM D445), illustrative

46.3 mm²/s, typical, TDS rev. 2026-03

45.9 mm²/s, typical, TDS rev. 2024-11

Yes, same method; check the gap against D445 reproducibility

Flash point, illustrative

228 °C, ASTM D92 open cup

212 °C, ASTM D93 closed cup

No; methods differ, retest one product

Rust prevention, illustrative

Pass, ASTM D665 procedure B

"Passes rust test", procedure not stated

No; ask for the procedure or retest

Foam tendency at 24 °C (ASTM D892), illustrative

30 mL, own lab test, lot 2617

10 mL, TDS typical value

Partly; incumbent stronger, both within the customer limit

Flash point is the row to study. The illustrative open-cup value of 228 °C cannot be set against a closed-cup value of 212 °C, so the apparent 16 °C advantage is not evidence until one product is retested by the other's method. The foam row keeps an illustrative incumbent strength in the table, with the note that both values meet the customer limit.

Read the table from the right-hand column first. Only rows marked "Yes" carry the conclusion. Rows marked "No" become retests, and rows marked "Partly" go into the incumbent-strength section with their effect under the customer's conditions. A comparison with more "No" rows than "Yes" rows is not ready to send.

What should a technical comparison checklist cover?

A technical comparison checklist should cover the conditions, criteria, methods, sources, fairness and conclusion, checked in that order before the document goes to the customer.

  • Every criterion traces to a customer specification, an equipment maker limit or a measured operating condition with a date.

  • Must-have criteria are kept apart from comparison criteria.

  • Every row names its test method and edition, and both values in a row come from the same method.

  • Differences smaller than the method's stated reproducibility are reported as no measured difference.

  • Every competitor value names its document, revision date, section and value type; missing values read "not published".

  • The rows where the incumbent is stronger are present, each with its effect under the customer's conditions.

  • No row uses "superior", "equivalent" or "drop-in" without a method and condition, and no line comments on the competitor company.

  • The conclusion names the conditions under which it holds and the checks the trial must close.

  • Internal notes, margins and other customers' names are absent from the customer version.

The practical test is simple: a comparison that passes every line can usually be forwarded to the incumbent supplier without harm. Lubinpla's document writing carries the comparison conclusion and the figures settled in the conversation into the document with their evidence, fills facts the records lack from public sources or by asking the user, and returns one cited document for the user to review and approve before it goes out.

Related posts