Prepare a verification protocol
Open the field-verification workspace to define a claim, site scope and sampling limits, then draft evidence checks, safeguards, findings notes, a response process and corrective actions. A fictional example makes the unresolved permissions explicit. Save and export the protocol for qualified local review.
The workspace conducts no visit, interview or audit and contacts nobody. User-entered findings remain unverified notes. Keep participant details, precise site locations and confidential material out. A completed checklist supplies no approval or consent for fieldwork; the reviewed protocol and local pilot in the charter remain institutional milestones.
What it is
Most of what donors know about a program comes from the organization that runs it. Field Verification would add an independent check. Local researchers would visit a sample of sites and ask two questions: did the work happen as reported, and what do the people it was meant to serve say changed?
How it works
Each check would follow a published protocol written for that kind of program. For a water project, that might mean visiting a random sample of water points to see whether they work. For a school program, it might mean comparing attendance records with what teachers and families report. People would be interviewed with their consent, in their own language and by researchers from their region. Only summary findings would be published, and nobody’s personal details would appear in a report.
Organizations would see the findings before publication, and their response would be printed alongside. Checks would be done with an organization, not to it, and any organization could ask for one.
Why it matters for the system
Field Verification would work on three conditions at once. It would close part of the Missing Feedback Loop by carrying what happened on the ground back to the people who paid for it. It would narrow the Measurement Gap with a shared service that small organizations couldn’t afford to build alone. And it would treat the Missing Voice by making the people served a primary source rather than an afterthought.
Others have built part of this. Feedback Labs, for example, helps nonprofits and funders listen to the people they serve and act on what they hear. Field Verification would add an independent, published check that any donor can read.
Risks and limits
Visits take people’s time, and an outside researcher can change what people are willing to say. Checks can also become a burden that falls hardest on small organizations. The protocol would limit visit length, pay local researchers fairly and go through ethics review before any pilot. Until partners, funding and a proper legal and governance setup are in place, the program accepts no money.
What success looks like
Within five years, independent checks are a normal part of how large programs report and their findings are public. At least some funding decisions have changed because of them.
Prepare a field-verification protocol
Specify what could be checked, where a conclusion would apply, what safeguards are unresolved and how findings, responses and corrective actions would be handled.
This is protocol-writing software. Charitology has conducted no field visit, interview, audit or independent verification through this workspace. User-entered findings are unverified notes. Do not collect or enter personal data, site coordinates, contact details, participant accounts or confidential documents here. A completed plan is not permission to do fieldwork.
Your work stays in this browser. No account or server submission. Save each form, then export a backup before sharing or changing devices. Sample records are fictional. Backups support up to 500 records (250 per collection) and 8 MB, including formatting; large projects must be split before that limit.
Opening the local record snapshot…
Software and institutional readiness are separate
This workspace is available now. These requirements are not established by using it:
- Local leadership and funding. An actual pilot requires funded local research partners, appropriate competence, fair compensation and community involvement in the protocol.
- Ethics, consent and safety. Resolve applicable review, permissions, voluntary participation, safeguarding and stop rules before any visit, interview or data collection.
- Independence and data governance. Agree conflicts, access, secure data handling, aggregation, retention and how small-group disclosure risks will be reviewed. This browser notebook cannot hold participant records.
- Response, correction and follow-up. Agree a fair response process, public correction route and accountable rechecks before promising an independent report. No field audit has been conducted by publishing this software.
Track evidence and outside authorization in the readiness records below. No local status confers legal approval, funding, accreditation or independent review.
1. Set the scope and assumptions
2. Review the current picture
3. Prepare a usable draft
Preview the generated kit below. It includes the context, every saved record, calculations, working documents and unresolved review prompts. Exports include all records even while a filter is active.
Read generated draft
Use Backups and recovery above to restore native JSON, remove this saved key, undo a record change or retry a failed save. Unfinished fields have a separate recovery download.
After a failed save, Retry keeps that exact change. To replace it instead, review the context or an existing record form below. Before adding a new record in another form, resolve the failed save; keep unfinished-field copies first.
Connect your program work
Keep chosen copies of records from Field Verification and the other partner workspaces together. Explain how a plan, evidence note or decision connects to another record, then review that connection when a copy changes.
This private browser notebook records your own snapshots and explanations. It does not establish permission, independent review, causation or observed results. The original workspaces stay separate. Files and records are not sent anywhere.
The companion notebook is loading. The original workspace remains available above.