The door is not the verdict.
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, and why it is wrong.
The published record arrives and the temptation is immediate: 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.
Run the six tests an inspector runs.
One real published record, from Zambia's OC4IDS mapping. Each test is a question an inspector asks of the data. The lamp turns one of three ways: sharp means the test can run, fogged means the record cannot answer, locked means the answer is withheld by law or policy. None of these is a verdict on the road. They are a verdict on what the record lets you check. Tap a test to read it.
The record is bright on the questions a procurement system likes to answer, and dim on the ones an inspector needs answered. The price is sharp. Who controls the contractor is locked. Whether the asset was maintained is pure fog. The door was real. The trophy was not.
Disclosure does not fail at random. It thins along the life of the project.
Zambia's mapping checked its public procurement system against the OC4IDS standard, phase by phase. The light is strong where a project is being awarded, and collapses where it is being built, maintained, and retired.
Coverage is fields mapped against applicable OC4IDS slots per phase, from the CoST Zambia field-level mapping (76 records, FY2023–2024). 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.
Take the test that stayed locked: who controls the contractor?
The record names a supplier. It carries a registration number, an address, a contract value, even an NCC capability grade from one to six. All of it is sharp. None of it answers the question.
A grade tells you a firm has the financial capacity and equipment to build a road. It does not tell you who owns the firm, who controls it, or who is connected to the people awarding the work. In Zambia's mapping, the Parties sheet fills 18 of 968 slots; beneficial ownership is not collected in any reviewed system, and the root cause is not a missing form. It is recorded as restricted by law or workflow. The fix is policy, not a database column.
That is the difference between sharp and locked. A locked test is not the record failing to try. It is the record showing you exactly where the next reform has to happen.
A capability grade is not the same as knowing who benefits.
Disclosure is the first door. Usability is the corridor.
A single record can pass every test and still teach you nothing, if you cannot line it up against the others. The questions that matter most are portfolio questions.
Useful. But one record cannot tell you whether this is normal or an outlier.
These need every record, structured the same way, reachable in bulk. That is usability, and it is a separate build from disclosure.
Uganda's portal 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. A contract record is not yet an accountable project, and a portal is only the first door.
This is the argument. Here it is, three times in the field.
Each of these essays runs one of the six tests against a real record, and watches it fog or lock. This page is the principle; those are the evidence.
The Name on the Certificate Is Not the Owner
The supplier is named, sharp and certain. Who controls it stays locked. The ownership x-ray, in full.
Open the x-ray →The Road May Be Complete. The Record Is Not.
Malawi marks a road complete, priced, finished. The proof you would need to check it is missing. Across all 162 projects.
Run the scanner →After the Award
The record is brightest at the moment of award and thins after it. What happens to the project once the contract is signed.
Follow the record →Methodology, sources and the honest limits
Anchor data. The inspection table and the lifecycle bars are built from the CoST Zambia OC4IDS v0.9.5 field-level mapping (model report, 20 May 2026, published under CC BY 4.0). The team analysed a purposive sample of 76 procurement records on the ZPPA e-GP platform for FY2023–2024, spot-checked against live records on 17, 18 and 20 February 2026. Verified figures used here: 35 OC4IDS fields publishable today; 55 within 12 months; roughly 25 fields needing policy action, including beneficial ownership, maintenance and decommissioning. The Parties sheet fills 18 of 968 slots. Lifecycle coverage by phase: Identification 28%, Preparation 12%, Procurement 21%, Implementation about 2%, Completion 8%, Maintenance 0%, Decommissioning 0%.
Supporting data. The portfolio figures are from Uganda's Government Procurement Portal (PPDA): it meets 17.6% of OC4IDS requirements, 26 of 148 data elements, and 4.2% of project-level disclosure paths (CoST Uganda and Shift Media News assessment, 2022).
The three states. Sharp, fogged and locked describe testability, not quality. Sharp: the field is published, structured and usable. Fogged: missing, not collected, held only as unstructured documents, or impossible to link. Locked: present somewhere but restricted by law, policy or workflow. The states are deliberately not a good/bad colour scheme; a project can be sharp on every test and still be a bad road, and that is the whole point.
The subject record. The inspection table represents a published Zambian infrastructure record as the mapping characterises the system as a whole; individual field outcomes follow the mapping's phase-level and sheet-level findings rather than a single named project, so no project is accused of anything by name.
What this essay does not claim. It does not argue that open data prevents corruption, or that more transparency produces better projects. It argues only that disclosure is the precondition for testing a project, and that the test still has to be run. Source brief references to external standards (BODS, FATF Recommendation 24, Open Ownership) are reflected as general principle, not quoted as findings, because they sit outside the verified materials behind this build.
Transparency does not make a project good. It lets you find out whether it is.
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.
Anchor data: CoST Zambia OC4IDS mapping · CC BY 4.0 | Portfolio data: Uganda GPP / PPDA · CoST Uganda 2022 | Standard: OC4IDS
Analysis, derived framing, visual design and essay: Michael Cengkuru · Published 27 Jun 2026