Practice 2026

Data for the
public good.

Open standards. Working systems.
The institutional capability to
keep them honest.

I work where open data standards meet the public spending, public investment, and public ownership records they describe. Mapping fields, wiring publication and validation, and building the institutional muscle to keep the data current and trustworthy long after the launch event is over. Deepest in OC4IDS. Present across OCDS, EITI, BODS, and adjacent standards.

Pen-and-ink illustration of a single bend of empty country road seen from directly above, drawn in matte obsidian line work with a restrained aluminium grey wash on the road surface. One short vermillion line is drawn alongside the outer edge of the bend as a small mark of attention.
One bend. One small mark of attention.

The practice, in three movements

Standard. System. Capability.

The work cuts across data standards and domains. The shape of it does not change.

01

Standard

Mapping public-interest data to the standard that fits it. Procurement to OCDS or OC4IDS. Extractives to EITI. Ownership to BODS. Whatever the domain, the work is the same: make the data comparable, publishable, and verifiable against a public definition.

  • Field-level mapping and gap analysis
  • Cross-standard migration and harmonisation
  • Validation, quality assurance, and review
  • Working with the schema, not around it

Deepest OC4IDS field-level mapping reviews across CoST member countries

02

System

The publication and oversight layer that turns a standard into a working public asset. Data model, API, validation routines, dashboards, anomaly signals. The system is what makes the standard usable; a portal is just one of its surfaces.

  • Publication layer, API, validation
  • Oversight dashboards and red-flag logic
  • Freshness, quality, and integrity signals
  • Recovery roadmap for stalled systems

Reference Kaduna State, Nigeria · 1,496 infrastructure projects published with cost, timeline and completion data

03

Capability

A standard and a system only survive when the institution can run them. Capability work transfers the practice into the team - their data, their workflows, their decisions, their muscle. I leave the institution stronger, not more dependent.

  • Implementation training for government teams
  • Using disclosure data for oversight
  • Data-quality routines and publication governance
  • Hands-on clinics with the institution’s records

Reference Uganda, Ghana, Malawi, South Sudan · in-country clinics with government teams

Disclosure without verification
is performance.

Data without accountability
is noise.

Pen-and-ink illustration of two columns of small horizontal tally-marks side by side on ceramic paper. The left column has every mark aligned, evenly spaced, drawn with discipline. The right column has the same number of marks but each one skewed at a slightly different angle, lengths uneven. One short vermillion check is drawn beside the topmost mark of the left column only; the right column has no mark. Drawn in matte obsidian line work with restrained aluminium grey wash.
Same count. One verified.

Receipts

Where the practice has run.

Seven engagements across twelve years. The bars overlap because the work overlaps — the practice has rarely been one country at a time.

  • Standard field-level mapping
  • System working portal
  • Capability transferred to team
  • Active still running

Years are engagement spans, not contract dates. Bars marked “present” are still active.

If you are working on this, I am happy to compare notes

No pitch deck. A conversation.

Write to me