How to Qualify a Polyacrylamide Brand-Equivalent Claim Before Approval

A supplier writes “equivalent to your current grade” and your approval workflow has to decide what that sentence is actually backed by. The words in a replacement offer range from a bare identity statement to a full drop-in guarantee, and each step up the range needs a different and larger evidence set. This guide gives a buyer-side method for classifying the claim you received, checking it against the evidence actually held, and releasing only the wording that evidence supports. Send the competitor brand, full model and suffix, physical form, current label or source document and your operating requirement, and ChinaPAM will classify the request and, where the locked identity, application and available evidence support a route, shortlist and quote a controlled candidate; otherwise it will identify the exact evidence needed for release.

The five claim classes a replacement offer can belong to

Most disputes over a polyacrylamide replacement are not disputes about chemistry. They are disputes about which claim was made. A supplier who says “this is the same type of anionic powder” has made a far smaller statement than one who says “this is a drop-in replacement,” yet both sentences often arrive in the same email, and a buyer who files them as one claim ends up approving the larger statement on the smaller evidence set.

Separate every replacement offer into exactly one of five classes before any evidence is reviewed. Each class answers a different question, and promotion from one class to the next is an evidence event, not a wording choice.

ISO 9001 auditing guidance for external providers describes the shape of this work in general procurement terms: define the criteria for selecting and evaluating an external provider, verify that the purchased product meets specified requirements, monitor provider performance, and scale the degree of control to the risk of what is being purchased. That guidance is an auditing reference for procurement controls, not a polyacrylamide specification or an equivalence standard, and it does not certify any supplier. What it does establish is that the verification activity is the buyer’s to define before release, which is exactly what the five classes above make explicit for a replacement claim.

1. Decision summary: approve, hold or reject the wording

The output of this method is one page, written before the approval email is sent. It names the claim, the decision requested, the highest class the evidence supports, the hold code if the request is held, and the single next evidence action. Everything else in this article exists to fill those five fields.

2. Capture the supplier claim exactly as received

Record the claim verbatim before anyone summarises it. A paraphrase written three days later tends to drift toward whichever reading the reviewer already prefers, and once the paraphrase is in the file the original sentence stops being the thing under review.

• Verbatim claim text. The exact sentence or sentences, copied, not retyped. If the claim was made verbally, write it down the same day and note that it was verbal and unconfirmed in writing.
• Channel and sender. Email, message, quotation document, catalogue, trade-show conversation or third-party listing. A claim in a supplier’s own quotation and a claim on a marketplace listing the supplier does not control are different evidential objects.
• Date received. Claims age. A statement about a product that has since changed revision is a statement about the earlier revision.
• Product referenced, as written. Whatever string the supplier used, including anything that looks like a typo. Do not normalise it yet; normalising is a decision you make in module 3 with the label in front of you.
• Which decision the claim is asking for. Suppliers rarely state this. Infer it, write down your inference, and check it in your reply. A quotation with no application mentioned is usually a class 2 offer being read by the buyer as class 4.

One more field is worth adding: whether the claim is accompanied by any document at all. A replacement sentence with no attached technical data, no label photograph and no issuer reference is a sales statement. It can still start a legitimate commercial process, but it cannot be promoted above class 1 by anything in the email itself.

3. Lock the complete product and source identity

A replacement claim has to preserve the full competitor model and suffix, the physical form, the document issuer, the source family and the document version, because removing any one of those fields can change the identity being compared. This is the field where most replacement files go wrong, and it goes wrong quietly: the brand number survives and everything attached to it is dropped.

A historical SNF FLOPAM catalogue illustrates the suffix point directly. On a single page it lists an FO 4498 SH column and an FO 4498 column as separate entries, and the catalogue carries its own limitation statement about the indicative nature of its data. Two items sharing a base number are presented by the issuer as distinct items. That is a 2007 indicative catalogue, not a current SNF specification and not any kind of cross-reference to another manufacturer’s range, so it proves nothing about present-day grades. What it does show is that the suffix is part of the issuer’s own identity scheme, which means a buyer who writes down “FO 4498” when the bag says something longer has already lost a comparison field before the technical review begins.

If a field conflicts rather than merely being absent, the conflict itself is the finding. Two documents describing the same designation differently, a label that disagrees with the quotation, or a current sheet that disagrees with an archived one are all reasons to hold the identity and ask which version governs. Do not reconcile a conflict by choosing the more convenient document. Looking for a specific named grade rather than running a claim review? The brand equivalents hub is where brand and exact-model discovery belongs, and it routes to the supply pages for individual designations.

A procurement release keeps the approved candidate tied to its full label, batch and document set. This is a general warehouse scene; it does not prove current inventory or that a specific lot passed inspection.

4. Classify the requested claim before reviewing evidence

Classify first, then review. Reviewing first invites the reviewer to settle on a class that the available documents happen to fit, which is how a thin file ends up supporting a thick claim. Write the class down, in the file, before opening the attachments.

Three classification habits cause most of the trouble:

• Silent promotion. The offer says “same type” and the approval note says “equivalent.” Nothing was decided between those two sentences; a word simply changed. If the file cannot show which evidence licensed the change, the change did not happen.
• Class inheritance from a previous file. A supplier whose earlier grade went through a full comparison is not thereby pre-approved for a different grade. Each designation carries its own class.
• Classifying the supplier instead of the claim. A well-audited supplier can still send a class 2 statement. Supplier qualification and claim qualification are separate records; the supplier audit checklist covers the first and this article covers the second.

One practical test: read the claim and ask what would have to be false for it to be wrong. If the answer involves only the label, it is class 1. If it involves chemistry family and form, class 2. If it involves your process, class 3. If it involves a comparison having been run, class 4. If it involves your plant having accepted the result, class 5.

5. Apply the evidence ladder

The ladder below is the evidence policy ChinaPAM applies to its own public statements, written out so a buyer can apply the same thresholds to any supplier’s claim. It is an internal publication standard rather than an external standard or a customer approval, and it is deliberately stricter at the top than most replacement correspondence assumes.

The substantive rule it encodes: a matching ionic type, physical form or qualitative band is a basis for candidate screening and nothing more. An exact-equivalence statement requires both complete product identities plus a traceable comparison under the same stated conditions. Performance or drop-in wording requires all of that plus matched-condition performance evidence and a customer or site approval. Each step adds a category of evidence, not just more of the same evidence.

For any incoming claim, fill in the evidence-held and evidence-missing rows for every class up to and including the one being requested. The highest class where all held rows are checked and no missing row is blank is the claim class you can release. Everything above it is held until the corresponding missing row can be supplied.

Same-type screening narrows candidates; comparable conditions and a buyer-defined acceptance record are required before stronger claims. This is a general laboratory scene; it does not show a named method, accreditation, batch result or performance approval.

6. Keep vendor scales and conditions separate

Charge density, molecular weight, hydrolysis degree, residual monomer level and viscosity are all reported by polyacrylamide manufacturers, but not always in the same units or against the same reference conditions. A charge density expressed as mol % and a charge density described as a qualitative band of “low,” “medium” or “high” are both legitimate within their own issuer’s range. The problem appears when a comparison file places one issuer’s “high” next to another issuer’s mol % figure and implies a conversion has occurred.

The cross-vendor scale firewall has one rule: each issuer’s data stays in its own column, using the issuer’s own labels, units and reference conditions as published. A comparison entry in the file is a claim that requires its own evidence. Before a same-condition test has been run and documented, the comparison cell is empty by definition, not filled by inference from two adjacent data sheets.

7. Hand document consistency to the existing owner

When the claim review reaches a point where the blocking question is whether the label, TDS, COA and SDS for the competitor product or the proposed candidate are internally consistent and mutually conformant, that question belongs to the COA, TDS and SDS field-by-field review. Duplicating the field review in this file would mean maintaining two separate inventories of the same consistency checks, one of which will fall out of date.

The handoff input list from this review is:

• the locked product designation, full suffix and physical form from module 3
• the issuer, source family, document title, revision and date for each document being checked
• the specific field or cross-document question that is blocking the claim class
• the hold code the review is expected to resolve

Return the review outcome as a dated entry in the evidence-held column for the affected identity field. Do not promote the claim class before the entry is recorded.

8. Hand validation to the existing sample-to-bulk owner

The evidence ladder in module 5 defines what a class 3 or higher release requires in terms of a comparison having been run. If that comparison has not been run, the claim is held at H-CMP. The comparison itself, including sample identity, same-feed bench test, plant trial and bulk-lot acceptance, is handled by the sample-to-bulk qualification process.

Before passing work to that process, prepare the inputs so that the comparison can be designed against the right question:

• the competitor product’s locked identity and the class 2 screening record from modules 3 and 5
• the application, process step, feed and current operating baseline from module 3
• the buyer-defined acceptance requirement that defines what a passed comparison looks like
• the current hold code and the exact claim class the comparison result is being used to support

When the comparison record returns, add its outcome as a dated entry in the evidence-held row for class 3 or 4 in module 5, then re-run modules 4 and 9 to re-assess the permitted wording.

The same separation applies to the inputs side. If the blocking gap is that your own requirement was never written down in a form a supplier can price or match, that is an RFQ problem rather than a claim-evidence problem, and the RFQ specification template is where those buyer inputs get assembled.

9. Issue the permitted-wording matrix

A claim review that ends in a class number has not finished. The usable output is a short list of sentences anyone in the organisation may write about the replacement, a matching list of sentences nobody may write, and the boundary that makes the permitted list true. Without that list, the class decision survives in one file while the sales and engineering correspondence drifts freely.

Downgrade examples

Downgrading is the normal outcome of a claim review, not a failure of one. Three worked examples, each written as the supplier sentence, the class actually supported, and the sentence that replaces it:

The two failure patterns this method is built against

Dropping identity fields while keeping the brand number. A buyer or supplier maps the number and discards the suffix, the physical form, the issuing entity or the document version. Because the number survives, the file looks complete. The consequence is that a quotation, a shortlist or a test record can end up tied to a different material or a different position in the range than the one being replaced, and nothing in the paperwork shows the substitution. The control is to hold the claim at H-ID until the full label and the original or current source document are locked, and to send a query about one specific designation to the page that owns that designation rather than answering it from a general file.

Promoting a screen or a single bench result into a performance claim. A same-type shortlist, or one comparison run under conditions nobody recorded, gets written up as exact, same-performance or drop-in proof. The consequence is that the buyer skips validation that was still required, even though feed, polymer preparation, equipment, dose, measurement method and lot conditions may all differ from the case the result came from. The control is to downgrade the wording to the class the evidence supports, record what is missing, and hand the actual testing and scale-up work to the qualification process that owns it.

10. Copy the hold/release record and request the supply route

The record below is the reusable artefact. One per claim, filled in whatever tool you already use. The hold codes come first because the code, not the prose, is what a later reader will search for.

Copyable hold/release record

Release only the highest class for which every field below is traceable and internally consistent. Otherwise hold or downgrade. A gap is not filled by a missing file, a third-party table, facts borrowed from an adjacent grade, a general photograph or confident phrasing.

• Supplier claim as received, verbatim
• Buyer decision requested
• Competitor brand, full model and complete suffix
• Physical form
• Issuer, source family, document title, revision and date
• Proposed candidate identity, if a named candidate is on the table
• Application, feed and current process baseline
• Evidence held, listed by claim class
• Evidence missing
• Highest permitted claim class
• Exact permitted wording
• Exact prohibited wording
• Decision owner and date
• Scope boundary and change-control trigger
• Linked document-review and test records
• Public-use permission status

Two fields are worth defending when the file is under time pressure. The first is the verbatim claim, because without it the review has no fixed object. The second is the change-control trigger, because a release that never expires becomes a standing claim about a product that may since have changed revision, form or source.

Evidence handoff checklist

Three handoffs recur, and each one travels better with its inputs attached:

• To document review. Locked designation, full suffix and form; issuer, source family, title, revision and date for every document in scope; the specific cross-document question that is blocking the class; the hold code expected to clear. See the document review guide.
• To validation. The class 2 screening record; the application, feed and operating baseline; the buyer-defined acceptance requirement; the class the result is meant to support. See sample-to-bulk qualification.
• To supplier qualification. The entity actually issuing the documents, which is not always the entity quoting. See the supplier audit checklist.

Request the supply route

An inquiry can start small. Send the exact label or the full model plus the application, and the classification can begin from that; the deeper test details are collected after contact rather than demanded up front. What gets sent back is the claim class your evidence currently supports and the specific item that would license the next one.

Send the competitor brand, full model and suffix, physical form, current label or source document, application, current process baseline and buyer acceptance requirement. ChinaPAM will classify the request and, where the locked identity, application and available evidence support a route, shortlist and quote a controlled candidate; otherwise it will identify the exact evidence needed for release. Exact-equivalence or performance wording is released only to the comparison and approval evidence actually held. You can also ask for the claim-evidence checklist and a hold/release wording review on your own correspondence, or go straight to the quote request once the inputs are assembled.