CAYPAXThe Open Contracting Data Standard (OCDS), maintained by the Open Contracting Partnership, is the most widely adopted open standard for describing the public contracting process. Governments and multilaterals use it to publish planning, tender, award, contract, and implementation data as one connected release history.
OCDS answers “what happened” in a procurement process. F-Procure is designed to answer a complementary question: “can what happened be independently verified?” The two are naturally aligned across F-Procure's four evidence records.
Submission proof corresponds most closely to OCDS tender data, bid statistics, and submission milestones. F-Procure adds independent, tamper-evident proof of what was submitted and when, not just a published record of it. Due-diligence status corresponds to OCDS parties roles and qualification information; F-Procure adds a verifiable statement of which checks were completed, by whom, before which decision point. The approval trail corresponds to OCDS milestones and release history, adding a linked chronology connecting each decision to the delegation that authorised it. Contract linkage corresponds to the OCDS awards-to-contracts references, adding a durable, verifiable link from the executed contract back to the full award evidence.
This alignment has three design implications. First, OCDS-shaped identifiers: F-Procure evidence objects can carry OCDS release identifiers (ocid and release id), so that an evidence package can be joined to a published OCDS release history without transformation. Second, evidence as an assurance layer over disclosure: where an organisation already publishes OCDS data, F-Procure's evidence layer can reference the published releases, adding verifiability (fingerprints, anchor references, verification results) without duplicating disclosure. Third, exceptions stay visible: OCDS models amendments and cancellations, and F-Procure treats exceptions such as late submissions, missing checks, or out-of-sequence approvals as first-class evidence. The combination supports honest publication rather than tidy retrospection.
This is a statement of design alignment: F-Procure's reference architecture maps cleanly onto OCDS concepts, and our ERP-sync work already contemplates OCDS alongside UK Find a Tender formats. It is not a claim of certification, endorsement by the Open Contracting Partnership, or a production integration. F-Procure remains a published framework, reference architecture, and working MVP progressing toward carefully scoped institutional pilots.