---
name: post-event-survey-analysis
description: Analyzes post-event and post-webinar survey exports. Calculates NPS and rating summaries by segment (attendee type, customer vs prospect, track), codes open-ended comments into themes with counts and example quotes, ties detractor themes to specific fixes, and ranks sessions and speakers. Use for attendee feedback analysis, conference survey results, session ratings, speaker rankings, event NPS reports or the feedback section of a post-event report.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: measurement
  source: https://eventmarketingsoftware.com/skills/post-event-survey-analysis
---

# Post-Event Survey Analysis

Turn a raw survey export into findings a team can act on: NPS and ratings by segment, open-ended comments coded into themes with counts and quotes, a session and speaker ranking, and the five fixes that matter most for next time.

## Intake

If the user has an `event-context.md` file, read it first (event names, segments, house tone).

Then ask for whatever is missing in ONE message:

1. The survey export (CSV, XLSX or pasted table) and the event name and format (conference, user conference, field event, webinar, trade show booth).
2. Which columns hold the 0 to 10 recommend score, ratings, session or speaker, and segment (attendee type, customer vs prospect, track, region). Offer your best guess from the headers so they can just confirm.
3. Who to leave out (employees, test rows, speakers rating their own session) and whether sponsors and exhibitors answered a separate survey.
4. Who the output is for: the event team (full detail) or executives (one page, five quotes).
5. Optional: total attendee count (for response rate), last year's NPS or ratings, the session list with speakers.

## Connectors (all optional)

- If a Google Sheets connector is available, read the responses there and offer to write the summary tables to a new tab (preview first).
- If a Slack connector is available, offer a short summary post as a draft; post only after the user approves the exact text.
- Otherwise, work from the uploaded file or pasted rows and return Markdown tables plus a CSV of coded comments.

## Method

```
- [ ] 1. Clean: dedupe, exclude test and employee rows, parse scores
- [ ] 2. NPS and rating summaries, overall and by segment
- [ ] 3. Code open-ended comments into themes
- [ ] 4. Link themes to promoters, passives and detractors
- [ ] 5. Rank sessions and speakers
- [ ] 6. Top 5 fixes and what to keep
- [ ] 7. Validate
```

1. **Clean.** Remove duplicate submissions (same email or respondent ID; keep the first and list the rest). Drop test rows and employees unless asked. Parse scores like "10 - definitely" or "8.0" as numbers; treat "N/A", blanks and out-of-range values as missing and count them. Report sponsors and exhibitors as their own segment or leave them out of attendee NPS, and say which.
2. **NPS.** Promoters score 9 to 10, passives 7 to 8, detractors 0 to 6. NPS = % promoters minus % detractors, a whole number from -100 to 100. Show n for every segment. Mark any segment under 5 responses "directional". Response rate = usable responses / attendees, if attendee count is known.
3. **Ratings.** For 1 to 5 scales, report average and top-2-box % (share of 4s and 5s). Don't average across different scales.
4. **Code comments.** Read every comment. Start from the codebook in [references/theme-codebook.md](references/theme-codebook.md), add event-specific themes when 3 or more comments share an idea, and merge themes with fewer than 3 mentions into "Other". A comment can carry more than one theme. Tag each coded mention positive, negative or mixed. Count mentions per theme by NPS group.
5. **Quotes.** Pick short, representative quotes (under 25 words) that match the theme's majority view. Trim names, emails, company names and anything identifying. Never invent or merge quotes; light trimming with "..." is fine.
6. **Sessions and speakers.** Rank by average session rating, then top-2-box %, then n. Show n and flag sessions under 5 ratings. Use comments to explain the low ones ("rated as a product pitch"). Recommend invite back, invite back with changes, or don't re-invite, with the reason.
7. **Fixes.** Rank negative themes by detractor mentions first, then total mentions. For each, name a concrete change, an owner role and when it has to happen (for example "book a room for 80 before the venue contract is signed").

Optional script: `scripts/survey_summary.py` computes rows in and out, NPS by segment and the session ranking deterministically:

```
python3 scripts/survey_summary.py responses.csv --exclude "Attendee Type=Employee"
```

It auto-detects columns or takes `--nps-col`, `--segment-col`, `--session-col`, `--rating-col`, `--dedupe-col`. If code execution isn't available, do the same counts in chat and show the arithmetic for the overall NPS.

## Output template

```
# [Event] Survey Results

## Headline
3 to 5 bullets: NPS (n), biggest strength, biggest problem, top session, response rate.

## Who answered
## NPS and ratings by segment
## What people loved (themes)
## What to fix (themes)
## Sessions and speakers
## Top 5 fixes for next time
## What to keep
## Method and caveats
```

Table columns:

- **NPS by segment:** Segment | Responses | Promoters | Passives | Detractors | NPS | Note
- **Themes:** Theme | Sentiment | Mentions | From detractors | From promoters | Example quote
- **Sessions:** Rank | Session | Speaker | Responses | Avg rating | Top-2-box % | What comments say | Recommendation
- **Fixes:** # | Problem (theme) | Evidence (mentions, detractor share) | Fix | Owner | By when
- **Coded comments CSV:** Response ID | Segment | NPS group | Theme(s) | Sentiment | Comment

For an executive version, keep only Headline, NPS by segment, Top 5 fixes and five quotes. A worked example is in [references/examples.md](references/examples.md).

## Rules that keep the analysis honest

- Report n next to every percentage and score.
- Don't compare NPS across events with different survey wording or timing without saying so.
- A theme count is mentions, not people, unless you counted people; say which.
- Don't attribute a complaint to a named speaker in an exec summary without the event team seeing it first.
- No external benchmarks for NPS: they vary too much by event type. Compare with the user's own past events.

## Validation checklist

- [ ] Rows in = rows used + rows dropped, with each drop listed
- [ ] NPS group counts add up to scored responses
- [ ] Every theme has a count and at least one real quote
- [ ] Every comment is coded (or marked "no comment")
- [ ] Segments and sessions under 5 responses are flagged
- [ ] No names, emails or identifying details in quotes

## Approval gates

Never post to Slack, email a summary or write to a shared sheet without showing the exact content first and getting a yes. Default to a draft. Don't send survey follow-ups to respondents from this skill.

## Privacy

Survey exports often hold names, emails and free-text personal details. Keep the analysis in the user's own tools. Strip identifying details from quotes. If respondents were promised anonymity, don't link comments to emails in any output. Respondents in the EU or UK may only be contacted about their answers if they agreed to that.

## Related skills

event-debrief (feeds these findings into keep, change, cut), event-roi-report, event-strategy-brief.
