A case file per tender.
Read, not skimmed.
The procedure documents are fetched and read in full, in the language they were written in. At the top sits the extraction sheet: the real deadline, the value, the criteria weights, the certifications, the guarantees. When the portal and the documents disagree, the documents win.
- Contract notice.pdf
- Technical specifications.pdf
- Award criteria annex.pdf
- Financial forms.xlsx
- ISO 9001 required
- Bid bond 2%
- Local partner required
What gets pulled out of the file.
Every extraction is traceable to the document it came from, so trust never has to be blind.
Deadline
The real one, from the documents, not the portal summary.
Estimated value
Base price and lots, as published.
Criteria weights
Price against quality, with the exact split.
Certifications
The ISO marks and registrations you must hold on submission day.
Guarantees
Bid bonds and performance guarantees, with their percentages.
Local requirements
Partner, presence or registration clauses that gate entry.
Key dates
Site visits, question deadlines, clarification windows.
Missing pieces
What the audit could not find, flagged instead of guessed.
The expensive mistakes live in the annexes.
Teams lose tenders they never should have entered, and miss ones they could have won, for the same reason: nobody had time to read the file properly. The deadline in the portal was wrong, the local-partner clause sat on page 40, the criteria rewarded price while the pitch was built on quality.
Case Files does the reading. The procedure documents are fetched and parsed, and the audit extracts what decides the bid: dates, values, weights, requirements, guarantees. When the portal and the documents disagree, the documents win.
The file assembles itself
Notices arrive with links scattered across portals. The documents are resolved, fetched and attached to the tender: one case file per opportunity.
The audit reads every page
Deadlines, values, criteria weights, certifications, guarantees, site visits, question windows: extracted and pinned to the top of the file.
From scattered links to one decisive page.
You decide in minutes
Open the file, see what decides it, bid or pass with reasons. The ninety-minute read becomes a five-minute decision.
What Case Files ships with.
- 03.1Deadline correctionWhen the portal summary and the documents disagree, the documents win, and the tender's clock is fixed from them.
- 03.2Every languageFiles are read in the language they were written in, criteria and clauses included.
- 03.3One-click briefingAny case file leaves the workspace cleanly: a WhatsApp message or a generated summary for a colleague.
- 03.4Traps surfacedDisqualifying requirements are flagged at the top of the file, not discovered at submission.
- 03.5Questions in timeClarification windows are pinned with dates, so the question that saves your bid gets asked while it still can be.
- 03.6Feeds the draftEverything extracted flows into the bid workspace, where the draft starts from the criteria, not from a blank page.
Reading is the middle of the story.
A case file begins as a radar hit or a signal, and ends as a bid on the board with the bench beside it.
Stop reading. Start deciding.
Bring one of your live tenders to the demo and we will open its case file together, extraction sheet and all.