A pre-post survey can help a nonprofit see whether participants report a meaningful change during a program. It does not need to be long, expensive, or technically sophisticated. But it does need to ask the right questions at the right times and make responses possible to compare.
Creating the online form is usually the easy part. The harder part is choosing what to measure, collecting a useful starting point and matching responses safely. You also need a result that helps without adding more reporting work. This guide gives small teams a practical process.
When a pre-post survey is the right method
Use a pre-post survey when participants can report the change your program hopes to support. You also need a clear point before and after the program. Examples include confidence, knowledge, skills, sense of connection, preparedness, or perceived ability to take a next step.
A pre-post survey may not be the right choice when:
- the intended change is unlikely to appear during the program period
- participants cannot safely or meaningfully answer the questions
- the program has no clear beginning or end
- very few participants will complete both surveys
- the measure requires clinical, diagnostic, or specialist evaluation expertise
In those cases, other evidence may work better. You could use attendance records, planned observations, interviews, follow-up conversations, service records or a mix of methods. Start with Impact Measurement 101 if the intended outcome and indicator are not yet clear.
Start with one outcome, not a list of questions
Write the intended near-term change in plain language. Then decide what sign of progress a participant could report. Only after that should you draft a question.
| Planning step | Example |
|---|---|
| Intended outcome | Participants feel more confident taking the next step in a job search |
| Indicator | Change in self-reported confidence between the first and final session |
| Survey item | “How confident do you feel taking the next step in your job search?” |
| Response scale | The same clearly labelled scale at both points |
| Use | Review the program approach and report the pattern with appropriate context |
The survey should not try to capture every benefit the program might create. Choose a small number of measures that the team will genuinely review. If a question has no clear decision or reporting use, leave it out.
Design comparable pre and post questions
For each outcome measure, use the same wording, response scale, and interpretation at both points. Changing a question between the pre and post survey makes the comparison weaker.
A short survey might include:
- two to five repeated outcome questions
- one optional open-ended question about what changed or helped
- only the background information needed for analysis
- a clear introduction explaining purpose, choice, and data use
Use plain, specific language. Ask one thing at a time. “I feel informed and confident” is two questions disguised as one. Avoid leading language such as “How much did our excellent program improve your confidence?” and avoid scales where the labels or direction change from one question to the next.
Keep the scale manageable and label its endpoints. The best scale is not automatically the one with the most points; it is the one participants can understand and the organisation can interpret consistently.
Include qualitative evidence without making analysis unmanageable
Numbers can show the direction and size of reported change. A short open question can help explain the experience behind the pattern. Useful prompts include:
- What, if anything, feels different for you now?
- Which part of the program was most useful, and why?
- What would have made the program more useful?
Use one or two focused prompts rather than a page of open questions. Decide who will read and code the responses before adding them. Qualitative comments should add context, not become a large pool of feedback that nobody has time to review.
Plan how responses will be matched
To measure change for the same people, you need a safe way to match each person’s first and final response. A simple unique code can work, but the method must fit your privacy, consent, safeguarding, and data-protection obligations.
Before launch, write down:
- whether responses are anonymous, confidential, or identifiable
- what information is genuinely necessary
- how matching will work
- who can access raw and matched data
- where it will be stored and for how long
- how participants can decline or skip a question
Do not promise anonymity if you collect an email address, name, or code that staff can connect to a person. If the subject is sensitive or the population is vulnerable, get appropriate specialist advice rather than relying on a generic template.
Build collection into the program workflow
The strongest survey design will still fail if the collection process depends on someone remembering at the last minute. Map the two moments into normal delivery:
- Before: choose the point before meaningful program exposure and name the staff owner.
- During: monitor completion and record any delivery issues that affect the data.
- After: collect the repeated questions at a comparable point and provide an accessible alternative where needed.
- Close: check completeness, record the final response rate, and secure the data.
- Review: discuss the findings at a scheduled program meeting and record any action.
Keep the survey short, explain why it matters, make it work on the devices participants actually use, and allow enough time during the program where practical. These choices usually do more for completion than repeated reminder emails.
Choose a tool after the workflow is clear
A basic form tool may be enough for a short survey. Choose based on accessibility, privacy and security requirements, permission controls, export options, ease of matching, and the work required to analyse results—not on the length of the feature list. Vendor plans and limits change, so verify current details directly before committing.
If your organisation needs a broader assessment or collection setup, compare the nonprofit program assessment tools against your actual process and safeguards.
Analyse the results without overstating them
Start with participation. Record how many people were invited, completed the pre survey, completed the post survey, and had responses that could be matched. Do not present a positive result from a small or limited group as if it represents everyone.
Then compare each repeated item. Depending on the scale and sample, that may mean showing the distribution of responses, the average or median at each point, the proportion reporting improvement, or the number reaching a clearly defined threshold. Keep the calculation consistent and explain it in plain language.
Look for patterns, exceptions, and missingness. Read the open comments alongside the numbers. Ask whether delivery changes, timing, participant mix, or drop-off could have influenced the result.
A pre-post survey can show that participants’ reported responses changed over the program period. On its own, it usually cannot prove that the program caused the change. Use careful language such as “participants reported greater confidence at the end of the program,” then add the response base, timeframe, and limitations.
Turn survey findings into decisions and reporting
Use the result first to improve the work. Discuss what appears to be changing, for whom, and where the evidence is unclear. Decide whether to change delivery, refine a question, improve collection, or investigate a pattern in more depth.
For external reporting, pair a small number of clearly explained findings with context and an appropriately consented participant perspective. A nonprofit impact dashboard can show the trend once the measure is stable enough to update consistently.
Use the free survey template as a starting point
Download the Program Feedback Survey Template, then adapt it to one clearly defined outcome, your participants, and your safeguarding and privacy requirements. Do not copy questions into a live survey until the team has agreed how each response will be used.
If survey collection and reporting are creating more work than insight, the next step is to review the wider measurement process. Simple and Engaging’s impact measurement tools service helps nonprofits design a practical, maintainable setup.
When should a nonprofit run pre and post surveys?
Collect the pre survey before participants receive meaningful program support and the post survey at a consistent point after delivery. The timing should match the outcome you expect to observe and be realistic within the program workflow.
How many questions should a nonprofit outcome survey include?
Use only the questions needed for a clear decision or reporting purpose. A practical pre-post survey may have two to five repeated outcome questions, one optional open-ended question, and only essential background items.
Does a pre-post survey prove that a nonprofit program caused a change?
Usually not on its own. It can show that participants’ reported responses changed between two points. Report the pattern with the response base, timing, and limitations, and avoid claiming causation without a design that supports it.





