Read a tender pack. Every figure beside the section it came from.
You upload a Word or PDF tender pack. Coira reads it by fixed rules and returns the award criteria and their weightings, the marks available, the pass/fail thresholds, the notional-hour schedules and the submission deadlines — each figure printed beside the document name and the section it was lifted from. Free, no account needed.
Read a tender pack
Word (.docx) or PDF with a text layer, up to 4 MB in total. Nothing about your pack is kept — the files are read in memory and forgotten; one lookup of the authority’s name against Coira’s own tender feed is the only thing that leaves the process (how that works).
What it reads
Built for Irish public consultancy tenders issued on the Office of Government Procurement template family — the ITT-S2(b) instructions, the QC2 suitability questionnaire and the FTS9 form of tender. A pack with no recognisable Instructions to Tenderers comes back saying so, with each file listed as read or not read and why.
Where the pack is silent — a deadline given as “as per eTenders”, a role with no hours — the reader shows a visible blank and the reason. Never a guess.
What it does not do
- It does not submit anything through an e-tender portal.
- It does not read a scan with no text layer.
- It does not decide whether to bid.
- It does not invent a field the pack never stated.
- It does not match the pack’s roles to your rates or price anything — that is the fee desk, behind a login.
What happens to your documents
Nothing about your pack is kept — not the files, not the extracted text, not the project name. The bytes are read in memory, the reading goes back to you, and the process forgets them.
Uploads are capped at 4 MB in total and 30 files, checked before anything is decompressed, and the reader is never given a file path — only the bytes you sent. Inside a Word file the decompression itself is bounded, so a small file cannot be made to demand gigabytes.
One value from the reading — the contracting authority’s name — is used to look up matching notices in Coira’s own public tender feed, so the reader can offer a deadline the pack defers to eTenders. That lookup is a database query, and the name can appear in the database provider’s request logs for a short time. Nothing else from the pack leaves the process.
The one thing kept is a count of reads per connection address, stored as a keyed hash of the address rather than the address itself, for up to 24 hours, so a free public reader cannot be flooded. The limit is 30 reads an hour per address — an office behind one address shares it. The record holds no file name and no content.
No language model is on the path of any figure. The values are located by fixed labels in the template, which is why each one can carry its section.
A worked example
See the reader on one real, public pack — Tipperary County Council’s design-consultancy tender for the Nenagh fire-service learning centre — including a contradiction the pack carries about its own marks.
Copy anything on this page straight into whatever you already use. If you want the reading priced against your own rate card, that is the fee desk — try Coira.