# Launch Is Not Landing

A launch proves the portal exists. Only use proves it landed. Training 143 officers did not close the work. It revealed where the portal still models contracts instead of delivery.

By Michael Cengkuru · Interactive version: https://cengkuru.com/posts/what-143-officers-taught-me-about-training/

## The story

On 8 and 9 April 2026 in Kampala, 143 officers from 59 public bodies sat with a live government procurement portal that already listed 395 projects. The training was not a demo day for a brochure. It was a room full of people who had to finish real procurement work on a system that had been declared ready.

Three plain gates mark whether a disclosure system has actually landed.

Gate one is regulator sign-off: the institution accepts responsibility. PPDA owning the portal proves institutional responsibility. It does not prove officers can use the system.

Gate two is officer training: real users test the system against real work. The April sessions tested whether officers could complete real procurement tasks. Training can prove usability under supervision. It cannot prove the data is correct over time.

Gate three is data quality over time: the public can trust and reuse what is published. That gate was still pending. It is the one that turns a live URL into a public good.

The ownership chain is simple. A build team hardens workflow assumptions. The regulator accepts institutional responsibility for adoption. Agencies test the portal against actual procurement. Public use only begins when trusted data can be reused.

In the room, one officer's edge-case question collapsed a design assumption that had survived for a year. The portal's model could describe who won which contract. It could not answer, cleanly, how three different procurement methods branch through delivery, completion, and the commitments that matter after award. The anecdote and the measurement are the same problem.

The documented coverage gap makes that concrete. An assessment cited by CoST Uganda and Shift Media News found 26 of 148 OC4IDS elements published, about 17.6 percent coverage, and only 4.2 percent of project-level disclosure paths mapped. The portal can publish who won what. It cannot publish whether works were completed on time, within budget, or to environmental and social commitments. Contracts without delivery are a receipt book without a roof.

There is also an OCDS publication trail, January 2019 to January 2025, available as JSON, Excel, and CSV from the Open Contracting Partnership Data Registry. Contract-level publication is not the same as project-level delivery transparency. OC4IDS is the standard that connects the two. Until more of that path is mapped, officers will keep hitting the fracture the training surfaced.

Launch, then, is a beginning. Landing requires the three gates in sequence, and the data model has to match the work people actually do: not only award, but delivery.

## The data

| Figure | Value | Source | Confidence |
| --- | --- | --- | --- |
| Officers trained | 143 | GPP training, Kampala | Observed (8-9 April 2026) |
| Public bodies | 59 | GPP training, Kampala | Observed (8-9 April 2026) |
| Live projects on portal | 395 | GPP at time of training | Observed (8-9 April 2026) |
| OC4IDS elements published | 26 of 148 | CoST Uganda / Shift Media News | Cited (2022 assessment) |
| OC4IDS coverage | 17.6% | CoST Uganda / Shift Media News | Cited (2022 assessment) |
| Project-level disclosure paths mapped | 4.2% | CoST Uganda / Shift Media News | Cited (2022 assessment) |
| OCDS contracting processes published | Jan 2019 to Jan 2025 | OCP Data Registry (publication 130) | Cited (retrieved Apr 2026) |

## Sources

- First-person account of GPP training, Kampala, 8-9 April 2026
- CoST Uganda / Shift Media News reporting on OC4IDS coverage
- Open Contracting Partnership Data Registry, publication 130

## The verdict

A portal can go live and still not land. Training surfaces the fracture. Closing it means publishing delivery, not only awards, and treating data quality over time as a gate equal to launch day.