We assume a solicitation's documents agree with each other. Most of the time they do. This August, on an LPTA equipment bid, they did not, and it nearly cost us a correctly priced quote submitted against the wrong line items.
What actually happened
The bid had a statement of work and a pricing form, the SF1449, both issued by the same contracting office as part of the same package. The statement of work numbered one line item as a piece of mounting hardware and the next as an adapter. The price schedule on the form numbered those same two positions in the opposite order.
We had built our pricing off the statement of work, the way we normally do, since that is where the actual item descriptions live. That meant our quote had the hardware price sitting against the form's row for the adapter, and the adapter price against the form's row for the hardware. The government's own two documents disagreed about which line was which, and our quote followed the wrong one.
We caught this about forty minutes before the deadline, and only because a question about the signing process sent someone back into the form for an unrelated reason. Nothing in our process compared the line item order in the price schedule against the line item order in the statement of work. Each was checked against itself, never against the other.
On this particular bid the two prices happened to be close enough that the totals came out nearly identical either way, so no money was actually at stake. That was luck, not the process working. On a bid where the two swapped items carry meaningfully different prices, this same mismatch turns into a priced-wrong submission, on the exact document the contracting officer uses to award.
Why the form wins
A statement of work describes the requirement. The price schedule on the form is the part of the offer the government actually evaluates and awards against. When the two disagree about which item is which, the form is the one with legal weight, because it is what gets executed. An offer that matches the statement of work but mismatches the form is not offering what the form says it is offering, even if the underlying intent was clearly right.
This is not a hypothetical dispute resolution question. It comes up as a plain reading problem: which document decides the CLIN order, when a human or a system builds pricing off the wrong one by default.
Why this is easy to miss
The statement of work is usually the richer document. It has the specifications, the delivery terms, the technical detail that pricing actually depends on, so it is the natural place to build a quote from first. The price schedule, by comparison, often looks like a formality, a table to transcribe numbers into once the real work of pricing is done. That asymmetry is exactly why a numbering mismatch between the two survives unnoticed: everyone's attention is on the document that describes the item, not the document that assigns it a row.
A compliance matrix built from Section L and Section M catches missing requirements. It does not, by itself, catch two government documents contradicting each other about item order, because that check requires reading the same fact twice, from two different places, and comparing them.
There is also a quieter reason this kind of mismatch is dangerous: it does not announce itself. A missing signature is visibly missing. A missing attachment is visibly absent from the list. A CLIN table built off the wrong ordering looks completely normal on its own. Every row is filled in, every price ties to an item description, the math checks out internally. Nothing about the document looks wrong until it is laid side by side with the government's own schedule and the rows are traced one at a time. That is a much higher bar than most reviews clear before a bid goes out the door.
What we changed
The fix is not "read the form more carefully." It is treating CLIN order as a fact that has to be verified against the solicitation's own schedule, not assumed to match the source document a quote was built from.
In PrimeWright, the line items come from the solicitation's own schedule and a bid cannot be marked submitted while a review flag is open, so a CLIN question gets raised and recorded before a signature, not after. See how our pipeline reads a solicitation before pricing ever starts.