Comparison without a parameter table
Comparison of leaching agents often starts with a table, and a table promises more than it can deliver when the rows are not measured the same way. A table with mismatched rows compares labels, not agents, and a buyer who trusts the table will choose on the basis of wording rather than fit. Comparison without a table is slower, but it compares the case, not the label.
Begin instead with the case: one ore, one step, one question. Put the same case to each agent, and let the replies differ where the agents differ. When the case stays fixed, the differences that emerge belong to the agents; when the case shifts between agents, the differences may belong to the shifting case.
A table is not forbidden as a habit; it is unhelpful when its rows are invented. If a reply supplies figures, keep them attached to the case they were given for, and do not lift them into a general table where the case is stripped away. Figures without a case travel badly, and a table of travelling figures misleads more than it informs.
Dimensions that come from the case
Dimensions for comparison should come from the case, not from a catalogue of possible dimensions. The case supplies the ore, the step, the surrounding stages, and the local requirements; each of those can become a dimension by asking how an agent behaves at that point. A dimension that the case does not need adds noise, and noise is the enemy of a useful comparison.
Ask each agent the same questions in the same order, and record the answers side by side. Same questions, same order, same case: the discipline sounds dull, and it is the whole method. Without it, the comparison reflects the order of asking more than the difference between agents.
Weight the dimensions by the case, not by habit. A dimension that decides the case deserves more attention than a dimension that merely interests the buyer, and the message should say which dimensions decide. Stating the deciding dimensions up front lets the reply address them first, and lets the buyer see at once where the replies diverge.
Claims to read as claims
Read every claim as a claim, with its attribution attached. A company profile claim carries the company's weight; a third-party finding carries a different weight; and a claim with no attribution carries none at all. The inquiry should keep the three apart, and should never upgrade a company claim into a finding by repeating it without its attribution.
Replacement claims deserve special care, since they compare two things at once. Ask what is replaced, in which step, and for which ore, before accepting the comparison. A replacement that holds for one step may not hold for another, and a claim that omits the step omits the part that makes it testable.
Treat superlatives the same way. Words like best and only describe a ranking, and a ranking needs a field, a measure, and a source. Ask for the field, the measure, and the source in the inquiry, and let the reply supply them or withdraw the word. A superlative without those three is decoration, not information.
Questions that separate two agents
Questions that separate two agents are questions with different answers. Ask each proposer what it proposes for the named combination, and ask what would change the proposal. If both replies match word for word, the questions were too general; sharpen them until the answers diverge, since divergence is the point of comparison.
Ask about documents and arrangements for each agent in the same terms. Name the purpose for the document question, and name the commercial points for the arrangement questions, so the replies can be laid side by side. A comparison that covers documents for one agent and price for the other compares nothing at all.
Ask about limits for each agent, not only strengths. A limit, stated plainly, tells the buyer where an agent stops being suitable, and limits often separate agents more cleanly than strengths do. A proposer that names its own limits gives the buyer something a proposer that hides them cannot: a boundary to plan around.
What a reply should settle
A reply should settle the combination question first: what is proposed for the named ore at the named step, and on what particulars the proposal depends. Everything else in the reply, documents, arrangements, and local requirements alike, hangs from that answer, and a reply that leaves the combination question open leaves the comparison open with it.
A reply should also settle what it cannot answer. A plain statement of what is unknown, or what depends on particulars not yet supplied, is more useful than a confident answer to a different question. Judge a reply by what it settles and what it marks unsettled, not by its length or its confidence.
When replies arrive, compare them question by question, not impression by impression. Lay each answer beside the question that asked for it, and mark where answers diverge, where they agree, and where one reply leaves a question open. The comparison then follows from the answers, and the choice that follows rests on answers rather than impressions.
Comparisons that settle nothing
A comparison settles nothing when the case shifts between agents, when the questions differ, or when the answers are recorded without their questions. Each of those faults breaks the chain from question to answer, and a broken chain cannot support a choice. Check the chain before trusting the conclusion: same case, same questions, answers attached to questions.
A comparison also settles nothing when it ranks agents on a dimension the case does not need. An impressive win on an irrelevant dimension is still irrelevant, and a buyer who chooses on it has chosen well for a case that is not theirs. Keep the deciding dimensions in view, and let the rest stay in the background.
Finally, a comparison settles nothing when claims are repeated without attribution. A claim that enters the comparison as a company statement and leaves it as a finding has been upgraded without evidence, and every conclusion built on it inherits the upgrade. Keep attributions attached through every round, from first message to final choice.
Turning comparison into an inquiry
Turn the comparison into an inquiry by writing the deciding dimensions as questions, in order, for the named case. Name the ore and the step, put the same questions to each proposer, and ask for documents and arrangements in the same terms. The inquiry is the comparison, written as questions rather than as a table.
Gold Extraction Chemicals: What to Ask sharpens the document questions; Sustainable Gold Extraction Approaches sets the longer view beside the comparison; and Gold Dressing Agent Inquiry Checklist orders the whole message. Use the three to check the comparison before sending it.
Send the comparison as one message per agent, or as one message that names each agent and its questions separately. Keep a record of questions and answers side by side, so the choice can be traced back to answers, and so a later question can reopen exactly the point it concerns.
To ask about this page, use the inquiry form to name the ore, the process step, and the question, and ask what information is needed next.