Position is derived, never chosen. Move the two switches. That is the whole mechanic. Everything downstream follows.
A tender becomes a list of these. Q&A is a view of the list, not a separate product. reuse is the commercially important field: it decides what Qeema does and, more importantly, what it refuses.
| reuse | Meaning | Qeema |
|---|---|---|
vault | Same answer every tender CR number, ICV score, ISO certs, CVs | Fills it. No model involved. Answered from records. |
adapt | Same substance, reframed "Describe your HSE system", methodology | Drafts from past proposals, cited. Needs review. |
human | New every time Price, project plan, who is assigned | Refuses. Structures the slot, names an owner, writes nothing. |
Their own documents. Uploaded once, used in every tender. Storage is not the feature, expiry is. A bid rejected on a certificate that lapsed last month is a clerical failure, and it is the reason to keep paying in a quarter with no active bid.
About twenty documents. Finite, so it shows as a checklist rather than an open dropzone.
A per-org toggle. It degrades, it does not break:
For a first-run trial, or a customer who will not upload certificates until they trust you.
No exemptions, no bulk shortcuts. The reason is the audit trail: when a bid fails on a wrong CR number you can name who approved it. The risk is rubber-stamping, so approval must be fast, not skippable.
If Rand owns it, her deputy approves. One line of logic, and it is the difference between a gate and a checkbox. Applies to human-written items too, whoever writes the pricing answer does not approve it.
Edit an approved answer, or update the document it cites, and it drops back to drafted. Same when the tender is amended, affected questions reset and are flagged as changed.
Unanswerable questions produce a specific request, priced in questions: "Upload your HSE policy, answers 4 more." Uploading re-runs retrieval for those questions only. No org completeness meter; completeness is per tender.
The buyer supplies the structure. You author one shell, about three pages of boilerplate and merge fields, and nothing else.
Preferences must be asserted in the bid to apply, and nobody backdates them. The SME set-aside, the Qatari-content preference and the guarantee exemption get claimed here, detected at the verdict, asserted in the letter.
Annex letters assigned once by the packer, so "CV at Annex C" always points at a real file.
The empty answer is the trust mechanism. A tool that fills every box is one you must check every box of.