When a program operates across provinces, through partners, or in areas a donor or head office cannot easily visit, its own progress reports may not be enough. Decision-makers need independent confirmation that activities happened as reported, and that the evidence behind the numbers can be checked. That is what third-party monitoring is for.
Third party monitoring Afghanistan programs use is not a replacement for a project’s own monitoring. It is a separate, independent check by a firm that is not implementing the work it is verifying. This guide answers the questions program managers most often ask when scoping it, in general terms. It does not describe any specific past engagement or donor requirement, and it is not a substitute for a particular assignment’s terms of reference.
Frequently asked questions
What is third-party monitoring, and how is it different from a project’s own monitoring?
A project’s own monitoring is part of delivery. Program staff track activities, collect output data, and report progress against targets, usually as they go. That work is essential, but it is self-reported: the same team responsible for delivery is also reporting on it.
Third-party monitoring sits outside that chain. An independent monitor visits sites, checks records, speaks with staff and participants, and verifies a sample of reported results against what can be observed. It does not manage the program, approve payments, or take over implementation decisions. Its value lies in that separation: a donor or senior manager can read the report knowing it was not written by the people whose work is being assessed.
When does a program need TPM?
Not every program needs independent monitoring, and a credible provider should say so when it does not. It is most often used when access is constrained, when scale or geography makes direct oversight impractical, when a funding arrangement requires independent verification, or when there is a specific question to answer — a reported result that needs checking, a new delivery model that needs testing, or a concern that needs an impartial look before more money is committed.
Ask what decision the monitoring will inform. If it is a funding release, a partner continuation decision, or a course correction, independent verification is likely worth its cost. If it is only routine record-keeping, the program’s own monitoring may be sufficient.
Our TPM services Afghanistan cover field verification, remote monitoring, and reporting for donor-funded programs.
What does a TPM visit or verification actually check?
A verification visit is not a general tour. It follows a plan agreed in advance, based on reported activities and the client’s questions. A monitor will typically check that the activity took place at the reported place and time, that quantities and quality match the plan, and that records — attendance lists, distribution registers, stock records, photographs, and financial documents — are consistent, complete, and free of duplication or alteration. It will also speak with staff and, where appropriate and safe, participants, to see whether their account matches the paperwork.
No single source of evidence is treated as proof on its own. A strong verification triangulates: a register, a photograph, a physical observation, and a conversation should point in the same direction. Where they do not, that gap is itself a finding, to be reported honestly rather than smoothed over.
Where distributions are involved, beneficiary verification Afghanistan checks confirm that recipients actually received what was reported.
How is remote monitoring done where field access is limited?
In parts of Afghanistan, physical access to a site may be limited by security, distance, weather, or local restrictions. That does not make verification impossible, but it changes how it must be done — and a provider should be clear about those limits rather than pretending remote checks are the same as a visit.
Remote monitoring typically combines structured phone or video calls with staff and participants, review of photographs, videos, and documents submitted by the implementer — checked for consistency with dates, locations, and other records — and geospatial information where a program has it. Transparency is key: the report should say plainly what was verified remotely, what could not be verified, and what confidence each finding deserves. A report presenting remote checks as full field visits overstates its evidence.
How are findings reported, and how quickly?
Reporting should be agreed before fieldwork begins, not improvised afterwards. A program manager should expect a written report that separates facts from judgement: what was checked, what evidence was seen, what matched the program’s records, and what did not. Findings should be specific enough to act on, with the site, activity, and evidence identified, rather than general statements about overall performance.
The report should also distinguish factual discrepancies, such as a quantity that does not match a register, from process weaknesses, such as an incomplete record, and from recommendations for change. On timing, no single standard fits every assignment: agree a reporting timetable in the terms of reference, with an early alert for serious issues and a clear process for the implementer to respond to draft findings before finalisation.
How is TPM independence protected from the implementer being monitored?
Independence is the whole point of third-party monitoring, so it has to be protected in practical ways, not just stated in a proposal. The monitoring team should not be part of the implementation team, should not report to the implementer, and should not take instructions from it about what to find. The monitor, not the implementer, should decide which sites, activities, and records to check, even if the implementer helps with logistics.
There should also be rules on gifts, payments, and relationships with implementer staff, a process for declaring conflicts of interest, and reporting lines sending findings to the commissioning client, not to the implementer for approval — even though the implementer should be able to respond to factual points. Vagueness about site selection, report recipients, or uncomfortable findings suggests weaker independence than the proposal claims.
What should a program manager ask before commissioning TPM?
- What decision will this monitoring inform, and what evidence is needed for that decision?
- Which sites, activities, and results will be verified, and how will the sample be chosen?
- How will field access be handled, and what happens where a site cannot be visited?
- Who will lead the work, and what experience do they have with similar programs in Afghanistan?
- How will independence be protected, including site selection, reporting lines, and conflicts of interest?
- What will the deliverable contain, and what reporting timetable has been agreed?
- How will the implementer respond to draft findings, and how will that response be reflected in the final report?
- What information and access does the monitor need from the program and its partners, and by when?
- What are the fees based on, and what would change them if the scope or geography changes?
- What happens if a serious issue is found mid-assignment — who is told, and how quickly?
Listen for specifics: named methods, a sampling approach, a reporting timetable, and clear independence rules. A proposal that offers only reassurance, without those details, is not yet a plan.
What does a credible TPM deliverable look like?
A credible deliverable is useful to someone who was not in the field. It should start with scope and method — what was verified, where, when, and how, including sites that could not be visited and why — then present findings site by site, with the evidence for each, so a reader can see how a conclusion was reached rather than taking it on trust.
It should be honest about limits: if a result could only be partly verified, say so and explain what that means for confidence. Separate verified results from unverified claims, avoid claiming more certainty than the evidence supports, and end with practical, prioritised recommendations — what should change, who owns it, and what to check next time. The test is simple: could a manager who was not there use this report to defend a funding decision? If not, the monitoring has not done its job.
Talk to Blue Presto
Blue Presto Consultant Services is a Kabul-based firm helping donor-funded programs and international organizations verify delivery, understand performance, and strengthen accountability in Afghanistan — with independent field verification, clear reporting, and evidence that stands up to review. Learn more about our monitoring, evaluation and learning services, visit Blue Presto Consultant Services, or contact us to discuss a monitoring assignment.