Cengkuru Michael · Open data systems

I build the systems that make public spending harder to hide.

Since 2015. Seven countries. One discipline

Most disclosure portals die within three years. I work on the ones that survive, open contracting, infrastructure transparency, beneficial ownership, with the government teams who own them after I leave. Now: Data Specialist, CoST, Infrastructure Transparency Initiative

100,000+
contracts published through Uganda’s national portal
7
country systems across procurement and infrastructure data
2015
to present, still building and maintaining

Role

Data Specialist

CoST, the Infrastructure Transparency Initiative. Disclosure and monitoring systems with government teams across Africa.

Span

2015 to present

Started on Uganda’s National Procurement Portal. It now publishes 100,000+ contracts, and is still live.

Standards

OC4IDS · OCDS · BODS

Open Contracting for Infrastructure Data Standard. Open Contracting Data Standard. Beneficial Ownership Data Standard.

II · The origin

I started where most transparency systems break: inside the build.

In 2015 I started as a developer on Uganda’s National Procurement Portal. At first the work looked technical: data models, forms, publication flows, dashboards. The longer I sat with the institutions that had to own the system, the clearer the real problem became.

A disclosure system does not survive because it launched. It survives because the data keeps moving, the record can be checked, and the government team can run the routine after the build team leaves. That is a different job from building a website, and it is the job I have done ever since.

The lesson Disclosure without verification is performance. Data without accountability is noise.

II · The pattern

The homepage can look alive while the workflow is dying.

I have worked on procurement and infrastructure platforms across seven countries. The failure pattern is consistent. Governments want the system. Donors fund it. Most are dead within three years, not because the website broke, but because the work underneath it stopped: stale extracts, no link from procurement to delivery, no independent review, no real user task, and no funding for the pipeline once the launch money ends. The ones that survive keep the capability inside the government team, not the consultant.

II · The diagnostic

I look for the break in the record.

When I walk into a disclosure system, these are the questions I answer first. They decide whether the work becomes accountability or just another public website.

  1. 01

    Freshness

    Is the data still moving, and is updating a byproduct of the real workflow rather than a heroic manual chore?

  2. 02

    Linkage

    Can the procurement record connect to delivery, completion, quality, and location, or does it stop at the award?

  3. 03

    Verification

    Who checks the claim against reality, and what happens when the record turns out to be wrong?

  4. 04

    Use

    Can a citizen, auditor, journalist, engineer, or procurement officer finish a real task with it?

  5. 05

    Ownership

    Who inside the institution keeps the pipeline alive when the consultant leaves?

II · One scene

The question that breaks the demo is the work.

In Kampala, 143 officers from 59 public bodies tested Uganda’s Government Procurement Portal against 395 live projects. An hour into the second day, one officer asked what happens when a single project uses three procurement methods. The clean demo answer was not enough. The question exposed the real test: not whether the portal could publish a tidy example, but whether it could survive actual government work.

That is how I judge systems now. Not by the launch. By the question that breaks the demo.

III · Regional ledger

Where the method has been tested.

The map is not a travel record. Each point is a system receipt: a public owner, a data standard, an implementation role, and the visual layer that turns disclosure into decisions.

  1. 01 Map the source data
  2. 02 Validate the standard
  3. 03 Surface the decision
  4. 04 Transfer ownership
Seven sites, one route.

Method receipt

Hover a country

System
Seven sites, one route.
Role
Move across the map or ledger to inspect the work.
Authority signal
Country-specific implementation record.
  1. 01 Uganda Lead architect National Procurement Portal
  2. 02 Nigeria Technical assistance Open Contracting Disclosure Portal
  3. 03 Mozambique Implementation lead Infrastructure Transparency Portal
  4. 04 Kenya Technical assistance Kenya Tender Portal
  5. 05 Ghana Technical assistance GANEPS EGP system
  6. 06 Malawi Ongoing advisory Infrastructure Disclosure Platform
  7. 07 South Sudan Technical assistance National Procurement System

IV · Operating principles

The rules I work by.

  1. The portal is not the product. The pipeline is the product.
  2. A public record is only useful when someone can test it.
  3. Standards matter because they make records comparable, not because they look good in a proposal.
  4. Capability has not transferred until the institution can run the routine without me.
  5. The best system is the one that survives an ordinary Tuesday.

Working with me

I am useful when a disclosure system has to become real: a portal that is stale, a standard mapping that does not hold, a dashboard that cannot answer a hard question, or a government team expected to own a workflow built around them.

No pitch deck. Bring the record, the workflow, and the question the system needs to answer.

Write to me View services →