Lowest price, technically acceptable evaluation does not grade on a curve. A product either meets every stated minimum in the solicitation or it does not, and if it does not, the offer is non-responsive regardless of price. We say this to clients constantly. We also, this August, nearly violated it ourselves.
The case
A solicitation called for a piece of equipment against several stated minimums: airflow, engine displacement, and a few others tied to how the equipment would actually perform on the job. One requirement called for a minimum airflow rating. The machine we had priced and were prepared to submit ran three units under that minimum. A later amendment to the same solicitation existed specifically to clarify the engine displacement floor, a floor the priced machine also missed, on a smaller engine than the amendment called for.
Neither miss was large. Both were misses. Under a best-value tradeoff, a buyer might weigh a near-miss against a lower price. Under LPTA, there is no weighing. A stated minimum is a line, and a machine on the wrong side of that line is rejected on that basis alone, whatever the price.
A separate solicitation the same week called for a specific equipment size. We had a machine sourced and priced at a smaller size against that requirement for twelve days before anyone caught it, because the record describing the sourced machine had been marked as compliant.
How the near-miss got marked as a pass
In both cases, someone had recorded the product as meeting the requirement before anyone had actually done the arithmetic. A note in the file said the sourced part was "matched to" the requirement. That phrase was never tested against the manufacturer's own published numbers for that exact part number. It described an intention, not a comparison.
The deeper issue: a manufacturer sells a family of machines under one model name, and that family spans a range of specifications across its individual built configurations. A spec sheet for the model family, or a table pulled from a workshop manual describing the family in general, is not the spec sheet for the one part number actually being bought and priced. Two machines can share almost the same name and differ on the exact number that decides whether the offer is responsive.
The recorded pass survived because nothing forced the comparison between the stated requirement and the specific SKU's actual published number. A status field said the product was sourced, sourced was read as compliant, and the gap between "we found a price" and "we confirmed the specs" never got closed until someone did the arithmetic by hand.
What we changed
The recorded status now separates two different facts that had been living in one field: whether a price exists for a line item, and whether the specific product at that price actually clears every stated minimum. A line item is not treated as ready to quote until every numeric requirement in the solicitation has a recorded actual value for the specific part number being bought, compared directly against the stated minimum, not against a description of the product family. A gap between a stated minimum and a recorded actual now blocks the bid from moving forward until someone resolves it, rather than sitting in a note that nobody re-reads.
The rule underneath all of it is simple to state and easy to skip under deadline pressure: recorded compliance has to come from checking the specific part number against the specific requirement, not from a checkbox someone ticked because the product looked close enough on paper. On LPTA, close enough is not a category.
How PrimeWright handles this
A stated minimum pulled from a solicitation is compared against the recorded actual value for the specific part being sourced, and the arithmetic overrules the tick: a recorded miss blocks the bid at the review gate rather than sitting silently in a note. See how the AI analysis pulls requirements in the first place.