Data sources

Documents supplied directly to ZEPRA by the project coordinator. Held with restricted access; not redistributed.

The Authority’s published past-projects register (2005 onwards, with contractor, contract sum and dates for the current programme) and its current grid development sites.

ZPPA publishes e-GP data under ODC-PDDL 1.0. Users may copy, distribute, use, produce works from, modify, transform and build upon the data.

Compiled OCDS releases carry tender, award and supplier information. Procuring-entity and supplier contact points present in the feed are deliberately not imported: ZEPRA holds organisation identity, not contact details.

Robots policy permits retrieval. Page extraction is held back because the OCDS publication already carries the same procurement records in structured form; this connector would only add notices that OCDS does not cover.

Enable only for notice categories absent from the OCDS feed, and only after confirming ZPPA has no objection.

Annual procurement plans are submitted through the e-GP system. No public bulk endpoint is published.

Reaching these means going through e-GP, which is behind authentication. ZEPRA does not read behind an access control; a data-sharing agreement is the only route.

The e-GP platform is the authoritative transactional system. Direct integration requires a written data-sharing agreement and credentials issued by ZPPA.

ZEPRA links suppliers back to e-GP for every action; it does not and must not attempt to read behind its authentication. A data-sharing agreement is the only route to direct integration.

Published as budget documents. Terms of reuse are not stated on the publication, so redistribution is withheld pending written confirmation.

The most valuable single source for approved project budgets and financial years. Priority for an institutional data-sharing agreement.

Reuse terms are not stated on the publication, so redistribution is withheld pending written confirmation.

Carries appraisal and approval status, which is what separates a pipeline entry from an announcement. The ministry host was unreachable from ZEPRA's server when this was registered, so no retrieval has been attempted.

Project lists are published periodically. Reuse terms unstated.

PPP projects carry a different financing structure and must not be shown as fully budget-funded.

No structured public dataset identified. Institutional submission through the ZEPRA workspace is the intended route.

No structured public dataset identified.

CDF reporting is published by councils in varying formats. Each council must be registered as its own source before ingestion.

CDF carries the largest count of small projects in the country. Expect a high volume of low-value records and plan deduplication accordingly.

Published openly by the agency on its own website as part of its statutory reporting.

Read from the published PDF. Only the current plan year produces upcoming projects; superseded years are kept as planning records, because a project that was new in 2016 is not upcoming now.

No structured public dataset identified at registration. Road projects are corridor-shaped and need route geometry rather than a point.

Serves /api/projects as JSON. The collection also holds unpublished drafts, which are skipped.

Registered individually as each body is onboarded.

Registered individually as each administration is onboarded.

Structured files and workspace entries supplied by the responsible institution, which retains ownership of and responsibility for the content.

Records arriving this way are labelled "Institution submitted" and are attributed to the submitting institution, never to ZEPRA.

Published openly on the Ministry's website without a stated licence. ZEPRA links to the Ministry's copy and retains the document to evidence what it read.

The Ministry publishes no projects API. Its document catalogue gives each publication's own title and publication date, which is the provenance the register needs. The Ministry's server omits an intermediate certificate; ZEPRA supplies it rather than relaxing verification.