For tender and bid teams
Know what the tender asks for before you commit to it.
Tender packs arrive as hundreds of pages and a deadline. With Fennec, your team asks the pack questions and extracts a requirements register in which every line is cited to the clause it came from.
The workflow
A bid review with a source for every line
Triage the pack
Upload every volume and addendum into one document set. Ask for the scope, the key dates and the eligibility criteria first, and decide early whether the tender deserves a full review.Build the requirements register
Define the fields your register needs and extract them across the set. Each entry arrives with its page, its location and a confidence score, ready to check.Interrogate the risky clauses
Ask follow-up questions about securities, penalties, payment terms and specifications. Answers cite the clause, so disagreements are settled by opening the page.Decide and hand over
Take the bid decision with the evidence in front of you, then hand the register and its citations to estimating and, if you win, to the project team.
Examples
Questions bid teams ask a tender pack
Each answer comes back with the page and passage it came from.
- What is the submission deadline, and how must bids be submitted?
- What are the eligibility and pre-qualification criteria?
- What bid security is required, in what form, and for how long?
- Which specification clauses govern the earthworks?
- What are the liquidated damages, and are they capped?
- How long is the defects liability period?
- What are the payment terms and the retention?
- Which key personnel must be named, and with what experience?
Examples
Fields worth extracting into a register
You define the fields; these are the ones bid teams most often start with.
- Submission deadline and bid validity
- The dates that decide whether you can bid at all.
- Bid security and performance security
- Amount, form and validity, which tie up working capital.
- Eligibility and pre-qualification
- Turnover, experience and similar-work criteria that disqualify quickly.
- Scope and quantities
- What is included and excluded, and the schedule items that drive the price.
- Liquidated damages and caps
- The rate and ceiling that set the risk of delay.
- Payment terms, retention and price adjustment
- When money moves, and whether prices move with it.
Boundaries
What Fennec does, and what stays with your team
Fennec
- Reads every page of the documents you upload
- Answers questions and extracts fields, with citations
- Shows a confidence score for each extracted value
- Keeps the original value when a reviewer corrects it
Your team
- Decides whether to bid
- Prices the work and carries the commercial risk
- Prepares and submits the bid
- Checks the cited sources for anything that matters
Bidding for road and highway works? Chainage takes over once the works begin, with inspections, test evidence and approvals mapped along the road.
Questions
Tender analysis FAQ
Can Fennec read addenda and corrigenda?
Yes. Upload them into the same document set as the original tender and ask what they change. Answers can cite both the addendum and the clause it amends.
Does Fennec work for any kind of tender?
Fennec reads the documents you upload rather than a fixed tender format, so it works across public and private tenders. It has been built and tested on construction documents: specifications, conditions of contract and schedules.
Who checks the extracted values?
Your team does. Every value has a citation and a confidence score, so reviewers can open the source, confirm it or correct it. Corrections are kept next to the original value.
Bring your next tender pack
We will load it in a demo and ask it the questions on your checklist.