The difference between reporting a launch and understanding it is the evidence pack behind it. On the day a national programme is unveiled, the temptation is to describe the ambition; the discipline is to fix what can actually be verified from primary documents, and to hold everything else for a dated follow-up. Uganda’s Parish Development Model, launched this week, is a strong candidate for that discipline — a large claim that deserves a source-led package rather than a summary of its own promises.

The model organises local planning, financial inclusion, production, storage, processing and marketing around the parish, with a parish-level delivery unit, revolving finance and data systems. Building the evidence package means separating what the documents establish today from what only time can confirm.

The Primary Record: What the documents establish

The evidence pack starts with the founding documents. The Ministry of Local Government’s Parish Development Model page and the Presidential Initiatives description together establish the verifiable core: the parish as the delivery unit, the stated functions across production, storage, processing and marketing, the revolving finance mechanism, the data systems, and the explicit aim of moving subsistence households into the money economy.

Those are claims of design and intent, and as of today that is exactly what they are — design and intent, not yet outcomes. A source-led package says so plainly. It records what the state has committed to and how the model is meant to work, and it resists the slide from what is announced to what is assumed to follow. On the launch date, the primary record is the ceiling of what can be asserted.

The takeaway: the documents establish design and intent, and an honest package reports them as that and no more.

The Chronology and the Data Visual: Structuring the story

A package needs structure, and two forms suit this story. A chronology fixes the sequence knowable today — the model as designed and launched — and leaves clearly marked space for the dated entries that will follow as implementation unfolds. That discipline keeps later developments from being read back into the launch.

A data visualisation is the second element, and here honesty means showing the architecture rather than inventing results. The model’s structure — parish unit, revolving fund, data systems, the functions it coordinates — can be mapped as a flow that a reader understands at a glance. What cannot yet be charted is performance: recovery rates, output changes, adoption. Those axes belong on the visual as placeholders to be filled over seasons [TK], not as numbers asserted on day one. The visual explains the machine; it does not pretend to show the machine running.

The takeaway: chronology and a structural visual can carry the story now, provided performance figures are left as marked gaps rather than invented.

The Follow-Up Discipline: What must wait

The defining rule of a source-led package on launch day is knowing what to withhold. Every question that matters most — does the fund recycle, do households adopt, does output rise, does value move into local processing — is a question the launch cannot answer. Each is a separate, dated follow-up, and treating it as anything else would be reporting the future as if it were the present.

This is not caution for its own sake; it is what makes the package trustworthy. A reader returning to it later should find a clean record of what was known on the launch date, with the outcomes clearly deferred to their own moments. The reporting questions — which bottleneck is removed, whether finance reaches producers, where processing captures value — are logged now as the agenda for that follow-up, not answered prematurely. The evidence pack’s value is that it dates its own knowledge.

The takeaway: the outcomes that matter most are deferred by design, and logging them as pending is what keeps the record honest.

So What: Build the record, date the claims

For anyone producing a serious account of the Parish Development Model, the task on launch day is to build a clean, source-led record: what the primary documents establish, structured as chronology and architecture, with performance left as marked gaps. The decision it invites is editorial restraint — report the design fully, defer the outcomes explicitly, and set the agenda for the follow-ups that will test the model against reality. The story that matters will be told over seasons; the responsibility today is to fix the starting point accurately so the later chapters have something honest to measure against.