You have lost an EU tender even though your offer was cheaper than the winner’s. Not once: several times. And each time, the same bewilderment. How can a more expensive bidder prevail on a contract funded by European public money?
The answer sits in a document most bidders open too late, or never: the PRAG. And in a reading habit almost no one applies: studying the scoring grid before writing the first line.
What the PRAG actually is
PRAG stands for “Practical Guide”: the practical guide to contract award procedures for European Union external action. It is produced by the European Commission’s Directorate-General for International Partnerships (INTPA : A Practical Guide (PRAG)).
Here is what matters, and it is verifiable. The PRAG governs the procurement and grant award procedures financed under the EU’s external action instruments. It covers the full lifecycle, from preparing the tender dossier to publishing notices, evaluation, award and contract implementation. It is the common reference for contracting authorities, beneficiaries, applicants and tenderers involved in EU-funded contracts.
In practical terms, for a consultancy in Accra or an NGO in Ouagadougou, this means one simple thing. When you respond to a contract paid for by an EU delegation, you are not playing a game where the rules shift with the committee’s mood. The rules are written, public and binding. You still have to read them in the right order.
Where the notices are published
A useful first move that costs nothing: know where the EU publishes. Calls for proposals and contract notices for external action run through the official EU Funding & Tenders Portal, and the full version of the PRAG is hosted on the Commission’s external action wiki, accessible with an EU Login account.
The information is not hidden. It is scattered. An EU-funded contract may appear on the central portal, but it may also be relayed by the delegation in the relevant country, by a specific thematic programme, or by an implementing partner. Tracking all of that by hand means an hour every morning sorting mismatched alerts. Time taken from writing and from fieldwork.
The price fallacy
Here is the mistake I see most often, and it comes from a classic private-sector reflex: rushing to the costing. You receive a call, you compute a tight price, you assume you have a strong offer because you are cheaper. And you lose.
Why? Because many service contracts in international cooperation are not awarded to the lowest bidder. They are awarded on best value for money, against a grid that weights a technical score and a financial score. When the technical component carries significant weight in the total, optimising the price at the expense of proposal quality is a strategic error. You can be noticeably more expensive than a competitor and still win, if your technical score is higher.
Take the exam analogy. In a science baccalaureate, mathematics carries a coefficient of 8 and English a coefficient of 2. You can slip in English and still earn distinction if you excel in maths. A tender works on exactly the same mechanics. The scoring grid tells you where the points are. And most bidders never look at it before they write.
Read the weighting before the pen
The move that changes everything is not writing better prose. It is taking the dossier apart to extract three things, in this precise order:
- Exclusion and eligibility criteria. A missing administrative document, an unmet participation condition, and the file is dropped before the technical review even begins. It is the most common reason for elimination, and the most avoidable. You handle it first because it is binary: compliant, or out.
- Technical versus financial weighting. How many points for methodology, the expertise of the proposed experts, the timeline, comparable experience? How many for price? That ratio dictates where to invest your hours. A bid that elaborates a secondary section and rushes the decisive one loses on score, not on substance.
- The required format. Page limits, the language required, the mandatory structure, how and when to submit. A bid outside the format can be penalised or rejected, however strong its content.
One honest caveat, because it matters: the exact weightings vary from one contract to the next. Never start from a ratio you heard elsewhere as though it were the norm. Each dossier carries its own grid. The work is to read it in this one, not to assume the last one.
Once the grid is clear, the allocation of effort becomes obvious. You know where each writing hour earns points, and where it earns almost none. The bid/no-bid call is made there too: if the highest-weighted section demands a reference you do not hold, better to know it before writing thirty pages than the night before the deadline.
The real bottleneck
Everything above assumes one thing: seeing the call in time. And that is often where the game is lost, well before the writing.
An EU contract you discover three days before the deadline is already lost, even with the best technical score in the world. Response windows in international cooperation are tight, often a few weeks, sometimes less for restricted procedures. When three calls land in the same week and a terms-of-reference dossier routinely runs to 50-200 pages, analysing each one by hand takes half a day few teams have.
It is that lack of time, not a lack of connections, that makes firms miss good contracts. The loop is public. It is just poorly covered.
Where the tool saves time
This upstream work is exactly what Coco, the AI assistant in ICOpedia, speeds up. It reads a 47-to-200-page terms-of-reference dossier in three minutes, extracts the exclusion criteria, the technical-versus-financial weighting grid and the mandatory sections, and computes a match score against your profile.
Let us be clear about what it does and does not do. Coco tells you where the points are and where your offer is likely to fall. It does not write your bid for you: the methodology, the choice of experts, the technical argument, that is yours. What it spares you is two weeks spent on a contract you were never eligible for from page one, or spreading your effort blindly across a grid you never read.
And for detection, it is the same principle as for World Bank tenders: a watch that aggregates the sources and alerts you by sector and country, instead of leaving you to monitor ten portals one by one.
What to take away
On EU-funded contracts in Africa, the firms that win consistently are not the cheapest. They are the ones who read the grid before they write, who place their effort where the points are, and who say no quickly to contracts where they lack the decisive reference.
The PRAG is not one more regulatory wall. It is the map that tells you where the contract is won. Open it before you cost the bid, not after.
Want to read the weighting of your next EU tenders without spending half a day on each? Try ICOpedia free, seven days, no credit card.
