tender-documents-legal is an AI software product that answers complex, raw natural-language queries over legal and large-volume document sets — most prominently tender documents. A user uploads tender PDFs and then asks questions that require reading across the whole document set, such as "how many documents do I have to submit at bid time?" The user can also add their own documents and ask the system to check their eligibility against a tender. The product's purpose is to answer any kind of complex query the user asks about multiple documents, synthesizing a single correct answer from many sources rather than performing a single-document lookup.
The audience is the Document Analyst / Bidder: bid managers, tender analysts, and small-business owners who must read hundreds of pages of contract language under deadline and need a traceable, correct answer rather than a pile of search hits.
The current product is a first-party web application with application-owned identity. A Document Analyst / Bidder creates an account, uploads tender PDFs and their own documents, composes complex natural-language questions spanning the uploaded collection, and reviews synthesized answers that cite the exact source pages behind every claim.
Current delivery covers:
Narrow exclusions: the product does not perform single-document keyword search as its purpose, does not act as a bidding portal or submission channel to any tendering authority, and does not provide legal advice. No future-horizon requirements are currently accepted.
The product is delivered as a first-party application with its own custom interface and its own identity. Because uploaded documents, composed queries, and synthesized answers are durable, analyst-specific state that must be resumed across sessions and kept bound to the correct participant, the application owns identity: a first-use enrollment surface and a returning verification surface are prerequisites to the protected workspaces. The anonymous entry surface is a distinct access boundary and cannot itself establish access to the protected destinations.
All document ingestion, query composition, and answer review happen inside first-party pages. The AI reading and synthesis work is backend execution supporting the analyst's interaction; the analyst always initiates the query and always receives and reviews the answer in a first-party destination. No provider-owned or external destination is part of the current delivery, and no headless-only delivery is accepted.
Not applicable — no reference directive with content_source authority was supplied.
01 carrying the typed sample question; numbered source rail; bottom metadata rule reading TENDER-2024-118 · 412 PAGES · 7 DOCUMENTS · 1 ANSWER.FR-1 — Complex raw query answering over legal and large document sets (explicit) As a Document Analyst / Bidder, I should be able to ask complex raw natural-language queries over legal and large volumes of documents, such as tender documents, so that I receive a synthesized answer rather than a single-document lookup.
FR-2 — Upload tender PDFs and ask how many documents must be submitted at bid time (explicit) As a Document Analyst / Bidder, I should be able to upload tender PDFs and then ask how many documents I have to submit at bid time, so that I know the required submission set.
FR-3 — Add own documents and check eligibility against a tender (explicit) As a Document Analyst / Bidder, I should be able to add my own documents and ask the system to check my eligibility against a tender, so that I know whether I qualify before bidding.
FR-4 — Answer any kind of complex query across multiple documents (explicit) As a Document Analyst / Bidder, I should be able to ask any kind of complex query across multiple documents, so that questions spanning several documents are answered as one coherent result.
FR-5 — Self-service enrollment before first use (required_inference) As a Document Analyst / Bidder, I should be able to create my own account before first use, so that my uploaded documents, queries, and answers belong to me and can be resumed.
FR-6 — Returning verification before accessing prior documents, queries, and answers (required_inference) As a Document Analyst / Bidder, I should be able to verify myself on return, so that I regain access to the documents I uploaded and the queries and answers I previously produced.
FR-7 — Upload or add the relevant tender and user documents before submitting a multi-document query (required_inference) As a Document Analyst / Bidder, I should be able to upload or add the relevant tender documents and my own documents before submitting a multi-document query, so that the query has the sources it needs.
Product context. The analyst works under bid deadline against large volumes of legal and tender material — tender PDFs running to hundreds of pages, plus their own compliance, financial, and eligibility documents. They are not looking for a search box; they are looking for a correct answer they can act on and defend.
Primary goal. A correct, complex answer synthesized across many documents rather than a single-document lookup — for example, how many documents must be submitted at bid time, or whether their own documents make them eligible against a specific tender.
Distinct accepted responsibilities.
Relevant inputs and decisions. The tender PDFs and the analyst's own documents; the wording of the complex question; the document scope for that question; and the decision of whether the cited evidence supports the answer well enough to act on.
Interactions with other accepted participants. The analyst is the sole accepted human participant. The AI reading and synthesis work is backend execution that the analyst initiates and whose result the analyst receives and reviews; it is not a separate human participant.
Observable success. The analyst receives one synthesized answer to a multi-document question, every sentence of which carries a citation chip that opens the exact page excerpt, and — for eligibility questions — a ruled checklist with green checks or red crosses and the tender clause number in the right column.
What makes this role distinct. The work is cross-document synthesis under deadline pressure, not retrieval. The analyst's value comes from questions whose answers only exist in the relationship between documents, and from being able to trace every claim back to a numbered source.
Muse and headline. Erik Spiekermann — typography as infrastructure. The interface reads like a well-signed transit station: numbered wayfinding, signal colours used like transit lines, warmth inside order. Headline: "Ask the whole tender. Get the whole answer."
Mode. Dark mode.
Colour tokens (exact hex by role).
| Role | Hex | Use |
|---|---|---|
| Background (ground) | #14120F | Deep warm charcoal page ground |
| Surface | #1E1B17 | Raised panels and cards |
| Text | #F2EDE4 | Warm off-white body and heading text |
| Primary | #E8B23A | Signal yellow — active state, line numbers, currently-selected source citation |
| Accent | #D94F2B | Transit red — eligibility failures, deadline warnings, destructive actions |
| Muted | #8C8578 | Metadata, page numbers, secondary labels |
| Border/hairline | #2C2822 | 1px zone separators |
| Document-class line — green | #5E8C4A | Source-rail document-class line colour only |
| Document-class line — blue | #3E7CA6 | Source-rail document-class line colour only |
Proportion: roughly 70% ground, 20% surface, 10% signal. The green and blue appear only as document-class line colours in the source rail, never as UI chrome. No blue or indigo primary on a white ground; no gradient washes.
Typography. Headings and body: Fira Sans. Headings use Fira Sans SemiBold and Bold at large sizes with tight tracking (-0.02em); sentence case for editorial headings, uppercase with +0.08em tracking for section labels and system metadata. Weight contrast carries the hierarchy — no display face, no serif. Scale: 1.250 modular on a 16px base — 64 / 51 / 41 / 33 / 26 / 21 / 17 / 16 / 14 / 12. Headings 64 and 51 for landing, 33 for page titles, 21 for section heads, 16 body, 14 metadata, 12 uppercase labels.
Shape language. Functional and rectilinear. 4px radius on inputs and buttons, 8px on panels and cards, 0px on the source rail and any element that behaves like a sign. Hairline 1px borders in #2C2822 separate zones instead of shadows. Numbered circular badges (24px, 1px border, signal colour when active) act as wayfinding markers throughout — every document, query, and citation gets a number.
Spacing rhythm. Strict columns with generous 48px gutters; horizontal 1px rules between answer sections.
Imagery style. No stock photography, no 3D renders, no decorative illustration. Visual content is the product's own material: real tender page excerpts rendered as legible document fragments with the cited clause highlighted in signal yellow; schematic transit-style network diagrams of the document set showing which documents a query touched; pictograms for document classes drawn in 2px stroke. The hero uses a single photographed-overhead shot of a physical tender binder on a warm charcoal desk, cropped tight, with a printed page edge visible.
The public entry is a station board for the document set. A full-viewport dark warm-charcoal stage (#14120F) is divided on the same grid the workspaces use.
#E8B23A) and the rest in warm off-white (#F2EDE4). Directly beneath it, a real query input rendered as a ruled form field — not a rounded search bar — carrying a numbered badge 01 and a typed-in sample question animating across it.
Reading across the document set
Document set — each stop is one uploaded source
Upload the tender PDFs and ask a plain question: how many documents do I have to submit at bid time? The product reads across the whole document set — conditions of contract, scope of works, submission checklist and addenda — and returns a single counted answer instead of a list of pages to search.
Each item in the answer is traced back to the clause it came from, so a count is never just a number. You can open the exact page that stated it and check the wording yourself before the deadline closes.
The clause that governs a submission count is usually written once and buried. The answer surfaces it, labelled with its clause number and page.
Clause 4.2 The Tenderer shall submit the documents listed in this section in a single sealed package, marked with the tender reference and the Tenderer's name.
Clause 4.3 The package shall contain seven documents: the Form of Tender, the priced Bills of Quantities, the programme of works, the method statement, the signed conditions of contract, the compliance register and the eligibility statement. Any package missing a listed document shall be non-responsive.
Clause 4.4 Documents submitted after the closing time stated in the tender notice shall not be considered.
Cited clause · answer source
Add your own compliance, financial and eligibility documents alongside the tender, then ask whether you qualify. The product holds both sides of the question at once: the tender's stated requirements and the evidence you already have on file.
The result is a ruled checklist rather than a paragraph. Each requirement is a row with your position on the left and the tender clause that set it on the right, so a fail points straight at the clause you have to answer — and a pass is as traceable as a fail.
Rows read across document classes: financial, compliance and eligibility documents are checked as one set against the named clauses.
Meets requirementDoes not meet requirement
The document workspaces are reached after enrollment or verification.

Reading across the document set
Document set — each stop is one uploaded source
Upload the tender PDFs and ask a plain question: how many documents do I have to submit at bid time? The product reads across the whole document set — conditions of contract, scope of works, submission checklist and addenda — and returns a single counted answer instead of a list of pages to search.
Each item in the answer is traced back to the clause it came from, so a count is never just a number. You can open the exact page that stated it and check the wording yourself before the deadline closes.
The clause that governs a submission count is usually written once and buried. The answer surfaces it, labelled with its clause number and page.
Clause 4.2 The Tenderer shall submit the documents listed in this section in a single sealed package, marked with the tender reference and the Tenderer's name.
Clause 4.3 The package shall contain seven documents: the Form of Tender, the priced Bills of Quantities, the programme of works, the method statement, the signed conditions of contract, the compliance register and the eligibility statement. Any package missing a listed document shall be non-responsive.
Clause 4.4 Documents submitted after the closing time stated in the tender notice shall not be considered.
Cited clause · answer source
Add your own compliance, financial and eligibility documents alongside the tender, then ask whether you qualify. The product holds both sides of the question at once: the tender's stated requirements and the evidence you already have on file.
The result is a ruled checklist rather than a paragraph. Each requirement is a row with your position on the left and the tender clause that set it on the right, so a fail points straight at the clause you have to answer — and a pass is as traceable as a fail.
Rows read across document classes: financial, compliance and eligibility documents are checked as one set against the named clauses.
Meets requirementDoes not meet requirement
The document workspaces are reached after enrollment or verification.
No comments yet. Be the first!