We treat the solicitation as the source of truth for what a bid needs. This August, a submission portal proved that assumption wrong at the worst possible moment: while the offer was actually being uploaded, against a closing clock.
What actually happened
The bid was fully prepared. Every requirement in the solicitation had been checked, priced, and signed. While uploading the offer, the portal refused it, stating that a specific document type had to be attached in order to submit, citing a federal safety data standard by name.
We went back to the solicitation. All nine pages of it. We searched for the document type, for "safety data," for the standard cited, for the word "hazard." Zero matches, anywhere in the document. The requirement the portal was enforcing did not exist in the solicitation at all. It existed only inside the portal itself, surfaced at the moment of upload, with no advance warning anywhere in the notice.
We were able to satisfy it immediately, and only because a safety data sheet for the product had already been pulled into the bid folder earlier in the process, for an unrelated reason: confirming the product's country of origin. That document happened to be a complete safety data sheet matching the exact product being quoted. It went in, the portal accepted the offer, and we closed with about ninety minutes to spare against the deadline.
Had that document not already been sitting in the folder by coincidence, this would have been a scramble to source, generate, or request a safety data sheet with the clock running, on a document type the solicitation gave zero indication we would need.
This was also not the first portal-only surprise on that bid. The solicitation itself stated, on an earlier page, that the actual closing date and time were set inside the portal's own solicitation module, not fixed in the notice text. Two separate facts on the same bid, both live only on the portal side: what time the bid was actually due, and what documents were required to submit it.
Why this matters
A solicitation reads like the complete list of what a compliant offer needs. For most requirements, it is. But a submission portal is a separate system, with its own upload rules, and those rules are not guaranteed to be reflected anywhere in the document you are actually bidding against. A package that satisfies every page of the solicitation is not automatically a package the portal will accept.
This is not the portal being unreasonable. Certain document types, like a safety data sheet on a hazardous or chemical line item, are a real and standard requirement for that category of item, entirely independent of whether a particular solicitation happened to spell it out. The gap is not that the requirement is wrong. It is that nothing about it appears where a bidder is naturally looking.
The same bid also carried a second version of this same problem. The solicitation itself said the closing time lived inside the portal's own module, not in the notice text. Two facts that decide whether an offer is even eligible to be considered, what documents it must carry and when it is due, sat outside the one document every reviewer treats as the complete definition of the bid. A checklist built only from the solicitation's text will pass a bid straight into a portal that has its own separate opinion about both.
That is the actual lesson here, wider than any one document type. A portal is not a neutral mailbox for a package the solicitation already fully specified. It is a second source of requirements, and treating it as a formality at the end of the process is how a fully compliant package still gets refused with the clock running.
What we changed
The fix is not reading the solicitation more thoroughly. We had already read it thoroughly, and the requirement genuinely was not there to find. The fix is treating any hazardous or consumable line item as needing its safety data sheet gathered during sourcing, before submission day, regardless of whether the solicitation text asks for one, so it exists in the folder before the portal ever asks.
PrimeWright reads the submission channel out of the solicitation and shows it on the bid, so you know before prep day whether the offer goes to a portal at all and can go read that portal's own rules early. See how our pipeline handles sourcing and requirements before a bid ever reaches a portal.