Open Contracting Data Standard 1.1.5
OCDS defines a common data model for publishing data and documents across planning, tender, award, contract, and implementation stages of public contracting.
What the authority record establishes
OCDS defines a common data model for publishing data and documents across planning, tender, award, contract, and implementation stages of public contracting.
Voluntary unless required by an implementing authority or funder
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
Public-procurement systems can be evaluated for identifiers, stage continuity, releases, records, documents, data quality, and publication interfaces rather than only front-end tender workflows.
Affected operating stages
- Planning
- Tender
- Award
- Contract
- Implementation
- Publication And Analysis
Capabilities to examine
Request Intake And Procurement Orchestration
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for request intake and procurement orchestration.
Strategic Sourcing And RFx Management
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for strategic sourcing and RFx management.
Contract Authoring, Repository, And Obligation Handoff
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for contract authoring, repository, and obligation handoff.
Supplier Onboarding And Master-Data Governance
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for supplier onboarding and master-data governance.
Supplier Network, Portal, And Transaction Collaboration
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for supplier network, portal, and transaction collaboration.
Purchase Order And Change-Order Management
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for purchase order and change-order management.
Savings Pipeline, Value Tracking, And Performance Analytics
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for savings pipeline, value tracking, and performance analytics.
ERP Integration, Data Lineage, And Access Governance
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for ERP integration, data lineage, and access governance.
Affected buyer audiences
- public contracting authorities
- open-data teams
- civic and oversight organizations
- e-procurement providers
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
An OCDS-compatible export does not establish procurement legality, data completeness, value for money, or effective public oversight.