# The door is not the verdict.

Transparency does not make a project good. It lets you find out whether it is.

By Michael Cengkuru · 27 Jun 2026 · Interactive version: https://cengkuru.com/essays/the-door-is-not-the-verdict/

## The story

A door is marked Transparent Project. You expect to walk into a trophy room. You walk into an inspection room. Good, the inspector says, now: good by what test?

The tempting sentence arrives with the published record: the project is transparent, so the project is accountable, so the project, surely, is good. That sentence is easy to attack. Anyone can find one transparent project that failed and one secret project that worked, and the claim collapses. So this essay does not make it. It makes the harder, truer one. Without disclosure, you cannot test whether a project is good. With disclosure, you still have to run the test. Transparency is not the verdict. It is the light that makes a verdict possible. A visible contract is not yet a knowable project.

To show what that means, the essay runs six tests an inspector runs on one real published record, drawn from Zambia's OC4IDS field-level mapping. Each test resolves one of three ways. Sharp means the test can run: the field is published, structured and usable. Fogged means the record cannot answer: the data is missing, not collected, unstructured or unlinked. Locked means the answer is withheld by law, policy or workflow. None of these is a verdict on the road. They are a verdict on what the record lets you check.

Test one: who owns the contractor? Locked. The supplier is named and graded, but who owns or controls the firm is not collected in any reviewed system. The mapping records the cause as restricted by law or workflow, and the remedy as policy action, not a missing form. The Parties sheet fills 18 of 968 slots, and beneficial ownership is absent.

Test two: was procurement competitive? Sharp. Procuring entity, procurement method, number of bidders, cost estimate and contract price are published. This is the part the system is built to disclose, and it does.

Test three: did the price change? Fogged. Contract variations are captured by the National Council for Construction under its monitoring mandate, but they never reach the public e-GP system. The change exists; the public record of it does not.

Test four: did the project finish on time? Fogged. Progress updates, payment certificates and actual completion dates are collected inside government but are not integrated into any public system. You can see the project was awarded, not whether it landed on time.

Test five: was the asset maintained? Fogged. Maintenance schedules, cost logs and inspection data are not captured in any reviewed system. This is not withheld; it is simply not collected, so the test cannot even be built yet.

Test six: can anyone verify the record? Fogged. The Linked Releases sheet is empty, 0 of 6, and most implementation evidence sits in unstructured forms or behind the disclosure line. A record you cannot attach proof to, or link to others, can be read but not verified.

The tally: 1 sharp, 4 fogged, 1 locked. One test can run. Five cannot. Visible is not the same as testable. The record is bright on the questions a procurement system likes to answer, and dim on the ones an inspector needs answered. The door was real. The trophy was not.

The evidence behind the table is real. Zambia's mapping analysed a purposive sample of 76 procurement records on the ZPPA e-GP platform for FY2023 to FY2024, spot-checked against live records in February 2026. It found 35 OC4IDS fields publishable today, 55 within 12 months, and roughly 25 needing policy action, including beneficial ownership, maintenance and decommissioning.

Disclosure does not fail at random. It thins along the life of the project. Phase by phase, the mapping's coverage runs: Identification 28 percent, Preparation 12 percent, Procurement 21 percent, Implementation about 2 percent, Completion 8 percent, Maintenance 0 percent, Decommissioning 0 percent. The pattern is structural, not accidental: in four of the seven phases the dominant cause is "collected but not yet disclosed". The data already sits inside government; it just never reaches the public. Maintenance and decommissioning score zero because no reviewed system collects them at all.

Even a record that passes every test can teach you nothing on its own. The questions that matter most are portfolio questions: what share of contracts has no disclosed owner, is that share rising, which sectors disclose least, can the records even be linked. Those need every record, structured the same way, reachable in bulk. That is usability, and it is a separate build from disclosure. Uganda's Government Procurement Portal makes the point: it meets 17.6 percent of OC4IDS requirements, 26 of 148 data elements, and 4.2 percent of project-level disclosure paths. It can tell you who won which contract. It cannot yet tell you whether the works were finished on time, within budget, or to the commitments made.

The close turns each gap into a work order. A locked test is not the record failing to try; it is the record showing you exactly where the next reform has to happen. Beneficial ownership needs policy change, not a database column. Variations and completion data need a disclosure switch flipped on data government already holds. Maintenance needs a capture workflow that does not yet exist. The honest verdict is not "this project is good." It is "this project can now be tested." That is a smaller claim, and a far harder one to take away from you.

## The data

### The six inspection tests

| # | Test | What it checks | Verdict | Evidence as the essay states it |
|---|------|----------------|---------|---------------------------------|
| 1 | Who owns the contractor? | beneficial ownership | Locked | Parties sheet: 18 of 968 slots; beneficial ownership needs policy action |
| 2 | Was procurement competitive? | method, bidders, award | Sharp | Procurement phase fields populated and publishable |
| 3 | Did the price change? | contract variations | Fogged | Implementation phase about 2% disclosed; variations held by NCC, not public |
| 4 | Did the project finish on time? | progress, completion date | Fogged | Completion phase 8% disclosed; deviation reasons held by NCC and audit bodies |
| 5 | Was the asset maintained? | maintenance schedules, inspections | Fogged | Maintenance phase 0% (not collected) |
| 6 | Can anyone verify the record? | documents, linkable releases | Fogged | Linked Releases 0 of 6; implementation evidence not public |

Tally: 1 sharp, 4 fogged, 1 locked. 1 test can run. 5 cannot.

### Lifecycle disclosure coverage (Zambia mapping, true percentages)

| Phase | Coverage | Dominant cause |
|-------|----------|----------------|
| Identification | 28% | mixed (some not collected) |
| Preparation | 12% | held by line ministries |
| Procurement | 21% | collected, partly disclosed |
| Implementation | 2% | collected, not yet disclosed |
| Completion | 8% | collected, not yet disclosed |
| Maintenance | 0% | not collected |
| Decommissioning | 0% | not collected |

Coverage is fields mapped against applicable OC4IDS slots per phase. In four of the seven phases the dominant cause is "collected but not yet disclosed".

### Evidence states as the essay labels them

| State | Meaning |
|-------|---------|
| Sharp | The test can run: the field is published, structured and usable |
| Fogged | The record cannot answer: missing, not collected, held only as unstructured documents, or impossible to link |
| Locked | Present somewhere but restricted by law, policy or workflow: withheld by design |

The axis is testable versus not testable, not good versus bad. A project can be sharp on every test and still be a bad road.

## Sources

- CoST Zambia OC4IDS v0.9.5 field-level mapping (CoST Zambia, National Council for Construction, Zambia Public Procurement Authority), model report, 20 May 2026, published under CC BY 4.0. Purposive sample of 76 procurement records on the ZPPA e-GP platform, FY2023 to FY2024, spot-checked against live records on 17, 18 and 20 February 2026. Anchor for the inspection table and the lifecycle bars.
- Uganda Government Procurement Portal (PPDA) assessment: 17.6% of OC4IDS requirements met, 26 of 148 data elements, 4.2% of project-level disclosure paths. CoST Uganda and Shift Media News, 2022.
- OC4IDS, the Open Contracting for Infrastructure Data Standard, is the standard the mapping tests against.
- BODS, FATF Recommendation 24 and Open Ownership are reflected as general principle only, not quoted as findings, because they sit outside the verified materials behind the essay.

Companion essays, where the argument runs against real records in the field:

- The Name on the Certificate Is Not the Owner (test 1, the ownership x-ray): https://cengkuru.com/essays/the-name-on-the-certificate/
- The Road May Be Complete. The Record Is Not. (test 6, Malawi, 162 projects): https://cengkuru.com/essays/the-scanner-under-the-portal/
- After the Award (tests 3 to 5, the record thins after the award): https://cengkuru.com/essays/after-the-award/