Fennec · Tender and project document intelligence
Answers from your tender documents, cited to the page.
Upload a tender pack, a specification or a contract. Ask a question, or define the fields you need, and Fennec answers with a citation to the page and passage it came from, so your team can check it before it goes into a bid.
- Status
- In pilot with Group Surya
- Reads
- Tender volumes, specifications, conditions of contract, schedules, drawing sets (PDF)
- Every answer opens to
- The page and the passage, highlighted
- Access
- By invitation, in the browser
What bid security is required, and how long must it stay valid?
A bid security of 2% of the bid value, furnished as a bank guarantee. It must remain valid for 45 days beyond the bid validity period, which the instructions to bidders set at 120 days after the submission deadline.
Choose a citation to open its page.
Extracted fields
| Field | Value | Source | Conf. |
|---|---|---|---|
| Submission deadline | 14 Nov, 15:00Vol. 1, p. 3 | Vol. 1, p. 3 | 0.98 |
| Bid security | 2% of bid value, bank guaranteeVol. 1, p. 14 | Vol. 1, p. 14 | 0.96 |
| Bid validity | 120 daysVol. 1, p. 9 | Vol. 1, p. 9 | 0.97 |
| Defects liability period | 24 monthsVol. 2, p. 41 | Vol. 2, p. 41 | 0.94 |
| Liquidated damages | 0.05% per day, capped at 10%Vol. 2, p. 38 | Vol. 2, p. 38 | 0.91 |
Showing source 1: Vol. 1, page 14, clause 19.1.
19Bid security
19.2Any bid not accompanied by an enforceable and compliant bid security shall be rejected by the Employer as non-responsive.
Source 1Vol. 1 · page 14 · clause 19.1confidence 0.96
The clause that matters is rarely where you expect it.
A tender pack runs to hundreds of pages across volumes, conditions, specifications and addenda. Teams copy requirements into spreadsheets by hand, under deadline. Fennec does the reading and shows its sources, so the review goes faster and every line can be checked.
- Eligibility
- Turnover, experience and similar-work criteria, buried in the instructions to bidders. Miss one and the bid is non-responsive.
- Securities and penalties
- Bid and performance security, liquidated damages and their caps, retention. Miss one and it is a cost nobody priced.
- Specification
- What a material, method or test must meet, spread across volumes and amended by addenda. Miss one and it becomes rework.
From a stack of PDFs to an answer you can check.
Five stages, each one there so the next can say where its answer came from. The detail is under each stage; the reasoning behind the design is on our approach page and in our published benchmark.
- 01
Read every page
Each PDF becomes pages, page images and typed blocks: headings, paragraphs, tables, figures, and key–value pairs such as drawing title blocks. Every block keeps its page, its box on the page and a confidence score.
Under the hood
Boxes are stored as fractions of the page, so a citation can be drawn at any zoom. The parser’s raw output is kept, so an improved mapping can be replayed over past documents without parsing them again.
- 02
Recover the structure
Sections come from headings, with continued runs stitched back together. Drawing sheets are identified from their title blocks. References between them are found: sheet ids, callouts, code sections, “see” phrases.
Under the hood
A reference to a sheet that is not in the set is kept as a finding rather than dropped, because a missing sheet is something a bid team needs to know.
- 03
Navigate, don’t guess
A question is answered by an agent that moves through the document’s own structure: the outline, keyword search, reading a section, looking at a page image, following a reference.
Under the hood
There are no embeddings and no vector store. Tenders are numbered clauses, schedules and sheet ids; on documents like these, structure beats similarity, and our own benchmark showed similarity search is blind to questions that span documents.
- 04
Cite every claim
Each claim in an answer names the blocks it rests on, and each block resolves to a document, a page, a box and the quoted text. Extracted fields carry the same, plus a confidence.
Under the hood
Click a citation and the page opens with the passage highlighted, so checking an answer takes a click rather than a search.
- 05
Say what wasn’t checked
Every question runs inside limits on tool calls and time. If a limit stops the search, the answer says so instead of presenting a partial search as a complete one.
Under the hood
A reply cut off at the output limit is retried once, and otherwise delivered marked as cut off, never as complete.
Upload, ask, extract, check.
Step 1: Upload the documents
Create a document set and upload the PDFs: tender volumes, specifications, conditions of contract, schedules, drawing sets. Each is read into pages, sections, tables, figures and title blocks, usually within minutes.Step 2: Ask
Ask a question across the whole set. Fennec moves through the documents’ own outline, clause numbers and cross-references to find the passage, and cites it.Step 3: Extract
Define the fields you need, such as dates, amounts, criteria or line items, and run them across the set. Each value comes back with its page, its box on the page and a confidence score.Step 4: Check
Click any citation to open the source page with the passage highlighted. Export results as JSON or CSV for the register, the estimate or the bid decision.
Built to be checked, not just believed.
- Cited answers
- Each claim in an answer carries a citation that opens the source page with the passage highlighted.
- Structured extraction
- Fields you define, returned as a table in which every value has a page, a box on that page, an excerpt and a confidence score. Export as JSON or CSV.
- Tables, figures and title blocks
- Schedules and bills of quantities are read as tables, so line items keep their quantities and units. Drawing sheets are identified from their title blocks.
- Navigation by structure
- Fennec answers by working through the outline, headings, clause numbers and references, plus full-text search, rather than by keyword similarity alone.
- Missing references, surfaced
- A reference to a sheet or clause that is not in the set is kept as a finding instead of being silently dropped.
- Answers that admit their limits
- If a search limit stops Fennec before it has checked everything, the answer says so. A reply cut off at its length limit is marked as cut off.
- Usage you can see
- A usage screen shows what each document read, extraction and question has consumed against your allowance.
For everyone who has to read the tender before the deadline.
- Bid and tender managers
- Triage a pack, build the requirements register and prepare the bid decision.
- Estimators and pre-construction
- Pull scope, quantities and specification requirements with the clause behind each one.
- Commercial and procurement
- Find securities, penalties, payment terms and notice periods across the conditions of contract.
- Engineering and project teams
- Look up what the specification requires for a material or method without searching every volume.
What Fennec does today, and its edges.
We would rather you know the edges before a demo than find them after one.
- PDFs
- Fennec reads PDF documents. Text-based PDFs work best; if your packs are scanned, bring one to the demo and we will show you how it reads.
- Drawings
- Title blocks, labels and notes are read, but not every dimension on a drawing sheet is transcribed yet. Specifications, conditions and schedules are the strongest use.
- Answer time
- Simple questions answer in seconds. Questions that span several documents take longer, and run inside limits on time and steps; if a limit is reached, the answer says so.
- Access
- Fennec is in pilot. Accounts are set up for your organization by invitation; there is no self-serve sign-up.
Fennec FAQ
What documents can Fennec read?
PDFs such as tender volumes, specifications, conditions of contract, schedules, bills of quantities and drawing sets. It reads text, tables, figures and drawing title blocks. It does not yet transcribe every dimension on a drawing.
How are answers cited?
Every claim in an answer and every extracted value points to a document, a page and a box on that page, with the quoted text. Clicking the citation opens the page with the passage highlighted.
Why does Fennec not use embeddings or a vector database?
Tender documents are organised by numbered clauses, schedules and sheet ids, and the questions bid teams ask often span documents. Navigating that structure finds the passage and can say exactly where it came from. In our own published benchmark, similarity search over a fixed number of passages could not answer questions that depend on a whole document set.
Can we define our own fields to extract?
Yes. You describe the fields you need, such as the submission deadline, bid security, eligibility criteria or BOQ line items, and Fennec extracts them across the document set with a citation and a confidence score for each value.
Does Fennec make the bid decision?
No. Fennec finds, extracts and cites what the documents say. Your team decides whether to bid and how to price it, with the source for every requirement one click away.
Is our data used to train models?
Fennec does not train models on your documents. It uses third-party document-parsing and language-model services to process them, and we can walk your security team through those providers and the data flow.
How do we get access?
Fennec is in pilot. Book a demo, and if it fits your work we set up an account for your organization and invite your team.
Building roads as well as bidding for them? Chainage runs quality assurance on site, from inspection request to approval.
Bring a tender pack to the demo.
We will load it, ask it the questions your team asks, and show you the source of every answer.