NGOs treat data collection as a compliance back office — something field staff do to fill donor reports. But the instrument you use to collect data shapes what you can later communicate, and what you can communicate shapes what you can fund. A survey form built to log activities will never yield the outcome stories that move funders. The fix isn't more data. It's redesigning the instrument to capture what changes, not just what happens.
Your field staff are in the villages every week. They fill forms. They submit reports. You have data — a lot of it. Workshop counts. Beneficiary counts. Attendance sheets. Income figures at intake.
And yet when a funder asks the one question that decides whether you get the grant — "what actually changed for the women in your program?" — the strongest answer isn't in your database. It's something a field officer mentioned in passing. A widow in Sangli who built a tailoring business after her husband's accident. A woman who said the program gave her the leverage to push back against patriarchal expectations at home.
You have the data. You have the stories. They're sitting in two different places, and neither is doing the work the other needs.
This isn't a data shortage. It's an instrument problem. And it's quietly capping your funding.
In early 2026, a journalist named Siddhi Jojare spent 13 days conducting quantitative field surveys across Solapur, Sangli, and Wardha districts in Maharashtra, interviewing women entrepreneurs about their businesses, incomes, and struggles. She was working with a research and data analysis organization that serves nonprofits, government agencies, and CSR projects.
She noticed something. When she introduced herself as a surveyor rather than a journalist, women were less guarded. The absence of a story-extracting intent made them more candid. And after the formal survey questions ended, the real material emerged:
When introduced as surveyors rather than journalists, people were noticeably less guarded. The absence of a "story-producing" intent made respondents more open and candid. After the formal survey questions ended, women shared powerful personal stories — a widow in Sangli who built her business independently after her husband's accident, and another woman who described how entrepreneurship helped her challenge patriarchal expectations at home.
— Siddhi Jojare, "A journalist turns surveyor and discovers new stories," IDR Ground Up (June 2026)
None of it made it into the submitted data. The survey was quantitative. The form had fields for income, business type, household size. It did not have a field for "what changed in your life because of this." So the stories — the exact material a funder would need to understand why this program works — were dropped at the point of collection.
This is what every compliance-designed survey form does, every day, across the Indian social sector. It logs what happened. It drops what changed.
The Sambodhi and Dasra "Measuring What Matters" study (2025) found that 73% of MEL data collected by Indian NGOs flows upward to donors, but only 18% informs internal decisions, and only 6% is used for communication or community engagement. The instrument is optimized for the upward flow. The downward uses — learning, communication, community feedback — are afterthoughts.
Your survey form is not a neutral recording device. It's a filter. And the filter was designed by what the donor asked for, not by what a future funder would need to hear.
The obvious fix is to ask field staff to do better. Capture the stories. Note the outcomes. Write them up. This is where most NGOs locate the problem — in field staff capacity.
The data says that's the wrong diagnosis.
The IDR fieldworker productivity study (2024) surveyed 40 fieldworkers across six states and found that 45% reported no uniform reporting formats, and one fieldworker manages 30–32 different data formats monthly. When a field officer is juggling 30 formats, she is not listening for outcome signal. She is surviving the reporting load.
The Sambodhi/Dasra study also found that 42.5% of NGOs rely on program staff — not dedicated MEL teams — for evaluation, and 59% spend less than 5% of program budgets on MEL. The people collecting data are the same people delivering the program. They are not trained evaluators. They are not even evaluated on the quality of what they capture. They are evaluated on whether the form gets submitted on time.
| What field staff are asked to do | What funders actually need |
|---|---|
| Fill 30+ formats monthly | Outcome stories with baselines and causal chains |
| Report activities on deadline | Translate activities into what changed |
| Serve as data extractors | Serve as the closest listeners to ground truth |
| Optimize for compliance | Optimize for learning and communication |
The field staff are not the problem. The instrument is. Asking them to rescue the data while handing them a compliance form is like asking a surgeon to operate with a spreadsheet. The tool shapes what's possible.
The data collection instrument sits at the top of a pipeline. What it captures flows downstream. What it drops is gone.
Three stages, three failure modes:
1. Collection. The form logs what happened — workshops conducted, beneficiaries reached, kits distributed. It does not capture what shifted for the beneficiary. The raw material for outcome communication is dropped here, at the point of collection. Everything downstream is working with a deficit.
2. Translation. We've written about the translation problem before — the gap between field stories and funder metrics. But translation requires something to translate. If the field story was never captured in a structured form, there's nothing to extract. The program director knows the stories. The database doesn't. The communications team can't translate what was never recorded.
3. Communication. The annual report lands on the funder's desk with activity counts and a couple of disconnected case studies. The funder sees what you did. They don't see what it produced. This is the pattern we named in our flagship post — organizations with the strongest field work lose funding to organizations with weaker programs but sharper communication. The drop at stage 1 becomes a pass at stage 3.
The pipeline doesn't fail at the end. It fails at the beginning. By the time your communications team is drafting the proposal, the outcome signal was already lost — six months earlier, in a village, on a form that had 40 fields and not one of them asked "what changed."
1. Your survey form has 30 fields, none of which ask "what changed." Count the fields on your most-used field form. If every field logs what was done — workshops conducted, beneficiaries reached, kits distributed — and zero fields capture what shifted for the beneficiary, your instrument is a compliance log. A funder reading your data can answer "how much activity happened?" They cannot answer "did it work?"
2. Your most powerful impact evidence isn't in your database. If the strongest material your team has — the stories that would make a funder stop scrolling — lives in a WhatsApp group, a field officer's notebook, or a program director's memory, and not in your M&E system, your instrument dropped the signal at collection. You're funding a database that stores the least useful version of your impact.
3. Your annual report uses numbers from the form, but stories from outside the form. If your M&E team supplies the counts and your communications team hunts for stories separately, the two tracks aren't connected. The instrument was designed to feed one track. The other track is running on scavenged material. This is why your annual report reads like two different organizations — one that counts things, and one that tells stories. A funder notices the disconnect.
This is the reframe.
Most NGOs think of data collection as the back office of impact work. It's the thing field staff do so the donor report gets filled. It's upstream of nothing — it's a filing task.
But data collection is the front line of communication. It's where the raw material of your funding case is either captured or dropped. The instrument you use decides what you'll have available when a funder asks the question that matters.
A compliance instrument asks: "How many women attended the training?" A communication instrument asks: "What was the woman's income before the training, and what is it now?" Same field visit. Same field officer. Different form. Different funding outcome.
This isn't about adding a qualitative research wing to your organization. The 5 most common Theory of Change mistakes all trace back to the same structural problem: activities are listed, causal links are absent, baselines are missing. The survey form is where that problem begins. If the form doesn't capture the baseline, the causal link, and the outcome, no amount of proposal writing downstream will manufacture them.
The fix isn't more data collection. It's collecting the right things, on the instrument you already use, in the field visits you're already doing.
1. Audit one field survey form for outcome fields. Take the most-used form your field staff fill. Count the fields that capture what changed for the beneficiary versus fields that capture what was done. If the ratio is 30:0, you've found your funding ceiling. See how to extract outcome signal from the data you already have →
2. Add three outcome questions to your existing field instrument. Not a new survey. Three questions on the current form: What was the beneficiary's situation before? What changed? What did it take to produce that change? That's the raw material for outcome communication. We've written about why baselines are the single most common gap in NGO communication.
3. Run your five strongest field stories through the Extract step. The stories your program director tells when someone asks "so what does your program actually do?" already contain baselines, causal mechanisms, and outcomes. Pull them out. The translation framework is here →
4. Map each outcome to the CSR categories it aligns with. One program often maps to three funding streams — livelihood, climate, women's empowerment. If you report under one category, you're leaving two on the table. The same outcomes, framed differently, unlock different funding.
Because the data was collected for compliance, not for communication. Donor-report data answers "what did you do?" Funders deciding new grants ask "what changed, and why?" Those are different questions, and a form designed for the first one won't yield the material for the second. Volume of data isn't the issue. What the instrument captures is.
Start with the existing form. Redesigning forms is cheaper than adding a new data collection layer, and it reaches the field staff who are already in the villages. Add three outcome questions to the current instrument — baseline, change, mechanism — before building a parallel qualitative track. If the existing form can't carry those questions, then a separate interview is worth the cost.
You're presenting the two tracks separately — stories in the case study section, numbers in the outcomes section. Funders don't want either alone. They want the story and the number connected: "This woman went from ₹5,000 to ₹32,000 a month. Here's how. Here's the scale." The fix is translation, not choosing one track over the other. The framework for translating field stories into funder metrics is here.
You don't add burden. You change what the existing form asks. Field staff are already asking questions in the village — the form just dictates which questions. Replace three activity fields with three outcome fields. The field officer's workload doesn't increase. The instrument changes. If your field staff are filling 30+ formats a month, adding more is not the answer. Replacing is.
Only if it's collected without structure. The three outcome questions — baseline, change, mechanism — are verifiable. "Income went from ₹5,000 to ₹32,000" is a checkable claim. "The training caused the income change because it removed three specific barriers" is a causal chain a funder can evaluate. Unstructured anecdote is cherry-pickable. Structured outcome capture is not. The difference is the instrument, not the data type.
The IDR journalist discovered something in Sangli that every NGO director already knows: the most powerful evidence of your impact is not in your database. It's in the conversations that happen after the form is closed. Your survey form is the first link in the chain that ends with a funder saying yes or no. What it captures flows downstream. What it drops is gone.
The NGOs that win funding aren't the ones with more data. They're the ones whose instrument was designed to capture what changed — not just what happened. The fix isn't a new M&E system. It's three questions on the form you already use, in the field visits you're already doing.
If this post named a pattern you recognize, the next step is translation — taking the field stories your program team already tells and structuring them in the language funders need. Read the field-stories-to-funder-metrics framework →
Related Reads: