When to use it

Use this prompt after closing a customer, employee, member or event survey, when you need to share results quickly without overstating them. It works with exported counts from most survey tools and with a sample of the open-text answers.

It is designed for descriptive summaries: what respondents said, how often, and how groups differ. If you need formal significance tests, weighting to match a population, or results that will be published as research, work with someone trained in survey statistics or use an assistant that can run code on the raw data and show its method. The summary from this prompt is still a useful first draft for those cases.

How to customize it

  • [AUDIENCE] sets length and tone. Leaders want the summary and next steps; a project team may want all segments.
  • [SURVEY PURPOSE] keeps the findings focused on the decision rather than on every question.
  • [INVITATIONS AND RESPONSES] allow the model to state the response rate, the most important caveat.
  • [RESULTS] should be counts if possible; percentages without a base hide small samples.
  • [MINIMUM N] is your threshold for segment comparisons. Thirty is a common rule of thumb, not a statistical guarantee.

Why it works

Survey summaries go wrong when percentages are reported without bases, when a difference between two tiny subgroups becomes a headline, or when open answers are ignored. Every finding here must carry its number and n, and small segments are explicitly labelled.

Chart suggestions with a takeaway title follow a simple rule of data communication: the title says what the reader should notice. Restricting the model to the numbers you supplied, and asking it to show any calculation, keeps the summary checkable.

Tips and variations