Methodology
How TPMready supports verification

Step 01 of 08
Sampling and site selection
Are we visiting the right places, enough of them?
Coverage starts with the monitoring plan, not with whichever sites are easiest to reach. Each implementing partner has an IP plan that sets what will be monitored, where and in which period, and the visit list is built from it.
In the platform
- IP plans per partner, with a completeness score showing what information is missing.
- Sample-size settings for the number of interviews or data points each tool or site should have.
- A facilities register, so sites are recorded once with consistent names, types and locations.
- Random or risk-based samples of partner reports for re-verification under fourth-party monitoring.
Step 02 of 08
Team preparation and deployment
Does every team know what to do, and is it ready to go?
Each visit names its team: a team leader, enumerators, logistics staff and drivers. Preparation work, from confirming access to briefing enumerators on the tools, is set out as tasks with an owner and a deadline, so readiness can be checked rather than assumed.
In the platform
- Visit cards with collection method (in-person or remote), dates, team and number of interviews.
- Task assignments for preparation steps, with status: pending, in progress or completed.
- Field logistics for teams, drivers, vehicles and base locations.
- Stalled alerts when preparation tasks stop moving, with one-step escalation.
Step 03 of 08
Evidence capture in the field
Can we show the visit happened as reported?
Teams record their work on the visit as it happens: interviews completed, observations, files and photos. Location and time attached to the evidence make it possible to confirm that data was collected at the site, on the day.
In the platform
- Tracking on each visit, from Waiting for tracking to Tracking in progress.
- Geotagged, time-stamped photos and notes attached to the visit record.
- Interview counts recorded against the target set in planning.
- A round overview comparing visits planned, under way and finished.
Step 04 of 08
Data quality checks
Is the data complete and internally consistent?
Before a report can be approved, a data analyst reviews the dataset and records the result. The check is a required step in the workflow, not an optional review at the end.
In the platform
- A data checks board where reviewers record the outcome of each check.
- Visits held in Post data collection / Data check until the check is recorded.
- Dataset cleaning by the data analyst role before reporting.
Step 05 of 08
Review and approval
Has a responsible person signed off on what the client will read?
Field reports are submitted for approval. A reviewer approves the report or returns it with comments. Only approved visits move to Completed and become available to the client.
In the platform
- Submitted-for-approval and approved site visit lists.
- Rejection with comments, returning the report to the team.
- Read-only guest access, so clients and donors see approved results without editing rights.
Step 06 of 08
Triangulation and pattern detection
Is this an isolated incident or a systemic problem?
A single finding may be bad luck. The same finding at several sites, or for the same partner, points to something structural. TPMready compares findings across sites, partners and rounds, and highlights repeated red flags as a pattern.
In the platform
- Red flags tagged by issue type, partner and location.
- Pattern detection when several active flags of one type appear in an area or for a partner within a set window.
- Adjustable thresholds: how many flags, within how many days.
- Partner and site visit summaries to compare results across the portfolio.
- Fourth-party re-verification compared against the original monitoring report.
Step 07 of 08
Follow-up and remediation
Did anything change as a result of the finding?
A finding matters only if someone acts on it. Every red flag has an owner, a deadline and a status, and recommendations from a visit are tracked on post-visit cards until they are closed.
In the platform
- Red flag statuses from open to resolved, viewable as table, Kanban or calendar.
- Post-visit cards for actions and recommendations.
- Patterns raised on the manager's home page and in the AI assistant.
Step 08 of 08
Accountability and audit
Can we show who did what, and when?
Every record created, updated or deleted is logged with old and new values side by side. Actions taken with AI help are marked, and AI drafts are never saved without a person accepting them.
In the platform
- A searchable audit trail across the project.
- Clear marking of AI-assisted actions.
- Role-based access so each action is tied to a named, invited user.
Verifying the verifiers
Where partners run their own monitoring, the same sequence can be applied one level up, testing the partner's systems and re-verifying a sample of their reports.
Fourth-party monitoringProtecting people and data
How access is separated by contract and role, and what we share with procurement and IT reviewers.
Security and data protectionWalk through the method with your own plan
We can map your sampling, tools and approval lines onto a TPMready round, so your M&E team can see each check in place.