Why third-party monitoring strengthens donor accountability

Third-party monitoring, TPM, is often treated as a compliance line item: a box a donor ticks because a grant agreement requires independent eyes on a programme. Used well, it does far more than that. It is one of the few mechanisms that lets a donor see a programme the way its intended participants experience it, rather than the way an implementing partner's own reporting describes it.

What TPM actually buys

A good TPM arrangement gives a donor three things an internal monitoring system usually cannot: independence from the implementer's own incentives, access to locations an implementer may not prioritise for a site visit, and a comparison point across multiple grantees using a consistent methodology. In access-constrained settings, that third point matters as much as independence. A donor funding six implementing partners across a region rarely has a way to compare their real performance unless someone applies the same instrument, the same sampling logic and the same quality checks to all six.

Where it tends to fall short

TPM disappoints when it is designed as a paperwork exercise rather than a learning one. Two failure patterns show up repeatedly. The first is a monitoring plan built around what is easy to count rather than what the programme actually needs to know, so the donor ends up with tidy output tables and very little insight into whether the programme is working. The second is a feedback loop that is too slow to matter. Findings that reach a programme team eight months after data collection cannot change anything; they can only be filed.

Both failures are avoidable with the same fix: designing the MEL framework and the reporting cadence together, before the first field visit, rather than treating monitoring design and monitoring delivery as separate problems.

What good practice looks like

The TPM arrangements that hold up under scrutiny share a few traits. Indicators are chosen because they answer a real programme question, not because they are convenient to collect. Field teams are trained and supervised consistently across sites, so results are comparable. Data quality checks happen close to collection, not months later during analysis. And findings are shared on a cycle that is fast enough for a programme team to actually act on them.

None of this is exotic. It is disciplined, unglamorous MEL practice, applied consistently. That consistency is what turns TPM from a compliance requirement into a genuine accountability tool, for the donor, and for the people the programme is meant to serve.