Open Data

The registers ZEPRA publishes, what is in them, how current they are and what may lawfully be done with them.

Two licences apply, and they are not the same. ZEPRA's own structuring, identifiers and annotations are published under Creative Commons Attribution 4.0 International (CC BY 4.0). The underlying records remain subject to the terms of the institution that published them, which ZEPRA cannot alter or extend. Each dataset states its source terms, and every row carries its source.

Datasets

Project register

Every published project record, with budget, delivery stage, location, reported completion and source attribution.

Records: 930
Of which demonstration: 0
Last updated: 19 Oct 2026
Standard: OC4IDS-aligned project fields

CSV JSON

Procurement register

Published procurement processes, from plan and invitation through evaluation to award or cancellation, linked to their project where a link is known.

Records: 178,733
Of which demonstration: 0
Last updated: 13 Oct 2026
Standard: OCDS 1.1 tender fields

CSV JSON

Contract awards

Published contract awards with supplier, value, period, amendments and tender reference.

Records: 30,076
Of which demonstration: 0
Last updated: 19 Oct 2026
Standard: OCDS 1.1 award and contract fields

CSV JSON

Every record in these downloads comes from a published official source. The register holds no test or illustrative rows. Every row carries an is_demonstration column so that the guarantee can be checked rather than taken on trust.

Documentation

Data dictionary Every published field, its type and what it actually means.
Data quality methodology How records are validated, matched, scored and labelled.
API documentation Programmatic access to the same registers.
Source coverage Which institutions ZEPRA collects from, and under what terms.
Changelog What has changed in the published data and its structure.

Update frequency and coverage

Published projects: 930
Procurement processes: 178,733
Contract awards: 30,076
Sources last returned: 19 October 2026 at 03:15 Connectors run on their own schedules; see source coverage for each.
OCDS version: 1.1
OC4IDS version: 0.9
Publisher prefix: zm-zepra

Known limitations

These are stated plainly because a dataset used without them can mislead.

Coverage is partial. ZEPRA holds records from the sources connected so far. Absence from these datasets does not mean a project or tender does not exist.
Retrieval is not verification. A record a connector fetched successfully is labelled Imported automatically, not Source verified. Only a record a person has checked against its source carries a verified label.
Coordinates are sparse and never inferred. Latitude and longitude are populated only where the responsible institution published a site location. ZEPRA does not substitute an administrative centroid.
Physical completion is a reported figure. It is what an institution stated, on the date stated. It is never calculated from expenditure.
“Not assessed” is not “on track”. Most records carry no delivery assessment. Treating an unassessed project as on track would misrepresent the data.
Demonstration rows exist. They are excluded by default and flagged in every export. They are not government records.
Linking is conservative. A procurement process is linked to a project only where the connection is published or confirmed by a data steward, so many processes show no project link.