A comparison of Google Forms, KoboToolbox, Jotform, Typeform, SurveyMonkey, Qualtrics, Submittable and Sopact for nonprofits that need forms, documents and follow-up surveys in one record per person.
Nonprofit data collection software is any tool a programme team uses to gather information from participants, such as intake forms, surveys, case notes and uploaded documents. The real options range from free form builders (Google Forms, KoboToolbox), to survey platforms (SurveyMonkey, Qualtrics, Typeform, Jotform), to application and case tools (Submittable), to platforms built to keep everything about one person in one record (Sopact).
They all collect. They differ in what happens after: whether the intake form, the mid-programme survey and the follow-up six months later end up as one story about one person, or as three spreadsheets someone has to reconcile.
Key takeaways
Until recently, a stack of open-ended answers meant a consultant or a month of coding. Language models made reading text cheap, so programme leads started doing it themselves. Once they did, the questions got harder: not "what did people say?" but "did the same people say something different after the programme?" That is a longitudinal question, and most collection tools were never built to answer it.
In most organisations one person builds the reports and everyone else waits. The dashboard answers the question you had nine months ago, because by the time the export, the cleaning and the merge are done, the programme has moved on. The enemy is not any one tool. It is the gap between collecting data and being able to ask a new question of it.
Three things moved together: text analysis stopped needing a specialist, funders began asking for follow-up outcomes rather than attendance counts, and programme teams got tired of waiting on a quarterly report. The result is that the person closest to the programme now wants to run the analysis, and the tool has to let them.
Can a programme manager set up a form, collect responses and ask a question of them without an IT ticket or a data analyst? Most form builders pass the first half. Few pass the second.
Who does this well
Survey answers, a caseworker's note, an uploaded document and attendance should hang off the same person. If they live in separate tools, someone rebuilds the link every reporting cycle, and the duplicates start there.
Who does this well
Reading 40 comments is easy. Reading 4,000 across five programmes is where sampling creeps in and the quote that suits the narrative wins. Ask whether the tool processes every response.
Who does this well
A wave is one round of collection. Tracking change means matching wave two to wave one on a contact ID rather than an email address that changed or a name spelled differently. Attrition (people who drop out between waves) is only visible if the match is reliable.
Who does this well
The rating tells you how much. The comment tells you why. When they sit in separate tools, the "why" gets dropped from the report. Look for themes tied to scores, with the original quote one click away.
Who does this well
Case notes, PDFs and uploaded essays hold some of the most useful evidence a programme has. Most survey tools store the file and ignore the content.
Who does this well
The test is simple: ask "which participants improved least, and what did they say?" and see whether you get an answer with the records behind it.
Who does this well
Reproducible means the same question gives the same number next week. Traceable means you can click from a figure to the records behind it. Funders increasingly ask for both, and a chat answer on a pasted spreadsheet offers neither.
Who does this well
Duplicates, missing fields and mismatched IDs are cheapest to prevent when the form is filled in. Tools that give each participant a unique link, validate fields as they are entered and let people correct their own record save the cleaning sprint before every funder report.
| Tool | Best at | Where it stops |
|---|---|---|
| Google Forms | Free, fast one-off forms | No person-level record across forms |
| KoboToolbox | Offline field collection | Analysis and longitudinal linking are DIY |
| Jotform / Typeform | Polished forms and workflows | Each form is its own dataset |
| SurveyMonkey | Quick surveys and standard reporting | Multi-wave tracking is manual |
| Qualtrics | Enterprise-grade research | Cost and admin overhead for programme teams |
| Submittable | Applications and review | Not built around ongoing outcome surveys |
| Sopact | One clean record per person, qual and quant, over time | Not a general-purpose form builder or a grants CRM |
Often, yes. Many teams keep Google Forms or SurveyMonkey for simple one-off needs and bring the programmes that need follow-up into a person-level system. The honest limit: historical data collected without a persistent ID can be imported, but matching it to people depends on how clean the original identifiers were.
The one that keeps each participant as a single record across programmes and waves. For a single simple survey, a free form builder is enough. For several programmes with follow-up, look for persistent IDs and built-in analysis.
Few do all three. Submittable covers applications and documents, survey platforms cover follow-ups, and Sopact is built to hold forms, uploaded files and later surveys on one participant record.
For one-off collection, yes. It becomes costly when you need to follow the same people over time or combine forms.
Assign a unique ID or link at first contact and reuse it in every later form, rather than matching on name or email afterwards.
