01 · Finding and base
02 · Reasons and evidence
03 · What stays unknown
04 · Next action
Download opens as an HTML report. Use its Print / Save as PDF button. Longer notes may need more than one page.

Live webinar: Wednesday, October 7, 2026 | 9:00 AM PT
Building context across your data. In 30 minutes, see how to connect data and definitions across teams, with the right permissions and governance, so scattered data points become intelligence your teams and AI can actually use.
Save your spot (free)USE CASE / PRACTICAL GUIDE
A survey report explains what a survey found, who the findings describe, how the evidence was collected and what action it supports. A good report lets its reader check the numbers, understand respondents’ reasons and see what remains unknown. It connects results to a decision rather than presenting charts without an explanation.
The difficult part is keeping the meaning intact. A percentage can hide missing responses, an appealing quote may not represent a common view, and a change between survey waves may reflect different people answering. These four worked examples show how to report those distinctions clearly for training, customer experience, employee feedback and partner reporting.
AI can help analyze comments and draft reports, while shared definitions and source records keep the findings reviewable. Explore the examples below, then use the interactive worksheet to draft your own report. All figures and respondent quotations are fictional; they illustrate reporting choices, not customer results.
State what happened, among whom and in which period.
Show respondents’ reasons and what remains unknown.
Name the action, responsible person and review date.

Try one of the article’s examples, or add your own counts. Keep the finding, reasons, unknowns and next action together. Copy your draft or download a printable report.
Download opens as an HTML report. Use its Print / Save as PDF button. Longer notes may need more than one page.
A one-page summary can answer a focused reporting question, with the method and detailed tables in an appendix. In this fictional training program, the delivery manager wants to know which completers used the skill at work after 30 days, and what stopped the others.
15 of 25 respondents (60%) used the skill at work within 30 days. Twenty-five of 40 completers answered “Have you used the skill at work?” Response coverage was 62.5%. Keeping all 40 in view prevents the 60% from being mistaken for a result for the whole cohort.
Finding: 15 of 25 respondents used the skill.
Coverage: 25 of 40 completers replied.
Of the 10 who had not used it, 8 described a barrier, and 5 of those 8 said they had no time to practise. One declined the open question and one left it blank. Two answers carry the pattern better than a chart could:
“My manager moved me to the evening shift and there was nobody to practise with.”
“My manager hasn’t asked me to use it.”
Illustrative responses from the fictional follow-up
15 completers did not reply, and the report says so: their experience is unknown, not “no.” Answers are self-reported, and a follow-up without a comparison group cannot show that the course caused the change.
Test a 45-minute practice session with the next cohort and ask the same question in the same window. Owner: course coordinator. Review: one week after the next 30-day wave closes.
The wording matters. “60% of respondents used the skill” describes the 25 people who answered. “60% of learners used the skill” would incorrectly extend that finding to all 40 completers.
The infographic below follows this example from its sources to the finished report: the roster, survey and documents that feed it, the definitions agreed before writing, the checks made as answers arrive and what each report panel adds. It ends with examples 2 to 4 read the same way. All figures are fictional.

A customer survey report should distinguish a case marked closed from a customer who says the problem is solved. In this fictional example, 200 recent service users were asked whether their issue was resolved; 120 answered.
90 of 120 respondents (75%) said their issue was resolved; 30 said it was not.
Comments from the 30 unresolved respondents describe delays, incomplete fixes and unclear explanations. One illustrative response: “The case was closed, but the refund never came through.”
80 invited customers did not answer. Their experience may differ from that of the respondents.
Give the largest verified unresolved category an owner and ask the 30 customers again at the next check-in.
Report the next wave on its own base. If 12 of those 30 customers reply and 9 report resolution, write “9 of 12 follow-up respondents.” The experience of the other 18 remains unknown.
An employee survey report needs enough detail to guide action while protecting the people who answered. In this fictional example, 90 of 150 invited employees reported whether responsibilities were clear during a process change.
54 of 90 respondents (60%) agreed that responsibilities were clear; 18 were neutral and 18 disagreed.
Comments described unclear handoffs. Identifying details were removed. One illustrative response: “Nobody told us who signs off the new form.”
60 employees did not respond. A group result does not reveal any named person’s view.
Clarify the handoff, then repeat the question after employees have worked through the change.
A minimum group size helps, but it does not guarantee confidentiality. A role, location or distinctive incident can identify someone even after their name has been removed.
A partner report needs to answer three separate questions: did partners submit, were their submissions complete, and were the figures accurate? This fictional example covers 30 partners due to submit quarterly evidence.
24 of 30 expected partners submitted (80%). Of those 24 submissions, 18 were complete: 75% of submissions, or 60% of all expected partners.
Missing fields reflected unavailable data or unclear definitions. One illustrative response: “We count enrolments, not completions, so we left it blank.”
6 partners did not submit. Complete submissions can still use different reporting periods, units or populations.
Resolve definition conflicts, request missing evidence and keep a record of each correction.
The guide to combining many programs into one picture explains how to aggregate partner results without adding unlike measures.
A survey report should include its scope, a short summary, the method, results with their bases, interpretation, limitations, actions and an appendix. The examples’ four parts belong in the summary and results; the supporting sections explain how those findings were reached.
Use the interactive report worksheet ↑ to draft the summary with its scope, finding, response base, reasons, limitations and next action. Keep the questionnaire, sampling and recruitment method, measure definitions and detailed tables in the full report or appendix.
Before drafting, check for duplicate records, blanks and reversed score directions. AAPOR’s disclosure standards explain what to disclose about question wording, sampling, recruitment and method so readers can evaluate the findings.
Report open-ended answers as themes with a stated unit and count, supported by illustrative quotations and traceable to the original responses. Say whether you are counting respondents, responses or coded mentions. If one answer can carry two themes, the theme totals may exceed the number of respondents.
Keep the explanation on the same record as the score. The training example can say “5 of 8 non-users who described a barrier” because each open answer sits beside that person’s Yes or No. The guide to connecting quantitative and qualitative survey data shows how to set this up.
Choose quotations that illustrate the pattern, with appropriate permission and identifying details removed. Include a contrary account when it changes the interpretation. Make clear which words came from the respondent and which conclusions came from the analyst.
AI can organize open answers and draft an explanation of the results. Its value depends on the evidence available: the original question, response group, reporting period and meaning of each measure. A fluent summary without that context can make an incomplete finding sound more certain than it is.
Sopact connects forms, files and feedback around the relevant person, program or organization. Analysis becomes available as new data arrives in the agreed workflow and remains usable through AI Assistance. Staff can ask a follow-up question with the earlier evidence still available, reducing repeated exports, matching and reading.
In the training example, the useful question after the first report is whether the practice opportunity helped. In the customer example, it is whether people confirmed that their issue was resolved. The report becomes part of continuing program knowledge, with human review of the underlying responses.
Define the measures that readers will compare. “Skill used” in the example means self-reported use within 30 days, among respondents who answered that question. “Response coverage” means replies divided by invited completers. These definitions preserve the distinction between an outcome among respondents and coverage of the whole cohort.
For partner reports, agree the unit, period and inclusion rule before combining results. Enrollments and completions remain different measures; an unknown result stays unknown. A shared dictionary makes a portfolio total interpretable without forcing every program to report identical outcomes.
For identified, permitted follow-up, retain the respondent relationship across waves. Anonymous feedback remains anonymous. Keep the question and counted responses available so a reader can reproduce each finding. Lesson 6: Report explains how to connect claims with supporting evidence.
Ask someone who did not write the report to open the sources, recompute the figures and check the limits. These are the questions that review should answer:
Some limits remain after review. Answers can be self-reported, respondents may differ from nonrespondents, and a before-and-after change can have other explanations. Keep those limits visible beside the finding.
Choose one survey you already run and one reader who needs to make a decision. Draft the report before expanding the workflow; the first version will show which links between findings and answers need attention.
You should finish with a short report, a list connecting every figure to its question and base, and a record of any missing connections to fix before the next wave. Use what you learn to improve the next round of collection—the collect, analyze and improve cycle.
A sample survey report is a worked example showing a finding with its base, respondents’ reasons, the unknowns and the decision the evidence supports. Use the fictional training report above as a structure, then replace its numbers, questions and quotations with your own checked evidence.
Long enough to answer the reporting question transparently. One page can carry a summary of the finding, reasons, unknowns and decision. Keep the method, full questionnaire and detailed tables in an appendix when they would interrupt the main explanation.
Yes. Ratings describe a pattern, and comments can help explain it. Keep the question, respondent group and collection stage clear, and distinguish a counted theme from a single person’s experience.
No. A conventional margin of error depends on a probability sampling design. Do not automatically apply it to an opt-in or convenience sample, or to a follow-up with substantial non-response. Report counts, coverage and who is missing, and describe what the respondents said.
AI can help draft and organize a report from checked data. Keep the source records and definitions available, recompute figures independently and review the interpretation. A person still approves quotations, checks claims and signs off on the report.
Explore how Sopact can connect survey responses, supporting context and follow-up so your team can answer new reporting questions without rebuilding the analysis.
See it with your workflow →