A Technical Assistance Facility that works across multiple countries is not simply a single-country facility at greater scale. It is a different operational challenge. The requests come from different institutions under different regulatory contexts. The experts operate across jurisdictions. The funding may flow from multiple sources with different reporting requirements. And the programme management team is expected to give a coherent account of all of it, simultaneously, on demand.
Most facilities at this scale reach the same conclusion: the data is not in one place. It was never designed to be in one place. And the effort required to assemble a consolidated picture is itself a significant programme cost that produces nothing for the beneficiaries.
What changes at multi-country scale
When a facility spans one country, the data management problem is manageable, if not elegant. The files are in a shared drive, the team is small enough that everyone knows where things are, and the reporting exercise — while painful — can be done in a room with the same four people.
When the facility spans six countries with five partner institutions each, the same approach produces a different result. Every country team develops its own way of tracking requests, activities and expert assignments. Each partner institution submits data in whatever format it finds natural. The shared drive becomes six shared drives, none of which are organised the same way. And when programme management needs consolidated figures for a quarterly report, the answer is not a query — it is a two-week email campaign.
The consolidation effort does not scale. It grows faster than the portfolio.
The shadow tracker problem
The natural response to this fragmentation is the creation of shadow trackers: master spreadsheets maintained at programme level, into which the data from country-level sources is periodically transferred, normalised and validated. Facilities with multi-country portfolios are almost universally running them.
Shadow trackers have an important property: they work, in the sense that reports get produced and donors receive figures. They have an equally important weakness: they are always out of date. The figures in a shadow tracker are the figures as of the last time someone did the transfer, which means they are never the figures as of today. And the gap between "as of the last update" and "now" is precisely where discrepancies accumulate that are painful to explain.
What the data model has to support
A portfolio view is not a feature added on top of a system designed for single-country operation. It is a property of the data model. To run a genuine portfolio view — one that reflects the actual state of all activities across all countries without manual consolidation — the system has to capture data at the right level of granularity from the outset.
That means: requests tagged to the requesting institution and country, activities tagged to the partner and funding source they sit under, expert assignments tagged to the activity, working and mission days recorded at assignment level, and results linked to the indicators of the specific funding source that required them.
When those connections exist in the data, a portfolio view is a query. When they do not exist, it is a project.
The bottom line
Multi-country scale is achievable when the data model is right. When every record enters the system with the context it needs — institution, country, partner, funding source, activity — consolidated reporting is automatic. When that context is missing at entry and has to be reconstructed later, scale becomes a management burden rather than a programme asset. The portfolio view is not a dashboard to be built once the data is collected. It is the reason the data needs to be collected in a specific way.