When a project becomes public.
A project can be visible in concrete and still hidden in truth. To make it public, five links have to hold.
Public infrastructure is built in the open. Its truth is filed somewhere else.
The concrete is visible. The truth of the project, though, lives in files, portals, contracts, and explanations only insiders can decode. A sign on a barrier is not a project you can follow.
To understand the CoST toolkit, follow five public questions. The tools are often introduced as separate products. They are better understood as one chain: each link answers one question, and a chain is only as strong as its weakest link.
Five questions. Five links. One public project.
First, make the project followable.
IDS gives the project enough facts to be followed — the minimum a citizen needs across identification, preparation, procurement, delivery and completion, not just the moment a contract is awarded.
Without these facts, citizens cannot ask precise questions. They can only suspect.
Then give every fact a stable place.
IDS names the facts. OC4IDS gives each fact a stable place — a common structure so a portal, an analyst, a journalist and an oversight body all read one record the same way, connecting the project to the contracts underneath.
OC4IDS is not a trophy checklist. It is a shared structure. Structure does not prove quality. It makes quality testable. A record can pass schema validation and still be thin — which is exactly why the next link exists.
Same project. Same meaning. Readable across portals, systems, and users.
Disclosure is a claim. Independent Review tests it against reality.
Publishing data is not the finish line. An independent reviewer asks whether it is accurate, complete and understandable — comparing the published claim against the documents and the ground, then turning technical data into findings a non-specialist can use.
Illustrative trace, not a real project finding: it shows the shape of independent review. The two flags — a short delivery and an unrecorded change — are exactly what review exists to surface and explain in plain language. That is the link bending, then breaking open, under weight.
Trust begins when the record survives contact with the ground.
Now measure the system, not just the project.
ITI does not ask whether one project is visible. It asks whether the whole infrastructure system is becoming more transparent — a 0–100 score across four dimensions and 93 indicators, designed to be read again over time.
12 + 25 + 12 + 44 = 93 indicators, anchored as four bolts and rolled into one weighted score. The needle hangs from the chain; the dimensions hold it up. No country score is asserted here — the gauge shows where measurement happens and why direction, not rank, is the point.
A score read once is a ranking. A score read again is a direction.
Finally, the public can act.
Data only matters when someone uses it. The user does not have to be imaginary. The question can be real — and any of these users can re-run it.
of competitive infrastructure tenders attracted only one bidder. A single-bid rate is a risk flag, not proof of wrongdoing — it tells oversight where to look first.
Figures are a fixed snapshot of the live dashboard as read in June 2026; the dashboard recomputes, so your number may differ — that standing recomputation is the point, not a flaw.
Transparency is not the portal. Transparency is what the portal makes possible.
One chain, not five products. Pull a link out and watch what fails.
A chain is only as strong as its weakest link. Remove any one and the project stays visible but never followable. Tap a link to take it out.
Tap any link to remove it · tap again to restore
A project becomes public when people can follow it, read it, test it, measure progress, and use the evidence.
Not five disconnected tools, but one chain of public trust. The chain you followed is the whole point — it never let go of the project.
Continue the chain. Three links, run against real records.
Each companion essay takes one question and watches it pass or fail on a real published record. This page is the chain; those are it in the field.
The Door Is Not the Verdict
Transparency does not make a project good. It lets you test whether it is. Six inspection tests on a real Zambian record.
Run the tests →The Road May Be Complete. The Record Is Not.
Malawi marks a road complete, priced, finished. The proof you would need to verify it is missing. Across all 162 projects.
Run the scanner →After the Award
The record thins after the award, but the risk grows. Run the real query: 28.5% of competitive tenders attract one bidder.
Follow the record →Sources, terminology and the honest limits
Terminology. CoST materials previously referred to the independent check of published data as Assurance; CoST's Data Publication Manual now frames the approach through four pillars — data publication, independent review, multi-stakeholder working, and social accountability — and this essay uses the current term, Independent Review. The "five questions" are a storytelling structure for following the toolkit, not an official set of "five tools": IDS and OC4IDS sit inside the data-publication journey, and ITI is a measurement tool that can also be applied on its own.
IDS and OC4IDS. CoST IDS promotes publication of 40 proactive data points and 27 reactive disclosure items across the project lifecycle, covering both project and contract data. OC4IDS gives infrastructure project and contracting data a common structure so siloed information becomes comparable and usable. Schema validation alone does not prove data quality — structure makes quality testable, which is the bridge to Independent Review.
ITI. The Infrastructure Transparency Index scores on a 0–100 scale to assess and monitor transparency over time, across four dimensions: enabling environment; capacities and processes; citizen participation; and data publication. The indicator structure shown (12 + 25 + 12 + 44 = 93) follows the ITI manual. No country or sub-national ITI score is asserted here; the gauge illustrates structure and direction, not a measured result.
The real numbers, with a fixed snapshot. The single-bid figure is a snapshot of Uganda's GPP infrastructure dashboard, Competition view (PPDA), as read in June 2026: 543 tenders, 28.5% single-bid, 3.6 average bidders, 393 projects, UGX 4.0T. A single-bid rate is a risk flag, not a finding of wrongdoing. Because the dashboard recomputes, a later read may differ; the snapshot date and view are stated so the essay does not silently depend on changing live data. Separately, prior assessment found the GPP portal meets 17.6% of OC4IDS requirements (26 of 148 data elements), 4.2% of project-level disclosure paths (CoST Uganda, 2022).
Illustration and method. The opening project sign, the three SVG scenes (site, inspection, public hearing), the Link 1 fact tags, the Link 2 data route and the Link 3 verification trace are illustrative, drawn structures — no photographs, no invented named people, no specific project accused by name. The only hard figures stated as fact are the CoST framing counts (40 / 27 / 93 and the dimension split) and the Uganda GPP snapshot above. Page legibility is enforced against WCAG AA by an automated contrast audit of the rendered page.
Standards & framing: CoST IDS / OC4IDS / Independent Review / ITI · official | Portal data: Uganda GPP / PPDA · CoST Uganda 2022 + dashboard snapshot Jun 2026
Analysis, derived framing, chain mechanism, illustration and essay: Michael Cengkuru · Published 29 Jun 2026