Quick answer
An OCDS record is the compiled, up-to-date snapshot of a complete public contracting process, formed by merging all individual OCDS releases for that process into a single document that shows the current state of every procurement stage alongside a full audit trail.
In the Open Contracting Data Standard (OCDS), a record is the definitive, merged view of a single contracting process. While releases capture individual events as they happen, the record answers the question: "What is the current state of this procurement, in full?" It is the primary object that most procurement intelligence platforms index and surface to users.
What is an OCDS Record?
An OCDS record is generated by merging all releases that share the same contracting process identifier (OCID). The merge process follows defined rules: fields from later releases overwrite fields from earlier releases of the same type, producing a current, non-contradictory view of the whole process.
A well-formed OCDS record contains:
- A "compiledRelease" section: the merged, current-state view of all procurement stages (planning, tender, award, contract, implementation), reflecting the latest information for each field.
- A "versionedRelease" section (optional but recommended): a history of how each field changed across releases, enabling point-in-time reconstruction.
- A "releases" list: references to all the individual releases that make up the record, allowing downstream consumers to retrieve the raw event log.
The record is what a supplier sees when a procurement platform displays a "full contract overview." The data fields shown (value, award date, winning supplier, contract duration) are drawn from the compiled release within the record.
Why OCDS records matter for bidders
Records are the practical entry point for market intelligence. Rather than reading a sequence of individual releases, a bidder consulting an OCDS-powered platform sees a single, coherent summary: the tender details, who won, the awarded value, and any contract amendments. This makes it straightforward to build a buyer spending profile, identify incumbent suppliers, or compare contract values across similar categories.
High-quality records also reveal gaps. If a record has a tender stage but no award stage, the contract may still be under evaluation, or the publisher may not have issued an award release. If the implementation stage is absent entirely, the buyer has not yet published delivery or payment data. Recognising these gaps helps bidders assess both the opportunity pipeline and the data reliability of a given market.
Example
A French contracting authority issues five releases over 18 months for a facilities management contract. The publisher generates an OCDS record by merging all five releases. The compiled release shows: estimated value EUR 1.2 million (updated from the original EUR 900,000 via a tenderUpdate release), award to a named supplier at EUR 1.1 million, and a contract signed for 36 months. The versioned release shows that the scope was expanded at month two, explaining the value increase. A competitor bidding on a similar contract in the same region can use this record to calibrate their own pricing.
Frequently Asked Questions
Is a record the same as a contract notice?
No. A contract notice (as required under Directive 2014/24/EU or the UK Procurement Act 2023) is a legal publication announcing an opportunity or an award. An OCDS record is a structured data object that may incorporate information from multiple legal publications, including the notice, the award announcement, and subsequent contract documents. The record is richer and more machine-readable than the original notice.
How often is a record updated?
A record is updated each time a new release is published for that contracting process. In practice, update frequency depends on the publisher's internal systems and publication obligations. Some authorities publish in near real time; others batch-publish monthly. The Open Contracting Partnership tracks publisher timeliness as part of its data quality assessments.
Can two records share the same OCID?
No. The OCID is unique to a single contracting process within a given publisher's namespace. Each publisher registers a prefix with the Open Contracting Partnership, ensuring that OCIDs are globally unique across all publishers.
How Bidovate helps
Bidovate puts OCDS Record to work inside your capture and proposal workflow.
Tender discoverySee Bidovate in action
Book a demo and we will show you the platform using your actual contract data.
Related terms
OCDS Release
An OCDS release is a single, timestamped JSON document that records one event or change in a public contracting process, such as publishing a tender notice or announcing a contract award, and is the fundamental unit of data publication under the Open Contracting Data Standard.
ViewOpen Contracting Data Standard (OCDS)
The Open Contracting Data Standard (OCDS) is a global open data specification that defines how governments should publish structured, machine-readable information about public procurement processes, from planning through contract implementation, to improve transparency and enable analysis.
ViewContracting Process Identifier
A contracting process identifier (OCID) is the globally unique persistent identifier assigned to a single public procurement process in the Open Contracting Data Standard, linking every release and record across all stages of that process from planning to implementation within a single traceable chain.
ViewOCDS Planning Stage
The OCDS planning stage is the first lifecycle phase in an Open Contracting Data Standard record, capturing pre-procurement information such as budget allocation, rationale for the purchase, and procurement forecasts before a formal tender notice is issued.
ViewOCDS Tender Stage
The OCDS tender stage is the procurement phase captured in Open Contracting Data Standard releases that documents the publication of a contract opportunity, including notice details, estimated value, submission deadline, eligibility requirements, and any subsequent amendments before award.
View