The pack, in the buyer’s own numbering
Nothing is sorted and nothing is renumbered. A pack a buyer has to map back onto their own questionnaire is a pack that loses marks for reasons that have nothing to do with the answers.
The last thing a bid tool does is hand over a file, and it is the step where tools usually reveal that they were built around their own data model rather than around the buyer’s document.
A Bid-On pack comes out in the buyer’s own structure: their section headings, their numbering, in their order. Nothing is sorted and nothing is renumbered — a parser that tidied 4.1a into 4.2 produces a pack an evaluator cannot map onto their own questionnaire, and a file somebody has to rebuild by hand is where the numbering stops matching.
Three formats, each for a real destination. DOCX for the submission that gets attached, written through the platform’s own document model so the branding, the hashing and the renderer are the ones every other issued document uses. XLSX with a sheet per section, for the buyers who ask for a response matrix. And copy-ready text per question, because an online portal has a box per question and what somebody actually wants is to paste.
Every page carries the client’s name, the document reference, the page number against the total, and a content hash — so a page separated from its bundle still says what it belongs to, and the file can be verified later as the one that was sent.
The gate in front of it is the part that earns its keep. Export is refused while any mandatory answer is red or unapproved — both, not either, because an approved red is still a rejection at the gate and an unapproved green has had no person’s name on it. And it is refused while any mandatory document is outstanding, because a submission missing a required document is rejected exactly as completely as one missing an answer.
The refusal names what is actually wrong: the questions where answers are the problem, the appendices where documents are. A gate that reported red answers when the real problem was an unsigned order form would send somebody to re-read answers that were fine.
And rendering is refused unless that gate has passed, rather than producing a file with a disclaimer on it. A pack that exists is a pack that gets emailed.
One thing is deliberately absent from the file: the returnables checklist and our own internal dates. They are how the provider runs the job, and a buyer should not read them off the front page of a submission.
See the record being made rather than described.
Launch the demo environment