Your documents

Upload the specifications.
We tell you what is in them.

The specifications, the pricing schedule, your past bids. We read them page by page and draw findings out of them — the stated budget, the completion deadline, the security required — each tied to its page, and each labelled according to whether it is quoted verbatim or inferred.

It is the first step of preparing a bid: what comes out of this reading becomes the list of requirements, and then the list of documents to produce.

These findings do not move the price range. It stays computed from comparable tenders, and nothing you upload shifts it. We tell you what your documents contain; we do not pretend they make the forecast better.

SubscribeorBook a 20-minute demo

What you can upload

The tender's own documents: The specifications, the terms, the bid schedule, the addenda. That is where the requirements live that decide the real cost, and that nobody has time to read twice.
Your past bids: What you filed on earlier notices, and the results you got from them. They stay yours and are never shared.

PDF, Word and Excel, up to 50 MB per file. None of this is required: a report is produced entirely without it, from public data. It is an addition, never a condition.

What you get

Findings, with their page and their provenance.

“Quoted verbatim” means the text appears exactly as written on the page given: we check it against the page we read, without asking the model's opinion. Anything that fails that test is marked “Inferred”, and an inferred finding is a reading to check before you rely on it. The two are never mixed.

Quoted verbatim

This text appears exactly as written on the page given.

Stated budget$483K
“Le donneur d'ouvrage a prévu un budget maximal de 483 000 $ pour l'ensemble des travaux décrits à la section 3.”
devis-technique.pdf · page 12
Bid security
“Chaque soumission doit être accompagnée d'une garantie équivalant à 10 % du montant total soumis.”
devis-technique.pdf · page 4
Completion deadline
“Les travaux devront être entièrement terminés au plus tard le 15 novembre 2026.”
devis-technique.pdf · page 7

Inferred

An interpretation, to check before you rely on it.

Late penalty
“Une pénalité journalière semble s'appliquer au-delà du délai, sans que le montant soit chiffré dans les pages lues.”
devis-technique.pdf · page 7

Sample layout; the extracts and the amounts are invented. In a real report, every finding points back to the file and the page it was taken from.

Findings arrive as a new version of the report. The version you had does not change: it stays readable as it was, alongside, which lets you see exactly what your documents added. The one-page summary takes them into account when a finding is quoted verbatim — and a number taken from a document is presented there for what it is, the budget the buyer announced, never as a forecast of the winning price.

Why your documents do not move the range

A number read out of a PDF can make the report worse, not merely less good.

The range rests on the estimate the buyer published when there is one, and otherwise on what this family of contracts usually costs — a reference that exists for almost every notice. An amount taken from a document would take that reference's place. If it is less reliable than the reference, the forecast degrades instead of improving.

We set the bar before measuring: The level of fidelity an amount read out of a document has to reach was fixed in advance, and it is stricter than the accuracy of the estimates buyers publish themselves. We have not measured it yet: documents had to exist first. The day it is met, this page will change, and so will the report.
Quoted and inferred are never mixed: A quotation survived a word-by-word check against the page. An inference, by construction, did not. Showing them in one list with a small label would invite skimming past the only distinction that decides a number's weight.
A document that was not read stays on screen: Too large, unreadable, or beyond the page budget for a report: it appears with its reason. A section that silently drops what it could not read claims a coverage it does not have.
A shared document never shows its name: A public specification read once serves every report on that notice. Its file name does not travel: it often contains a company or project name, and it has no business in someone else's report.

Where to upload

On a report you bought

Documents upload straight into the report, and the findings are added to it as a new version. Up to 20 documents per report.

The report in detail →

In your workspace library

With a subscription, documents belong to your company rather than to a report: a past bid uploaded for one notice serves the next. That is what an upload attached to a single report cannot do.

The subscription in detail →

Questions

What we get asked before anyone uploads anything.

Does uploading documents improve the price forecast?

No, and we will not let anyone believe it does. The range stays computed from comparable tenders, and nothing you upload moves it. What documents add is findings: what the specifications require, what they announce as a budget, the deadlines, the guarantees. That is useful for preparing the bid; it is not an improvement to the model — and the report says so in the very place where it shows those findings.

What is the difference between “quoted verbatim” and “inferred”?

A quoted finding was found exactly as written on the page given: we compare the text character by character against the content we read, and it only passes if it genuinely matches. Anything that fails that test is marked “inferred” — that is a reading by our models, plausible and to be checked before you rely on it. The two groups are never mixed in the report, because the distinction decides how much weight you can put on a number.

Who can see the documents I upload?

You, and the members of your workspace if you subscribe. They are never shown to another customer. One thing only circulates: a public tender document — the specifications, an addendum — read once serves the other reports on that same notice, without its file name ever being shown, because a file name often contains a company or project name. Your past bids are never shared or reused that way.

Who actually reads my documents?

Models, at two providers, and nobody else. The first converts the file to text and receives its full content; the second reads that text to draw out the findings. They are named, each with what it receives, in our privacy policy. We could not read a 200-page specification without sending it somewhere, and saying so is better than implying it.

Can I delete a document?

Yes, and “delete” means removed from your view rather than erased: the document disappears from your lists, no link can reach it any more and it stops being read, but the file is kept — as is the text we extracted from it. That is deliberate: the file is the only witness to what you had uploaded, and a name in a log answers neither “what was it” nor “can you put it back”. The findings already written into a version of a report also remain, for the same reason a sold forecast never changes. If you want a real erasure, write to us and we will do it. We say so here rather than letting the button promise more than it delivers.

What happens if a document is too large?

It still appears in the list, with the reason it was not read. A report that silently dropped the 900-page appendix it could not process would be claiming a coverage it does not have. The limits: 50 MB per file, 400 pages per document, 1,500 pages in total per report, and 20 documents per report.

The next step

An option on the report, included.

Uploading documents is not a separate product and is not billed: the library comes with the subscription, like the feed and the reports.