01 / Tender intelligence
Turn procurement documents into structured evidence.
Tender and RFQ documents are ingested and reduced to structured findings — requirements, quantities and lot-level constraints — each one anchored to the exact source passage it came from.
What gets extracted, and how it's qualified.
- Document ingestion across PDF, DOCX and XLSX tender packs
- Structured extraction of requirements and eligibility conditions
- Quantity extraction with explicit status: exact, range, minimum, maximum, estimated or conflicting
- Lot-level feasibility reasoning, not just whole-tender summaries
- Every finding carries an evidence reference back to its source document
- Missing evidence is never silently assumed — unresolved requirements are reported as unresolved
Quantity status model
A quantity is never just a number.
Tender language rarely states a clean, single quantity. Brisora preserves that ambiguity as an explicit status rather than collapsing it into a false-precision figure.
Exact
The document states a single, unambiguous quantity.
Range
A minimum and maximum are both stated, as an explicit range.
Minimum / Maximum
Only one bound is stated — a floor or a ceiling, not both.
Estimated
The document itself labels the figure as an estimate, not a commitment.
Conflicting
Two passages disagree — reported as a conflict, never silently resolved to one value.
Where this feeds
Every finding here becomes an input downstream.
Structured findings from this layer feed directly into commercial analysis — landed cost, margin and feasibility are evaluated against the requirements and quantities extracted here, not against a fresh reading of the document. See how both layers fit into the full architecture.
See what happens to this evidence next.
Commercial analysis compares supplier and BOM options against the requirements extracted here.