Coira reads a Word or PDF Irish public tender pack — the Office of Government Procurement template family — and gives back the award criteria, the marks, the thresholds, the notional-hour schedules and the deadlines. Every figure carries the document and the section it came from. Where the pack does not say, you get a blank. Free to run, with no account and no card.
Drop a tender pack here, or . Word or PDF.
Your file is read and returned. Nothing about the pack is kept and none of it trains anything. What is and is not kept →
Twenty minutes with Fionán Denver, who built it →
Who it is for: bid managers and commercial leads at construction consultancies and contractors holding an Irish public tender pack. The award archive underneath covers Europe; the reader is built for the Irish OGP templates and says so when a pack is not one of them.
European public construction award notices
markets
refresh
Plus a fixed archive of Irish OGP and eTenders open data. What is in the data →
Three rules, and the mechanism behind each one.
Every figure carries its source.
Beside each criterion, mark, threshold, hour figure and date, Coira prints the document it came from and the section it sat in. You can open the pack at that section and check it. Nothing is returned that cannot be pointed at.
A blank where the pack is silent.
If the pack does not state a page limit, Coira returns an empty field labelled as not stated. It does not fill the gap with a number that looks right. A blank you can see beats a number you have to check.
The same pack always gives the same answer.
No language model sits in the extraction path. The reader works by fixed rules over the document, so two runs of the same pack return the same figures, and so does a colleague’s run next week.
Determinism buys you reproducibility and a source for every figure. It does not buy correctness. When a clause is worded in a way the rules do not recognise, the reader stays silent rather than inventing something. That is the trade, stated plainly.
Coira will hand back fewer fields than a tool that advertises AI, and it will refuse packs it cannot parse. A scanned pack with no text layer is refused. A pack whose criteria table is an image is refused. That is the discipline working, not the software failing.
When the reader refuses, it says why, and it opens the manual route in the same screen: paste the text straight in, or key the values yourself. Anything you enter by hand is labelled as entered by hand, so a figure you typed never gets mistaken later for a figure Coira lifted from the document.
A publicly available Irish tender pack, read by the reader, with nothing tidied up afterwards. The extracted criteria, marks, thresholds and deadlines sit beside the source document, every section reference visible, every blank left blank.
This is here instead of a testimonial. Coira is new and has no case study to show you. A pack you can open and check yourself is better evidence than a quote from somebody you have never met.
Two things sit behind a login. Both start from a pack you have already read.
“I have a fee to price.”
Coira Bid
AvailablePrice the fee off your own rate card, then hand the client a Word fee letter and an .xlsx. Bid as a team across firms without your rates leaving your office.
For the firm bidding for the work: M&E consultants, quantity surveyors and design practices, pricing alone or as part of a team.
“The returns are in and I have to justify a recommendation.”
Coira Adjudicate
AvailableLevel the returns, check them against the award archive, and issue the tender report as a Word document with a citation behind every flagged line.
For the firm that issued the tender and now has to defend a recommendation to a client or a board.
Adjudicate opens after a conversation rather than a sign-up form.
60,498 European public construction award notices, across 31 markets, from TED, the EU’s public procurement journal, together with a fixed archive of Irish OGP and eTenders open data. Ireland refreshes every night; every other market is reached by a rotating sweep within 10 days.
Fixed means exactly that: the Irish archive is a snapshot held in full, not a live feed, and it is labelled that way everywhere it appears.
The archive answers one question, and it is the same question a fee and an adjudication both ask: what has this kind of work actually been awarded at. It is not a separate product and there is nothing to browse for its own sake.
Three rules, enforced in the code rather than in a policy.
A firm’s cost rate per hour never appears in anything a client sees.
Not in the fee letter, not in the spreadsheet, not in any export. The client sees a fee. Your cost of doing the work stays inside your firm.
No rate crosses between firms on a team bid.
When two or three practices bid together, each firm prices its own scope. Only a scope and a figure ever cross the line. No rates, no hours, no names of staff.
Tender packs are not stored and are not used to train anything.
The reader takes the file, returns the figures, and keeps none of it. One value — the contracting authority’s name — is looked up against Coira’s public tender feed to offer a deadline the pack defers to eTenders, so that name reaches a database query. Nothing else from the pack leaves the request. The full account →
Why not just run the pack through ChatGPT?
You can, and it will give you an answer for every field. The problem is telling which of those answers came out of the document and which one it composed. Coira prints the document and section beside each figure and leaves a blank where the pack is silent, so the checking work you would otherwise do line by line is already done.
Could we not build this ourselves?
The reader is rules over documents, so yes, in principle. What takes the time is the long tail: the pack that puts marks in a footnote, the one that splits the hour schedule across two appendices, the one whose deadline is in the covering letter. That work is why it is free to run — try it against your own packs before you decide.
What happens when it reads something wrong?
Open the section it cites and you will see it. That is the point of printing the source beside the figure. If it cannot read a pack at all it refuses, tells you why, and lets you key the values in by hand. It will not quietly produce a plausible number.
Can my client see my hourly cost?
No. A firm’s cost rate per hour never appears in any document Coira produces for a client, and on a team bid no rate crosses between firms. Only a scope and a figure do.
Who else is using this?
Coira is early and small, and it is run by one person. There is no logo strip, no customer list and no case study, because there is nothing honest to put in them yet. That is why the reader is free, public and needs no account: run it on a pack you already have and judge it on what comes back.
No ISO 27001. No SOC 2. No per-person permissions — everyone in a company account sees every fee and every rate in it. It is operated by one person.
These are stated here rather than left for a procurement questionnaire to find. What Coira does have, and how it is set up, is written out in full.
Coira Reader — free.
No account, no card, no email address. Capped at 30 reads an hour per connection address, which an office on one address shares.
Coira Bid — €2,400 per firm, per year.
Ex VAT, 5 people included. Rate card, fee letters, .xlsx exports, team bids across firms. Invoiced annually — there is no card checkout. What is included, and what is not →
Coira Adjudicate — starts with a call.
Adjudication work is scoped to the tender, so it starts with a conversation rather than a checkout. Talk to Fionán →
Coira is built and run by Fionán Denver, a mechanical and electrical building-services engineer working in Ireland.
Coira is decision support. It is not a substitute for a chartered quantity surveyor’s cost plan, and it does not give professional advice.