OCDS, OCIDs and Compiled Releases: How Find a Tender Builds a Current Procurement View

Purpose: A plain-English explanation of the data concepts behind Summarised Search and what they mean for procurement research.

A plain-English explanation of the data concepts behind Summarised Search and what they mean for procurement research. This matters because public procurement decisions are rarely isolated events. A choice made during planning can affect competition, affordability, service quality, supplier behaviour and the ability to manage the contract later. The strongest approach is therefore to use the source guidance as part of an end-to-end commercial process, with clear ownership and evidence rather than as a document that is completed after the key decisions have already been taken.

Quick summary

• Find a Tender publishes structured data using the Open Contracting Data Standard, or OCDS.
• Each procurement has an OCID that is used to link notices across stages of the commercial lifecycle.
• Tender, award and later notices can therefore be connected to the same procurement process.
• Summarised Search uses the OCDS concept of a compiled release to combine information from multiple notices into a current-state record.
• The service derives or calculates selected fields in defined cases to improve filtering and sorting.

What the guidance means in practice

The source material gives several anchors for that process. Find a Tender publishes structured data using the Open Contracting Data Standard, or OCDS. Each procurement has an OCID that is used to link notices across stages of the commercial lifecycle. Tender, award and later notices can therefore be connected to the same procurement process. These are not interchangeable statements: some describe statutory or policy requirements and others describe recommended commercial practice. Teams should identify which category each requirement falls into, apply it to the organisation and procurement in scope, and keep a record of the judgement. Where guidance from 2021 or 2023 predates the Procurement Act 2023, its commercial principles can remain useful, but current legislation, regulations and current statutory guidance take precedence on legal process.

The practical value becomes clearer when the remaining guidance is read alongside the project lifecycle. Summarised Search uses the OCDS concept of a compiled release to combine information from multiple notices into a current-state record. The service derives or calculates selected fields in defined cases to improve filtering and sorting. Advanced users can access notice data in OCDS JSON format through the Find a Tender API. In day-to-day terms, this means the buyer should be able to answer three questions at any approval point: what outcome are we trying to achieve, what evidence supports the proposed commercial approach, and what will need to be managed after the decision is made? If those answers are weak, more analysis is normally more useful than adding another layer of narrative to an approval paper.

A practical process to follow

A proportionate process can be built into existing governance. The steps below are deliberately practical. They are not a substitute for the detailed source guidance, legal advice or local standing orders, but they provide a useful structure for a procurement or commercial team.

1. Step 1. Use the OCID as the consistent reference when following a procurement through its lifecycle. Record any assumption that could change the conclusion and when it will be reviewed.
2. Step 2. Read the summarised record to understand the latest picture. Keep the analysis proportionate to the value, risk, novelty and criticality of the requirement.
3. Step 3. Check the latest notice type where status or timing is important. Capture the source evidence and name the person accountable for the next decision.
4. Step 4. Open individual notices when exact legally published information is required. Record any assumption that could change the conclusion and when it will be reviewed.
5. Step 5. Be aware of fields documented as derived rather than copied directly from a notice. Keep the analysis proportionate to the value, risk, novelty and criticality of the requirement.
6. Step 6. For repeat data analysis, record the extraction date because compiled records can change. Capture the source evidence and name the person accountable for the next decision.

What good looks like

Good practice is visible in the decision trail, not only in the final document. A reviewer should be able to follow the line from the service need, through market and cost evidence, to the route, evaluation, contract terms and management arrangements. Where several functions contribute, the file should show who owns each decision and where challenge occurred. The same principle applies to handover: useful assumptions, models, KPI definitions, risks, supplier information and approval conditions should move into mobilisation and contract management instead of being left in the sourcing archive. This continuity is particularly important for long-running public services, where staff can change but the organisation remains accountable for the outcome.

Recommendations for procurement teams

The following recommendations are suitable for teams that want to embed the topic into normal ways of working rather than create a parallel compliance process:

• Teach analysts what the OCID represents so notices are not double-counted as procurements.
• Separate current-state intelligence from event-by-event audit work.
• Use machine-readable data when repeat analysis justifies it.
• Retain source notice references behind important commercial conclusions.
• Re-run analysis when new notices are published.
• Treat the compiled view as a navigation and analysis aid, not a replacement for notices.

Common pitfalls to avoid

The most common problems are usually process failures rather than a lack of templates. Watch particularly for the following:

• Counting every notice as a separate procurement.
• Assuming every displayed field came directly from the latest notice.
• Using an extract without recording its date.
• Ignoring notice history when a procurement has materially changed.

Easy-to-read takeaway

For ocds, ocids and compiled releases: how find a tender builds a current procurement view, the core discipline is to start early, connect the analysis to a real decision and preserve enough evidence for the next stage of the lifecycle. The source material should help teams make better decisions, not merely produce more paperwork. Before acting on a live procurement, confirm the current version of the Procurement Act 2023, regulations, Procurement Policy Notes and any organisation-specific approvals or delegations. This is especially important for thresholds, notice duties, exemptions and policy requirements that can change over time.

Source basis

Primary source used: Find a Tender: Help and Support for Summarised Search. Related articles in this collection also draw on the other supplied Cabinet Office, HM Treasury and Procurement Act materials where the topics overlap.

This article is general procurement support content. It should be read alongside current legislation, statutory guidance and your organisation’s own governance and legal advice.