Most supply solicitations that name a product do not actually want that product. They want what it does. "Brand name or equal" is the buyer pointing at a known model to describe a need, then inviting anyone whose product meets that need to offer it instead. The invitation is real, and equals win. But an equal can also lose in a way the brand name never can: not because the product falls short, but because the offer never showed that it does not. Equals that would have worked get rejected, routinely, because the evidence was not on the page. ## The salient characteristics are the requirement The brand and model are a reference point. The requirement is the list of salient characteristics — the physical, functional and performance features the solicitation says matter. A capacity, a dimension, an operating range, a certification, compatibility with equipment the buyer already runs. That list works in both directions, and bidders tend to learn only one of them. An equal has to meet every characteristic on it. It does not have to meet anything that is not on it. The named model has hundreds of features the buyer never mentioned, and an agency that rejects an equal for lacking one of those is evaluating against a requirement it never published. GAO sustained a protest on exactly that in 2024, where an agency rejected equipment offered as an equal to a named Caterpillar machine using characteristics the solicitation never listed. So read the list as the contract it is: everything on it is mandatory, and nothing off it is. ## The evaluator reads your offer, not the market The federal brand-name-or-equal clause is blunt about where the burden sits. An equal is evaluated on the information furnished in the offer or identified in it, and the contracting officer is not responsible for going to find anything else. Your product's website may prove compliance on every line. If the offer neither includes that evidence nor points to it, the evidence does not exist for the evaluation. The same clause carries a default that catches people. Unless the offer clearly says the product is an equal, the offeror is taken to be providing the brand name product. A line item that quietly describes a different model, without saying "equal" and naming the make and model, has not clearly offered an equal at all. ## The four ways an equal gets rejected **1. Literature that does not address every characteristic.** A manufacturer's product sheet covers what the manufacturer likes to advertise, which is rarely the same list as the solicitation's. One characteristic left unaddressed is enough. **2. The right value in the wrong terms.** The requirement is stated in one unit, test method or standard, and the spec sheet meets it in another without ever connecting the two. Do not count on the evaluator doing the conversion. The equivalence you know to be true is the thing you did not write down. **3. Modifications that are not described.** If the product meets a characteristic only with an option, an accessory or a change you plan to make, the offer has to describe the modification and mark it on the literature. An unmarked option reads as the base model. **4. The characteristic that moved.** Salient characteristics are not always in one table. Some sit in an attachment, and some arrive by amendment in answer to another bidder's question. An offer checked against the original list can be fully compliant with a solicitation that no longer exists. ## A compliance table does most of the work The reliable fix is unglamorous: one row per salient characteristic. The requirement in the solicitation's own words, your product's value against it, and the page of the literature that proves it, with the relevant line marked. Put the make and model at the top, say in plain words that it is offered as an equal, and give every modification a row of its own. Build the table from the solicitation and every amendment, not from memory of the first read. It takes an hour. It turns the evaluator's job from searching into checking, and an evaluator who is checking finds the answers you put in front of them. ## When the list itself is the problem Sometimes the characteristics are written so tightly that only the named product can meet them — a dimension to the millimetre, a proprietary interface, a feature with no functional reason to be there. That is a brand-name-only requirement wearing an "or equal" label, and a buy restricted to one brand is something an agency has to justify. The cheapest time to raise it is before the solicitation exists, in a response to the market research that preceded it. The next cheapest is the question period, in writing, asking whether a named alternative would be acceptable. An objection to the solicitation's own terms generally has to be raised before offers are due, not after the award goes elsewhere, which is one more reason to read the list on day one rather than the night before. Offra reads a solicitation and its attachments into a requirement checklist, each item cited to the passage it came from — which is most of a compliance table before anyone has opened a spec sheet. Related reading: [the five documents that sink a public tender](/blog/five-documents-that-sink-a-public-tender) and [a Sources Sought notice is the bid before the bid](/blog/how-to-answer-a-sources-sought-notice).