The half of a submission that is not answers

Bid-On · CONSTRUX Engineering · 3 min read · 21 October 2026

An invitation to tender for a measured term contract arrives as nine documents. The questionnaire, an order form to complete and sign, a cost model to price, a schedule of amendments to accept or qualify, a stock list, a specification, a code of conduct. Three of them carry questions. Five are obligations with no question attached.

A submission missing a signed order form is rejected exactly as completely as one missing an answer. And until this was built, readiness on such a pack read 100% with the order form unsigned — because readiness was about answers, and nothing in the module knew those documents existed as obligations. That is the most expensive kind of wrong available to software: confidently wrong at the one moment nobody re-checks.

So a bid now carries a register of what has to be returned rather than answered: the buyer’s own reference, what it is, whether it is mandatory, the format, any page or file-size limit, whether it needs signing, who produces it, and our own internal date — which is earlier than the buyer’s on purpose, because the internal date is the one that actually binds.

The field it turns on is who produces it. The provider writes prose; the customer prices their own rates and signs their own contract. A cost model is the customer’s, so it appears in the request that goes to them rather than on a bid writer’s list of things they have failed to do — and it goes in the same message as the evidence gaps, because asking for it a week later in a second email is how a submission goes out short of the one document the buyer cared about.

It gates through the readiness figure rather than beside it. A separate check at the export would have left the screen saying “ready” while the export refused, and a screen that disagrees with the gate is worse than no screen. The refusal names the documents rather than the answers, because a gate reporting red answers when the real problem is an unsigned order form sends somebody to re-read answers that are fine.

The register appends rather than being confirmed once. A question list is confirmed in one sitting against the source; returnables are found across nine documents over an afternoon, and a register that had to be right in one go is a register nobody fills in. A duplicate reference is refused, and an internal date set after the buyer’s return date is refused — a date that binds nothing is not a date.

A signature is treated as a lead time rather than a task: a mandatory one with no internal date raises a question to put to the buyer, because a wet signature discovered on the last afternoon is the classic way a complete submission misses.

And waiving a returnable takes approval with a mandatory reason, because it removes a gate. A waiver with no reason is indistinguishable from a document nobody chased, and the difference matters when a submission comes back rejected for a missing one.

← All posts