---
canonical: https://trinta.ai/blog/open-contracting-data-ocds-eforms-and-the-structured
language: en
updated: 2026-09-24
publisher: "TRINTA"
publisher_url: https://trinta.ai
---
# Open Contracting Data: OCDS, eForms, and the Structured Procurement Web

> Open contracting data is making public procurement machine readable. Learn how OCDS and eForms work and what suppliers can build on top of them.

Source: https://trinta.ai/blog/open-contracting-data-ocds-eforms-and-the-structured · Published: 2026-09-24 · Category: AI & Technology · 4 min read
Keywords: open contracting data standard, OCDS procurement, eForms EU procurement, machine readable tender data, structured procurement data, open contracting partnership

For most of its history, public procurement has been a paperwork exercise dressed up as a website. A notice gets published as a PDF, a human reads it, a human decides whether to bid, and nothing about the process is designed for a machine to understand. That is changing, quietly but decisively, as governments adopt structured data standards that turn tender notices into something software can actually parse, compare, and act on.

Two standards matter most right now: the Open Contracting Data Standard, and the EU's eForms. Together they are building what amounts to a structured web layer sitting on top of public procurement, and it is worth understanding both if you plan to bid competitively over the next decade.

## What OCDS actually is

The Open Contracting Data Standard, maintained by the Open Contracting Partnership, is a common data model for describing the full lifecycle of a public contract: planning, tendering, award, contract signature, and implementation. Instead of a government publishing a tender as free text in whatever format a web developer chose that year, OCDS defines a consistent schema, fields for buyer identity, procurement method, value, deadlines, and award outcome, that any system can read the same way regardless of which country published it.

**The point is comparability.** A researcher, a journalist, or a piece of matching software can pull data from a dozen different national portals and treat it as one dataset, rather than writing a custom parser for each one. Countries across Latin America, Africa, and Eastern Europe have adopted OCDS to varying degrees, often as part of broader transparency and anti-corruption commitments, since open contracting data makes it far harder to quietly steer a contract to a favoured supplier.

## What eForms changes in the EU

The European Union's equivalent effort is eForms, the standardised set of electronic forms that contracting authorities across the EU now use to publish notices to TED. Before eForms, national procurement portals fed TED in wildly inconsistent formats, and matching a construction tender in Poland against one in Portugal required handling two different structures. eForms replaces that patchwork with a single structured format built around the same kind of consistent fields OCDS champions: standardised codes for procurement procedure, contract nature, CPV classification, and lots identification.

The practical effect is that TED's underlying data is now considerably more reliable to build software against. Fields that used to require guesswork, is this an open or restricted procedure, is this contract divided into lots, are now consistently tagged, which matters enormously for anyone running automated matching at scale.

## Why this matters beyond government transparency

Open contracting data is usually framed as an anti-corruption and civic transparency tool, and that framing is accurate but incomplete. It is also, quietly, an infrastructure upgrade for every company that bids on public contracts.

**Search stops being the bottleneck.** When tender data is structured, finding relevant opportunities no longer depends on guessing the right keyword or checking the right portal on the right day. A system built on OCDS or eForms data can query directly for contracts in a given CPV category, value range, or country, and get a complete, structured answer.

**Comparison becomes possible at scale.** With consistent fields across markets, a company can start asking questions that were previously impractical to answer manually: which buyers award construction contracts fastest, which countries publish the highest volume of restricted procedures, where does the same buyer repeatedly award to the same small pool of suppliers.

**Award data closes the loop.** OCDS in particular tracks the full contract lifecycle through to award and, in more mature implementations, spending against the contract. That means a supplier can, for the first time in many markets, systematically study who wins and at what price, rather than relying on anecdote.

## The gap that remains

Structured data standards only help where governments actually implement them well. Plenty of OCDS-committed countries publish partial or inconsistently populated data, and eForms adoption across EU member states has been uneven in practice even where it is formally mandated. A standard is only as useful as the discipline behind its publication, and for the foreseeable future, structured feeds will need to sit alongside more traditional scraping and monitoring of portals that have not caught up.

Still, the direction of travel is clear. Procurement is moving from a system built for human readers toward one built for structured querying, and the companies that build their tender monitoring around that shift now will have a meaningful head start once the rest of the market catches up.

## Reading structured procurement data so you do not have to

Structured standards like OCDS and eForms are powerful, but only if something is actually watching them on your behalf and translating raw fields into opportunities worth acting on. TRINTA reads what your company sells and matches it against tenders surfaced daily from official procurement sources across Africa, Europe, the Middle East, and Latin America, structured feeds included, so the underlying data standard never has to be your problem.

## Frequently asked questions

**What is the Open Contracting Data Standard used for?**

OCDS is a common data schema for publishing information about public contracts through their full lifecycle, from planning through tendering, award, and implementation. It lets governments, researchers, and software treat procurement data from different countries as one comparable dataset instead of dozens of incompatible formats.

**What is eForms in EU procurement?**

eForms is the European Union's standardised set of electronic forms that contracting authorities use to submit procurement notices to TED. It replaced inconsistent national formats with a single structured schema covering procedure type, CPV classification, and contract details, making TED's underlying data much easier to query programmatically.

**Does open contracting data help small suppliers, not just researchers?**

Yes. Structured procurement data makes it possible to search and compare tenders across markets by category, value, or buyer without manually checking dozens of portals. It also allows suppliers to study award outcomes systematically, seeing which buyers award to which suppliers and at what price, information that was previously very hard to access at scale.

**Is procurement data fully machine readable everywhere now?**

No. Adoption of standards like OCDS and eForms varies considerably by country and even by contracting authority within the same country. Some publish complete, well structured data, others publish partial or inconsistent fields, and many smaller portals have not adopted structured standards at all, so gaps still need to be filled by monitoring the underlying websites directly.

**Who maintains the Open Contracting Data Standard?**

The Open Contracting Partnership maintains OCDS. It works with governments, civil society organisations, and technical implementers worldwide to define the schema and support countries adopting it as part of broader procurement transparency reforms.

---

All guides: https://trinta.ai/blog · Site index for agents: https://trinta.ai/llms.txt
