In a sector thick with announcements, the harder discipline is separating what a project has documented from what it has merely promised. The inauguration on 9 May of the Regional Rusumo Falls hydropower plant by Burundi, Rwanda and Tanzania is a case for that discipline. The task is to assemble what the primary record actually supports on this date, and to be equally clear about what it does not yet show.
The Evidence Pack: What The Primary Record Shows
The verifiable core is compact. An 80 MW hydropower plant on the Kagera River has been inaugurated as a regional facility. It is jointly owned by three countries, and it carries shared transmission infrastructure delivering power across their grids. Those points are set out in the project’s own documentation from the regional cooperation programme that developed it and its multilateral backers, and they form the spine of any responsible package.
Everything in a report should trace back to that spine. Where a claim cannot be sourced to the inauguration materials or the project record, it belongs outside the evidence pack rather than dressed up inside it. The value of a source-led package is not its length but its traceability: every figure, every actor, every claim tied to a document a reader can open. A short pack that holds up beats a long one that cannot be checked.
Takeaway: the documented facts are few and firm, and they are the whole foundation.
The Chronology: A Long-Planned Regional Asset
A timeline is the natural backbone of the package, and here it must be handled with care. What is knowable on this date is that Rusumo was conceived, financed and constructed as a shared regional project and has now reached inauguration. It is the product of sustained multi-country cooperation rather than a sudden build.
The specific milestone dates, the financing-close date, the construction start, the commissioning steps, are not established by the facts to hand and should be marked [TK] rather than filled in. A chronology with honest gaps is stronger than a tidy one built on guesses, and it tells a reader exactly where the record thins. Those marked gaps also double as a reporting list: each [TK] is a question to put to the operators and lenders when the package moves from baseline to full report.
Takeaway: build the timeline from confirmed points only, and flag the missing links rather than inventing them.
The Data Visual: What The Numbers Support
The data story is small but clean, which suits a clear visual. One figure anchors it: 80 MW, shared among three countries drawing on one river. A simple schematic serves better than a chart pretending to precision, a single generation source with three transmission lines fanning out to three national grids, the shared-ownership idea rendered at a glance.
Resist the temptation to manufacture proportions or trends the facts do not carry. The honest visualisation shows the structure of the asset, not performance metrics that are not yet in evidence.
Takeaway: visualise the confirmed structure, not numbers the record cannot support.
The Follow-Up Discipline: What Must Wait
The defining rule of this package is what it withholds. Actual output delivered, reliability in service, tariff outcomes, and the plant’s measured effect on each national grid are all future questions. On 9 May they are not answerable, and each belongs in a separate, separately dated follow-up rather than in today’s report.
For an operator or analyst using this as an evidence base, the decision implication is to treat the inauguration as a verified starting point and to schedule the follow-ups deliberately. Build the source pack now, mark the open questions, and return to them when the data exists, rather than pre-writing conclusions the record has not yet earned.
Takeaway: file today’s package as a clean baseline, and let performance be a dated follow-up rather than a promise.




